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.
- build-uiSkill
- design-mdSkill
- ios-screensSkill
- ui-from-screenshotSkill
- ui-statesSkill
- no-ui-slopSkill
- uxkin-researchSkill
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
- Distinctive: line 9
Before building or restyling a screen, page or flow:
- Distinctive: line 11
Read the existing design system first: tokens, components and the screens next to the one you're changing.
- Distinctive: line 13
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 …
- Distinctive: line 22
Check the rendered result at phone and desktop width before saying it's done.
≈ “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.
Files
<!--
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:
- Read the existing design system first: tokens, components and the screens next to the one you're changing. Reuse before adding.
- 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_referencesfor how shipped apps and websites handle it,get_journeyto see a whole flow screen by screen,find_ui_materialsfor colors, type and components from real sites.
- 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.
- Design every state: loading, empty, error, success and disabled.
- 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.
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.

