pf-design-mode
Create and edit Figma design files using PatternFly-approved component libraries. Use when building, updating, or restructuring Figma frames and components. Requires Figma MCP.
What this skill does
# PatternFly Design Mode Use this skill for write-focused design tasks in Figma. ## Required prerequisites This skill requires two skills from the **official Figma plugin** — see the [plugin README](../../README.md) for install instructions. - `figma-use` — mandatory before every `use_figma` call; never skip it - `figma-generate-design` — required when the task involves creating a full page or screen from code Rules: - Never call `use_figma` directly without first loading `figma-use`. - If the task includes broad screen creation from code, pair `figma-use` with `figma-generate-design`. ## Approved component sources (strict) Use components and patterns only from the files listed in `references/approved-sources.md`. Rules: - Do not use components from any other library or file. - Only use semantic design tokens and spacers from the approved files. - Do not create ad-hoc replacement components when an approved component/pattern exists. - If a needed component/pattern is missing in these sources, stop and ask the user before proceeding. ## Pattern-first selection (strict) Whenever possible, prefer larger patterns denoted with the `🧰` emoji. - Select `🧰` patterns before assembling equivalent UI from smaller components. - Only compose from smaller components when no suitable `🧰` pattern exists for the requirement. ## Page creation behavior (strict) If the user asks to "make a new page": - Do not replace, clear, or mutate existing page content as the starting point. - Create a new top-level frame for subsequent changes. - Apply all new work to that new frame unless the user explicitly asks to edit an existing frame. ## When to use Use this skill when a request includes one or more of the following: - "Create this in Figma", "edit this Figma file", "update this screen" - "Make a new page" or equivalent phrasing for a new screen - Layout restructuring (auto-layout, spacing, constraints, frame hierarchy) - Component/variant updates, token/variable binding, or style cleanup - Figma URL-driven implementation work ## Workflow 1. Confirm target - Identify `fileKey` and `nodeId` from the Figma URL when provided. - Clarify expected output (new frame, edits to an existing frame, component updates). 2. Load prerequisite skill - Invoke the `figma-use` skill instructions first. 3. Resolve approved assets with pattern-first priority - Search and import from the approved PatternFly files only (see `references/approved-sources.md`). - Prefer matching `🧰` patterns first, then fall back to smaller components if needed. - Verify each chosen component/pattern comes from an approved source. 4. Handle page intent - If request is "make a new page", create a new top-level frame first. - Otherwise, edit only the user-specified existing frame/scope. 5. Make incremental edits - Prefer editing existing nodes/components over rebuilding from scratch (except new-page requests). - Use approved design-system components and variables instead of hardcoded values. - Apply changes in small batches and verify after each batch. 6. Validate outcome - Check hierarchy, alignment, spacing, constraints, and variant states. - Ensure all inserted components/patterns come from approved sources only. - Confirm `🧰` patterns were used whenever a suitable option exists. ## Guardrails - Reuse approved library assets first; avoid duplicate ad-hoc components. - Bind variables/tokens where possible (color, type, spacing, radius). - Keep names semantic and stable for handoff (frames, components, variants). - If requirements are ambiguous, ask a focused clarification question before making large edits.
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.