tacomancy/skills

guidance-tiers

Establish frozen and living documentation tiers in a repository — a never-edited reference directory, living docs (a vocabulary file, an architecture document, ADRs), a precedence rule in the guidance file, and a check script run in CI that fails when the r…

View source
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Guidance tiers

Two tiers. The frozen tier is the design document the project started from, kept byte-for-byte in a reference directory with an index README. The living docs are the project's current understanding: a vocabulary file, an architecture document, and ADRs. Precedence: living wins where it speaks, frozen is the fallback, and every divergence traces to an ADR. A check script, run in CI, is what makes these rules rules.

1. Inspect

Before asking anything, read what the repository already has. Look for each piece the scaffold writes: a reference directory with contents, CLAUDE.md or AGENTS.md, a vocabulary file, an architecture document, an ADR directory, a check script, a CI workflow. The header of `scaffold.sh` names the default location of each; a piece counts as present at any location. Done when each piece is marked present or absent.

2. Ask only what the inspection left open

At most three questions, in one message, each skipped when the repository already answers it:

  1. The frozen artefact — what it is and where it lives now: a path inside the repository, a path outside it, or "not yet in the repo". Skip when the reference directory already has contents.
  2. The guidance fileCLAUDE.md or AGENTS.md. Skip when exactly one of them exists.
  3. The architecture document's name — only if none exists; offer the default.

Everything else takes the scaffold's default; change one only when the owner says so. Done when every open question has an answer.

3. Scaffold

Run `scaffold.sh` from inside the repository with the answers as flags; its header lists them. It writes each piece only where absent and prints one line per piece saying what it did. Done when the script exits 0.

4. Prove the check

Run the installed check against the base branch, for example bash scripts/check-guidance.sh origin/main. Done when it prints guidance check passed. A FAIL: line here means the repository already broke a rule before the tiers existed — say which and stop; the owner decides.

5. Report

Close with three short lists: what was created; what was found and left alone, a differing check script with the scaffold's summary of the difference; what the owner still has to do. The third always includes making the CI job a required status check, a repository setting no agent can change, and, for a CI other than GitHub Actions, the one command the scaffold printed to wire in. Done when every created: and found: line is in one of the first two lists.

Origin: Vitrine's CLAUDE.md § Reference material and § Rules, docs/reference/README.md, and Scripts/check-guidance.sh.

from this repository

More skills

All skills
tacomancy
Community

adr-shape

Write and review architecture decision records in one shape — a lead paragraph naming what the ADR closes, numbered decisions with their reasoning inline, a verdict on every considered option, consequences that separate better from worse and list what was deliberately left open, a status that is a condition when it needs to be, and corrections as dated updates. Ships the template and a lint for the mechanical parts. Use when an ADR is to be written from a resolved discussion or an existing one reviewed against the shape.

installs
1
GitHub stars
0
Updated
Sep 20
tacomancy
Community

hidden-verify

Run, screenshot, or verify a change in a desktop application without a window ever appearing — the project skill for launching the application, which run looks for first. An environment contract the shell reads at start makes a run render the window unseen, capture a PNG after a delay, quit, and keep every piece of non-project state in a scratch directory. Use when asked to run the application or confirm a change works in it, when a change needs proof for a PR, or when the application lacks the hook and is about to be verified beside a person.

installs
1
GitHub stars
0
Updated
Sep 20
tacomancy
Community

land-ticket

Merge a ticket's green PR, close the ticket, open the public-site issue when the change moved the page, and report the new frontier.

installs
1
GitHub stars
0
Updated
Sep 20
tacomancy
Community

pin-prototypes

Draft and run the prompt set that takes a project's brief through an HTML-exporting design tool the human drives. Use when a project has a brief and is about to prompt a design tool for its surfaces, when a design session has degraded and needs splitting, or when a surface is about to be implemented from a pinned prototype — or has none.

installs
1
GitHub stars
0
Updated
Sep 20