Dev skills blueprint · sheet 01
Quox dev skills, as a system.
Sixty-eight skills, drawn as what they actually are: a small set of disciplines that execute, wrapped in a large set of operating manuals. Every rule marked in copper was paid for by a real incident.
Plate 1 · The system
Skills fall into five families. Only the first family runs during work and changes what gets done; the rest are loaded on demand to teach a surface or drive a terminal.
Operating manuals, loaded on demand
- quoxpert family (14) · core, cli, flow, mcp, bastion, qluster, plan, protocols…
- quox-user family (5) · drive the product as a user
Terminals and daemons
- terminal9 · build queue
- watch · monitor · nucleus-watch
- telegram-owner · gripe
Content and craft
- writing · glass-design-system
- higgsfield · nano-banana · blog-hero
- screenrecord · screenshot-walkthrough
Plate 2 · /proof-loop
The sibling of /fix-loop. Where fix-loop takes a bug to a passing test, proof-loop takes a claim to shipped evidence. Seven stages, and the last two are the ones that get skipped, which is exactly why it is a loop.
Plate 3 · How a lesson travels
The rule added on 2026-08-06. A lesson written only to memory is passive recall. A lesson written into a skill executes, every time that skill runs.
or a correction
should have
caught it?
at the step where it fires
a skill needs the section,
or a skill needs creating
and the cross-links
Plate 4 · What the inventory exposed
Drawing the system found faults in it, which is the same yield the loop claims for products.
| Finding | Detail | State |
|---|---|---|
| Six skills were undiscoverable | deploy, docker-rebuild, quoxify, quoxplan, remind and yolo-fix had no frontmatter at all, so nothing could select them by intent. They existed and could not be found. All six now have a name and a description.Correction: this sheet first said TEN. The four higgsfield-* skills were fine; they use block-scalar descriptions my inventory script could not read. The measurement was wrong, not the skills. Filed as its own lesson. | fixed 08-06 |
| Three skills were not loadable at all | release-check and cc3d-dev were bare files at the skills root; cli-audit had no frontmatter. All three were cited in CLAUDE.md as if usable. | fixed 08-06 |
| The disciplines had absorbed nothing | The five skills that autonomous work actually runs were last meaningfully updated in February and March, while ten fresh lessons went to memory instead. | fixed 08-06 |
| Overlap worth resolving | Eight image and design skills, three roadmap surfaces, seven terminal daemons. Not urgent, but it dilutes the set that matters. | noted |
The product thought. This is maintained the way the dashboard's glass-design-system is maintained: one page, one source of truth, amended when reality changes. If the dev-skills blueprint becomes a product surface, this sheet is its first plate, and the DEVSUITE stream is where it belongs.