メニュー
Stay aligned with Vinyan governance — generator/verifier separation, no self-evaluation, deterministic routing, content-addressed evidence, trust gates. Use when designing routing, verification, or commits.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review code changes for correctness, error handling, scope creep, and style. Use when the goal mentions reviewing a PR, diff, or file.
Walk through a stack trace or error log to find the root cause. Use when the goal mentions debugging, investigating an error, or tracking down a bug.
Write a Conventional Commits message describing a code change. Use when the goal mentions creating a commit, writing commit message, or committing changes.
Outline unit tests for a function or module before writing them. Use when the goal mentions writing tests, test plan, or test coverage.
Keep effort proportional to risk — prefer the cheapest sufficient workflow, escalate only on evidence, refuse over-analysis on simple tasks. Use when choosing depth, level, or workflow shape.
Map required capabilities to persona roles and available skills. Detect missing skill coverage and decide whether to acquire a skill, request one, or proceed generically. Use when scoping a workflow.
| name | governance-guardrails |
| description | Stay aligned with Vinyan governance — generator/verifier separation, no self-evaluation, deterministic routing, content-addressed evidence, trust gates. Use when designing routing, verification, or commits. |
The orchestrator's reliability comes from rules that hold even when the model is wrong. When designing a workflow, the rules are not optional; they are the load-bearing part.
When you find a guardrail violation, name it explicitly: which axiom · how it is violated · the deterministic alternative. Do not silently fix; surface and propose.
