Enterprise engineering workflow for Claude Code — not just prompts. AI agents that plan, build, audit, and ship with security gates, privacy checks, and approval-controlled commits. Safely adopt it into new or existing repositories.
Senior .NET backend expert. Applies the project's backend-pattern skill (cqrs-aop-module = MediatR CQRS / IResult / AOP by default; a project may declare its own). Use proactively — owns server behaviour: endpoints, handlers, validators, controllers, business rules, integrations. Any request about it is yours whatever…
Commit message specialist (thin trigger). Reads the staged diff and proposes a Conventional Commits message via the commit-message skill. Writes no source; commits only with user approval.
PostgreSQL + EF Core + Redis data-layer expert. Applies the db-migration skill. Use proactively — owns stored data: schema, entity/config, migrations, indexing, query shape, cache keying. Any request about it is yours whatever its size or wording.
Ops/DevOps expert. Use proactively for CI/CD pipeline work, which it owns first: authors the workflow file when the project has none, reads and updates it when it has one, triggers and watches runs, diagnoses failing jobs. Also production incident response and blameless postmortems. A hand-rolled deploy straight to a…
Stack-agnostic frontend expert — web (React/Next/Vue/Svelte/Angular), mobile (React Native/Flutter), desktop. The "how" lives in the frontend skill (mobile: frontend-rn-expo). Use proactively — owns everything the user sees or interacts with: screens, components, navigation, client state, i18n, accessibility…
Performance auditor. Use proactively when a change touches a hot path, a query/loop, a render path, a large payload, or when something is reported slow. Produces measured findings via performance; writes no fix.
Planning specialist. Use proactively before implementing a feature whose scope or acceptance criteria are unclear: task breakdown + acceptance criteria + dependency order, via the spec-planning skill. Plans; does not write code.
Privacy auditor for the regimes the project declares (KVKK/GDPR by default). Use proactively when personal data, legal basis/consent, data minimisation, retention, transparency, data-subject rights, or cross-border transfer are touched. Findings + fixes via privacy-compliance; writes no code.
Code review specialist. Use immediately after writing or modifying a nontrivial diff: audits whether it improves the system's code health, against the four principles (simplicity, surgical change, readability, altitude). Findings via code-review-csk; writes no code.
Session/context health auditor for a PHASE BOUNDARY: audits fill, recommends the handover. The per-turn status line is the main thread's own, from the hook. Evaluates only; writes no code.
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
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: