From example-skills
Extracts and formalizes individual intents from rough markdown, session exports, or prose into classified prompt atoms (law, value, directive, constraint, question, branch-vector) with YAML frontmatter. Useful for converting loose operator text into registry-grade, machine-readable units.
How this skill is triggered — by the user, by Claude, or both
Slash command
/example-skills:prompt-atom-formalizationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Convert loose operator prose into atoms: minimal, classified, machine-readable units of intent that registries can store, pipelines can route, and future sessions can execute without re-interpreting the original wall of text.
Convert loose operator prose into atoms: minimal, classified, machine-readable units of intent that registries can store, pipelines can route, and future sessions can execute without re-interpreting the original wall of text.
Operator intent arrives packed — one dense paragraph can carry a standing law, two directives, a constraint, and an open question. Left as prose, that intent is executable only by whoever re-reads and re-derives it. Atomized, each unit gets an ID, a class, a lifecycle state, and provenance — it becomes governable. The doctrine: atoms are permanent; extraction is additive; nothing in the source is destroyed by being formalized.
| Class | Nature | Lifetime | Example |
|---|---|---|---|
| law | standing rule; governs all future behavior | permanent until amended | "nothing local-only — every artifact git-tracked AND pushed" |
| value | weighting/preference; shapes choices without mandating one | durable | "prefer user coinages over standard vocabulary" |
| directive | one concrete executable action | until DONE | "register the 5 bench agents in fleet.yaml" |
| constraint | boundary on how any action may be done | scoped or permanent | "never chezmoi add over existing source without diffing" |
| question | open decision owned by a human | until answered | "GCP_SA_KEY provisioning — enable CI deploys?" |
| branch-vector | a fork in possible futures; options held in superposition | until collapsed | "skills live in domus OR a-i--skills — decide before next install" |
Every atom records which state it is in; an extraction pass may legitimately stop at CLEANED.
{file, line-range} or {session-id, message-index}.- id: ATM-NNNNNN # mint from the registry's counter — never invent ranges
class: constraint
state: CLEANED
text: "Never `chezmoi add` over existing source without `chezmoi diff` first."
raw: "…also for god's sake diff before you chezmoi add anything again…"
provenance: {session: 8bb8f846, message: 41}
captured: 2026-06-07
status: OPEN # OPEN | DONE | ANSWERED | COLLAPSED | SUPERSEDED-BY:{id}
links: [ATM-013811] # related atoms; liberal linking
tags: [chezmoi, destructive-ops]
Rules:
raw is mandatory: the verbatim or span-referenced source. Formalization without provenance is paraphrase, not extraction.text field needs "and", split it.For laws/values/constraints that recur across ≥2 independent sources:
state: ELEVATED and route to the appropriate standing surface (constitution tier, reliquary, registry) by pointer — the atom stays in the registry; the surface cites it.SUPERSEDED-BY back-link).npx claudepluginhub a-organvm/a-i--skills --plugin document-skillsProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.