## Knowledge systems - Knowledge architecture - designing knowledge structures with meaningful connections ([[Knowledge base design]], [[Zettelkästen]], [[Directed acyclic graph]], [[PARA method]]) - AI-assisted knowledge workflows - LLMs as a co-processing layer for knowledge, not just text generation ([[Multi-agent second brain]], [[Claude + Obsidian Setup]]) - Agent-prompt design - prompts as "source code" for agents operating on a knowledge base #compose link to a concrete example or note: what does this look like in practice (input, output, agent boundary) - PKM systems thinking - why-first orientation: understanding why a system exists before deciding how to build it ([[Knowledge types]]) - Persistent memory design - solving the statelessness problem in AI workflows via external memory layers ([[Knowledge retention system design]]) - Toolchain integration - composing tools ([[Obsidian]], Claude Code, MCP, shell scripting) into coherent, maintainable systems ## AI & delivery - Multi-agent system design ([[Multi-agent second brain]]) - AI-augmented delivery workflows ([[AI-augmented delivery]]) #compose this section is thin - expand with: agent orchestration patterns, prompt engineering, LLM evaluation, specific tools and frameworks you work with ## Engineering leadership - Cross-team standards and culture - Delivery framework articulation - aligning engineering practice with commercial positioning ([[Delivery framework articulation]]) - Technical strategy (IC track, [[Senior Staff Engineer]]) #compose add a depth marker: where this is strongest (standards, culture, cross-team alignment) vs where it is not (P&L ownership, headcount management) ## Engineering breadth - Full-stack engineering (.NET → JavaScript) - Cross-domain context-switching across engineering, product, and business - Scope across full-stack, DevOps, and Data #compose be specific: what does DevOps and Data exposure actually mean (tools, depth, real examples), and where the breadth stops ## Community & content - Tech evangelism and thought leadership ([[Tech Evangelist]]) - Developer community building - meetups ([[DevDuck]]), podcasts ([[Better Tech Leadership]]), events - [[DevRel]] #compose add concrete outputs: articles published, talks given, community reach - make the competency verifiable, not just claimed