Neutral source of coding standards, agent roles, skills, and workflows, rendered to native config for Claude Code, Codex, and Amp. Successor to agent-workflows.
Design rigorous evaluations and benchmarks for AI agents, developer tools, retrieval systems, and repository-scale automation. Covers task selection, contamination control, metric choice tied to engineering decisions, and statistical validity. Use when asked to design an eval/benchmark, critique an existing benchmark…
Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.
Binary search for root cause: define a search space and a pass/fail oracle, then halve the space each step until the culprit commit, config key, or dependency is isolated. Works across git history, configuration, dependencies, or code modules.
Structured brainstorming with research-driven exclusion zones and shape-uniqueness enforcement. Forces divergent thinking through volume and a hard constraint: no idea may take the same shape as any prior art or any earlier idea. Use when exploring solutions to a problem, designing features, or when the obvious…
Ultra-compressed communication mode. Cuts token usage 75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or…
Comprehensive security and quality review of uncommitted changes. Scans the diff for injection, hardcoded secrets, auth gaps, and correctness issues, reported by severity.
Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.
Index of this project's coding-practice rules — architecture, coding style, testing, security, git workflow, task management, context layering, anti-slop, performance, and language-specific rules. The thin always-on essentials live in .claude/rules/common/house-rules.md; the full per-topic detail ships under…
Structured debate and refinement. Independent advocates argue competing positions and trade-offs over divergent findings, then converge on a refined synthesis. Pairs with diverge.
Essence extraction via progressive compression. Chained compressors each halve the previous output while keeping what matters; what each layer drops reveals the priority hierarchy.
Multi-perspective divergent research. N independent agents with uncorrelated context explore a question from different angles, then synthesize into one analysis and PRD.
Thin methodology for end-to-end tests of critical user journeys — define journeys by risk, use semantic locators and condition-based waits, quarantine flaky tests with a tracked reason, and capture artifacts on failure. Use when adding or stabilizing E2E coverage; the e2e-runner agent applies it in depth.
Record a "don't do X here, it breaks Y" lesson into AGENTS.md so an agent doesn't repeat a mistake. Dedupes against CLAUDE.md/instincts before writing, promotes generalizing lessons out of memory, and keeps AGENTS.md under budget. Use after a bug, regression, or near-miss, or when the user says "capture this" / "make…
Single-task execution loop (plan, execute, verify, hand off). Keeps one agent on one unit of work with a structured context handoff so progress survives across sessions.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree one at a time. Use for ambiguous or complex collaborative specs before any code is written.
Prospective failure narratives. Independent agents each write a story from a future where the project failed for a different root cause, synthesized into a risk registry with severity ratings and mitigations.
Map the tribal knowledge of a codebase into per-area COMPASS.md files — the why, the gotchas, and how each area connects — for existing repos and as they grow. Use when the user says "map this codebase", "generate compass files", "refresh the compass", or after a significant area changes.
Decision framework for choosing between regex and LLM when parsing structured text — start with regex, add LLM only for low-confidence edge cases. Use when parsing quizzes, forms, invoices, or documents with repeating structure and cost matters.
Review a repository for long-term architectural leverage rather than code quality — system structure, module boundaries, dependency graph, coupling, and drift. Produces a ranked set of highest-ROI improvements with evidence, effort, and risk. Use when asked to review the architecture, assess a codebase's…
Multi-model code review of uncommitted changes. Spawns parallel reviewers across providers (Anthropic reuse/quality/efficiency + Codex grounded review) so blind spots in one model are caught by another. Use after writing or modifying code, before opening a PR, or when /simplify alone feels insufficient. Codex…
Build-order planning via competing sequencing strategies. Independent agents each propose a different build order for a chosen design, synthesized into a recommended plan with milestones, dependencies, and risks.
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
Reduce a diff to its essential complexity, removing dead paths, over-engineering, premature abstraction, and incidental churn, without changing behavior.