Skip to content

ericrisco/rsc-harness / skills/harness

harness

Flagged

Use when governing a workspace's control plane, code or not — the `01-TOOLS/` tooling layer, the `02-DOCS/` chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy `XX-*` folders, scaffolds provider tooling, sweeps the inbox, eats a file the person hands over ("cómete este fichero", "guárdalo en la documentación": moved into 02-DOCS/raw/ and documented), writes root CLAUDE.md/AGENTS.md. NOT the bootstrap front door (that is `init`, which hands off here).

references/claude-md-template.md

View on GitHub
# CLAUDE.md — {{PROJECT_NAME}}

> Template generated by `harness` on {{TODAY}}.
> Edit it freely: the skill respects your changes and only adds sections
> that are missing on future runs.

This file is the root instruction source for agents working in this
workspace. If you're working in a subproject that also has its own
`CLAUDE.md`, read this file first and then the subproject's `CLAUDE.md`.

## What this project is

> One or two sentences describing the product and its audience.

## Knowledge map

The **full** index of this project's conventions lives in **`02-DOCS/wiki/index.md`** — maintained by
the stack skills plus the `harness/` topic. Read the relevant article before working in its area, and
update it when conventions change. Keep this section a **short pointer**: CLAUDE.md is read on every
turn, so the full per-area table belongs in `02-DOCS/wiki/index.md`, not here. New index entries go
there, not into this file.

Read first, always:

| Area | Article |
|------|---------|
| User profile (register: technical or analogies) | `02-DOCS/wiki/harness/user-profile.md` |
| SDD constitution (project non-negotiables) | `02-DOCS/wiki/sdd/constitution.md` |
| **Everything else — full index** | `02-DOCS/wiki/index.md` |

## Workspace map

| Path | Role |
|------|------|
{{SUBPROJECT_ROWS}}
| `01-TOOLS/` | Operational arsenal: one folder per external provider, with co-located credentials and a working `test_connection`. |
| `02-DOCS/` | LLM wiki: immutable sources in `raw/`, compiled articles in `wiki/`, plus `wiki/index.md` and `wiki/log.md`. |

The root is not a single Git repo; the Git repos live inside the main
subdirectories. Do not assume that `git status` at the root works.

## Working rules

- Before touching a subproject, run `git -C <subproject> status --short`.
  The user may have in-flight changes; don't revert or merge them without
  understanding them.
- Ignore generated outputs unless the user asks for them: `node_modules/`,
  `.next/`, `.venv/`, `.pytest_cache/`, `.ruff_cache/`, `.mypy_cache/`,
  `.dart_tool/`, `build/`, `__pycache__/`.
- Keep subproject boundaries clean. Don't mix dependencies or stacks
  across repos.
- Never publish secrets. `01-TOOLS/**/.env`, `CREDENTIALS.md`, SSH keys,
  service accounts, and tokens are sensitive even though they live in the
  workspace.
- For UI changes, read the canonical design document for the affected
  surface before editing.
- For documentation, update `02-DOCS/` following the embedded wiki
  protocol: new sources go in `raw/<topic>/`, distilled knowledge in
  `wiki/<topic>/`. The skill maintains `wiki/index.md` and `wiki/log.md`.

## Main commands

{{SUBPROJECT_COMMANDS}}

## Operational tooling

Manual operations against external services live in `01-TOOLS/`. Each
folder has `test_connection.{sh,py}` as a smoke-test.

| Tool | What it's for |
|------|---------------|
{{TOOLS_ROWS}}

To add a new tool: `cp -r 01-TOOLS/_TEMPLATE 01-TOOLS/<NAME>` and follow
the README in `01-TOOLS/`.

## Documentation

- `02-DOCS/raw/` — immutable source material (READMEs, ADRs, notes).
- `02-DOCS/wiki/index.md` — index of compiled articles.
- `02-DOCS/wiki/log.md` — append-only ingest/query log.

When you learn something new and reusable, ingest it with
`harness` (the wiki protocol lives embedded in the skill,
no external skill required).
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall