A disciplined engineering suite for Claude Code — six composable plugins (maestro, prd-builder, architect, taskmanager, scribe, laravel).
Skill Claude CodeCodex
Use whenever a change needs a system-design decision — architecture, system design, data model, module/service boundaries, interface/API contracts, scalability/scale, or an ADR. The canonical discipline for designing systems: architecture is tradeoffs, engineered, never over-engineered. Right-size the present, place…
Skill Claude CodeCodex
The house rules for building Filament v5 panels — schema layout (sections/fieldsets/tabs), clusters for multi-domain pages, navigation grouping, list-page stat widgets, grouped row actions with named delete confirmations, relation managers with create/delete, save-redirects, no create-another, field hints, inline…
Skill Claude CodeCodex
Opinionated CORE Laravel 13 + Pest 5 conventions, applied by default on any Laravel project — artisan-first file creation, Eloquent/migration/queue/ scheduler patterns, fail-closed multi-tenancy, parallel-safe tests, and a "verified before done" bar. Composes with (never duplicates) maestro's stack-agnostic…
Skill Claude CodeCodex
Take a conclusion, code, fix, or design you just produced and spawn an independent agent to adversarially re-check it — assuming it likely missed something, with the job of finding holes rather than affirming. Trigger: you just reached an important conclusion/fix/design and want to confirm before delivering, or you…
Skill Claude CodeCodex
Use at the start of any multi-step task and during exploration — before reading files, searching, or re-checking completed work, especially when tempted to read whole files, re-verify known facts, or run independent lookups one at a time.
Skill Claude CodeCodex
Stay focused on the project with the task in hand; recall another project's knowledge ONLY when the task actually needs it. When a task requires changing a shared dependency you own (a local composer/npm package in another repo), make the change IN that owning repo — commit, push, retag — then update and re-verify the…
Skill Claude CodeCodex
Use when asked for a deep audit, deep analysis, production-readiness review, architecture assessment, or prioritized recommendations across a whole codebase or subsystem — orchestrates parallel reader agents with adversarial verification and publishes findings to docs/deep-analysis/.
Skill Claude CodeCodex
Run a large, multi-place, uncertain task to completion via "plan → adversarial review → serial execute → synthesize & verify." Trigger: cross-file refactor, data migration, large feature build, system audit, deep research — tasks that can't be done in one pass and touch many places. Manual invocation: /deep-work.
Skill Claude CodeCodex
Use before ending any turn that used tools or produced a deliverable — when tempted to ask "Want me to…?", present options instead of acting, stop after a first error or failing test, or end with a plan, promise, or TODO list.
Skill Claude CodeCodex
Use when asked to implement, build, add, fix, refactor, or change anything non-trivial in a codebase — especially vague asks ("do that", "make it work") that need clarification, planning, and verified delivery with tests and commits.
Skill Claude CodeCodex
Use when writing or editing code in an existing codebase — before adding comments, docstrings, try/catch blocks, validation, logging, or TODOs the surrounding file doesn't have, and before explaining your style choices in the reply.
Skill Claude CodeCodex
Use when writing any user-facing reply — answers, status updates, summaries, or final reports — especially after multi-step work, when tempted to show thoroughness, add headers or bullets to a short answer, open by classifying the question, or open with praise.
Skill Claude CodeCodex
Use before claiming anything works, is fixed, is done, or passes; before status updates on changes you haven't run; before agreeing with someone else's claim about your work; and before state-changing commands like restarts, deletes, or config edits.
Skill Claude CodeCodex
The discipline behind maestro:regression — prove a change didn't break existing work by running the suite, an adversarial bounded blast-radius probe against documented architecture contracts, and honest coverage, then emit a verdict taskmanager's done-gate enforces. Trigger: a change is about to be marked done /…
Skill Claude CodeCodex
Turn the work just done into VETTED lessons that survive across sessions and projects — harvest the session's decisions/errors, draft candidate lessons, refute them adversarially, and promote only the survivors into taskmanager memories. The self-improvement loop, gated so a false lesson can never silently change how…
Skill Claude CodeCodex
The suite's risk-sized front door: given a request, name the right top-level PIPELINE (which existing entry points, in what order) by scope and risk — analysis, trivial change, bug fix, feature/high-risk, or codebase health. Advisory; it routes the pipeline only and never sizes verification depth (the brain's job).…
Skill Claude CodeCodex
Use when implementing any change in existing code — when tempted to clean up nearby code, add unrequested validation or options, fix something "arguably in scope", or when the diff is growing past what was asked.
Skill Claude CodeCodex
A durable, disposable home for in-flight thinking that overflows a single context window — layered scratch → (optional) blackboard → (optional) conclusions under thoughts/ /, refuted by the existing adversarial-verify and drained into durable truth (scribe / deep-analysis) when it settles. Trigger: ONLY when one task…
Skill Claude CodeCodex
This skill should be used when conducting PRD interviews, creating product requirements documents, planning new features, documenting bug fixes, or when using commands like "/prd-builder:prd", "/prd-builder:feature", "/prd-builder:bugfix", or "/prd-builder:refine". Provides comprehensive interview frameworks and…
Skill Claude CodeCodex
Use whenever you make or discover a decision, fix a non-trivial error, change architecture or what the system does, or defer something undecided — and before acting on any task. The canonical contract for how docs/ works: docs/ is the single source of truth (read it first, write it after), its truth is typed and…