From personal-brain-skill
Use this skill when the user asks to "log ADR", "architecture decision", "debugging session", "tech debt", "code patterns", "project status", "log this bug fix", "what did I decide about", "engineering decisions", "code review notes", "snippets", or mentions ADR, debugging log, tech-debt tracking, engineering patterns, project tracking, or architecture decisions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/personal-brain-skill:engineering-knowledgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill governs the engineering knowledge modules of the Personal Brain OS. It covers architecture decisions, debugging logs, tech debt tracking, engineering patterns, and project tracking. These files capture the accumulated engineering judgment that compounds over time — past decisions, hard-won debugging insights, and evolving code conventions.
This skill governs the engineering knowledge modules of the Personal Brain OS. It covers architecture decisions, debugging logs, tech debt tracking, engineering patterns, and project tracking. These files capture the accumulated engineering judgment that compounds over time — past decisions, hard-won debugging insights, and evolving code conventions.
The engineering knowledge module manages both entity directories (decisions, debugging, tech-debt) that require glob + frontmatter scanning and static narrative files (patterns, projects) that are loaded in full. Observation masking is critical for entity directories to avoid context bloat.
Load this skill for any of the following:
Do NOT load this skill for personal identity, content creation, contact lookups, goal tracking, or journaling — those belong to other modules.
All paths relative to ~/brain/:
| File | Purpose | When to Load |
|---|---|---|
code/decisions/ | Directory of ADR .md files | When logging or searching architecture decisions |
code/debugging/ | Directory of debugging entry .md files | When logging or searching past debugging sessions |
code/tech-debt/ | Directory of tech debt item .md files | When tracking or prioritizing tech debt |
code/patterns.md | Narrative engineering patterns reference | When user asks about coding patterns or conventions |
code/projects.yaml | Project registry with status | When checking project status or cross-referencing |
Setup check: If any of these files or directories is missing, inform the user and suggest using the /bootstrap command to create them from the reference templates in skills/engineering-knowledge/references/.
These rules operationalize observation masking and efficient file access for the engineering knowledge module. They are non-negotiable for all engineering queries.
When searching architecture decisions:
code/decisions/*.mdid, date, status, tags, projectNever load all ADR bodies at once. Frontmatter-first scanning prevents context bloat.
When searching past debugging sessions:
code/debugging/*.mdid, date, project, difficulty, tags, statusIf the user is logging a new debugging session (not searching), skip the scan and create a new entry from the template.
When tracking or reviewing tech debt:
code/tech-debt/*.mdid, project, severity, effort, impact, statusstatus: open by default (unless the user asks for all statuses)Load body of a specific tech debt item only when the user needs the full description or proposed fix.
When the user asks about coding patterns, conventions, or engineering preferences:
~/brain/code/patterns.md in full — it is a narrative file, not an entity directorypatterns.md is absent: inform the user and suggest bootstrapping from the templateDo not glob or scan patterns.md — always load it completely.
When ADRs, debugging entries, or tech debt items reference a project:
~/brain/code/projects.yaml for project contextprojects.yaml and present the relevant entryWhen searching engineering decisions: glob code/decisions/*.md, load frontmatter only (id, date, status, tags, project). Load body of specific ADR files only when full context is needed. When searching debugging entries: glob code/debugging/*.md, filter by tags matching current symptom, load frontmatter only for initial triage, then load body of top 2–3 matches. Tech debt: glob code/tech-debt/*.md, filter status: open, sort by severity.
These files live in skills/engineering-knowledge/references/ and serve as the starting templates for bootstrapping the user's ~/brain/code/ directories. Use /bootstrap to copy them into the vault.
| Template | Copies To | Purpose |
|---|---|---|
adr-template.md | ~/brain/code/decisions/ | Architecture Decision Record template |
debugging-template.md | ~/brain/code/debugging/ | Debugging session log template |
tech-debt-template.md | ~/brain/code/tech-debt/ | Tech debt item template |
patterns-template.md | ~/brain/code/patterns.md | Engineering patterns narrative reference |
projects-template.yaml | ~/brain/code/projects.yaml | Project registry with status tracking |
engineering-knowledge sub-skill. Covers code decisions, debugging, tech debt, patterns, and project tracking. Entity directories use frontmatter-only scanning with observation masking. Behavioral rules EK-1 through EK-5 implement efficient context loading.npx claudepluginhub lsetiawan/agentsos --plugin personal-brain-skillFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.