godmode

- Read the full error output before proposing any fix. Do not skim.

- Always run `git branch --show-current` before any commit. If on main, STOP.

- Cap parallel subagents at 5 concurrent.

- Default to read-only. Do not modify files unless the command explicitly

- Plan files go in `.ctx/tasks/`, not `.ctx/plans/`.

Dialectic proposer — Advocate stance. Argues for the most straightforward, favorable interpretation of a question. Used as a proposer in the dialectic synthesis pipeline.

Dialectic proposer — Alternative stance. Proposes a fundamentally different approach that reframes the question or solves it by other means entirely. Used as a proposer in the dialectic synthesis pipeline.

Dialectic pipeline orchestrator. Frames a question into adversarial roles, dispatches dialectic-advocate, dialectic-skeptic, and dialectic-alternative in parallel, then passes proposals to dialectic-synthesizer. Use when a decision benefits from structured adversarial analysis before committing to an approach.

Dialectic proposer — Skeptic stance. Finds failure modes, edge cases, and reasons to reject or challenge the premise. Used as a proposer in the dialectic synthesis pipeline.

Dialectic synthesizer. Reads all proposer outputs, maps disagreements, and produces a single reconciled answer with rationale, open questions, and rejected positions.

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems in Rust. Use this skill when building agents that call external tools, implementing policy-based access controls, adding semantic intent classification to detect dangerous prompts, creating trust scoring systems for multi-agent workflows, building audit trails, or enforcing rate limits and content filters. Covers policy composition, tool wrappers, trust decay, and JSONL audit trails — all in Rust.

Use when creating a new local skill or fixing an existing skill that was saved to the wrong skills tree. Symptoms - a skill was written under ~/.claude/skills, the active setup uses ~/.agents/skills, or skill instructions still reference the old path convention.

Use when adding new BAML types/functions to cruxx-agentic. Symptoms - need to add structured extraction functions, mirror types to cruxx-types.

Use before any creative work — new features, new components, architecture decisions, adding crates, designing APIs. Triggers on "let's build", "I want to add", "design X", "how should we structure", or any request that would produce new code structure.

Commit and push workflow with pre-flight validation and hook recovery. Use when the user says "cap", "commit and push", or "ship it". Runs cargo nextest, fmt, clippy, stages all changes, writes a conventional commit, handles pre-commit hook failures, and pushes.

46 hooks across 4 events