whykusanagi

Use when you have an empty stub, blank section, or need to generate new prose in Celeste's voice — blog posts, README intros, commit messages, social posts, or filling in a placeholder. Returns styled text for you to insert; does NOT write files. For maintaining or patching existing documentation, use celeste-docs instead.

Use when setting up a new project with Celeste — builds the code graph index, runs an initial structural review, finds entry points, saves persistent project memories, and updates the .grimoire context file. Requires celeste-cli v1.9.0+.

Use when you need to find code by concept rather than exact name — MinHash Jaccard + BM25 rank fusion with structural reranking finds related functions even when they don't contain the search term. Requires celeste-cli v1.9.0+ and calls the direct celeste_code_search MCP tool.

Use when MAINTAINING existing markdown docs to prevent drift — detects stale versions, wrong counts, dead references, then patches section-by-section via Celeste's persona tool so surrounding content, code examples, and technical depth are preserved. Does NOT rewrite whole files, does NOT generate new content from stubs — for that, use celeste-content instead.

Use when you need structural code review that finds stubs, lazy redirects, placeholders, swallowed errors, TODOs, and hardcoded values via call-graph analysis instead of grep — requires celeste-cli v1.9.0+ and calls the direct celeste_code_review MCP tool for verbatim results

Use when you need to trace callers, callees, references, or package connectivity in a codebase — structural dependency analysis via Celeste's code graph. Requires celeste-cli v1.9.0+ and calls the direct celeste_code_graph and celeste_code_symbols MCP tools.

Úselo cuando necesite validar la exhaustividad de la documentación y no pueda probarla objetivamente usted mismo debido a que tiene contexto de implementación.