agentleFS
uxkinuxkin/agent/examples/AGENTS.md

agent / examples

AGENTS.md8 starsChanged 40 days agoMITView on GitHub

Before building or restyling a screen, page or flow: 1. Read the existing design system first: tokens, components and the screens next to the one you're changing. Reuse before adding. 2. If the decision isn't settled by the codebase (a new kind of screen, a flow we haven't built, an empty or error state), look up real examples with UXKIN: - find_ui_references for how shipped apps and websites handle it, - get_journey to see a whole flow screen by screen,…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository7 other files it gives its agents.

The file

We split this AGENTS.md 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:

    Before building or restyling a screen, page or flow:

    line 9
  2. Distinctive:

    Read the existing design system first: tokens, components and the screens next to the one you're changing.

    line 11
  3. Distinctive:

    If the decision isn't settled by the codebase (a new kind of screen, a flow we haven't built, an empty or error state), look up real …

    line 13
  4. Distinctive:

    Check the rendered result at phone and desktop width before saying it's done.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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
AGENTS.md
<!-- Example project instructions. Copy the section below into your project's AGENTS.md (Codex, Cursor, Copilot and others) or CLAUDE.md (Claude Code) and edit it to fit. It assumes the UXKIN MCP server is connected. -->

UI work

Before building or restyling a screen, page or flow:

  1. Read the existing design system first: tokens, components and the screens next to the one you're changing. Reuse before adding.
  2. If the decision isn't settled by the codebase (a new kind of screen, a flow we haven't built, an empty or error state), look up real examples with UXKIN:
    • find_ui_references for how shipped apps and websites handle it,
    • get_journey to see a whole flow screen by screen,
    • find_ui_materials for colors, type and components from real sites.
  3. Say which references you used and what you took from each, in one or two lines. Don't copy a product's branding, text or images.
  4. Design every state: loading, empty, error, success and disabled.
  5. Check the rendered result at phone and desktop width before saying it's done.

Skip the lookup for small fixes that don't change how something looks or works.

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.