lev-content

[WHAT] Standalone alignment auditor for north-star drift. [HOW] Scans codebase state, compares to canonical docs, classifies drift, proposes corrections. [WHEN] Use only for explicit deep-dive alignment audits. [WHY] Default alignment should run inside `work`; this remains for focused audit sessions. Triggers: "align lev", "check north star", "what's our direction", "audit alignment", "detect drift", "product pivot"

[WHAT] Builder workflow for developing `~/lev` and migrating proven work to core paths. [HOW] Assess existing code, run prior art checks, decide placement against `~/lev/docs`, apply patches, validate E2E. [WHEN] Use when formalizing POCs, placing modules, or migrating workshop output into production architecture. [WHY] Prevents drift and duplicate effort by enforcing file-based routing and docs-aligned placement. Triggers: "build feature", "migrate poc", "where should this go", "prior art check", "placement decision", "formalize"

Agentic UX design language and pattern library. Establishes CLI-as-Prompt paradigm where every CLI output is a prompt to the next agent. Includes Enriched Response Protocol, vernacular (Self-Injection, Teachable Touch, Bi-Directional), and implementation patterns for validation gates and trust calibration.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Agent-human interaction protocol for AI agents. Use when agents need human approvals, selections, research direction, or async feedback. Triggers on "human in the loop", "approval", "agent interaction", "get human input", or "wait for response".

Think and reason like a software architect. Analyze systems through quality attributes, trade-off analysis, and architectural drivers. Use for system design, tech selection, ADRs, architecture reviews, C4 descriptions, fitness functions, and PR review. Triggers: "architect this", "design system", "architecture review", "ADR", "trade-off analysis", "quality attributes", "fitness functions", "C4 diagram", "system design", "review PR", "review this", "/review".

Create Mermaid diagrams (activity, deployment, sequence, architecture) from text descriptions or source code. Use when asked to "create a diagram", "generate mermaid", "document architecture", "code to diagram", "create design doc", or "convert code to diagram". Supports hierarchical on-demand guide loading, Unicode semantic symbols, and Python utilities for diagram extraction and image conversion.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Multi-agent orchestrator for Claude Code. Use when user mentions gastown, gas town, gt commands, bd commands, convoys, polecats, crew, rigs, slinging work, multi-agent coordination, beads, hooks, molecules, workflows, the witness, the mayor, the refinery, the deacon, dogs, escalation, or wants to run multiple AI agents on projects simultaneously. Handles installation, workspace setup, work tracking, agent lifecycle, crash recovery, and all gt/bd CLI operations.

Fast git sync with project codes - add, commit, pull (no rebase), push

Wizard-mode questioning skill for structured decision-making. Uses framework library (SCAMPER, First Principles, Systems Thinking, etc.) to guide users through complex decisions one question at a time.

[WHAT] 7-step systematic Root Cause Analysis (RCA) workflow for debugging [HOW] REPRODUCE → ISOLATE → TRACE → HYPOTHESIZE → VERIFY → FIX → VALIDATE [WHEN] Triggered by "uld" or "ultradebug" keywords, or explicit debug request [WHY] Structured debugging prevents guess-and-check, ensures minimal fixes Triggers: "uld", "ultradebug", "debug rca", "root cause analysis"

[WHAT] Classification engine and complexity-based routing for CDO workflows [HOW] Analyzes input intent, confidence, complexity → routes to Quick/Base/Deep/Epic [WHEN] First step of every CDO invocation - determines execution strategy [WHY] Right-sized workflows prevent over/under-engineering Triggers: Called automatically by lev-cdo main skill

[WHAT] Semantic search and discovery of skills for CDO workflow nodes [HOW] Uses lev-catalog CLI to browse, search, and load skills from axioms/hidden-gems [WHEN] Before building Deep/Epic workflows - discover skills to attach to graph nodes [WHY] Don't reinvent patterns - reuse existing decision frameworks and mental models Triggers: Called before Deep/Epic workflow construction

[WHAT] Graph-based thinking playbook (CDO) [HOW] Classifies input by complexity, routes to appropriate workflow (Quick/Base/Deep/Epic) [WHEN] Use for design, architecture, and complex problem decomposition requiring multi-perspective analysis [WHY] Provides a repeatable thinking playbook instead of ad-hoc brainstorming. Triggers: "think", "design", "architect", "complexity", "cdo", "graph", "multi-agent", "deep analysis"

[WHAT] Four complexity levels of CDO workflows: Quick, Base, Deep, Epic [HOW] Graph-based agent dispatch with disk-based artifact passing (no groupthink) [WHEN] After classification determines complexity level [WHY] Different problems need different depth - prevents over/under-engineering Triggers: Called by lev-cdo router based on complexity classification

[WHAT] UX-first design workflow from problem framing to wireframes [HOW] 7-step agentic pipeline with parallel research and framework-driven analysis [WHEN] Use when starting new features, redesigns, or product discovery requiring structured UX thinking [WHY] Design is late-stage compression - must understand users, jobs, tasks, and structure before drawing rectangles Triggers: "design", "ux", "wireframe", "user flow", "screen", "interface", "prototype"

Code analysis tool that gives AI agents exactly the code they need - 95% token savings, 300x faster queries across 16 languages for code-analysis, semantic-search, llm-tools, debugging, refactoring, codebase-understanding, token-optimization, ai-assistance, program-analysis, dependency-tracing

Quick Markdown Search - Full-text and vector search for markdown and JSONL files. Use for searching conversation history, documentation, and any text-based collections. Triggers on "search for", "find in sessions", "query history".

[WHAT] Context retrieval backend for `lev get` (legacy name: lev-find). [HOW] RRF fusion across indexes (codebase, docs, sessions, tasks, memory) plus optional research backends. [WHEN] Use for context gathering, prior art, and memory recall. [WHY] Keeps one root primitive (`get`) while preserving `find/search` aliases. Triggers: "find", "search", "lookup", "where is", "locate", "discover", "what do we have on", "related work", "prior art", "recall", "remember", "what did we discuss", "search memory", "find in history", "conversation history" Category: GET (context gathering, memory recall, semantic search) Indexes: codebase, documentation, ideas, sessions, tasks, skills, memory

[WHAT] Vector index management for semantic search using LEANN (97% storage reduction) [HOW] Build indexes from directories, add content incrementally, search semantically via gRPC service on port 50052 [WHEN] Use when building/updating indexes, checking index health, or directly querying a specific index [WHY] Enables semantic search across code and docs with efficient graph-based storage Triggers: "build index", "search index", "index status", "add to index", "update index", "semantic search"

[WHAT] Universal content intake system for URLs (GitHub repos, YouTube videos, articles, PDFs) and skill packages (skills.sh, skill:// protocol) [HOW] Phase 1: Clone repos/fetch transcripts/scrape content/resolve skills to ~/lev/workshop/intake/. Phase 2-3: Load workshop/intake.md for full analysis [WHEN] Use when user provides a URL to analyze, says "intake/download", wants to evaluate external content, or references a skill package [WHY] Systematically evaluates external content and skill packages for adoption/adaptation with tier classification and ADR creation Triggers: "intake", "download", "analyze this url", "check out this repo", "review this video", "evaluate content", "install skill", "skill://"

[WHAT] Guided learn-mode intake for ambiguous or early-stage work. [HOW] Runs a one-question-at-a-time interview, infers context when missing, writes a proposal artifact, then hands off to `work` for lifecycle continuation. [WHEN] Use for "learn", "learn <context>", "help me figure this out", or when the request needs structured context building before spec authoring. [WHY] Converts fuzzy intent into a concrete proposal without skipping lifecycle gates.

[WHAT] CLI operations reference for lev runtime management. [HOW] Routes to daemon/debug/reference commands and links canonical docs. [WHEN] Use for daemon status, runtime checks, and operational troubleshooting. [WHY] Keeps runtime ops discoverable while lifecycle/process behavior stays in `work`. Triggers: "install lev", "lev daemon", "lev status", "manage daemons", "lev architecture", "debug lev", "lev setup"

[WHAT] Legacy install/setup reference for Lev CLI. [HOW] Documents historical install paths and commands. [WHEN] Use only when explicitly troubleshooting installation behavior. [WHY] Active install guidance should live in `~/lev/docs` and runtime commands (`lev-core`). Triggers: "install lev", "lev install", "setup lev", "upgrade lev", "verify installation", "lev setup", "configure lev"

Autonomous SDLC router. Takes a job, classifies complexity, executes the appropriate lev-* workflow (from trivial fix to full epic), and returns "done" with runnable instructions. One shot to full auto: spec/bd/poc/impl. Subagent returns completion artifact. Triggers: "sidequest", "side quest", "just do it", "autonomous", "one shot"

Multi-modal multi-agent deliberation for complex problems. Each parliament seat uses a DIFFERENT model (Claude, Gemini, Llama, DeepSeek) for genuine perspective diversity. Includes `lev get` pre-step for context injection. CDO 5-stage cycle, confidence-based routing, and anti-groupthink safeguards. Triggers on "parliament", "deliberate", "multi-perspective", or strategic decisions.

[WHAT] Deep Research Intelligence System — Unified research orchestration with recursive confidence, multi-perspective synthesis, and session management. [HOW] Routes based on query complexity: QUICK (brave/firecrawl), STANDARD (multi-tool), DEEP (valyu+oracle) [WHEN] Any research, search, or information gathering task [WHY] Eliminates decision fatigue - one entry point routes to optimal backend(s) Keywords: search, research, deep, oracle, sherlock, social, investigate, analyze

[WHAT] CLI and SDK reference surface for Lev primitives. [HOW] Maps natural language aliases to stable primitives: get/work/ask/check/go. [WHEN] Use when you need command syntax, alias mapping, protocol routing, or SDK usage. [WHY] Keeps CLI usage stable while lifecycle/process logic lives in `work`. Triggers: "lev", "leviathan", "get", "search", "find", "lookup", "read", "ls", "research", "think", "spec", "plan", "execute", "analyze", "design", "validate", "align", "lifecycle", "work", "check", "scan", "security", "daemon", "daemons", "ask", "wiz", "wizard", "go", "handoff", "exit", "learn", "workflow", "skill"

Multi-platform social research: Twitter/X via Bird CLI and Reddit/TikTok via PostCrawl; aggregate results and generate sentiment/trend reports.

[WHAT] Workshop lifecycle for building and evolving plugins, hooks, and integrations [HOW] Four phases: intake (capture ideas), analysis (scope/approach), POC (build prototype), poly integration (promote to production targets) [WHEN] Use when developing new lev capabilities, promoting POCs to production, or systematically building hooks/plugins [WHY] Ensures systematic development from idea to production with quality gates at each phase Triggers: "workshop this", "analyze for workshop", "poc this", "integrate to poly", "workshop status", "build capability", "new hook"

Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.

Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.

Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.

Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.

Router for skill creation: routes doc/repo-to-skill codification or routes to skill-creator for authoring. Use for doc-to-skill, new skills, or merging skills.

Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.

[WHAT] Static analysis gate using Ultimate Bug Scanner (UBS) — multi-language AST-level bug detection. [HOW] Runs `ubs` scoped to changed/staged files, parses findings by severity, fixes critical issues inline. [WHEN] Before every commit. On PR review. When asked to scan for bugs, static analysis, or code quality. [WHY] Catches resource leaks, null derefs, type narrowing gaps, and concurrency bugs that linters miss.

UX design hub: 7-step wireframe pipeline + product design (design-os) + visual prototyping (pencil) + agentic UX patterns (lev-ref). Use for wireframes, flows, IA, JTBD, product design, CLI design, agentic UX, design systems, or component architecture.

Unified lifecycle/process router. Concurrent FSM that discovers context, runs embedded alignment checks, researches, proposes, specs behavior, and routes to specialist skills. Guard scoring is constant, not gated. Artifacts are spec-first.