Guides

Each guide covers one real developer goal. You get the Skill to select, the request to type, the behavior to expect, and how to verify the result yourself. Requests are plain language; there is no Kiyo command syntax.

Evidence status

Guides describe the framework’s authored contracts. Native Skill behavior on every host is NOT_TESTED, so keep your own evidence (git status, diffs, and command output) when you follow them.

Setup

Onboard a repositoryPreview, then initialize Memory and configuration with Init.

Configure project policyFill .kiyo/policy.md, choose an optional preset, reference accepted policy.

Daily engineering

Define a requirementTurn a request into acceptance criteria and a readiness verdict.

Implement a changeBug fix or feature with real verification and bounded repair.

Review changes read-onlyFindings with severity and confidence; zero writes.

Assess, run, and write testsThree test modes with separate effects.

Governance, context, and security

Handle sensitive actionsScoped approval requests, reuse, and reassessment.

Detect architecture driftCompare Memory and approved decisions with current code.

Audit a third-party SkillReview a Skill package against AST01–AST10 without running it.

Add a stack profileExtend Kiyo with guidance for another technology.