agentleFS
wahmohwahmoh/claude-react-kit/CLAUDE.md

claude-react-kit

CLAUDE.md2 starsChanged 9 months agoMITView on GitHub

This project follows a layered architecture with strict import boundaries: Import rules (NEVER violate): - Features NEVER import from other features - core/ has ZERO business domain awareness - Components NEVER fetch data — they receive it via props - Pages/routes are the ONLY place for data fetching See @.claude/rules/architecture.md for full layer definitions. IMPORTANT: When context is compacted, always preserve: - The complete list of files modified and their current state - Any errors encountered and how they were…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. aleolidev/claude-react-kit★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use guard clauses (early returns) over nested conditionals

    line 37
  2. Very specific:

    NEVER use any — use proper types or unknown

    line 53
  3. Very specific:

    Use interface for objects, type for unions/primitives

    line 54
  4. Distinctive:

    Always handle null/undefined explicitly

    line 55
  5. Distinctive:

    Verify zero new errors introduced

    line 60

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

Commands

# Replace these with your project's actual commands
npm run type-check     # TypeScript verification
npm run lint           # Linting (zero warnings allowed)
npm run test           # Run tests
npm run build          # Production build

Architecture — MANDATORY

This project follows a layered architecture with strict import boundaries:

app/pages/routes/  →  src/features/  →  src/shared/  →  src/design-system/  →  src/core/
      ↓                    ↓                 ↓                  ↓                   ↓
  Data fetching      Feature UI +      Cross-feature       UI primitives      App infra
  Route handling     domain logic      reusables           (tokens, atoms)    (auth, net, i18n)

Import rules (NEVER violate):

  • Features NEVER import from other features
  • core/ has ZERO business domain awareness
  • Components NEVER fetch data — they receive it via props
  • Pages/routes are the ONLY place for data fetching

See @.claude/rules/architecture.md for full layer definitions.

Component Rules

  • Single responsibility: one component = one job
  • Target < 100 lines, hard max 200 lines (split into subfolder)
  • Functions: max 20 lines, max 3 parameters
  • Use guard clauses (early returns) over nested conditionals

Naming Conventions

ItemConventionExample
Component foldersPascalCaseUserProfile/
Infrastructure folderslowercase/kebab-casehooks/, shared/services/
Component filesPascalCase.tsxUserCard.tsx
Hook filescamelCase.tsuseUserData.ts
Type/const filescamelCase.tsuserTypes.ts
Booleansis/has/can/should prefixisLoading, hasError
Handlershandle + Subject + ActionhandleFormSubmit

TypeScript

  • NEVER use any — use proper types or unknown
  • Use interface for objects, type for unions/primitives
  • Always handle null/undefined explicitly

Before Finishing Any Task

  1. Run type-check: npm run type-check
  2. Verify zero new errors introduced
  3. Confirm no cross-feature imports were added

Compaction Instructions

IMPORTANT: When context is compacted, always preserve:

  • The complete list of files modified and their current state
  • Any errors encountered and how they were resolved
  • The current task scope and what remains to be done
  • Which architectural layer each change belongs to

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.