atomic-design-planning
Use this skill when discussing UI components, design systems, frontend implementation, or component architecture. Guides thinking about Atomic Design methodology - atoms, molecules, organisms - and promotes component reuse over creation. Triggers on UI/frontend discussions, "what components do we need?", "should I create a new component?", or design system questions.
What this skill does
# Atomic Design Planning Skill This skill guides UI component architecture using Atomic Design methodology, emphasizing reuse of existing components and proper categorization of new ones. ## When to Use Apply this skill when: - Planning UI features or components - Deciding whether to create new components - Discussing frontend architecture - Users ask "what components do we need?" - Reviewing UI implementation plans - Discussing design system structure ## Atomic Design Hierarchy ``` ┌─────────────────────────────────────────────────────────┐ │ PAGES - Complete screens with real content │ ├─────────────────────────────────────────────────────────┤ │ TEMPLATES - Page-level layout structures │ ├─────────────────────────────────────────────────────────┤ │ ORGANISMS - Complex UI sections (Header, LoginForm)│ ├─────────────────────────────────────────────────────────┤ │ MOLECULES - Simple groups (SearchInput, NavItem) │ ├─────────────────────────────────────────────────────────┤ │ ATOMS - Basic blocks (Button, Input, Icon) │ └─────────────────────────────────────────────────────────┘ ``` ## Component Categories ### Atoms Smallest, indivisible UI elements: Buttons, Inputs, Labels, Icons, Typography. - No dependencies on other components - Highly reusable, controlled by props only ### Molecules Simple combinations of 2-4 atoms: SearchInput, FormField, NavItem. - Single responsibility, reusable in multiple organisms ### Organisms Complex, distinct UI sections: Header, ProductCard, LoginForm, DataTable. - May connect to data/state, often feature-specific ### Templates Page-level structural layouts: DashboardLayout, AuthLayout. - Define content placement, handle responsive behavior ### Pages Specific instances with real content: HomePage, ProductDetailPage. - Templates filled with data, route-specific ## The Reuse-First Principle Before creating ANY component: 1. **Search existing atoms** - Is there a Button/Input that works? 2. **Search existing molecules** - Can a FormField be adapted? 3. **Search existing organisms** - Does a similar Card exist? 4. **Only then create new** - Is this truly unique? ## Decision Table | Question | If Yes | If No | |----------|--------|-------| | Does something similar exist? | Reuse/extend it | Continue evaluation | | Will this be used in 2+ places? | Consider extracting | Inline it instead | | Is it truly indivisible? | Make it an atom | Make it a molecule+ | | Does it combine 2-4 atoms? | Make it a molecule | Make it an organism | | Is it a complete UI section? | Make it an organism | Reconsider structure | ## Anti-Patterns to Avoid - **Creating when reusing works** - Configure existing Button with props instead - **Feature-specific atoms** - "UserProfileButton" should be an organism - **Skipping levels** - Pages shouldn't directly use atoms - **Wrong abstraction level** - Atoms shouldn't have business logic ## Integration with Linear Workflow When planning UI features, create issues for: 1. **Atom issues** - New basic components needed 2. **Molecule issues** - New component combinations 3. **Organism issues** - New feature-level components Investigation phase should identify existing components to reuse. Remember: **Reuse existing components. Only create what's truly missing.**
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.