angular-css-bem-best-practices
Angular + BEM CSS methodology guide for creating reusable components and shareable front-end code. Enforces component-scoped BEM blocks, max 2-level nesting, proper component decomposition, semantic element naming, correct modifier patterns, and flat selectors. Use when writing, reviewing, or refactoring Angular component styles. Triggers on tasks involving CSS, SCSS, SASS, component styling, BEM naming, or CSS architecture.
What this skill does
# Angular + BEM CSS Best Practices A methodology guide for combining Angular's component architecture with BEM (Block Element Modifier) CSS naming convention to create reusable components and enable code sharing in front-end development. Contains 6 rules with bad/good examples in CSS, SCSS, and SASS. ## When to Apply Reference these guidelines when: - Writing CSS/SCSS/SASS for Angular components - Naming CSS classes in Angular templates - Reviewing component styles for consistency - Deciding whether to split a component based on styling complexity - Setting up CSS architecture for a new Angular project - Refactoring existing styles to follow BEM methodology ## Core Principles - **1 Component = 1 BEM Block** — The block name matches the component selector - **Max 2 Levels** — Only `Block` and `Block__Element`, never `Block__Element__SubElement` - **Split When Deep** — If you need a third level, extract a child component - **Flat Selectors** — No descendant, child, or tag-qualified selectors - **Semantic Names** — Element names describe _what_, not _how_ or _where_ - **Modifiers for Variants** — Use `--modifier` for states and variants, always with the base class ## Rule Categories by Priority | Priority | Rule | Impact | File | |----------|------|--------|------| | 1 | Block = Component Selector | CRITICAL | `bem-block-selector` | | 2 | Max 2 Levels of Nesting | CRITICAL | `bem-max-nesting` | | 3 | Split Child Components | CRITICAL | `bem-split-components` | | 4 | Element Naming Conventions | HIGH | `bem-element-naming` | | 5 | Modifier Patterns | HIGH | `bem-modifier-patterns` | | 6 | No Cascading Selectors | HIGH | `bem-no-cascading` | ## Quick Reference ### 1. Block = Component Selector (CRITICAL) - `bem-block-selector` - BEM block name must match the Angular component selector (minus prefix) ### 2. Maximum 2 Levels (CRITICAL) - `bem-max-nesting` - Never nest beyond `.block__element` — no `.block__element__subelement` ### 3. Split Child Components (CRITICAL) - `bem-split-components` - Extract child components when BEM depth would exceed 2 levels ### 4. Element Naming (HIGH) - `bem-element-naming` - Use semantic, descriptive kebab-case names for BEM elements ### 5. Modifier Patterns (HIGH) - `bem-modifier-patterns` - Use `--modifier` correctly for states and variants with Angular class bindings ### 6. No Cascading (HIGH) - `bem-no-cascading` - Avoid descendant, child, and tag-qualified selectors — keep BEM flat ## BEM Cheat Sheet ``` .block → Component root (matches selector) .block__element → Child part of the component .block--modifier → Variant of the entire block .block__element--modifier → Variant of a single element ✅ .user-card ✅ .user-card__avatar ✅ .user-card--featured ✅ .user-card__name--highlighted ❌ .user-card__header__title (3 levels) ❌ .user-card .user-card__avatar (descendant selector) ❌ div.user-card (tag-qualified) ``` ## How to Use Read individual rule files for detailed explanations and code examples: ``` rules/bem-block-selector.md rules/bem-max-nesting.md rules/bem-split-components.md rules/bem-element-naming.md rules/bem-modifier-patterns.md rules/bem-no-cascading.md ``` Each rule file contains: - Brief explanation of why it matters - Incorrect code examples (CSS, SCSS, SASS) - Correct code examples (CSS, SCSS, SASS) - Angular component integration patterns - Summary table and references ## Full Compiled Document For the complete guide with all rules expanded: `AGENTS.md`
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.