adlinter
CLAUDE.md4 starsChanged 6 months agoApache-2.0View on GitHub
Use the /browse skill from gstack for all web browsing. Never use mcpclaude-in-chrome* tools. Available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /design-shotgun, /design-html, /review, /ship, /land-and-deploy, /canary, /benchmark, /browse, /connect-chrome, /qa, /qa-only, /design-review, /setup-browser-cookies, /setup-deploy, /retro, /investigate, /document-release, /codex, /cso, /autoplan, /plan-devex-review, /devex-review, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade, /learn Always read PRODUCT.md at the repo root before making product, copy, or scope decisions. Primary user is agencies/freelancers auditing client work. The wedge is privacy — the trustable alternative to pasting…
We split this CLAUDE.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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: line 3
Use the /browse skill from gstack for all web browsing.
- Very specific: line 9
Always read PRODUCT.md at the repo root before making product, copy, or scope decisions.
- Very specific: line 17
Always read DESIGN.md at the repo root before making any visual or UI decision.
- Distinctive: line 18
All font choices, colors, spacing, border-radius, motion, and aesthetic direction are defined there.
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.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
gstack
Use the /browse skill from gstack for all web browsing. Never use mcp__claude-in-chrome__* tools.
Available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /design-shotgun, /design-html, /review, /ship, /land-and-deploy, /canary, /benchmark, /browse, /connect-chrome, /qa, /qa-only, /design-review, /setup-browser-cookies, /setup-deploy, /retro, /investigate, /document-release, /codex, /cso, /autoplan, /plan-devex-review, /devex-review, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade, /learn
Product
Always read PRODUCT.md at the repo root before making product, copy, or scope decisions.
Primary user is agencies/freelancers auditing client work. The wedge is privacy — the
trustable alternative to pasting client creative into ChatGPT. Findings must be
defensible and citable. AdLint is not a generator, not a campaign manager, not a
performance predictor.
Design System
Always read DESIGN.md at the repo root before making any visual or UI decision.
All font choices, colors, spacing, border-radius, motion, and aesthetic direction
are defined there. Do not deviate without explicit user approval.
In QA mode, flag any code that doesn't match DESIGN.md or PRODUCT.md.
Merging
Standing permission from the owner (Christopher Landaverde, 2026-10-30): agents merge their own pull requests, user-visible ones included, without asking, when all of these hold:
- CI is green on GitHub on the PR's latest commit (
gh pr checks <n>; local runs don't count). - An agent other than the author reviewed the diff and posted
Blocking findings: none. - The PR merges cleanly into
main.
Merge with gh pr merge <n> --squash --delete-branch, then confirm main CI passes. Still stop and ask for: releases, tags, store or package publishing, deploys, repo settings or visibility, spending money, and deleting anything you didn't create. Never push directly to main or force-push a shared branch.
In this repositoryOne other file it gives its agents.
- public/llms.txtllms.txt
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.