Stand up a NEW Bun/TypeScript, Next.js, or Java (Quarkus) repo to the atelier standard from zero — scaffold the Clean Architecture (or Atomic Design) layout, copy the gate assets, wire the git hooks, write the build scripts, lay a minimal green walking skeleton, and prove every gate passes before the first commit. Use when starting a fresh repo or a new monorepo package from scratch — say "scaffold a new Bun repo", "bootstrap a new project to the standard", "set up a new atelier repo / Next.js package", or "scaffold a new Java/Quarkus service". Greenfield only. NEVER use it for work inside an existing codebase (adding features, setting up lint or tooling, config changes) — those belong to the main atelier skill, or to atelier-review-me adopt mode for bringing a brownfield repo up to the standard.
Use when the user wants to stress-test, pressure-test, or poke holes in a plan, design, migration, or architectural decision before building or committing to it, de-risk a big decision, walk through a design's tradeoffs, validate whether a new product or feature is worth building at all (problem evidence, demand test, go/no-go), or says "grill me" or "grill me on this". It then relentlessly interviews you one question at a time, each with a recommended answer, exploring the codebase before asking, until every branch of the decision tree is resolved and you reach shared understanding.
Review a diff against the atelier standard before it lands — a rule-aware conformance audit that maps each changed file to the hard rules that bind it, cites the exact rule number — or the red flag — a change violates, applies the security false-positive filter, and defers generic correctness bugs to /code-review and mechanical cleanups to /simplify. Use to pre-land-review staged changes, a feature branch, or a PR, to check a diff for rule violations, or when the user says "review me" / "review my changes against the standard". Also runs an adopt mode for brownfield — scan a whole existing repo and emit a staged plan to bring it up to the standard, e.g. "adopt the standard into this repo", "migrate this repo to atelier", "bring this repo up to standard".
Senior-engineer coding standard for Bun/TypeScript, Next.js, and Java (Quarkus) repos. Enforces strict TDD (primary-port SUT, hand-written fakes, no mocks), Clean Architecture (`src/{domain,use-cases,infra,presenter,composition}`), `Result<T, E>` at IO boundaries, branded types at trust boundaries, Bun-only or Maven toolchains (no `class`/`function` declaration/`interface`/`console.*` in TS), Atomic Design, a logic-free design system (no Tailwind in app code), and production disciplines covering privacy (no PII in logs/URLs), tenant isolation, IO deadlines, soft-delete, expand-contract migrations, optimistic locking, observability, AI ports with evals, delivery, accessibility. Backed by pre-commit gates, coverage tiers, mutation testing. Use for ANY code task in a Bun, Next.js, or Java repo, covering writing, scaffolding, testing, refactoring, review, React components, APIs, persistence, debugging, security. Consult even when conventions are not mentioned; rules are non-negotiable; violations are rewritten.
Run the full-surface QA health check of the ask-marcel-office CLI by executing docs/QA-PLAYBOOK.md phase by phase — offline gates, bundle smoke tests, manifest-driven parameter matrix, conversion contract matrix, live read-only Graph drift probes, agent-ergonomics journeys, and gap/roadmap analysis. Use when the user asks to audit the CLI, run QA, check CLI health, find bugs/regressions across the command surface, or re-verify after a Microsoft Graph change. Produces a severity-ranked report and a proposed fix plan; never fixes code during the run.