ontology_spec
Skill5 starsChanged 39 days agoNo licenceView on GitHub
Write and maintain an ontology-based design-doc set (ONTOLOGY.md + CRITERIA.md + RATIONALE.md + ARCHITECTURE_LOG.md, plus DYNAMICS.md for games) instead of a single SPEC.md. ONTOLOGY is the implementation reference — purpose, entities as structs, invariants, rules as short pseudocode, commands and events, numbers — with provenance tags ([D]/[P]/[T]) and Serves tags; CRITERIA turns every rule into input → expect rows, each owning a test directory; RATIONALE records the why of current decisions with alternatives and evidence; ARCHITECTURE_LOG holds the dated history. Use when starting a new app, game, or major system, when converting an existing SPEC.md into this format, when the user says "ontology", "/ontology_spec", or asks for design docs where the *why* matters. Also use for a teleology review (does each thing still do what it's for?).
In this repository14 other files it gives its agents.
- codingSkill
- game-designSkill
- horizonSkill
- implementSkill
- java-spring-boot-coldstartSkill
- java-spring-bootSkill
- java-vibeSkill
- reverse_socratic_examinationSkill
- self-ownSkill
- skill-creatorSkill
- socraticSkill
- specificationSkill
- voomSkill
- yuwakisa_game_factorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 9 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.