Pursue structural signals — dead code, cycles, duplicate exports (twins), hotspots, runtime traces, command/event/pipeline graphs. Use during cleanup, audit, refactor planning, or when investigating "is this used?" questions at module/system scope. Triggers on phrases "follow signals", "find dead code", "find cycles"…
Score conceptual smear (drift, spread, runtime centrality, authority diversity, drift risk, closure evidence) across two or more task framings on the canonical 0..15 rubric. Use BEFORE running vc-polarize, BEFORE choosing a doctrine cut, or whenever an agent needs structural evidence for the abort/memo/pass/doctrine…
Structural and literal repository perception before edits, deletes, refactors, or unfamiliar-code work. Use context/repo-view/focus/slice/impact/find/follow to establish scope, dependencies, blast radius, exact occurrences, and analyzer coverage before acting.
Use when an agent should work with Lifeblood's MCP semantic-code tools: analyzing C# or Unity workspaces, querying symbols/dependencies/blast radius/file impact/test impact, checking architectural invariants, validating edits with compilecheck/diagnose, or choosing the right Lifeblood tool instead of grep-style…
USE WHEN you need a structured OLAP slice of a large codebase, log stream (including multi-GB .gz), CSV export, sitemap or HTML crawl, or an SDD artefact catalog — WITHOUT reading raw file bodies into the context window. Single-pass aggregator: streams input, folds records into an in-memory cube by user-picked…
Add a new top-level block to .techdebtrc.json — extends TechDebtConfig type, validator, consumer wiring, and dogfood self-scan fixture in one coordinated change.
Run tech-debt-mcp-local against this repo, refresh TECHDEBTSCAN.md, and propagate Health / Debt Score / Issues / Remediation to README.md, ARCHITECTURE.md, CONTRIBUTING.md in a single commit.
Automatically run a tech-debt scan before opening a pull request, after large refactors, or when the user asks for a code review — surface actionable findings without being asked.
Use when builds data transformation flows on top of cocoindex — a Python framework with a Rust engine for ultra-performant, incremental data indexing (ETL, RAG ingestion, knowledge graphs, vector search). Covers the flow-building public API: FlowBuilder, DataScope, DataSlice, Flow, FlowLiveUpdater, sources, targets…
Builds apps on top of cognee v0.5.8, the knowledge-graph memory engine for AI agents. Use when ingesting text/files/URLs into persistent agent memory, building knowledge graphs with entities and relationships, searching graph-backed memory with multiple search modes (GRAPHCOMPLETION, CHUNKS, SUMMARIES, TEMPORAL…
Authors Storybook v10 stories using the consolidated storybook package import surface for React plus Vite. Use when writing or editing .stories.tsx, preview.ts, or .storybook/main.ts files on a Storybook 10.3+ project, including CSF3 story syntax, play functions with storybook/test, preview-api hooks, theming, MDX doc…
Query the codebase-intelligence CLI to understand TypeScript architecture, dependencies, blast radius, and risk before reading files. Use for any "how is this structured", "what breaks if I change X", "where is the complexity" question.
Manage Symbiote's Developer DNA — the learned coding preferences, style rules, and anti-patterns that persist across sessions. This skill should be used when the user asks to "show my coding preferences", "manage DNA", "update my coding style", "what are my coding rules", "switch DNA profile", "export DNA", "import…
Trace the blast radius of a code change using Symbiote's dependency graph. This skill should be used when the user asks to "analyze impact", "what will this change break", "show affected files", "check blast radius", "impact analysis", or "what depends on this".
Initialize Symbiote for the current project. Scans the codebase and extracts developer DNA (coding preferences), project constraints, and architectural decisions from the current context. Use when the developer runs /symbiote-init, asks to "initialize symbiote", "set up symbiote", or "scan my project". Requires…
Reduce Claude AI token consumption by 5x-27x using prompt-native workflows and structural code manifests. Forces Claude to reason from CONTEXTMANIFEST.md first, fetch max 3 files per turn, and output in a strict compressed format. Use when user says optimize context, reduce tokens, context optimizer, manifest, blast…
Reduce Claude AI token consumption by 5x-27x using prompt-native workflows and structural code manifests. Forces Claude to reason from CONTEXTMANIFEST.md first, fetch max 3 files per turn, and output in a strict compressed format. Use when user says optimize context, reduce tokens, context optimizer, manifest, blast…
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable.
Interactive codebase polish loop. Run parallel audit agents across chosen lenses, synthesize findings, and persist state in POLISH.md for incremental improvement across sessions.
Mine the ecosystem for open workstreams — paused arcs, abandoned/soft-abandoned sessions, parked design questions — apply the liveness discriminator, and produce two artifacts: registry entries for docs/open-threads/ and a fresh WIP snapshot. Use when the user wants to find loose ends, recover dropped threads, audit…
Turn a large codebase into a short, ranked reading list of security-relevant code paths worth a human researcher's time, using the flyto-indexer MCP tools. Use when asked to find, prioritize, or triage potential vulnerabilities / taint flows / attack surface in a repository indexed (or indexable) by flyto-indexer …
Test codeweave-mcp tools against any project using TestHarness. Use this whenever verifying tool behavior, testing a code change, or running custom assertions — e.g. "test the harness", "run tests against X project", "does semanticsearch work correctly".
Run CH015 vulnerability assessment workflows for source-code security architecture review, 8-dimension analysis, compliance checks, self-verification, evidence verification, and VA reporting.