This skill should be used by all kon agents at startup, before beginning work, to load relevant memory from public and repo indexes with relevance-based ordering and a 10-entry cap. Consumers: Azusa, Mugi, Mio, Jun, and any future memory-reading agent.
This skill should be used by the kon orchestrator on every /kon command, to frame the run with Ui narration at the opening, the closing, and stuck-point beats, and to enforce the emoji prefix on every mention of a kon agent or narrator.
Keep orchestrator chat lean — artifacts hold full agent output; orchestrator routes by file pointer only. Applies to all /kon: commands that spawn Task subagents.
This skill should be used by the kon orchestrator on every /kon command, alongside narration, to govern the conversational conduct of the main dialogue — AskUserQuestion widget discipline and word-choice norms.
Mandatory understanding check after exploration and before any Mugi planning step. Orchestrator asks high-level and implementation questions; do not spawn Mugi until answers resolve material gaps. Applies to /kon:team, /kon:design, /kon:debug.
Convention for per-repo skill directories at /.kon/projects/ /skills/ /SKILL.md. Each named subdirectory is one skill. Agents load all SKILL.md files as the first step before memory entries.
This skill should be used by the orchestrator at the end of pipeline commands (team, quick, design, debug, gc, address-comments) after /kon:summarize, to propose session learnings for public or repo memory with human confirmation before write.
This skill should be used by the kon orchestrator at the start of every command and after every agent step, to write a JSON session file to /.kon/projects/ /sessions/ that the dashboard reads.
This skill should be used when performing code review on a diff (whether implemented by another agent or an external PR), enforcing a strict reviewer stance, applying a mandatory 7-item golden checklist, demanding evidence, and giving specific改法 instead of vague critique.
This skill should be used when orchestrating the full kon teammate flow — Azusa explores, Mugi plans, Yui implements, Sawako cleans, Mio reviews. Applies to /kon:team.
Map a codebase for learning — glossary, architecture, flashcards, and quiz. Produces interactive HTML (clickable terms/diagrams + side panel) and an optional PDF.
This skill should be used when the user passes --yolo to any kon command. The orchestrator proceeds autonomously through all confirmation checkpoints, accepting defaults and auto-retrying failures. Stops only when genuine human judgment is required.