Loading...
Loading...
Found 63 Skills
A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.
Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.
This skill should be used when a team wants to create or refine the design guidelines document — for example "create the design steering doc", "document our design system", "write the design principles", "document our component patterns", "set up the design guidelines", or "update the design doc". Generates docs/steering/DESIGN.md as a living document capturing design principles, the design system, tokens, component patterns, and accessibility standards. Generated once and refined — not regenerated from scratch.
Generate reference documentation entry by entry for the public surface of a library (components, functions, commands, etc.), with manifest tracking, supporting both single-entry and batch modes. Fundamental difference from guidedoc: guidedoc teaches you how to use something, while libdoc tells you what each part looks like; guidedoc's information sources are solution docs + user knowledge, while libdoc's information source is the source code itself. Trigger scenarios: When the user says "write API documentation", "component documentation", "libdoc", "write documentation for each component", or when new public library interfaces are discovered after feature-acceptance.
Add a new package to the Remotion monorepo, including package scaffolding, monorepo registration, documentation, build scripts, tests, and release checklist updates. Use when creating a new @remotion package.
When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.
Produces a standalone multi-page research dossier on the jackin' docs site from a brief, drawing on web and codebase evidence. Use when the operator runs /jackin-dev:research.
Produce clear, accurate, and maintainable technical documentation for APIs, systems, and user workflows.
Generate Word documents (.docx) from Markdown.
Initialize a long-running project with a structured docs workflow, or update an existing project (new features, bug fixes, refactors, requirement changes). Use this skill whenever the user wants to start a new project, kick off a long-running build task, set up project documentation structure, or says things like "new project", "start a project", "init project", "project setup", or "I want to build something from scratch". Also use when the user mentions wanting a milestone-based plan, structured execution workflow, or asks to scaffold documentation for a complex multi-step build. Additionally, use this skill when the user wants to modify an existing project that already has a `docs/` directory — e.g., "add a new feature", "fix this bug", "refactor X", "I want to change how Y works", "new feature request".
Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.
Structured, reproducible analysis documentation. Use when documenting analysis findings, creating analysis notebooks, ensuring reproducibility, or building analysis archives for future reference.