agentleFS
giulio333giulio333/ClaudeLens/src/CLAUDE.md

ClaudeLens / src

CLAUDE.md67 starsChanged 40 days agoMITView on GitHub

The React app in the Electron renderer. main.tsx mounts App inside React.StrictMode; App.tsx sets up the providers and useDataChangedRefetch(); tabs/ProjectOverview.tsx is the navigation shell. The feature components and their rules are in components/project/CLAUDE.md, the shared ones (Markdown, wikilinks, LiveOrb, the banners) in components/CLAUDE.md. - Navigation state has one owner: ProjectOverview, through the useTerminalNav reducer (components/project/terminal/use-terminal-nav.ts), which also keeps the embedded terminals alive. Components receive onNavigate/onBack. - Data comes from the React Query hooks in hooks/useIPC.ts; unwrap() throws on an error…

The file

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

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add the case to the View union in components/project/types.ts.

    line 10
  2. Very specific:

    Add the IPC hook to hooks/useIPC.ts if the view needs data.

    line 11
  3. Very specific:

    Put the component in components/project/<domain>/.

    line 12
  4. Very specific:

    Add the case to the switch (view.type) in tabs/ProjectOverview.tsx.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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

src/ — renderer

The React app in the Electron renderer. main.tsx mounts App inside React.StrictMode; App.tsx sets up the providers and useDataChangedRefetch(); tabs/ProjectOverview.tsx is the navigation shell. The feature components and their rules are in components/project/CLAUDE.md, the shared ones (Markdown, wikilinks, LiveOrb, the banners) in components/CLAUDE.md.

Adding a view

  1. Add the case to the View union in components/project/types.ts.
  2. Add the IPC hook to hooks/useIPC.ts if the view needs data.
  3. Put the component in components/project/<domain>/.
  4. Add the case to the switch (view.type) in tabs/ProjectOverview.tsx.
  5. Reach it with onNavigate({ type: '…' }).

Conventions

  • Navigation state has one owner: ProjectOverview, through the useTerminalNav reducer (components/project/terminal/use-terminal-nav.ts), which also keeps the embedded terminals alive. Components receive onNavigate/onBack.
  • Data comes from the React Query hooks in hooks/useIPC.ts; unwrap() throws on an error result. useDataChangedRefetch() invalidates only the namespaces a data:changed names, and everything when the event carries none.
  • Theme: hooks/useTheme.ts + hooks/ThemeProvider.tsx (split for the fast-refresh rule). The preference lives in localStorage['cl-theme'] and is applied as <html data-theme>.

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.