cndoit18

This skill should be used when the user asks to analyze, ingest, import, summarize into, or update a memory palace, LLM Wiki, long-term notes, or durable knowledge base. It identifies stable architecture, decisions, responsibilities, reliability knowledge, constraints, and source evidence while excluding brittle details such as directory trees, script paths, file inventories, transient logs, and code-layout facts maintained by project instructions or live source search.

Software design philosophy guide based on John Ousterhout's "A Philosophy of Software Design." Use this skill during: code reviews, architecture discussions, API design, module decomposition decisions, refactoring guidance, complexity analysis, naming and commenting improvements, error handling strategy design. Trigger when the user mentions "code is too complex", "how to split modules", "interface design", "reduce coupling", "deep/shallow modules", "information leakage", "error handling", "code readability", "design philosophy", "pull complexity down", "define errors out of existence", or similar topics. Also trigger for any code review where design quality feedback is requested.

This skill should be used when the user mentions a "GitHub repository", provides a "github.com" URL, uses "owner/repo" format, asks to "explain a codebase", "how does this repo work", "what is the architecture of X", "how is X implemented", "tell me about" an open-source project, asks to compare how multiple open-source projects implement a feature, or needs documentation about a library's internals. Also use when the user invokes /deepwiki.

Organize a folder of Markdown notes into a clearer domain/project knowledge area. Use this skill whenever the user asks to organize, tidy, restructure, classify, link, split, merge, normalize, or review notes in a vault folder. Prefer this skill over ad-hoc editing for multi-note cleanup; it keeps changes scoped, conservative, and reviewable.