agentleFS
ontology-of-everythingontology-of-everything/concept-skills/skills/en/concept-model/SKILL.md

concept-model

Skill14 starsChanged 22 days agoApache-2.0View on GitHub

Use when the user requests concept modeling, or when design and maintenance reveal unclear responsibilities, confused concept boundaries, or coupled cross-concept collaboration. Clarify concepts and synchronization rules; do not activate by default for routine implementation or local fixes.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the structural pattern proposed by Daniel Jackson and Eagon Meng: build applications from concepts and synchronizations.

    line 12
  2. Distinctive:

    Use a representative behavioral history to explain how the purpose is fulfilled.

    line 19
  3. Distinctive:

    Keep references to external objects polymorphic, without depending on their concrete types or internal structure.

    line 25
  4. Distinctive:

    Verify concept contracts and composition purposes separately.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Concept modeling principles

Follow the structural pattern proposed by Daniel Jackson and Eagon Meng: build applications from concepts and synchronizations. Concepts are fully independent services; synchronizations are event-based rules that mediate between them.

Purpose

  • One concept, one clear user-facing purpose.
  • Fulfill the purpose with complete behavior.
  • Use a representative behavioral history to explain how the purpose is fulfilled; define behavior through state and action specifications.

Independence

  • Each concept manages its own state; mutable state is not shared.
  • Concepts are independently understandable; they neither invoke other concepts’ actions nor query their state.
  • Keep references to external objects polymorphic, without depending on their concrete types or internal structure.

Composition

  • Concepts define behavior; synchronizations define collaboration.
  • Synchronizations match action completions, query the required state, and invoke subsequent actions.
  • Application-specific cross-concept rules belong in synchronizations, which depend only on concept specifications.
  • Composed behavior must still conform to each concept’s specification.

Engineering additions

The following implementation and maintenance conventions belong to this skill; they are not presented as the authors’ original wording or distinctive principles.

Implementation

  • Actions uphold preconditions, outcomes, and invariants.
  • Make the observable outcomes of failure, retries, and concurrency explicit.
  • Verify concept contracts and composition purposes separately.

Maintenance

  • Determine responsibility before adding structure.
  • Preserve behavior when refactoring; make intentional changes explicit.
  • Limit changes to what is needed; retain clear code.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.