Articles, tutorials, and announcements
How the writing skill breaks content creation into five phases — research, drafting, self-review, editorial review, and publication preparation — with specific guards against fabricated numbers, broken links, and stale pricing.
Read more →How the writing-plans skill structures implementation plans as bite-sized TDD tasks with exact file paths, complete code, and expected command output — so an engineer with no prior context can execute without guessing.
Read more →How the visual-maps skill provides a fragment-based index of workflow diagrams so an agent loads only the diagram relevant to its current question, not the full map library.
Read more →How the verification-before-completion skill enforces a single rule: no completion claim without fresh verification output. The gate function, common failure modes, and why partial checks prove nothing.
Read more →How the v-ac-axis-split skill catches V-AC groups that mix rule-based and rate-based criteria, and why collapsing the two axes into one group produces false confidence.
Read more →How the utilities skill provides a library of native shell one-liners — from hashing to SSH remote execution — organized into fragments so only the relevant code loads.
Read more →How the using-git-worktrees skill sets up a clean, isolated workspace before feature work — and why it checks for existing isolation before touching anything.
Read more →How the testing skill structures verification across unit, integration, and E2E layers — and the specific rules that prevent mocks from creating a false sense of safety.
Read more →How the tech-stack skill eliminates guesswork when starting a new project by mapping project types to exact, opinionated technology choices.
Read more →How the systematic-debugging skill stops random patching and forces investigation through four phases — from evidence gathering to a single, verified fix.
Read more →