Total 50,320 skills, Documentation & Writing has 1450 skills
Showing 12 of 1450 skills
Polish paper for Q1 journal submission (ISI/Scopus). Use after paper draft is complete — handles notation sync with thesis, De-AI/De-translation protocol, and Q1 results table standards.
Write technical reports — experiment reports, system design documents, code documentation, and internal research memos. Use when documenting technical work that doesn't fit paper format.
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review
Keep a Changelog format. Covers structure, change types, versioning. Keywords: CHANGELOG.md, semver.
Maintain comprehensive changelogs and release notes following Keep a Changelog format. Use when documenting version history, release notes, or tracking changes across versions.
Use when structuring scenes or planning chapter content - provides a scene-sequel framework, tension management, and beat-by-beat structure for crafting compelling scenes
Generate comprehensive investor-ready business case document with market, solution, financials, and strategy
Hard-edged writing style contract for timeless, forceful English prose without AI tics
Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.
Interview-driven blog post drafting for technical product audiences. Use when user wants to write a blog post, article, or essay and needs help developing their thesis, structure, and initial draft. Triggers on "write a blog post", "draft an article", "help me write about X", "blog drafter", or when user has a topic they want to turn into written content. Conducts structured interviews using AskUserQuestion to extract the user's unique insights before generating drafts.
Generate comprehensive philosophy and standards documents for any domain (UX design, landing pages, email outbound, API design, etc.). Load when user says "create philosophy doc", "generate standards for [domain]", "build best practices guide", or "create benchmarking document". Conducts deep research, synthesizes findings, and produces structured philosophy documents with principles, frameworks, anti-patterns, checklists, case studies, and metrics.