satus / rules
Cursor rule1k starsChanged 15 days agoMITView on GitHub
The canonical engineering standards for this repo are in /AGENTS.md. Follow it for all code changes. AGENTS.md covers: enforced oxlint + TypeScript rules, house style conventions, component patterns, React 19 / Next.js 16 / Tailwind v4 specifics, integrations, and commands.
Trending
Quiet this year.thin dataabout the whole repository
Who's talking about darkroomengineering/satus
- sweeneytr/tristansweeney.com“Links to add”GitHub · Apr 24, 2025
- vercel/next.js“(turbopack) doesn't support mixing units in sass calculations, while webpack does”GitHub · May 1, 2024
The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- next-bundle-optimizerSkill
- react-doctorSkill
The file
Files
--- alwaysApply: true --- # Satus Project Guidelines The canonical engineering standards for this repo are in [`/AGENTS.md`](/AGENTS.md). Follow it for all code changes. `AGENTS.md` covers: enforced oxlint + TypeScript rules, house style conventions, component patterns, React 19 / Next.js 16 / Tailwind v4 specifics, integrations, and commands.
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.

