tedeuxx

fixture: one skill on disk, declared three ways

fixture

fixture: one skill on disk, declared once as authored and once in upper case

fixture

fixture: a manifest that declares skills over a tree with no skills/ directory

fixture

fixture: a declared skill that is a symlink out of the plugin tree

fixture

by Luiz Tadeu Mendonça

A Claude Code harness: 8 subagent personas — two leads that disagree by design (product-and-market, tech) and consolidate one demand, a tool-less scrum-master that ranks the eligible pool and names who acts next in a selection record the main session executes, one fullstack developer, a content pair that argues against one shared ruler at most twice (a content-writer that drafts published prose in the owner's voice and a content-reviewer that may block only on a clause it can quote, both contained the same way as product-lead — neither posts to a public surface directly), one gatekeeper (a quality-assurance that holds the merge gate and reviews both technical delivery and whether the change can break production), and an agents-lead that stress-tests proposed changes to the harness itself and, per ADR-0002, may implement the harness changes it reviews (never merging, never gating an MR) — PreToolUse hooks that mechanically deny the irreversible floor (force-push, terraform apply, rm -rf, secret writes), and 15 generic skills for AWS infrastructure, React/Vite frontends and CI/CD (<project>/<apex-domain> placeholders).

by Luiz Tadeu Mendonça

The knowledge layer of a public agent-harness reference: 15 dense, opinionated engineering skills covering AWS infrastructure, React/Vite frontends, BFF-on-Lambda backends, CI/CD, the development loop and its quality gates. Written project-agnostically with <project> / <apex-domain> placeholders. This Power ships skills only — the harness's personas, permission hooks and merge gates are deliberately not exported.