stancsz

meow — Nine Lives heartbeat for Claude Code. Run a life cycle (birth → phase → exit contract → rebirth), check status, review pending gates, or spawn a one-shot task. Trigger with "run meow", "one life", "grind the mountain", "meow status", "meow -p <task>", "meow live", "meow --target <repo>".

A local, file-based knowledge graph ("second brain" / 长脑子 / 脑子不够用了) for capturing, searching, linking, and recalling notes across conversations. Use this skill whenever the user wants to SAVE something for later ("remember this", "save this article/snippet", "note that...", "记一下", "存一下", "脑子记不住"), RECALL their own knowledge ("what do I know about X?", "what have I written on Y?", "catch me up on project Z", "我之前写过 X 吗"), find GAPS ("what am I missing on X?", "我还缺什么"), or manage a personal notes/wiki/zettelkasten. Trigger it even when the user doesn't say "second brain" — any time they treat you as if you should retain or retrieve their personal notes, reach for this skill instead of answering from training data. The store is a single SQLite file with full-text search and a wikilink-driven relation graph.

meow-the-skill — the mind of the Nine Lives exoskeleton. Loaded at the start of every life the heartbeat (bin/meow.ts) spawns. The birth prompt names ONE role and ONE phase; this skill dispatches to that role's file and enforces the life-cycle discipline. Trigger whenever a session begins with "You are meow — life of …", or when a human says "run meow", "one life", "grind the mountain".

Autonomous product-team iteration loop (磨杵 — grind the pestle into a needle). Run this skill on a product repo to perform ONE full improvement cycle — competitive recon, gap analysis across every product dimension (UI, features, docs, onboarding, performance, reliability, positioning), verifier authoring, implementation, verified shipping, and ledger update — with zero human prompting. Use this skill whenever the user says "run mochu", "grind it", "磨杵", "improve the product", "do an iteration", "close the gap with competitors", "find something to work on", "act like a product team", or invokes this repeatedly in a loop (fire-and-forget). Each invocation is one iteration; looping it produces compounding, regression-protected product improvement. Also use it to bootstrap a repo for mochu (creating the .mochu/ state directory).

Autonomous product-team iteration loop (磨杵 — grind the pestle into a needle). Run this skill on a product repo to perform ONE full improvement cycle — competitive recon, gap analysis across every product dimension (UI, features, docs, onboarding, performance, reliability, positioning), verifier authoring, implementation, verified shipping, and ledger update — with zero human prompting. Use this skill whenever the user says "run mochu", "grind it", "磨杵", "improve the product", "do an iteration", "close the gap with competitors", "find something to work on", "act like a product team", or invokes this repeatedly in a loop (fire-and-forget). Each invocation is one iteration; looping it produces compounding, regression-protected product improvement. Also use it to bootstrap a repo for mochu (creating the .mochu/ state directory).

Use this skill when acting as the design-and-decision half of a two-instance Claude Code workflow (architect + builder). Trigger whenever you are setting technical vision, turning vague intent into a plan, decomposing work into tasks, ruling on decisions raised by a builder, keeping a system coherent, or maintaining a project's `docs/` planning folder. Use it for any "plan this", "break this down", "what should we build", "review what the builder did", "make the architecture call", or "set direction" request, even if the word "architect" is not used. This is the Opus-tier role: it decides and keeps the system coherent, and never reads source code.

Use this skill when acting as the implementation half of a two-instance Claude Code workflow (architect + builder). Trigger whenever you are implementing a task spec, writing code to satisfy a plan, running and testing what you built, framing a decision for the architect, or reporting results through a `docs/` folder. Use it for any "build this", "implement the task", "make the spec work", or "pick up the next task from docs" request, even if the word "builder" is not used — especially when there is a `docs/tasks/` folder with task files in it. This is the Sonnet-tier role: it writes and runs code, triages what's worth surfacing, and never guesses.

A local, file-based knowledge graph ("second brain" / 长脑子 / 脑子不够用了) for capturing, searching, linking, and recalling notes across conversations. OKF v0.1-native, multi-device sync via git, psychological memory foundation. Use this skill whenever the user wants to SAVE something for later ("remember this", "save this article/snippet", "note that...", "记一下", "存一下", "脑子记不住"), RECALL their own knowledge ("what do I know about X?", "what have I written on Y?", "catch me up on project Z", "我之前写过 X 吗"), find GAPS ("what am I missing on X?", "我还缺什么"), or manage a personal notes/wiki/zettelkasten. Trigger it even when the user doesn't say "second brain" — any time they treat you as if you should retain or retrieve their personal notes, reach for this skill instead of answering from training data. The store is an OKF-conformant Bundle with a SQLite cache (fully rebuildable).

monkey-skills is the operating system for a one-person productized service (or small commerce). The Monkey King scaffolds a real business from a proven recipe, runs delivery / retention / reconciliation, and at every decision applies top-tier frameworks (HBS, Stanford, Wharton, MIT, YC) to advise the human on what to change to make more money. It is enforced by a deterministic hook harness, not by goodwill. Trigger on: "monkey chief run/init/status/retro/ deliver/reconcile", "run the monkey", "work the pipeline", "start a business", "scaffold a business", "what should I change to make more". Also trigger on first-time setup when BUSINESS_MODEL.md is missing.

Gradient-descent-style distillation for any content. Runs a distill→score→refine loop that compresses a source — documents, transcripts, code, logs, prompts, other skills, or a PERSON/AGENT's knowledge + personality + "soul" — to a target level while holding fidelity high, then reports the quality-vs-compression trade-off and stops at the knee of the Pareto frontier. Use whenever the user wants to distill, condense, compress, summarize-without-losing-fidelity, shrink, or tighten something, and ESPECIALLY when they care about the cut-vs-keep trade-off, mention a length/token budget, ask for a high-fidelity summary, or want the sweet spot between brevity and completeness. ALSO trigger for distilling a person, colleague, character, or agent into a persona that behaves and sounds like them (voice, decisions, values/soul graded via behavioral probes), for distilling prompts/context-packs/SKILL.md files, and for adding a new distillation type when no built-in one fits. Pairs with skills-flow.