design
This skill should be used when the user asks to "review code design", "check API design", "evaluate abstractions", "review naming", "check SOLID compliance", "design an API", "choose between REST and GraphQL", or discusses code quality, interface design, API contracts, or developer experience.
What this skill does
# Design
Code, component, and API design evaluation.
## Abstraction Quality
### Naming
- Does `processData()` actually process data?
- Do names reveal intent?
- Consistent vocabulary (don't mix "user" and "account" for same concept)?
**Red flags:**
- `Manager`, `Handler`, `Processor`, `Utils` — often god classes
- Single-letter names outside tight loops
- Abbreviations that aren't universally known
### Single Responsibility
- One reason to change?
- Can you describe the class without using "and"?
**Test:** "The {ClassName} is responsible for..." — if you need "and", split it.
### Leaky Abstractions
- Does implementation leak through interface?
- Are internal data structures exposed?
**Example leak:**
```typescript
// Leaky — exposes internal Map structure
class Cache {
getAll(): Map<string, Value> { return this.internal; }
}
// Clean — hides implementation
class Cache {
entries(): Array<[string, Value]> { return [...this.internal]; }
}
```
### Tell, Don't Ask
- Behavior on objects vs external orchestration?
- Objects should do things, not just hold data
**Ask (bad):**
```typescript
if (order.status === 'pending' && order.items.length > 0) {
order.status = 'confirmed';
}
```
**Tell (good):**
```typescript
order.confirm(); // Object owns its state transitions
```
## SOLID Compliance
| Principle | Question | Violation Signal |
|-----------|----------|------------------|
| **S**ingle Responsibility | One reason to change? | Class has multiple "and"s |
| **O**pen/Closed | Extend without modifying? | Switch statements on types |
| **L**iskov Substitution | Subtypes substitutable? | Instanceof checks |
| **I**nterface Segregation | Clients use what they depend on? | Empty method implementations |
| **D**ependency Inversion | Depend on abstractions? | `new ConcreteClass()` in domain |
## API Design
### Protocol Selection
| Protocol | Best For | Avoid When |
|----------|----------|------------|
| **REST** | CRUD, public APIs, caching | Real-time, complex queries |
| **GraphQL** | Flexible queries, multi-client | Simple CRUD, N+1 risk |
| **gRPC** | Internal services, performance | Browser clients |
| **WebSocket/SSE** | Real-time updates | Request-response |
### Universal Principles
1. **Contract-First**: Define API before implementation
2. **Consistency**: Same patterns everywhere
3. **Evolvability**: Version from day one
4. **DX**: Clear errors, good docs
## DX (Developer Experience)
- **Onboarding**: Can a new dev understand in 15 minutes?
- **Error Messages**: Actionable or cryptic?
- **Documentation**: Matches reality?
- **Conventions**: Consistent with ecosystem?
## Guild Members for Design
Primary: **Karman** (naming/abstractions), **Ace** (DX), **Burner** (coupling)
Secondary: **Dijkstra** (correctness), **Vector** (auth for APIs)
## Output Format
```
## Design Review: {Component}
### Abstraction Quality
- {Finding 1}
- {Finding 2}
### SOLID Violations
- {Principle}: {violation}
### API Assessment (if applicable)
- {Finding}
### DX Friction Points
- {Point 1}
### Recommendations
1. {Action}
2. {Action}
```
## Additional Resources
- **`references/solid-gotchas.md`** — Common SOLID violations with fixes
- **`references/api-rest.md`** — REST production gotchas
- **`references/api-graphql.md`** — GraphQL N+1, complexity, caching traps
- **`references/api-grpc.md`** — gRPC streaming, versioning gotchas
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.