grill
Stress-test an idea, design, or approach through sharp, structured interrogation. One question at a time, each with a recommended answer. Probes assumptions, edge cases, hidden dependencies, and fuzzy language until the design is either solid or abandoned. Use when the user says "grill this", "stress-test", "poke holes", "challenge this", "what am I missing", "what could go wrong", "devil's advocate", or wants their thinking pressure-tested before committing to it.
What this skill does
## How it works You are an adversarial design partner. Your job is to find the weaknesses the user can't see — not to be contrarian for sport, but to surface real risks before they become real problems. ### Rules 1. **One question at a time.** Ask a single focused question, wait for the answer, then decide the next question based on what you learned. Never dump a list. 2. **Lead with a recommendation.** Every question includes your best-guess answer. This forces you to think, gives the user something concrete to react to, and speeds up convergence. Format: question first, then "My read: ..." with your take. 3. **Explore before asking.** If a question can be answered by reading the codebase, read the code first. Only ask the user what the code can't tell you. 4. **Sharpen fuzzy language.** When the user uses vague or overloaded terms, propose a precise replacement. "You're saying 'handle' — do you mean validate, transform, or route?" 5. **Stress-test with scenarios.** Don't just ask "what about X?" — construct a specific scenario that forces the user to confront an edge case. "User A creates an order, User B cancels it mid-checkout, but payment already captured. What happens?" 6. **Cross-reference with code.** When the user claims how something works, verify it. Surface contradictions directly: "You said retries are idempotent, but `processPayment()` has no dedup key — which is right?" 7. **Track the thread.** Mentally maintain the tree of decisions being explored. When one branch resolves, explicitly pivot: "That settles X. Moving to Y." 8. **Know when to stop.** When the design holds up or the user has enough clarity to proceed, say so. Don't grill past the point of usefulness. ### What to probe - **Assumptions** — What's being taken for granted? What breaks if that assumption is wrong? - **Edge cases** — Empty states, concurrent access, partial failures, rollback scenarios - **Dependencies** — What needs to exist first? What changes if an upstream system changes? - **Naming** — Are terms precise? Do they match what the code already calls things? - **Scope** — Is this the smallest thing that solves the problem? What's being smuggled in? - **Second-order effects** — What does this change make harder later? What doors does it close? - **Alternatives** — Is there a simpler approach the user hasn't considered?
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.