service-design-coordinator
Use when starting or continuing service design analysis for a project — checks what artifacts exist, identifies gaps, recommends which analytical skill to run next
What this skill does
# Service Design Coordinator **Core principle:** A complete analysis for a service slice requires all 7 artifact types. The coordinator ensures coverage, not perfection. **When invoked, execute this workflow. Do not skip phases.** --- ## Phase 1: Inventory Scan `docs/service-design/` for existing slices. For the target slice, list every artifact with its `last_updated` date. If no slice exists, ask the user to name one before proceeding. **Say:** "Slice `<name>` has N/7 artifacts: [list present], missing: [list absent]." Flag any artifact older than 30 days as stale — treat stale the same as missing for recommendation purposes. --- ## Phase 2: Recommend Next Artifact Use this default order. Earlier artifacts feed later ones — but any order works if the user has context to supply. | # | Skill | Rationale | Prerequisites | |---|-------|-----------|---------------| | 1 | `service-design:actor-profile` | Shared foundation; every artifact references actors | None | | 2 | `service-design:stakeholder-map` | How all actors connect; staff experience drives customer experience | Actor profiles | | 3 | `service-design:service-blueprint` | Operational backbone; other artifacts reference it | Stakeholder map enriches it | | 4 | `service-design:empathy-analysis` | User's inner world (emotions, information needs) | Actor profiles (blueprint enriches it) | | 5 | `service-design:journey-map` | User's experience sequenced over time and channels | Actor profiles (blueprint + empathy enrich it) | | 6 | `service-design:gap-analysis` | Where understanding diverges from reality | Empathy + journey recommended | | 7 | `service-design:service-diagnosis` | Bottlenecks + improvement design | Blueprint + stakeholder map recommended | | 8 | `service-design:service-design-critic` | Stress-test the whole suite | 3+ artifacts required | Pick the first missing artifact in this order. If all 7 exist, recommend the critic. **Say:** "Recommend running `<skill>` next because [rationale]. Invoke now?" --- ## Phase 3: Invoke If the user confirms (or didn't object), invoke the recommended skill immediately. Pass the slice name as context. After the skill completes, return to Phase 1 — re-inventory and recommend again until the suite is complete or the user stops. --- **Remember:** This is a command. Execute each phase in order. Inventory before recommending, recommend before invoking.
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.