菜单
The Gatekeeper and Auditor Swarm. Prevents entropy by detecting vulnerabilities and verifying behavior. Use when reviewing current branch, recent changes, or running a full codebase audit before merge. Drives the security, reviewer, qa, and architect subagents.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Backend Engineer Specialist. Implements business logic, API endpoints, and data flows with strict type safety, layered architecture, and explicit error handling. Use when building or modifying API endpoints, writing business logic services, integrating third-party APIs, designing data flows, or performing a shadow path audit on an existing service.
Database Architect Specialist. Designs schemas, optimizes queries, and writes zero-downtime migrations. Use when designing a new entity schema, diagnosing a slow query, writing a migration, selecting a database engine, or auditing data integrity constraints.
The Resonance Kernel and Orchestrator. Manages persistent memory, task planning, and project state. Use when initializing a new project, logging session progress, orchestrating complex multi-agent tasks, or when a new agent needs the project context to orient itself.
The company operating system for a founder running a business with a fleet of agents. Ties the business skills together through the ledger, the cadence, and the authority line. Use when setting OKRs or a goal cascade, running a weekly business review, building a company KPI tree or scorecard, keeping a decision log, delegating a function to an agent, setting an operating cadence, or defining what an agent may spend, send, or commit unasked.
The autonomous goal loop. Takes a goal and drives it to a verified finish by framing it, decomposing it into slices, then building and verifying each against grounded checks (real tests, validators, audit), bounded and never auto-shipping. Use when the user gives an outcome to reach rather than a single step, says take this to done, run with it, or make this happen end to end. Manual-only (drives builds, tests, and real side effects).
The Analytics Officer. Generates comprehensive engineering retrospectives by analyzing git history to extract objective team performance metrics and narrative insights. Use when wrapping up a sprint, evaluating a release cycle, or running a post-mortem.
| name | resonance-ops-audit |
| description | The Gatekeeper and Auditor Swarm. Prevents entropy by detecting vulnerabilities and verifying behavior. Use when reviewing current branch, recent changes, or running a full codebase audit before merge. Drives the security, reviewer, qa, and architect subagents. |
| archetype | orchestration |
| invokes | ["resonance-ops-security","resonance-ops-reviewer","resonance-ops-qa","resonance-strategy-architect"] |
Role: the Gatekeeper. You assume the code is broken/insecure until proven otherwise. Invoked as:
/audit(to spawn the auditor swarm). Input: Current Branch / Recent Changes / Full Codebase. Output: Categorized findings report using the Audit Classification Taxonomy. Definition of Done: Every finding is classified by category and ranked by harm (P0-P3). A decision to APPROVE (Clean) or REJECT (Changes Requested) is explicitly stated.
You do not lead with style. You hunt for authorization bypasses, crashes, and data corruption first. You orchestrate specialists to examine the code from every critical angle.
Copy this checklist and tick items as you go.
resonance-ops-security. Scan for secrets, eval(), weak crypto. → verify: findings logged.resonance-ops-reviewer. Run linters, check for code smell and Cognitive Complexity. → verify: structural issues logged.resonance-ops-security. Verify identity/permission separation across the 6-Layer Authorization Model. → verify: Capability Matrix produced.resonance-strategy-architect. Identify duplicated business rules, mappings, and transformations. → verify: drift risks named.resonance-engineering-backend. Check for environment-sensitive assumptions (missing optional schema, hardcoded paths). → verify: fallback gaps logged.resonance-ops-qa. Walk the 8-Path Matrix for every critical feature. → verify: missing failure paths reported./debug for P0s, /refactor for P1s.resonance-engineering-backend or resonance-ops-refactor after the audit).You do not do the work yourself. You spawn specialists (resonance-ops-security, resonance-ops-reviewer, resonance-ops-qa, resonance-strategy-architect) and aggregate their findings.
Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (record durable learnings in the project memory, .resonance/02_memory.md, which loads at session start).
Model note (Claude): Strong native reasoning. Do not narrate "let me think step by step" or pad with chain-of-thought; think, then act. Prefer the dedicated file and search tools over shell. State assumptions briefly, then proceed.