kostja94kostja94/pagina/AGENTS.md

pagina

AGENTS.md1 starsChanged 9 days agoMITView on GitHub

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 31,439 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 repository2 other files it gives its agents.
- page-builderSkill
- page-content-adapterSkill

The file

Show its rules and text

We split this AGENTS.md into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Keep page-builder as the default entry point for constructing individual pages.
line 3
Distinctive:
Create a separate skill only when a page task develops a genuinely independent workflow, inputs, outputs, or tools.
line 4
Distinctive:
Treat page variants as choices within one page reference, not as separate skills.
line 6
Very specific:
Keep page-builder focused on new pages.
line 7
Very specific:
Keep product archetypes, surfaces, and page functions in catalog/taxonomy.json.
line 8
Very specific:
Treat Contextus as the sole owner of durable project context.
line 11
Very specific:
Keep Pagina usable without Contextus: read available project material, ask for missing facts, and report durable discoveries without …
line 12
Distinctive:
Treat route topology, deployment ownership, locale, and market as construction context.
line 13
Distinctive:
Prefer first-party page construction.
line 14
Distinctive:
Add only minimal page-local APIs or adapters and never simulate unavailable operational systems with sample data.
line 15
Distinctive:
Do not expand a page request into whole-site information architecture or silently redesign neighboring routes.
line 18
Very specific:
Update catalog/pages.json whenever a page reference is added, renamed, or removed.
line 19
Very specific:
Run npm test before completing structural changes.
line 20

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

Repository instructions

Keep page-builder as the default entry point for constructing individual pages.
Create a separate skill only when a page task develops a genuinely independent workflow, inputs, outputs, or tools.
Maintain each page type in one reference under skills/page-builder/references/pages/.
Treat page variants as choices within one page reference, not as separate skills.
Keep page-builder focused on new pages. Use page-content-adapter for host-specific copy within existing component contracts. General existing-page optimization and reconstruction remain outside Pagina.
Keep product archetypes, surfaces, and page functions in catalog/taxonomy.json; do not invent near-duplicate labels in page references.
Maintain page-to-component recommendations in catalog/pages.json and generate catalog/component-page-map.json; never edit the reverse map manually.
Component IDs refer to Bricks when available, but target-project components take precedence and Pagina must remain usable independently.
Treat Contextus as the sole owner of durable project context. Pagina reads {project}.md when present and must not create another context template, lifecycle model, or archive.
Keep Pagina usable without Contextus: read available project material, ask for missing facts, and report durable discoveries without establishing a parallel memory system.
Treat route topology, deployment ownership, locale, and market as construction context; do not infer one from another or turn page work into whole-site architecture.
Prefer first-party page construction. Third-party platforms are recommendations unless the user explicitly selects one.
Add only minimal page-local APIs or adapters and never simulate unavailable operational systems with sample data.
Inspect the target product, route, neighboring pages, design system, content model, and implementation conventions before building.
Reuse existing components and use Bricks only when component-specific guidance is needed.
Do not expand a page request into whole-site information architecture or silently redesign neighboring routes.
Update catalog/pages.json whenever a page reference is added, renamed, or removed.
Run npm test before completing structural changes.

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