Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By Camilool8
Four non-negotiable safety hooks (command-guard, secret-scan, verify-gate, audit-log) plus cross-cutting engineering modules as auto-loading skills. Every Harness domain pack depends on this.
npx claudepluginhub camilool8/harness-engineering-templates --plugin harness-basePipeline stage 2 gate. Read-only. Reviews the spec for architectural soundness before any code is written. Different model family than the implementer.
Executes ONE bounded task from the planner's plan in an isolated context (supervisor-worker topology). Has Edit/Write/Bash. Returns a typed diff summary. Invoke once per task.
Pipeline stage 3. Implements an approved spec. Has Edit/Write/Bash. Returns a typed diff for the tester stage.
Decomposes a goal into an ordered, typed plan of bounded tasks with acceptance criteria. Read-only — never edits code. Invoke once at the start of supervisor-worker work.
Stage-two review. Read-only. Assesses code quality, maintainability and risk. Uses a DIFFERENT model family than the implementer to avoid sycophancy. Runs only after spec-reviewer passes.
Store and query provenance-aware, time-bounded facts in the Zep knowledge-graph MCP. Use when working with facts that have a source, change over time, or need multi-hop reasoning across related entities.
Write, index and prune durable knowledge as markdown notes in .claude/memory/. Use when you learn a fact, make a decision, resolve an incident, or discover a recurring procedure that a future session would need.
Store and retrieve durable facts from the Mem0 vector-memory MCP. Use at session start to recall task-relevant memories, and whenever you learn a durable user- or domain-fact worth keeping.
Writes Gherkin .feature files from a user story so non-technical stakeholders can sign off on behavior. Use before implementing any user-visible behavior change.
Builds and iterates evals for LLM/ML output. Use whenever changing a prompt, model, retrieval config, or tool surface, or when an output's correctness is judgmental rather than deterministic. Arm the Stop gate with eval = true in .claude/HARNESS.toml.
Matches all tools
Hooks run on every tool call, not just specific ones
Executes bash commands
Hook triggers when Bash tool is used
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.
Memory compression system for Claude Code - persist context across sessions
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
AI image generation Creative Director powered by Google Gemini Nano Banana models. Claude interprets intent, selects domain expertise, constructs optimized prompts, and orchestrates Gemini for best results.
Curated DevOps engineering pack with four sub-domains — cicd-platform, infrastructure, kubernetes-platform, and observability-sre — wiring domain skills, read-only architect/auditor agents, propose-never-apply IaC and Kubernetes safety hooks, and a Sigstore supply-chain posture.
Curated data engineering pack with four sub-domains — analytics-engineering, data-analyst-notebook, llm-app, and ml-pipeline — wiring domain skills, read-only architect/auditor agents, warehouse read-only and sample-then-scale guards, provenance audit logging, and eval-separation discipline.
Curated mobile engineering pack with four sub-domains — flutter-app, native-android, native-ios, and react-native-expo — wiring domain skills, read-only compliance/UX-critic agents, a simulator/emulator-in-the-loop verification skill, store-compliance gates, and an OAuth-first credential posture.
Curated web engineering pack with five sub-domains — api-service, design-system, distributed-backend, frontend-app, and fullstack-app — wiring domain skills, read-only architect/auditor agents, accessibility-first verification, and Core Web Vitals gates.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
A library of opinionated Claude Code harness templates for software engineering across four curated domains — web, data, DevOps, and mobile.
The premise (per Birgitta Böckeler, Anthropic engineering, METR, and the practitioner consensus of 2025–2026):
Agent = Model + Harness. Templates that lean on the model's good judgement fail their first incident. The harness — not the agent — is the contract.
The full reasoning lives in docs/explanation/why-harness.md.
Install from inside Claude Code — add the marketplace, then install the pack for your domain:
/plugin marketplace add Camilool8/harness-engineering-templates
/plugin install harness-web@harness-engineering # or harness-data / harness-devops / harness-mobile
/harness-web:init # pick a sub-domain
Installing any domain pack pulls in harness-base automatically (the four non-negotiable safety hooks). Full walk-through: docs/tutorials/getting-started.md. Plugin catalog and the HARNESS.toml opt-in flags: docs/reference/plugins.md.
Prefer committed
.claude/artifacts in your repo (audit-heavy or regulated teams)? The bash assembler is still supported as an eject path — seedocs/reference/eject.md.
Five installable plugins — a shared harness-base plus four curated domain packs (harness-web, harness-data, harness-devops, harness-mobile):
.claude/HARNESS.toml; memory, progress-tracking, methodology, and orchestration guidance ship as auto-loading skills.permissions block; see docs/reference/recommended-permissions.md for an opt-in starting point.Every default is the 2026 practitioner consensus.
| You want to… | Read |
|---|---|
| Install a pack for the first time | docs/tutorials/getting-started.md |
Browse the plugin catalog + HARNESS.toml flags | docs/reference/plugins.md |
| Pick a domain pack and sub-domain | docs/how-to/pick-a-recipe.md |
| Use the bash assembler (eject path) | docs/reference/eject.md |
| Understand the design | docs/explanation/why-harness.md |
| Contribute a module, addon, or sub-domain | docs/how-to/ and CONTRIBUTING.md |
The full documentation index, organised by Diátaxis quadrant: docs/README.md.
Three deep-reference essays (the why behind the design):
docs/HARNESS_ENGINEERING.md — foundations, the Claude Code primitive reference, per-domain templates, cross-cutting concerns, universal anti-patterns.docs/METHODOLOGIES.md — SDD, TDD, BDD, ATDD, DDD, Agile, Waterfall, Lean, DevOps/SRE, Eval-Driven Development — each adapted to AI harnesses.docs/AGENT_ROLES.md — single-agent baseline, multi-agent topologies, the canonical role catalog, sub-agent design principles.docs/ user-facing documentation (start here)
tutorials/ learning-oriented walk-throughs
how-to/ problem-oriented recipes
reference/ schemas, CLI, catalogs, glossary
explanation/ understanding-oriented design notes
HARNESS_ENGINEERING.md deep reference
METHODOLOGIES.md deep reference
AGENT_ROLES.md deep reference