Monorepo for Aesthetic.Computer
aesthetic.computer
score: add "Adding a Piece" section — template, meta() visibility, curation
Documents the repo-level piece workflow that was implicit: npm run new,
header comment convention the docs auto-scan reads, meta() export as the
opt-in signal for list/autocomplete, and the docs.js pieces map as the
curation override. Points out to WRITE-A-PIECE.md (user flow) and
CLAUDE.md (API surface) for depth.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
+30
+30
SCORE.md
+30
SCORE.md
···
112
112
# Or filter: npm run test:kidlisp -- --filter=<spec-name>
113
113
```
114
114
115
+
### Adding a Piece
116
+
117
+
Every piece is a single `.mjs` (JS) or `.lisp` (KidLisp) file in
118
+
[`system/public/aesthetic.computer/disks/`](system/public/aesthetic.computer/disks/).
119
+
Scaffold from the template:
120
+
121
+
```bash
122
+
npm run new <slug> "one-line description"
123
+
```
124
+
125
+
**Header convention** — the docs auto-scan reads lines 1–2:
126
+
127
+
```js
128
+
// Name, YY.MM.DD.HH.MM
129
+
// One-line description shown in `list` and prompt autocomplete.
130
+
```
131
+
132
+
**Lifecycle exports** (all optional except whichever ones you need):
133
+
`boot`, `paint`, `sim`, `act`, `leave`. Export `meta()` to opt the piece **into**
134
+
`list` and prompt autocomplete — omit it and the piece stays reachable at
135
+
`/<slug>` but hidden from indexes (good for drafts).
136
+
137
+
**Curating the entry** (richer `desc`, `colon` params/`examples`, force
138
+
`hidden: true`, or override an auto-entry): edit the `pieces` map in
139
+
[`system/netlify/functions/docs.js`](system/netlify/functions/docs.js). Curated
140
+
entries always win over the auto-scan.
141
+
142
+
See [`WRITE-A-PIECE.md`](WRITE-A-PIECE.md) for the end-user `source` / `publish`
143
+
flow and [`CLAUDE.md`](CLAUDE.md) for the full piece API surface.
144
+
115
145
### Development Environment
116
146
117
147
**Terminal Workflow (IMPORTANT):**