skills-garden

Transform a raw product idea, brief, or rough technical sketch into a sharp software design doc written by a senior staff engineer who has shipped real systems. Use this skill whenever the user mentions a "software design doc", "engineering design doc", "eng spec", "technical design doc", "TDD", "architecture doc", "system design", "implementation plan", or says anything like "how do we build this", "tech-spec this", "what's the architecture", "scope the engineering", "the eng side of this", "design the backend". Also triggers when the user has bullet-point thoughts about data models, APIs, infra, or trade-offs and wants them expanded. Output is a single self-contained Markdown design doc covering architecture (with a mermaid diagram), data model, API surface, key trade-offs with rejected alternatives, risks, a testing strategy (consumed by the `test-driven-dev` skill), rollout plan, and an honest scope of what's NOT being built. Push toward boring tech, smallest viable architecture, and explicit trade-offs —

Transform a rough product idea, hackathon pitch, or napkin sketch into a sharp product design doc (PRD) written by a senior PM who actually ships. Use this skill whenever the user mentions a "product idea", "PRD", "product spec", "product design doc", "product brief", "feature pitch", a "hackathon project", or says anything like "I want to build X" / "turn this into a real product doc" / "let's PM this" / "what's the spec for this" / "make this shippable" — even if they don't say "PRD" explicitly. Also triggers when the user has a bullet-point pitch (contract, scope, magical moment, signature detail) and wants it expanded. The output is a single self-contained Markdown PRD with sharp scope discipline, opinionated trade-offs, and a clear handoff to UX and Eng. Push toward shipping the smallest thing that proves the magic — not the org chart's wishlist. This skill operates independently — it reads only the raw brief, not other design docs.

Transform a raw product idea, brief, or rough pitch into a sharp UX design doc written by a senior product designer who actually ships. Use this skill whenever the user mentions a "UX spec", "UX design doc", "design doc", "interaction design", "wireframes", "user flow", "screen-by-screen design", or says anything like "design this", "what does it look like", "spec the UI", "the UX side of this", "make this designable". Also triggers when the user has bullet-point thoughts about screens, flows, components, or interactions and wants them expanded. Output is a single self-contained Markdown UX design doc covering the user journey, screen-by-screen specs, interaction details, edge states, and the one signature interaction that defines the product. Push toward fewer screens, fewer states, one defining interaction — not a Figma library of every possible component. This skill operates independently — it reads only the raw brief, not other design docs.