Menu
Load full Yap project and z-yap design-space state, and become aware of the support files and procedure skills for working in the knowledge base.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Canonical procedure for authoring and executing a Yap implementation plan under z-yap/resources/plans/: plan shape, z-yap tracking (thread/queue/zettels/paper trail/session zettel), verification, and close-out reconciliation. Apply when the user asks for a plan, phased work, or a feature/refactor broken into milestones.
Spawn an independent reviewer agent to audit Yap code against the project's strict style contract. Use when the user asks to review, audit, or check code quality after implementation, or when a plan includes an audit/review pass. Detects: type assertions, mutation, else blocks, null usage, loose equality, narration comments, missing provenance, ts-pattern violations, fp-ts misuse.
| name | load |
| description | Load full Yap project and z-yap design-space state, and become aware of the support files and procedure skills for working in the knowledge base. |
| disable-model-invocation | true |
| user-invocable | true |
Load the current state of the project and its design-space zettelkasten (z-yap), and surface the support files and procedure skills that govern work in the knowledge base. This skill loads state and awareness — it is not the session/interaction protocol. That lives in the zettelkasten skill.
All paths are relative to the yap repo root unless noted.
Follow links recursively until you have a complete picture; do not stop at the first file.
AGENTS.md — project overview, key references, style summary, rule index..github/copilot-instructions.md — architecture, build/test, testing patterns, V2 migration, agent interaction style. Follow its pointers into .cursor/rules/*.mdc (coding-style, pattern-matching, conventions, testing, agent-behavior, session-start).z-yap/init.md — z-yap orientation and the map of skills and support files.z-yap/README.md — federation model, zettel format, connection format, federation URIs.z-yap/REGISTRY.md — tag and edge-label registry (the descriptive vocabulary).z-yap/thread.md (scroll to end) — what happened most recently.meta zettels — knowledge-base conventions and design-to-implementation pipeline:node z-yap/scripts/catalog.js --tag meta
node z-yap/scripts/current-state.js # composite: pulse + baseline + ADR roll-up + hub snapshot
node z-yap/scripts/status.js # thread + queue summary
node z-yap/scripts/threads.js --pending # non-implemented items per thread
node z-yap/scripts/queue.js # pending queue items
When the session targets a specific thread or topic, pull its neighborhood:
node z-yap/scripts/neighborhood.js <thread-slug> # fuzzy slug match
z-yap/.cursor/skills/zettelkasten/SKILL.md) — canonical procedure for all knowledge-base writes: creating/updating/connecting zettels, hubs and threads, ADRs, the paper trail, the queue, the session/interaction workflow, and the quality theory for zettel content.z-yap/.cursor/skills/zettel-quality-rework/SKILL.md) — phased campaign for reworking low-quality (IMPL-MAP / MIXED) zettels into durable design knowledge..cursor/skills/create-plan/SKILL.md) — authoring and executing implementation plans under z-yap/resources/plans/..cursor/skills/yap-reviewer/SKILL.md) — code review for the yap implementation.After reading, confirm full context with a brief summary: current status, active threads, ADR state, and any open queue items relevant to the user's intent. Surface contradictions between these docs and the actual code (per .github/copilot-instructions.md § Instruction self-maintenance).
Follow .cursor/rules/agent-behavior.mdc and .github/copilot-instructions.md § Agent interaction style: do not edit the repo in response to questions or meta feedback unless explicitly asked; confirm before substantive changes; surface contradictions rather than resolving them silently.