JSai23/claude-tooling - Page 2

find-connections-a

This skill should be used when the user asks to "find connections", "what relates to this", "how does this connect", "map connections", "show related work", or needs to discover relationships across the vault.

living-doc-k

This skill should be used when the user asks about "living documents", "living doc", "update MOC", "MOC maintenance", "how do MOCs work", "keep docs updated", "project brief", or needs to understand or apply the living document pattern.

sem-search-a

This skill should be used when the user asks to "search notes", "find similar notes", "semantic search", "reindex vault", "rebuild index", "query vault", or needs to find notes by meaning rather than keywords.

common-testing-k

Testing philosophy — what good tests look like, anti-patterns, coverage priorities, naming

doc-a

Generate or update standard code documentation — docstrings, rustdoc, API references, READMEs

verify-design-a

Architecture review in hindsight — what to question, dependency analysis, abstraction assessment

verify-larp-a

Fake code detection — performative implementations, test theater, misleading patterns, red flags

verify-quality-a

Quality verification framework — dimensions, severity levels, grading criteria

verify-style-a

Code cleanliness — AI-generated slop, naming, dead code, over-engineering, simplification

ask

Ask questions about design, architecture, or how code fits together

create-handoff

Create session handoff document for transferring work to another session

doc

Generate or update project documentation

resume-handoff

Resume work from a previous handoff document

rust-quality

Rust code quality audit based on Apollo best practices

tldr

Token-efficient code analysis reference. Use when analyzing large codebases or needing structured code intelligence.