メニュー
Coding conventions and architectural constraints for the Glassbox repository — ESM-only, zero-dependency, no-network, single normalization boundary, strict layering, one-metric-per-file, graceful degradation. Read when writing or reviewing any code in this repo.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
The Glassbox harness operating loop — how to start a session, work one feature at a time, verify before claiming done, and leave a clean handoff. Based on walkinglabs Learn Harness Engineering. Read at the start of any working session and before claiming completion.
Reference for the Claude Code JSONL transcript schema as consumed by Glassbox — the normalized Event model and the (to-be-confirmed) raw field mapping. Read when working on discover.js, read.js, normalize.js, or classify.js. Update the "Confirmed raw schema" section after the Slice 1 discovery spike.
| name | glassbox-conventions |
| description | Coding conventions and architectural constraints for the Glassbox repository — ESM-only, zero-dependency, no-network, single normalization boundary, strict layering, one-metric-per-file, graceful degradation. Read when writing or reviewing any code in this repo. |
package.json has "type": "module". Use import/export, never require.node bin/glassbox.js. No bundler, no TypeScript
compile, no Babel.fs, path, os, readline, node:test, util (parseArgs).
A new dependency requires explicit justification against NFR-03 in the PR.util.parseArgs — no commander/yargs.src/normalize.js understands the raw transcript schema.
Downstream code consumes the normalized Event model (TSD §3.1). Never read event.raw for
behaviour outside debugging.discover → read → normalize → classify → timeline → metrics → render. No
back-references. render/ must not reach into metric internals; metrics are pure functions of
Event[].src/config.js as plain arrays/objects so they can be re-tuned in one edit.src/metrics/, registered in metrics/index.js REGISTRY.stableStringify, successOf, taskSegments) live in src/metrics/helpers.js — import from there, do not duplicate.JSON.parse; count bad lines, don't throw (NFR-05, AC-12).unknown; missing field → null + a warning.
Metrics return status:'unknown' with a note rather than failing (BR-13).http/https/net/dns imports anywhere. Reports are self-contained
(inline CSS/JS, no external URLs).stableStringify (key-sorted) for any hashing (e.g. loop detection).node:test only. Co-locate suites in test/*.test.js; fixtures in test/fixtures/.