agentleFS
Sign inStart free
BennettxaiBennettxai/FounderOS/CLAUDE.md

FounderOS

CLAUDE.md1.4k starsChanged 26 days agoMITView on GitHub

Read this first. Same rules apply to any agent (see AGENTS.md). FounderOS v3 is the GladOS codebase plus two things of its own: - founderos/: the FounderOS v1 Agents board and Social pages (app/agents, app/social) and the UI they need. They read GladOS's database and connectors; nothing in founderos/ has its own data layer. - lib/demo/: the demo company. A fresh clone runs in demo mode (Filming, in GladOS's words) and lib/demo/store.ts builds demo-data/ from it on first start. Demo…

  • Reads credentials

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. Bennettxai/FounderOS-DEMO★ 1.4k100% 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.

  • In this repositoryOne other file it gives its agents.

The file

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

5 rules. About 0 are common, 1 is distinctive, and 4 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.

  • 4

    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
  1. Distinctive:

    Read this first. Same rules apply to any agent (see AGENTS.md).

    line 3
  2. Very specific:

    Honest or absent: No placeholder metrics, fake "connected" states, or demo text dressed as real data.

    line 34
  3. Very specific:

    Never commit secrets: Only .env.example is tracked.

    line 38
  4. Very specific:

    Keep the seed structural (lib/seed.ts seeds departments only): real data (data/) starts blank.

    line 42
  5. Very specific:

    Run npm test and npm run typecheck before claiming a change works.

    line 45

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

FounderOS (on GladOS): project notes for coding agents

Read this first. Same rules apply to any agent (see AGENTS.md).

What this is

A Next.js 14 (app router) + SQLite personal operating system. One database (lib/db.ts, opened via lib/data.ts), typed with zod schemas in lib/schemas.ts. Pages under app/, shared UI under components/, domain logic and connectors under lib/. Tests are vitest (tests/), including smoke.test.ts (every page renders) and smoke-api.test.ts (every GET route answers 200).

FounderOS v3 is the GladOS codebase plus two things of its own:

  • founderos/: the FounderOS v1 Agents board and Social pages (app/agents, app/social) and the UI they need. They read GladOS's database and connectors; nothing in founderos/ has its own data layer.
  • lib/demo/: the demo company. A fresh clone runs in demo mode (Filming, in GladOS's words) and lib/demo/store.ts builds demo-data/ from it on first start. Demo rows never go into data/.

Project board

docs/PROJECTS.md is the live board of what is being built here, its state, and what each step is waiting on. Read it at the start of every session, right after this file. Update it before the session ends whenever a step changes state, a blocker clears, or a new project starts. Absolute dates only. Its ## Checklist section is rendered under the terminal input by the status line: keep it in sync with the tables (tick items when done, add new ones, ! prefix = waiting on the operator). Multi-step projects have a folder under docs/projects/<name>/ with TASKS.md; when the operator picks a project, read its folder first and brief them from it. Shipped projects move to docs/projects/_done/, never deleted.

House rules

  • Honest or absent. No placeholder metrics, fake "connected" states, or demo text dressed as real data. An unconfigured integration shows a Not configured badge and a Set up link (SetupLink / setupHrefFor; tests/setup-links.test.ts enforces it).
  • Never commit secrets. Only .env.example is tracked. Keys are read through lib/creds.ts.
  • No emojis in UI. Inline stroke icons only.
  • Every colour is a token in app/globals.css; no raw hex in components.
  • Keep the seed structural (lib/seed.ts seeds departments only): real data (data/) starts blank. Demo content belongs in lib/demo/ and only ever reaches demo-data/.
  • Run npm test and npm run typecheck before claiming a change works.

Env

GLADOS_DEFAULT_MODE (demo unless set to real: what a fresh clone opens on), GLADOS_DB (db path), GLADOS_HOST (bind address; loopback until a password exists), GLADOS_PASSWORD_HASH + GLADOS_SESSION_SECRET (written by Setup → Security, never hand-set), BRAIN_PROVIDER / GBRAIN_BIN / GBRAIN_STORE (brain), plus connector keys listed in .env.example.

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.

Check your setup, free