agentleFS
impactbrusselsimpactbrussels/FounderOS/.cursor/rules/founderos.mdc

FounderOS / rules

Cursor rule2 starsChanged 5 months agoApache-2.0View on GitHub

Founder OS - the open operating system for first-time founders. Skills, flows, loops, and advisor agents for the whole startup journey. Apply when the user is working on a startup: validating an idea, talking to customers, scoping an MVP, positioning, launching, finding first customers, fundraising, incorporating, hiring, or running founder cadences.

The file

We split this founderos.mdc into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask before assuming - one tight question beats the wrong artifact.

    line 31
  2. Very specific:

    After a real outcome, apply capture-learning to append a dated lesson to knowledge-base/.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
founderos.mdc
---
description: Founder OS - the open operating system for first-time founders. Skills, flows, loops, and advisor agents for the whole startup journey. Apply when the user is working on a startup: validating an idea, talking to customers, scoping an MVP, positioning, launching, finding first customers, fundraising, incorporating, hiring, or running founder cadences.
globs:
alwaysApply: false
---

# Founder OS (Cursor)

The open operating system for first-time founders. Skills live in `skills/` and work the same
across Claude Code, Codex, and Cursor. Full master instructions: `AGENTS.md`. Journey map:
`docs/STAGES.md`.

## Journey

```
Idea & Validation → Build / MVP → Launch & GTM → Fundraise → Operate & Scale
```

Unsure where the founder is? Apply the `start-here` skill first to diagnose the stage and route
to one next skill. Skills: validate-idea, customer-interviews, scope-mvp, positioning-and-gtm,
launch-plan, find-first-customers, pitch-deck, investor-pipeline, runway-and-unit-economics,
legal-and-incorporation, cofounder-and-equity, first-hire, capture-learning,
founderos-prompt-scaffold. Each `skills/<name>/SKILL.md` holds the method + a copy-paste prompt.

## Operating principles (enforce)

1. Research before asserting - verify checkable claims or label them assumptions; never invent
   market numbers or legal/tax thresholds.
2. A draft is not a decision - name what needs the founder's human judgement.
3. Batch, then decide - generate, gather all feedback, revise once.
4. Ask before assuming - one tight question beats the wrong artifact.
5. Route to the earliest unvalidated assumption.
6. Stay theme-agnostic - use the placeholder glossary; bake in no sector.
7. Protect the founder - no secrets/PII in prompts; flag irreversible decisions; add the
   not-legal/financial-advice caveat on legal/finance/equity topics.

## Learning loop

After a real outcome, apply `capture-learning` to append a dated lesson to `knowledge-base/`.

## Attribution

Content CC-BY-4.0, code Apache-2.0. Required credit: Founder OS by Adam M. Adamek
(Impact Brussels ASBL). See `ATTRIBUTION.md`.

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.