standards
Skill0 starsChanged 18 days agoMITView on GitHub
Default stack, code, UI, and security rules. Use before writing app code in a repo with no AGENTS.md.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- rylsherdamz-rgb/stellar-forgetheir own version, first seen Nov 8, 2026
- nearmap/shipyardtheir own version, first seen Nov 8, 2026
- denolfe/dotfilestheir own version, first seen Nov 2, 2026
- azamkhanuk/context-centraltheir own version, first seen Oct 11, 2026
- austintgriffith/ethskillstheir own version, first seen Oct 8, 2026
- BankrBot/openclaw-skillstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use spec and design.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 3 projects that use this
Microsoft AzureSkilldesign
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- BankrBot/openclaw-skills★ 1.2ksame name
- BankrBot/skills★ 1.2ksame name
- austintgriffith/ethskills★ 303same name
- denolfe/dotfiles★ 88same name
- rylsherdamz-rgb/stellar-forge★ 17same name
- azamkhanuk/context-central★ 2same name
- yknnv/brownspec★ 2same name
- emretasss/stellar-paygate-mcp★ 1same name
- nearmap/shipyard★ 1same name
- Endika/eskills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- convexSkill
- design-planSkill
- frontend-designSkill
- new-projectSkill
- prdSkill
- prSkill
- retroSkill
- setup-hostingSkill
- unslopSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 20
Never use @ts-nocheck. Fix the types.
- Distinctive: line 23
After every change, run build, typecheck, and lint for what you touched, plus targeted tests for the changed behavior.
- Distinctive: line 27
Every app is built from its own component library, so a change to one component reaches every screen.
- Distinctive: line 36
Never use a scroll indicator, animated dots, or "scroll" hint text.
- Very specific: line 37
Never allow horizontal page scroll.
- Very specific: line 38
Never use Tailwind's ! important modifier.
- Very specific: line 39
Never use alert(), confirm(), or prompt().
- Distinctive: line 43
No hardcoded secrets, keys, or credentials.
- Very specific: line 45
Never trust a client-supplied userId, email, or role for authorization.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Standards
My defaults for web apps. A repo's own AGENTS.md replaces them.
Stack
- Package manager is bun.
- Next.js App Router only. Never create a
pages/directory. - Server components by default. Client components only where interactivity requires it.
- Give each entity state its own route:
create/,[id]/,[id]/update/,[id]/manage/. Do not multiplex those states inside one route. - Convex for data and file storage. Better Auth for auth, Google as the initial provider, joined to Convex through the
@convex-dev/better-authcomponent. It replaced Auth.js, which gets only security fixes since September 2025. Stripe for payments, server-side only, Connect for multi-party payouts. Resend for email.
Code
- Never use
@ts-nocheck. Fix the types. - Target 200 lines per file. Exceed it when splitting would hurt cohesion, and say why.
- Import everything explicitly.
- After every change, run build, typecheck, and lint for what you touched, plus targeted tests for the changed behavior. Never merge with failing tests.
UI
Every app is built from its own component library, so a change to one component reaches every screen.
- Primitives live in
src/components/ui/and own every class and token: layout (stack, row, grid, split), text and headings, controls, feedback, tables, and the app shell. - Screens and domain components compose primitives. Outside
src/components/ui/, lint failsclassName,style, and CSS imports withreact/forbid-dom-props,react/forbid-component-props, andno-restricted-imports. - Primitive props take named options such as
tone="muted",columns="fields", orgap={4}, never raw classes or values. - A missing piece becomes a new primitive or a new variant of one. A pattern that shows up twice becomes a primitive, and both uses move onto it.
/dev/uidemos every shared component in each of its states, the way screens use it, and is a 404 outside development. A test fails when a component has no demo. A component and its demo change in the same commit.- Tokens for color, type, spacing, radius, shadow, and motion live in
globals.css. The repo'sDESIGN.md, orUxStyle.mdin an older repo, sets the direction and names the tokens. - Support dark and light themes.
- Never use a scroll indicator, animated dots, or "scroll" hint text.
- Never allow horizontal page scroll. Constrain layouts and set
overflow-x: hiddenat the root. - Never use Tailwind's
!important modifier. Fix the layout or hierarchy instead. - Never use
alert(),confirm(), orprompt(). Use the project's branded modal.
Security
- No hardcoded secrets, keys, or credentials. Environment variables only.
- Validate tokens server-side. Never trust client state.
- Never trust a client-supplied
userId,email, orrolefor authorization. Derive identity from the verified server session, then enforce ownership against stored records. - Deny by default. Missing auth, missing ownership, or identity mismatch fails immediately.
- Filter on the server. Pass each view's filters, search, sort, and page as query arguments, and return only the rows and fields the current user needs for that view. A client never receives a full collection to filter, sort, or trim itself.
- Validate and sanitize untrusted input at every boundary: API, server actions, database writes, webhooks.
- Log errors with enough context to debug and no sensitive payloads.
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.

