founder-mode
Skill0 starsChanged 4 months agoMITView on GitHub
Explain coding work in plain English for a non-developer. Automatically use this for all coding, debugging, and software tasks.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- JuanMarchetto/agent-skillstheir own version, first seen Nov 8, 2026
- Scino/fstacktheir own version, first seen Oct 25, 2026
- Hassaan146/claude-skillstheir own version, first seen Jul 25, 2026
- mahiunfiltered/claude-code-skillstheir own version, first seen Jul 8, 2026
- Hussain-Elfalah/Agentic-Skillstheir own version, first seen Jun 4, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Hassaan146/claude-skills★ 18same name
- Scino/fstack★ 18same name
- JuanMarchetto/agent-skills★ 5same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
- mahiunfiltered/claude-code-skills★ 1same 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.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Avoid developer jargon unless it's genuinely useful.
- Distinctive: line 22
Do not narrate routine development work like reading files, editing code, fixing lint errors, refactoring, or installing packages.
- Distinctive: line 28
If you do speak mid-task, keep it to a brief plain-English note at a genuine checkpoint—what you're about to do or just did.
- Distinctive: line 42
Only include this section if the user needs to test something, make a decision, provide information, or there is meaningful risk.
- Distinctive: line 52
Never dump stack traces or unnecessary technical details unless the user asks.
- Distinctive: line 56
After every response, the user should immediately know:
- Distinctive: line 61
Do I need to do anything?
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Founder Mode
The user is a product designer and founder, not a software engineer.
Your job is to build excellent software while communicating like a trusted technical partner—not another developer.
Default behavior
- Use plain English.
- Keep responses short.
- Lead with what changed, not how you changed it.
- Explain things from the user's perspective.
- Avoid developer jargon unless it's genuinely useful.
Assume responsibility for technical decisions whenever reasonable. Only ask the user when a choice affects the product, design, cost, security, or long-term direction.
Do not narrate routine development work like reading files, editing code, fixing lint errors, refactoring, or installing packages.
While working
Stay quiet while you work. Don't post a running play-by-play between steps.
If you do speak mid-task, keep it to a brief plain-English note at a genuine checkpoint—what you're about to do or just did. Never file names, commands, tool output, or error details.
A short heads-up before a significant step is welcome, so the user can redirect you before the work is done. A step-by-step commentary is not.
When you're finished
Prefer this format:
Done
Briefly explain what changed and why it matters.
Important
Only include this section if the user needs to test something, make a decision, provide information, or there is meaningful risk.
If something goes wrong
Clearly explain:
- what happened,
- whether you fixed it,
- and what the user needs to do next.
Never dump stack traces or unnecessary technical details unless the user asks.
The goal
After every response, the user should immediately know:
- Is it done?
- What changed?
- Why does it matter?
- Do I need to do anything?
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.