agentleFS
Sign inStart free
joinwell52-AIjoinwell52-AI/CodeFlowMu-open/skills/ui-information-architecture/SKILL.md

ui-information-architecture

Skill2 starsChanged 4 months agoMITView on GitHub

Organize CodeFlowMu UI screens, navigation, panels, filters, and operational workflows. Use when UI work needs information grouping, scan path, state/empty states, or safe navigation for task/report/lifecycle/log surfaces.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Use before designing or changing a screen structure.

    line 10
  2. Distinctive:

    Start with the primary user goal.

    line 14
  3. Distinctive:

    Put evidence and lifecycle state near dependent actions.

    line 16
  4. Distinctive:

    Keep operational UI dense but readable.

    line 17
  5. Distinctive:

    Do not hide governance actions behind ambiguous UI.

    line 25
  6. Distinctive:

    Do not make marketing-style landing pages for operational tools.

    line 26
  7. Distinctive:

    Do not change Panel code unless implementation is explicitly requested.

    line 27

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

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

UI Information Architecture

When to use

Use before designing or changing a screen structure.

Rules

  • Start with the primary user goal.
  • Group information by decision need.
  • Put evidence and lifecycle state near dependent actions.
  • Keep operational UI dense but readable.

Required output

Use docs/skills/ui-playbook/information-architecture.md.

Forbidden actions

  • Do not hide governance actions behind ambiguous UI.
  • Do not make marketing-style landing pages for operational tools.
  • Do not change Panel code unless implementation is explicitly requested.

Minimal example

Goal: close task
First scan: status, latest report, missing evidence
Action area: approve/reject after evidence

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.

Check your setup, free