skills
CLAUDE.md4 starsChanged 10 days agoMITView on GitHub
bun | TS 7 tsc/tsrs | Biome | Vitest | React Doctor Local policy wins. Navigation. - UI: @/components/ui/ first; buttons: <Button>, variants/tokens. Functional React components; React Compiler owns memoization. - State: zustand=client, TanStack Query=server, connect-query=ConnectRPC; app env from @/env. - Proto: enum names, not magic numbers. Validate formats, not only presence. - Tests: .test.ts unit, .test.tsx integration, .browser.test.tsx visual, e2e/*.spec.ts Playwright; co-locate with source. - Services: repo CLI. LaunchDarkly flags: ldcli only; read shared/ldcli.md. Follow local idioms. Preserve zoom,…
In this repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibilitySkill
- agent-watchdogSkill
- aipSkill
- animateSkill
- animation-performanceSkill
- animation-vocabularySkill
- ask-benSkill
- ask-sonnerSkill
- bazelSkill
- bend-lawsSkill
- blast-radiusSkill
- brain-dumpSkill
- break-uiSkill
- ci-fixesSkill
- codebase-designSkill
- codex-compatSkill
- codexSkill
- commit-push-prSkill
- connect-querySkill
- create-verification-skillSkill
- demoSkill
- development-lifecycleSkill
- diagnosing-bugsSkill
- docsSkill
- dogfoodSkill
- domain-modelingSkill
- e2e-testingSkill
- effect-tsSkill
- effect-v3-to-v4Skill
- efficient-frontierSkill
- eli5Skill
- excalidraw-diagramSkill
- extend-harnessSkill
- frontend-invariantsSkill
- frontend-starter-kitSkill
- full-sendSkill
- gesturesSkill
- golang-reviewSkill
- golangSkill
- goSkill
- grillingSkill
- handoffSkill
- hook-auditSkill
- implement-specSkill
- improve-animationsSkill
- improve-codebase-architectureSkill
- improveSkill
- launchdarklySkill
- lie-detectorSkill
- maintain-verification-skillSkill
- make-pr-easy-to-reviewSkill
- mobile-nativeSkill
- plan-arbiterSkill
- plow-aheadSkill
- postgresqlSkill
- primeSkill
- productSkill
- protobufSkill
- prototypeSkill
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
9 rules. About 0 are common, 1 is distinctive, and 8 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.
8
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 18
Follow local idioms. Preserve zoom, worktree isolation, secrets, types, generated files.
- Very specific: line 39
Commit: commit only. Push: commit, push.
- Very specific: line 44
Commit/push/rebase owned features without another permission prompt.
- Very specific: line 48
Never merge, use plain --force, or rewrite default/shared/foreign/concurrent branches without explicit permission.
- Very specific: line 51
Keep follow-ups in the current PR: pr/SKILL.md#existing-pr at start/resume and handoff.
- Very specific: line 64
Keep user's goal; known/expected user/business value or not established.
- Distinctive: line 80
No extra gates/ceremonies.
- Very specific: line 84
Only Opus 5.5/Sol 6.1 xhigh.
- Very specific: line 87
Before done: bun run lint:fix + bun run type:check.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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
Project rules
Toolchain
bun | TS 7 tsc/tsrs | Biome | Vitest | React Doctor
Local policy wins. Navigation.
- UI:
@/components/ui/first; buttons:<Button>, variants/tokens. Functional React components; React Compiler owns memoization. - State: zustand=client, TanStack Query=server, connect-query=ConnectRPC; app env from
@/env. - Proto: enum names, not magic numbers. Validate formats, not only presence.
- Tests:
.test.tsunit,.test.tsxintegration,.browser.test.tsxvisual,e2e/*.spec.tsPlaywright; co-locate with source. - Services: repo CLI. LaunchDarkly flags:
ldclionly; readshared/ldcli.md.
Follow local idioms. Preserve zoom, worktree isolation,
secrets, types, generated files; use exemplars/.
Code quality.
Human-facing text
shared/communication.md: decision/value/ask first; own claims, intent,
uncertainty. Above 200 words: <=120-word brief, then detail.
Tool-count word limits; never invent human endorsement.
Substantial artifacts: shared/intent-map.md maps objective, assumptions, references,
risks, implementation, verification and superseded choices. Trivial/single-path output stays linear.
Execution contract
Endpoint owns scope:
- Answer, explain, plan, review: return the artifact; do not edit.
- Build, fix, implement: plan, continue, verify, commit, push the user-owned feature branch unless explicitly told to stop earlier.
- Commit: commit only. Push: commit, push. PR: verify, commit, push, open via
/commit-push-pr. PR/draft: automatic upkeep viashared/delivery-workflow.md; publication is not readiness.
Earlier stop wins. Ask for reserved/irreversible production, legal/privacy, destructive
or high-security decisions; otherwise proceed reversibly.
Commit/push/rebase owned features without another permission prompt.
Owned PRs/drafts: fix CI/feedback, consolidate owned commits before rebase, resolve conflicts,
verify and lease-push automatically.
Push CI fix or rebase now (--force-with-lease).
Never merge, use plain --force, or rewrite default/shared/foreign/concurrent branches
without explicit permission.
Delivery follow-ups replace local stops; no restart/reconfiguration requests.
Keep follow-ups in the current PR: pr/SKILL.md#existing-pr at start/resume and handoff.
Push/PR/ship: verify origin HEAD/scope; follow shared/review-enforcement.md.
Report blockers; uncommitted/unpushed owned work is incomplete.
shared/remote-completion.md: recover verified scope; preserve local stops, unrelated work and active owners.
PR upkeep: one authorized transport; honor no-monitoring stops.
Agents/council require host-valid consent. Standing owner consent is reusable only
within its explicit scope; no nested delegation. Persistent setup needs authorization.
Isolate browser automation; never take over human-owned browsers/desktop apps.
End actions with one status line:
🟢 done — <evidence>, 🟡 awaiting decision — <decision>, or
🔴 blocked — <external blocker and needed input>.
Immediately before each: Intent: <outcome> | Impact: <value>.
Keep user's goal; known/expected user/business value or not established; invent no claims/metrics.
For any PR, include its full PR URL on the final status line.
Work
Smallest working diff; reuse code/tests. Apply proportionate verification. Temporary evidence, inline results; retain requested/required/reusable files. Project/user requirements win.
One outcome contract: Objective (end state), Guardrails (bounds), Verification (proof), Stop (endpoint/blockers).
inspect -> act -> verify -> repeat. Use scripts for repeatable work, judgment for uncertainty. Improve feedback loops before opt-in concurrency. Continue reversible decisions; pair status with the next action, not recaps/offers/non-blocking options. No extra gates/ceremonies. Add failing public-contract tests only for uncovered risks; reuse local notes for long-run checkpoints, not routine evidence/checklist files.
Quality-first: config/model-routing.json, /efficient-frontier.
Only Opus 5.5/Sol 6.1 xhigh; block other routes. No rankings/token-based usage guesses.
Promote models/effort/context only via agent-evals/context-ablation/.
Before done: bun run lint:fix + bun run type:check. Never hand-edit generated files
(*.gen.*, *_pb.*, *_connectquery.*, or an @generated/DO NOT EDIT header).
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.

