Loading...
Loading...
Found 4 Skills
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.
Generate self-contained, beautiful HTML documents that replace walls of markdown. Use this skill whenever the user asks for a report, comparison, explainer, slide deck, diagram, post-mortem, status update, code walkthrough, design system showcase, prototype, or interactive editor — or mentions creating HTML outputs, dashboards, visual documentation, or "instead of markdown". Covers 10 battle-tested patterns: comparison, walkthrough, review, design-system, prototyping, diagram, deck, explainer, report, and editor.
Use when the user wants a plan, spec, write-up, findings, summary, report, comparison, or UI mocks as readable HTML, or mentions HTML with no additional context. Do not use for HTML that ships in a product.
Render an explanation, analysis, plan, findings doc, or draft as a single self-contained HTML file (generous whitespace, sparse prose, diagram-first, one accent color) the user can open, screenshot, share, or copy from. Use when the user wants any standalone HTML document regardless of domain, e.g. says "explain this as html", "turn this into html", "visualize with html", or "make an html doc/report so I can review/discuss/copy". Content-agnostic; carries a fixed visual aesthetic.