haskeliumhaskelium/openprez/presentation/AGENTS.md

openprez / presentation

AGENTS.md1 starsChanged 2 days agoMITView on GitHub

This guide adds only user-deck-specific instructions. The repository root AGENTS.md is the source for shared slide-design, stage, shell, theme, asset, and validation rules.

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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- core/AGENTS.mdAGENTS.md
- showcase/AGENTS.mdAGENTS.md
- build-slideSkill
- build-templateSkill
- openprezSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
- opp-applySkill
- opp-archiveSkill
- opp-exploreSkill
- opp-proposeSkill
- promote-to-coreSkill

The file

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

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

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

Common
Distinctive
Very specific

Very specific:
Slide files: put slide components in presentation/slides/ and register each with defineSlide({ id, steps, tone, notes, Component }) using a …
line 6
Very specific:
Workflow: use /opp-explore, /opp-propose, /opp-apply, and /opp-archive for the matching phases.
line 7
Very specific:
Imports and assets: import foundation APIs only from @core, use relative paths within this deck, and store deck assets in …
line 8

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

User deck (`presentation/`) rules

This guide adds only user-deck-specific instructions. The repository root AGENTS.md is the source for shared slide-design, stage, shell, theme, asset, and validation rules.

Entry point: presentation/deck.tsx exports defineDeck({ title, date?, slides }); array order determines slide order. This folder ships as a starter deck; the first deck change replaces the starter slide's guidance with the user's own content.
Slide files: put slide components in presentation/slides/ and register each with defineSlide({ id, steps, tone, notes, Component }) using a unique id.
Workflow: use /opp-explore, /opp-propose, /opp-apply, and /opp-archive for the matching phases. Keep openprez/specs/presentation.md as the richer canonical source; slide notes are delivery aids derived from it.
Imports and assets: import foundation APIs only from @core, use relative paths within this deck, and store deck assets in presentation/assets/.

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