pmcc
7e6d30c3cd
- Restructure repo into chezmoi source layout (dot_ prefix) - Add .chezmoi.toml.tmpl mapping hostname to hosttype (laptop/desktop) - Template sway config.d fragments (outputs/inputs/binds) per host - Template waybar config.jsonc with shared bar/module definitions - Host-scope pulsemeeter (flow) and teams-for-linux (desktop hosts) via .chezmoiignore - Trim install.sh package lists to configured software + config deps - Remove stale kitty.conf.bak and untracked host fragments
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
- Prefer concise, readable code over clever one-liners
|
|
- No unnecessary comments — code should be self-documenting
|
|
- Docker-friendly: no hardcoded paths, use env vars for config
|
|
|
|
<!-- codebase-memory-mcp:start -->
|
|
# Codebase Knowledge Graph (codebase-memory-mcp)
|
|
|
|
This project uses codebase-memory-mcp to maintain a knowledge graph of the codebase.
|
|
ALWAYS prefer MCP graph tools over grep/glob/file-search for code discovery.
|
|
|
|
## Priority Order
|
|
1. `search_graph` — find functions, classes, routes, variables by pattern
|
|
2. `trace_path` — trace who calls a function or what it calls
|
|
3. `get_code_snippet` — read specific function/class source code
|
|
4. `query_graph` — run Cypher queries for complex patterns
|
|
5. `get_architecture` — high-level project summary
|
|
|
|
## When to fall back to grep/glob
|
|
- Searching for string literals, error messages, config values
|
|
- Searching non-code files (Dockerfiles, shell scripts, configs)
|
|
- When MCP tools return insufficient results
|
|
|
|
## Examples
|
|
- Find a handler: `search_graph(name_pattern=".*OrderHandler.*")`
|
|
- Who calls it: `trace_path(function_name="OrderHandler", direction="inbound")`
|
|
- Read source: `get_code_snippet(qualified_name="pkg/orders.OrderHandler")`
|
|
<!-- codebase-memory-mcp:end -->
|