JSai23/claude-tooling - 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.

原文の言語: 英語