The Dark Factory method — autonomous, governed, evidence-gated delivery.
Skill Claude CodeCodex
Run the Dark Factory QA stage — execute the validation rules as tests, capture unforgeable evidence per scenario (by correlationId), run the holdout, and return a Works? verdict. QA is the OBSERVER: a self-report is not an assessment. Use when testing a deployed system, mapping PO scenarios to test cases, verifying…
Skill Claude CodeCodex
Dark Factory Solution Architect stage: turn PO semantics into a Data Model, Data Flow (transform graph, pure|effect, idempotency, compensation) and Service Map, assigning each validation rule an enforcement locus. Triggers on "architecture", "data model", "data flow", "service map", "schema", "Avro contract"…
Skill Claude CodeCodex
Dark Factory Developer stage: build a service test-first (RED-GREEN-REFACTOR) where the test list is the PO validation rules and scenarios, not invented. Go and Python examples. Triggers on "TDD", "write tests", "test-first", "implement the service", "RED GREEN REFACTOR".
Skill Claude CodeCodex
Evaluate how easy it is for new engineers to work in a codebase. Use when assessing code quality, onboarding friction, or technical debt. Triggers on "code quality", "maintainability", "developer experience", "DX review", "onboarding", "cognitive load", "code smell", "refactoring", "tech debt".
Skill Claude CodeCodex
Audit frontend code for security, UX regressions, performance, and accessibility issues. Use when reviewing React, Next.js, Vue, Svelte, or any frontend code changes. Triggers on "audit frontend", "review UI", "check accessibility", "a11y audit", "frontend security", "UX review", "performance audit", "review…
Skill Claude CodeCodex
Design and architect microservices following Chris Richardson's Microservices Patterns. Use when designing services, APIs, data flows, or evaluating architecture decisions. Guides full workflow from feature intake to production-ready design with observability, async patterns, security, testing, and deployment…
Skill Claude CodeCodex
Verify whether a service, feature, or contract is safe to deploy to production. Use when preparing for deployment, reviewing release candidates, or validating production configs. Triggers on "production ready", "deploy review", "release check", "pre-deploy", "go-live checklist", "launch readiness", "deployment…
Skill Claude CodeCodex
Generate comprehensive repository documentation following team standards. Use when creating README, CLAUDE.md, ARCHITECTURE.md, DESIGNDECISIONS.md, or any project documentation. Includes Mermaid diagrams, status indicators, and AI context files.
Skill Claude CodeCodex
Interactive requirements gathering that produces machine-executable specs for microservices. Guides conversation through structured rounds to produce a complete requirements doc where every section maps to a code artifact (SQL, Zod schemas, handlers, tests). Triggers on "new feature", "new service", "requirements", "I…
Skill Claude Code
Security auditor for smart contracts - identifies vulnerabilities, logic flaws, reentrancy, access control issues, MEV/economic attacks, and oracle manipulation. Use when auditing Solidity, Vyper, or Rust/Anchor contracts, reviewing PRs for security issues, checking for exploits, or analyzing DeFi protocols. Triggers…
Skill Claude Code
Smart contract developer copilot for Solidity/EVM. Use when designing, implementing, refactoring, testing, or optimizing smart contracts; when adding features; when integrating with protocols; or when debugging failing tests.
Skill Claude CodeCodex
Identify attackers, assets, trust boundaries, and realistic attack paths. Use when analyzing security posture, reviewing new features for threats, or creating threat models. Triggers on "threat model", "attack surface", "security analysis", "trust boundaries", "attacker goals", "threat assessment", "security review"…
Skill Claude CodeCodex
Analyze a codebase to produce a complete service map — microservices, inter-service communication, database ownership, external integrations, and event flows. Generates AI-agent-friendly markdown. Use when onboarding to a new codebase, auditing architecture, updating CLAUDE.md, or before planning new features.…
Skill Claude CodeCodex
Assess whether tests actually protect the system from regressions. Use when reviewing test coverage, evaluating test quality, or identifying missing tests. Triggers on "test review", "test quality", "coverage gaps", "missing tests", "test assessment", "regression protection", "flaky tests", "test audit".
Skill Claude CodeCodex
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
Skill Claude CodeCodex
Run the autonomous, evidence-gated, Promise-Theory-verified control loop (the Vinculum governed loop + Dark Factory process) on any dev project. Use when the user wants to hand over a mission objective with full autonomy under a 2-trigger notify contract (done | blocked-on-all-fronts), evidence-gated decisions…
Skill Claude CodeCodex
Chart and work a Mission Map — a tracker-hosted index of decisions and tickets that carries a multi-session build across context resets. Use to start a long mission, claim the next ticket, record a decision, or resume after a handoff. Triggers on "chart the map", "mission map", "next ticket", "resume the mission"…
Skill Claude CodeCodex
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Skill Claude CodeCodex
Default operating stance — act autonomously inside reversible, non-production surfaces, and HARD-STOP for explicit permission before any irreversible real-world action. Resolve ambiguity through the toolchain (durable memory → working notepad → internet → codebase → team docs) before spending the operator's attention.…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: