xsefirosus

anti-hallucination

Use when producing any factual output -- paths, APIs, numbers, citations, config keys, or claims about code behavior. The canonical no-invention rule every agent points to; unknown lookups become UNKNOWN, unrun executions become PENDING, and every claim traces to a source.

backend-design

Use when designing or building anything below the API seam -- endpoints, data models, migrations, background jobs, or service boundaries. Contract-first API design with trust-boundary validation, idempotent mutations, reversible migrations, and an explicit error taxonomy.

Web & Frontend Listed

frontend-design

Use when designing, building, auditing, or redesigning any user interface, or studying a design reference. The anti-AI-slop craft skill -- one committed aesthetic direction from a named lane catalog, typography-first hierarchy, a spacing system, tokens, designed states, and non-negotiable accessibility.

loop-engineering

Use when designing, running, or resuming a loop, or mapping the five moves to repo mechanics. Covers discovery, handoff via worktrees, verification, persistence, and scheduling, plus grep-countable stop conditions, deterministic tripwires, and the git-trust and cycle-count resume rules.

memory-protocol

Use when reading from or writing to the memory vault, distilling notes, or maintaining the router. The Obsidian-style vault contract covering note frontmatter schemas, the router-based read ladder, the privacy-filtered append-only write path, and tier and scope promotion rules.

retro-improve

Use when running the self-improvement retro over qa-engineer rejects, gate failures, and metrics to propose bounded edits. Single-writer, append-only-safe self-improvement that edits only managed-by sefi-agents files and stops when improvement is disabled.

security-review

Use when reviewing a diff, dependency change, or configuration that touches a trust boundary before it can reach a PR. The security gate covering secrets, injection surfaces, unsafe constructs, dependency risk, authorization, and data handling.

sefi-orchestration

Use when routing a request to the right agent, handing off between agents, or dispatching a subagent. The always-loaded routing brain covering roster, handoff rules, the parse ladder for structured output, model routing, and pointers to the harness map and never-auto-merge rule.

technical-writing

Use when writing or revising user-facing prose -- READMEs, changelogs, guides, adapter docs, or release notes. Audience-first structure with a quickstart before theory, every claim verified against the repo, and no invented benchmarks or features.

n8n-workflow-design

Use when designing an n8n or similar automation workflow as an implementable spec. Opens with the must-haves Rule block covering triggers, idempotency, retries, secrets, webhook security, observability, and cost-per-run, and points to references/node-patterns.md for deep patterns.

strategy-gate

Use when judging a trading-strategy artifact against hard performance gates and assigning a tier. Opens with the Rule block for profit factor, drawdown, expectancy, and coefficient-of-variation thresholds at 4-6 folds plus the tier ladder; gate math and worked examples live in references/gate-math.md.

terse-mode

Use when terse_mode.enabled is true in sefi.config.yml and a chat reply exceeds roughly 1.5-2k output tokens. Narration compression with an explicit drop-list and never-touch-list; it compresses phrasing, never scope, and never touches code, paths, or safety warnings.