메뉴
SkillsMP는 lev-os/lev-content에서 42개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
수집된 skill 42개 중 40개를 표시합니다.
[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…
원문 언어: 영어
[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…
원문 언어: 영어
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…
원문 언어: 영어
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.…
원문 언어: 영어
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…
원문 언어: 영어
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…
원문 언어: 영어
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…
원문 언어: 영어
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…
원문 언어: 영어
[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…
원문 언어: 영어
[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…
원문 언어: 영어
[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…
원문 언어: 영어
[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 -…
원문 언어: 영어
[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]…
원문 언어: 영어
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,…
원문 언어: 영어
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…
원문 언어: 영어
[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…
원문 언어: 영어
[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:…
원문 언어: 영어
[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…
원문 언어: 영어
[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…
원문 언어: 영어
[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…
원문 언어: 영어
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.…
원문 언어: 영어
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…
원문 언어: 영어
[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…
원문 언어: 영어
[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…
원문 언어: 영어
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…
원문 언어: 영어
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…
원문 언어: 영어
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…
원문 언어: 영어
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,…
원문 언어: 영어
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…
원문 언어: 영어
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.
원문 언어: 영어