Skills
Each page uses the same reference layout: synopsis, YAML front matter, the full SKILL.md, then links to the rest of the pack.
- 01 write-tech-core Applies shared evidence, audience, structure, style, and verification rules when drafting or revising technical writing with the write-tech skill family.
- 02 write-tech-blog-post Writes or revises a technical blog post or article for a defined reader, using a focused claim, verified examples, and an intentional authorial voice.
- 03 write-tech-getting-started Writes or revises a getting-started tutorial that takes a new user through one verified path to an early, visible success.
- 04 write-tech-how-to Writes or revises a goal-oriented how-to guide for a reader who needs to complete one specific technical task.
- 05 write-tech-reference Writes or revises a precise, scannable reference page for a command, API, configuration surface, schema, or other technical interface.
- 06 write-tech-readme Writes or revises a repository README that helps the intended reader understand, try, use, and navigate a technical project.
- 07 write-tech-pr-comment Writes or revises evidenced, actionable pull request review comments and replies.
- 08 write-tech-pr-description Writes or revises a pull request title and description that explain the change, its reason, review boundaries, and verified checks.
- 09 write-tech-commit-message Writes or revises a Git commit subject and body that record one coherent change, its reason, and verified consequences.
- 10 refining-skills Use when a skill produced a bad result and there is an example plus a comment about what was wrong; when someone reports a skill failure or regression; when you are about to add a sentence to a skill and ship without reproducing the failure.