Loading...
Loading...
Found 65 Skills
Convention DESIGN.md pour design systems AI-friendly. Use when setting up a new project UI, documenting design tokens, or generating UI consistent with a design system.
Use when you need to generate an onboarding guide for new team members joining a project
Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks.
Generate a PRD from the client brief and write it as a local markdown file in issues/. Use when the user wants to turn a client request into a structured PRD.
Creates and amends product specification markdown — PRD, FRD, TRD, user story, and UI specs (flow, screen structure, view states) — with consistent layout and frontmatter. Use only when the user names this skill (`/building-product-specifications`, `$building-product-specifications`, or "building-product-specifications"), or references a spec file under a marked docs root (`@docs/prd.md`, `@docs/features/checkout/frd.md`) — no code implementation.
Explains bugs, code flows, protocols, and concepts in a Markdown document with SVG diagrams generated from small text specs, adapted to the reader's level. Use when the user asks for an explanation with diagrams or drawings, says "explain like I'm 5" or "me explica com desenhos", wants an illustrated explanation after not understanding text alone, or wants to change how Doodle explanations look or read (theme, colors, audience, depth).
When the user wants to create or update their startup context document. Also use when the user mentions "set up context", "tell you about my startup", or any other skill needs context that doesn't exist yet.
Extract and convert a website or docs site into clean markdown
Extract any website's design system into an agent-ready DESIGN.md using Firecrawl scrape evidence. Use when the user wants colors, fonts, spacing, components, layout patterns, or brand/UI guidance from a website so AI agents can create new websites, clone a look, or build pages inspired by that design.
Add a new book to the mmontes11/knowledge-base `books/` section: create the book-shaped entry (entry README, one numbered file per chapter, the source PDF), summarize each chapter faithfully and attribute it, add mermaid diagrams where they clarify a mechanism, and register the book in the root README's Tracked books table. Use whenever the user wants to add, create, or import a book into the knowledge base — "add this book to the knowledge base", "summarize <book> for the KB", "create a books/ entry for <title>", "work through chapter N of <book>" — even if they don't say "knowledge base" explicitly.
Create a new specification file for the solution, optimized for Generative AI consumption.
Research issues against highly credible primary sources and save findings as Markdown files in the repository. Suitable for users who want to research topics, collect documentation or API facts, or delegate reading tasks to background agents.