apple-hig
This skill should be used when designing UI for Apple platforms (iOS, iPadOS, macOS, tvOS, visionOS, watchOS). Covers choosing the right component (tab bar vs sidebar, sheet vs popover, list vs collection), applying HIG patterns (onboarding, search, settings, data entry, modality), and making visual design decisions (typography, color, layout, dark mode, motion). Activates on questions like "which navigation pattern should I use," "how should I design this screen for iPad," "what does Apple recommend for onboarding," or "check this design against HIG."
What this skill does
# Apple Human Interface Guidelines Reference This skill contains Apple's official Human Interface Guidelines. Use it to make informed, platform-correct design decisions. ## How to Use This Skill Follow the progressive discovery pipeline. Each step narrows the decision space for the next: ```text Features (user intents) -> Patterns -> Components -> Foundations ``` ### Step 1: Match Features to Patterns Read `indexes/patterns-by-intent.md` to find which HIG patterns match the user's feature intents. Then read the full pattern reference: ```text references/patterns/design-[pattern-name].md ``` Patterns tell you the approach - how Apple recommends handling things like entering data, searching, onboarding, managing notifications, and similar intents. ### Step 2: Select Components by Platform Read `indexes/components-by-platform.md` for the full component catalog with platform support flags. Filter by the user's target platforms. Then read the full component reference: ```text references/components/design-[component-name].md ``` Each component doc contains: - Best practices - bold-prefixed do/don't rules from Apple - Platform considerations - what differs on iOS vs iPadOS vs macOS - When to use / when not to use - concrete component selection guidance - Related - links to adjacent components and developer APIs ### Step 3: Apply Foundations Read `indexes/foundations-checklist.md` for the ordered list of 7 foundation decisions. Then read each foundation reference: ```text references/foundations/design-[foundation-name].md ``` Work through: Typography -> Writing -> Branding -> Color (+ Dark Mode) -> Materials -> Layout -> Motion. ## Key Rules - Always read the reference doc before recommending a component or pattern. Do not rely on general knowledge. - Always check platform support. Never recommend a component that is unsupported on the user's target platforms. - Be specific. Do not say "use appropriate typography" - cite guidance and name specific text styles. - Quote Apple's rules. When a component has a critical do/don't, cite it directly. ## Reference Structure ```text references/ ├── patterns/ # 25 files - design approach for user intents ├── components/ # 63 files - UI component guidance with platform rules └── foundations/ # 8 files - visual design decisions ```
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.