Total 50,473 skills, Documentation & Writing has 1451 skills
Showing 12 of 1451 skills
Creates 4 core project docs (requirements.md, architecture.md, tech_stack.md, patterns_catalog.md). L3 Worker invoked by ln-110-project-docs-coordinator. ALWAYS created.
Write/refactor the NSFC main text section (II) Research Content, and synchronously organize the Characteristics and Innovations and Three-Year Annual Research Plan, outputting three extraTex files that can be directly applied to LaTeX templates. Suitable for scenarios where users need to write/revise research content, research objectives, key scientific issues, technical routes, innovation points, three-year plans/milestones, etc.
This skill should be used when the user asks to "document discussion", "save meeting notes", "record conversation", "capture meeting", or mentions needing to document team discussions with participants, decisions, and action items.
Resume structure, achievement bullet formulas, ATS optimization, and job-targeted tailoring for software engineers. Use when reviewing resumes, crafting achievement bullets, extracting keywords from job descriptions, or tailoring content for specific roles.
Use when writing any React documentation. Provides voice, tone, and style rules for all doc types.
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do
Use this skill whenever a "diagram" is mentioned. Maintain and synchronize Unified Impact Diagrams following Diagram Driven Development (DDD) methodology. Create, update, and manage diagrams that connect user value to technical implementation.
Structure stories around essential emotional moments using Rodriguez's approach integrated with elemental genres. Use when plotting feels mechanical, when emotional beats need defining, or when building stories from vivid scenes rather than plot outlines.
Create or update system design documents. Supports initial design and incremental design modes. Use when users need technical architecture, API design, data models, design changes, or impact analysis. Triggers on keywords like "system design", "architecture", "technical design", "API design", "design change", "impact analysis", "design change", "impact analysis".
Generates Request for Comments documents for technical proposals including problem statement, solution design, alternatives, risks, and rollout plans. Use for "RFC", "technical proposals", "design docs", or "architecture proposals".
Create and maintain TYPO3 extension documentation following official docs.typo3.org standards. RST syntax, TYPO3 directives, rendering, and deployment. Use when working with documentation, rst, docs, readme, typo3 documentation.
Use when completing development phases or branches to identify and update CLAUDE.md or AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updates