ryanportfolio/Harness-Firmware

Keep project decisions and pitfalls with the code. Carry useful lessons into the next session. Review changes before carrying them into another repository.
Install the skills or start a repository · Visit harnessfirmware.com
quickstart
Use the **skills-only plugin** for an existing Claude Code repository. Use the **full template** for a new repository or Codex support.
existing repository · Claude Code plugin
Run these commands inside Claude Code:
Then try /claude-starter:recall or /claude-starter:brainstorming plan the next feature. Plugin skills use the claude-starter namespace.
new repository · full template
Create a repository with the kernel, hooks, committed memory, skills, and synchronization tools:
- GitHub: select **Use this template**, clone the new repository, then run Claude Code's /init-project command or ask Codex to use the init-project skill.
- From a cloned Harness Firmware checkout on macOS or Linux: bash bootstrap/new-claude-project.sh --name my-app --dest ~/code
- From a cloned checkout on Windows: double-click bootstrap/New-ClaudeProject.cmd.
In the created repository, run node .claude/scripts/doctor.mjs. Success means the doctor reports no failures. Then ask Claude Code or Codex to use recall before the first unfamiliar change.
Open the complete setup guide · View validation runs
what the firmware adds
| Need | Workflow built into the repository |
| --- | --- |
| Remember the project | recall loads relevant committed facts, decisions, and pitfalls before unfamiliar work |
| Finish sustained work | long-horizon records progress and evidence across bounded rounds, with fresh audit context |
| Challenge a result | Independent and cross-vendor review skills check work through available agents or authenticated CLIs |
| Verify a claim | fable-mode separates current-state, change, and causal claims and returns a verdict; perf-loop measures optimization against a baseline |
| Maintain skills | addskill handles creating, importing, updating, and installing skills with the resources each runtime needs |
| Improve the workflow | refine captures observed friction; sync-starter carries selected generic fixes between repositories |
These are agent instructions and supporting tools. Structural checks validate the package; actual execution still needs the appropriate model, tools, credentials, and evidence.
the repository feedback loop
The everyday loop is **recall → work → verify → refine → reviewed repository change → next task**. Project facts load before unfamiliar work. Verification captures evidence. refine turns observed friction into a small, reviewable change that strengthens the repository before the next task begins.
The dotted branch is separate: after human review, sync-starter can move a generic improvement into the template so future repositories begin with it. Keeping the lesson local remains the default.
two runtimes, explicit ownership
**43 Claude Code skills · 40 Codex skills · 40 native Codex workflows**
- **Claude Code:** reads CLAUDE.md, .claude/skills/, and hooks for canonical playbooks and Claude-specific startup behavior.
- **Codex:** reads AGENTS.md and .agents/skills/ for standalone Codex workflows with explicit capability and safety boundaries; every Claude skill has a maintained native Codex version or is disabled for Codex. Skill ownership and personal copies explains how they are maintained.
Both runtimes read the committed project topics under .claude/reference/. Shared workflows live under .claude/skills/; standalone Codex workflows live under .agents/skills/.
43 workflows, loaded when called
**8 core · 15 discipline · 20 specialist**
Only names and routing descriptions sit in the repository's generated skill index. Full workflow bodies stay on demand. The diagram's byte figures are a repository source-file estimate, not total runtime context; the guide documents the measurement.
Click to open the generated skill memory map
Click to browse all 43 skills