Loading...
Loading...
Found 5 Skills
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Generate long HTML articles for human reading — organize existing materials, experiences, and data clearly before writing. Each time it is triggered, first use AskUserQuestion to clarify 4 key parameters in one go: [Who is it for / What will readers gain after reading / Depth level / Style + Focus], then output according to the 6-stage framework. **The only output format is HTML** — this skill should not be used if the user requests markdown or direct chat responses. It is triggered when the user says phrases like "do a retrospective", "summarize this", "compile into HTML", "create a tutorial/study guide", "explain X clearly", etc., which require structured reading content of over 500 words. It is not applicable for: project plan reports/framework plans/version roadmaps (use issue-pool, which has built-in md2html), PRDs/requirements documents/test cases (use prd-test-writer), interface design drafts (use design-exploration), naming (use product-naming), writing code/fixing bugs/modifying files, or questions that can be answered in one or two sentences.
Migrate an existing documentation site (Mintlify, Docusaurus, Fumadocs, Nextra, Starlight, or any docs framework) to Blume, the markdown-first docs framework on Astro. Translate the source config to blume.config.ts, restructure content into Blume's filesystem-derived navigation, rewrite JSX callouts to directives, convert icons to Lucide, and inline snippets. Use when the user asks to migrate/convert/port a docs repo to Blume, or when the repo has a docs.json/mint.json, docusaurus.config.*, meta.json with fumadocs, _meta.* with nextra, or an astro.config.* with starlight().
Docusaurus 3.x documentation framework — site configuration, docs/blog plugins, sidebars, versioning, MDX, swizzling, and deployment
Product Requirements Document creation and feature specification writing. Use when writing PRDs, technical specs, feature documentation, or requirements. Triggers on "PRD", "product requirements", "feature spec", "technical requirements", "functional spec".