agentleFS
45ck45ck/hci-review-skill/.agents/skills/conceptual-model/SKILL.md

conceptual-model

Skill19 starsChanged 6 days agoMITView on GitHub

Build a conceptual model for a prototype or feature: actors, objects, actions, states, rules, and transitions.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a conceptual model for this scope:

    line 7
  2. Distinctive:

    Use ultrathink. Work from the repo, prototype, docs, screenshots, routes, components, and visible states.

    line 11
  3. Very specific:

    Write docs/hci/conceptual-model.md unless the user asked for another path.

    line 14
  4. Distinctive:

    Create the directory if it does not exist.

    line 15

≈ “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

Create a conceptual model for this scope:

$ARGUMENTS

Use ultrathink. Work from the repo, prototype, docs, screenshots, routes, components, and visible states. If details are missing, infer cautiously and mark assumptions.

Output

Write docs/hci/conceptual-model.md unless the user asked for another path. Create the directory if it does not exist.

Required sections

  1. Purpose of the system or feature
  2. Primary actors
  3. Primary objects/entities
  4. Actions available on each object
  5. States and transitions
  6. Rules, constraints, permissions, and guardrails
  7. Ambiguities or overloaded concepts
  8. Recommendations to simplify the model

Tables to include

Actors

| Actor | Goal | Main tasks | Notes |

Objects

| Object | Definition | Key attributes | Related objects |

Actions

| Action | Target object | Preconditions | Result |

States

| Object | State | Meaning | Entered by | Exited by |

Note: keep this state table high-level (name and one-line meaning only). Full lifecycle definition belongs in the state-model artifact. If a state-model artifact already exists, reference it rather than repeating it.

Diagrams

Add Mermaid diagrams:

  • state diagrams for major objects
  • entity relationship diagrams for object relationships

Evaluation lens

A strong conceptual model should make these obvious:

  • what exists in the system
  • what users can do
  • what state something is in
  • what will happen next

Flag anything that breaks these expectations.

Deliverable style

  • Clear headings
  • Markdown tables
  • Mermaid diagrams where useful
  • Direct language
  • No filler

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.