new-artefact git:20261019.2b9222eB

Immutable. This exact content never changes and is served at /api/v1/blob/88fc99106ed2521c.

---
description: Add a new kind of artefact to the forge — its position in the forge intent, its definition and template, its prefixes, its reviewers
argument-hint: "<name>"
disable-model-invocation: true
---

The definition of how a new kind of artefact is found, in the seven
blocks of POS.1310 of the forge intent; what it is to achieve and why
is POS.1430. Shared mechanism is cited and never repeated here: the
form of the conversation and one write per round (CLAUDE.md, Working
methods and prime directive 9), versioning with history
(CLAUDE.md, Versioning & status), the shape of a definition and of
its Map (POS.1310, POS.1320).

**Target.** The kind of artefact `$0`: the pair
`.claude/skills/forge/states/$0.md`, from the skeleton
`templates/artefact-definition.md`, and `templates/$0.md`, which has
no skeleton, each template differing whole; and what stands around
the pair in the forge's own project, `projects/forge`: a position of
the intent and an item of the solution design.

**Inputs.** The forge intent with its threads and its solution
design; the definitions in `.claude/skills/forge/states/` and their
templates; CLAUDE.md, ID scheme and Isolated reviewers; a brief of
the forge project where the principal has written one for the kind;
research and sources as he directs.

**Aim.** The forge has a kind of artefact a project can take through
`/forge $0`: wanted and reasoned in the intent, defined in the seven
blocks with a template as its pair, its items named by prefixes, its
reviewers decided, its realisation named in the solution design. It
is complete when every area of the Map has been found or knowingly
left. Whether the definition holds is told by the first artefact of
the kind on real work, which is `/forge $0`'s and not this
command's.

**Partner.** How the kind is composed is the principal's choice
(CLAUDE.md, Working methods, Handing over). Claude proposes and
decides nothing; every file is born on the principal's word
(CLAUDE.md, Working methods, Step by step). He says where the new
kind meets an existing one, the layer above it and the layer below,
and raises an overlap as a question. He copies no definition: a new
kind is written from what was found, the definitions on disk being
models of the shape and never of the content.

**Map.** What is found, whatever the order; an area may stay empty
when it was considered and found not to apply.
- what the artefact is and why it is wanted: for whom, what it holds
  that no other artefact holds, when a project takes it and when it
  does not;
- where it stands: what it is derived from, what stands above it,
  its number in the chain;
- the boundary: what of the layer above it cites or carries, what it
  must not hold, and what a layer below takes from it;
- how it is found: the seven blocks of its definition, its Map above
  all;
- what comes out: its template, the sections and the shape of an
  item;
- its items: the prefixes, existing or new, and where each lives;
- its wording: any rule of style of its own;
- its reviewers: whether it needs a challenger of its own and what
  that one hunts, what the critic must know is no defect in it,
  whether a check must know it;
- how it reaches a reader: whether a render or the README must show
  it;
- where it is realised: the item of the solution design.

**Instruments.** `/forge intent forge`: the position is written
through the intent's own definition, before anything is built
(CLAUDE.md, Working methods, Intent-first). `/research <topic>`:
proposed where the kind has a practice outside the forge, run on the
principal's word. `/forge solution-design forge`: the item of the
design. A persona from `templates/challenger-definition.md`, by the
principal's decision and only where what it finds genuinely differs
(CLAUDE.md, Isolated reviewers). `/check engine`: offered once the
kind stands, never run on Claude's own judgement.

**Course.** Stop where `.claude/skills/forge/states/$0.md` exists: a
kind that exists is changed through the intent, not added. The ways
in: a brief of the forge project holds the kind, and it is mined; a
few sentences of what the principal wants, and the kind is handed
over; neither, and the Map is walked by interview. The order of what
is born: the position in the intent; the definition, then its
template; the row of a new prefix in CLAUDE.md, ID scheme; the
reviewers, a persona file and the calibration of the critic's
contract where decided; the item of the solution design. End by
naming what was born and what stays open, offer `/check engine`,
and propose the first `/forge $0` on a project. The rosters need
nothing: `/forge`, `/man` and the README read the definitions from
disk.