Loading...
Loading...
Found 31 Skills
Comprehensive MDX component patterns (Note, Pitfall, DeepDive, Recipes, etc.) for all documentation types. Authoritative source for component usage, examples, and heading conventions.
Core technical documentation writing principles for voice, tone, structure, and LLM-friendly patterns. Use when writing or reviewing any documentation.
Technical writing skills specialized in drafting, structuring, and visualizing technical notes. Understand the essence from source code and official documents, and create explanatory articles in an engineer-friendly format.
Help the user shape technical blog posts, website articles, devlogs, essays, or long-form drafts without writing the full post for them. Use this whenever the user shares rough notes, a brain dump, unordered ideas, bullet points, or half-written sections, or asks for help turning notes into an outline, finding the angle, sharpening the hook or thesis, improving structure, clarifying the argument, tightening flow, stress-testing the payoff, or making a technical piece more engaging while preserving their voice. Use it even if the user does not explicitly ask for a writing guide, as long as they need help organizing and developing a post rather than having it ghostwritten. Guide with organization, critique, focused questions, and tiny example lines only; do not write the final article.
Narrative-first slide deck creation. Guides users through structured narrative design (ABCDEFG model), then delegates visual generation to baoyu-slide-deck. Triggers on "create slides", "make a presentation", "generate deck", "slide deck", "PPT", or when user needs to turn content into visual slides.
A long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
Generate lightweight section/subsection transitions (NO NEW FACTS) to prevent “island” subsections; outputs a transition map that merging/writing can weave in. **Trigger**: transition weaver, weave transitions, coherence, 过渡句, 承接句, 章节连贯性. **Use when**: `outline/subsection_briefs.jsonl` exists and you want coherent flow before/after drafting (typically Stage C5). **Skip if**: `outline/transitions.md` exists and is refined (no placeholders). **Network**: none. **Guardrail**: do not add new factual claims or citations; transitions may only refer to titles/RQs/bridge terms already present in briefs.