founder-voice
Skill16 starsChanged 18 days agoMITView on GitHub
How to word anything the founder reads or answers - questions, grilling rounds, approvals, decisions, summaries, reports - at the technical level saved in project.toml [owner] level (non-technical, basics or technical). Use before writing any message or document for the founder.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Scino/fstacktheir own version, first seen Oct 25, 2026
- assafkip/founder-voice-kittheir own version, first seen May 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Scino/fstack★ 13same name
- assafkip/founder-voice-kit★ 2same name
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 repository120 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent-agentic-workflow.mdcCursor rule
- .cursor/rules/agent-android-dev.mdcCursor rule
- .cursor/rules/agent-architect.mdcCursor rule
- .cursor/rules/agent-backend-dev.mdcCursor rule
- .cursor/rules/agent-dashboard.mdcCursor rule
- .cursor/rules/agent-debugger.mdcCursor rule
- .cursor/rules/agent-desktop-dev.mdcCursor rule
- .cursor/rules/agent-devops.mdcCursor rule
- .cursor/rules/agent-explainer-writer.mdcCursor rule
- .cursor/rules/agent-feasibility.mdcCursor rule
- .cursor/rules/agent-growth.mdcCursor rule
- .cursor/rules/agent-ios-dev.mdcCursor rule
- .cursor/rules/agent-legal.mdcCursor rule
- .cursor/rules/agent-optimizer.mdcCursor rule
- .cursor/rules/agent-orchestrator.mdcCursor rule
- .cursor/rules/agent-platform-architect.mdcCursor rule
- .cursor/rules/agent-platform-designer.mdcCursor rule
- .cursor/rules/agent-product-designer.mdcCursor rule
- .cursor/rules/agent-qa.mdcCursor rule
- .cursor/rules/agent-researcher.mdcCursor rule
- .cursor/rules/agent-reviewer.mdcCursor rule
- .cursor/rules/agent-rollback.mdcCursor rule
- .cursor/rules/agent-security.mdcCursor rule
- .cursor/rules/agent-setup.mdcCursor rule
- .cursor/rules/agent-social-media.mdcCursor rule
- .cursor/rules/agent-web-dev.mdcCursor rule
- .cursor/rules/skill-bug-fix.mdcCursor rule
- .cursor/rules/skill-commit.mdcCursor rule
- .cursor/rules/skill-context-budget.mdcCursor rule
- .cursor/rules/skill-cost-audit.mdcCursor rule
- .cursor/rules/skill-decision-log.mdcCursor rule
- .cursor/rules/skill-experiment.mdcCursor rule
- .cursor/rules/skill-founder-voice.mdcCursor rule
- .cursor/rules/skill-frontend-design.mdcCursor rule
- .cursor/rules/skill-gates.mdcCursor rule
- .cursor/rules/skill-grilling.mdcCursor rule
- .cursor/rules/skill-handoff.mdcCursor rule
- .cursor/rules/skill-human-design.mdcCursor rule
- .cursor/rules/skill-human-steps.mdcCursor rule
- .cursor/rules/skill-karpathy-guidelines.mdcCursor rule
- .cursor/rules/skill-known-reds.mdcCursor rule
- .cursor/rules/skill-legal-review.mdcCursor rule
- .cursor/rules/skill-new-feature.mdcCursor rule
- .cursor/rules/skill-observability.mdcCursor rule
- .cursor/rules/skill-ordered-steps.mdcCursor rule
- .cursor/rules/skill-performance.mdcCursor rule
- .cursor/rules/skill-readiness-gate.mdcCursor rule
- .cursor/rules/skill-release.mdcCursor rule
- .cursor/rules/skill-requirement-first.mdcCursor rule
- .cursor/rules/skill-safe-data-write.mdcCursor rule
- .cursor/rules/skill-setup.mdcCursor rule
- .cursor/rules/skill-single-source.mdcCursor rule
- .cursor/rules/skill-spec-audit.mdcCursor rule
- .cursor/rules/skill-tailoring.mdcCursor rule
- .cursor/rules/skill-twin-check.mdcCursor rule
- .cursor/rules/skill-verified-claims.mdcCursor rule
- .cursor/rules/skill-verify-green.mdcCursor rule
- bug-fixSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
When more than one question is open, number them and ask for answers by number ("1 yes, 2 no").
- Distinctive: line 41
Use the plain version, or say the thing it does:
- Distinctive: line 57
When there is no plain word, explain the idea in one sentence and drop the term.
- Very specific: line 64
Every decision the founder is asked for, in chat or in p1-open-questions.md, is one card: decision, recommendation, what could go wrong, …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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
<!-- Generated by tools/sync_adapters.py from skills/founder-voice/SKILL.md. Edit the source, not this file. -->Founder voice
The founder's level is in project.toml [owner] level. Read it before you write to them. If it
is missing or unset, the first question you ask is the level itself (below), worded for a
non-technical reader. Never guess it from how they write.
The three levels
| Level | Who | How you write |
non-technical | Has never written code. | No technical words at all. Every choice as what it means for the business, what it costs, what could go wrong, and your recommendation. Say what the founder will see or feel, not how it works. |
basics | Knows the ideas (a database, a server, a deploy) but does not code. | Plain words first; a technical term is fine when it is the clearest one, explained once in a few words the first time. No code, no commands, no file paths unless they asked. |
technical | Writes or reads code. | Brief. Technical terms, file paths and diffs are fine; lead with the decision and the diff. |
Asking for the level (setup, or the first grilling when it is unset): "How technical are you?
- I've never written code. 2. I know the basic ideas but don't code. 3. I write or read code. My suggestion is 1 unless you're sure; you can change it any time."
Every message, at every level
- One decision per question, with your recommendation, worded so that "yes" accepts it.
- When more than one question is open, number them and ask for answers by number ("1 yes, 2 no"). A bare "yes" with several open is asked back, never read as covering all of them; accepting every recommendation is said outright ("accept all") or marked in the choices file.
- Screens and pictures are shown, never pointed at: in the chat where the tool can show an image, or as one generated page that opens by itself. Never a file path to open.
- Facts you can look up, you look up; the founder is asked only for decisions.
- Numbers keep their units and their source: "about 20 dollars a month (provider's price page)".
- The founder can change their level any time ("explain less", "I don't follow"). Update
project.toml [owner] levelthe same day, with the date inp1-closed-decisions.md.
Words for non-technical
Use the plain version, or say the thing it does:
| Instead of | Say |
| deploy, release to production | put the new version live for your users |
| rollback | put the previous version back |
| repository, repo | your project's folder on GitHub |
| commit, push, merge | save the change, send it to GitHub, add it to the live version |
| database, migration | where the data is kept; a change to how it is stored |
| API, endpoint, integration | a connection to another service |
| frontend, backend | the part users see; the part behind it |
| bug, regression | something broken; something that used to work and now doesn't |
| test, CI, sweep | an automatic check; the checks that run after every change |
| requirement row, spec | one sentence the product must do; the written plan for a feature |
| environment variable, secret, API key | a private setting; a password for a service |
When there is no plain word, explain the idea in one sentence and drop the term.
Approvals
Say what will happen, what it changes for users or money, whether it can be undone and how long that takes, then ask.
Every decision the founder is asked for, in chat or in p1-open-questions.md, is one card:
decision, recommendation, what could go wrong, how to undo it, and two replies to copy, the
recommended one first (TPL-113). The shape, an example and the wording at each level are in
skills/founder-voice/card.md.
Saying something is done
A report that something is done, fixed or live ends with one thing the founder can check themselves in under a minute, without reading code (TPL-116): "Open yourapp.com/signup on your phone: the new page has the green button." Or: "Open the sheet: row 14 has today's orders." A report with nothing the founder can check yet says what it is waiting on before it can be seen.
Documents the founder reads
Specs, summaries, QA and legal reports, the dashboard, release notes: write the parts the founder must read or decide on at their level, and put the technical detail other agents need in a separate section headed for them.
A review reaches the founder as its "For the founder" list (agents/reviewer.md), word for
word, with how many lines block launch and how many can wait; never summarised into "a few
issues" (TPL-106).
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.

