Menu
Use when a system is carrying meaning beyond utility. Owns meaning-layer interpretation only.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | system-building-as-meaning-making |
| description | Use when a system is carrying meaning beyond utility. Owns meaning-layer interpretation only. |
| category | domain |
| source_group | hermes-existential |
| compatibility | opencode |
Load this when the user's system-building is not merely instrumental but is carrying meaning: a way of making vocation, memory, responsibility, identity, or continuity concrete.
The skill owns the meaning-layer interpretation. It names why the system matters beyond efficiency without turning that meaning into extra process.
Do not use this for implementation planning, technical diagnosis, operator fit, structural simplification, tone calibration, or action-forcing. If the system only needs to work, do the work without interpreting it.
Return the meaning read: the system, the meaning it carries, the evidence for that read, and the design implication if one follows.
Use when the direct message or commitment handoff needs the right register. Owns tone and candor only.
Use when agency, obligation, and fear are tangled. Owns ownership sorting only.
Use to extend a live idea with one useful angle. Owns additive thinking only, not mode selection or action forcing.
Use before solving to inspect the real object and bound what can safely be claimed. Owns pre-solution contact only, not diagnosis or verification.
Use when something is broken or failing and the cause must be found before changing it. Owns failure diagnosis only.
Use when a canned frame would obscure the real object. Owns rejection of default scripts only.
