Menü
Personal knowledge base conventions and session workflow for ~/Projects/kb
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Work with MusicXML scores (.musicxml / .xml / .mxl) - read them, reason about them at the level of chords / keys / progressions / structure, make semantic edits, and preview the result live in a browser. Use this skill whenever the user asks about or wants to modify a music notation file.
Use this skill when the user asks to create an agent, add a subagent, write a system prompt, define triggering conditions, choose tools or model settings, or adapt an agent format for a different client.
Use when analyzing codebases requiring search patterns, dependency tracing, or architecture discovery. Invoke for ripgrep patterns, call graph analysis, security scanning.
Creates Excalidraw diagrams programmatically. Use when the user wants flowcharts, architecture diagrams, system designs, or any visual diagram instead of ASCII art. Outputs .excalidraw files that can be opened directly in Excalidraw or VS Code with the Excalidraw extension.
Use when working with Git requiring branching strategies, commit conventions, or collaboration workflows. Invoke for rebasing, merging, conflict resolution, PR workflows.
Convert Markdown files into a Google Doc with tabs and extract tab content as markdown. Supports Obsidian-flavored markdown: frontmatter, wikilinks, callouts, GFM tables, task lists, fenced code blocks.
| name | kb |
| description | Personal knowledge base conventions and session workflow for ~/Projects/kb |
Framework for working with the Obsidian knowledge base at ~/Projects/kb. Full conventions are in ~/Projects/kb/AGENTS.md — read it at the start of any KB session.
| Location | Purpose |
|---|---|
inbox/inbox.md | Raw capture buffer — drop anything here |
notes/<topic>.md | Atomic zettelkasten notes (flat, title-based) |
mocs/<area>.md | Maps of Content — curated entry points into notes |
projects/<name>/ | Project overview, progress, and session files |
reference/<topic>.md | Stable lookup facts |
people/<name>.md | One file per person |
codebases/<name>/ | Codebase orientation notes |
| Type | Schema |
|---|---|
note | Atomic zettelkasten note — one idea, densely linked |
moc | Map of Content — navigable entry point into a topic cluster |
project | Project overview — goals, status, people, todos |
progress | Current state snapshot — read first, update last |
session | What happened in a work session |
reference | Stable lookup facts |
person | Who someone is |
projects/<project>/progress.md — current phase, in-flight, next up, blockersprojects/<project>/progress.md — reflect actual current stateprojects/<project>/sessions/YYYY-MM-DD.mdjj describe -m "<brief description>" && jj newAll files have YAML frontmatter with alphabetized fields. Key fields:
type: categorizes the note (note, moc, project, progress, session, reference, person)updated: ISO 8601 date, updated whenever the file changesproject: wikilink to project overview, e.g. "[[projects/mvcp/mvcp]]"Use Obsidian wikilinks with full vault-root paths:
[[notes/active-passive-design]]
[[mocs/atlas-control-plane]]
[[projects/mvcp/progress|progress]]
[[people/craig-wilson|Craig Wilson]]
[[reference/mongodb/fiscal-calendar]]
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Zettelkasten | references/zettelkasten.md | Creating or linking notes, unsure what belongs in notes/ vs elsewhere |
| Research | references/research.md | Conducting research, creating new notes from investigation |
| Project management | references/project-management.md | Starting, continuing, or completing a project |
| Inbox processing | references/process-inbox.md | Processing inbox, synthesizing captures, clearing inbox items |
❌ Creating a note without first checking if one already exists
❌ Ending a session without updating progress.md
❌ Using git instead of jj
❌ Putting atomic knowledge in projects/ instead of notes/
❌ Creating a MOC with fewer than 3 linked notes