setup-workspace
Skill13 starsChanged 3 months agoMITView on GitHub
Personalize this starter workspace. Interviews the user about their company, product, users, and preferences, then fills in CLAUDE.md and the context files and renames the example project. Use on first launch, or whenever the user wants to re-run onboarding.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- Richicinschi/studio-ostheir own version, first seen Nov 8, 2026
- probabl-ai/skillstheir own version, first seen Oct 27, 2026
- Cassius2584/claude-uni-workspacetheir own version, first seen Oct 22, 2026
- probabl-ai/skore-skillstheir own version, first seen Oct 15, 2026
- Flop19/legal-workspace-startertheir own version, first seen Oct 8, 2026
- timscheuerai/gtm-architecture-templatetheir own version, first seen Sep 14, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- probabl-ai/skills★ 144same name
- probabl-ai/skore-skills★ 144same name
- Flop19/legal-workspace-starter★ 8same name
- Cassius2584/claude-uni-workspace★ 5same name
- timscheuerai/gtm-architecture-template★ 2same name
- hunterbohm/solo-staff★ 0same name
- Richicinschi/studio-os★ 0same 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- file-feedbackSkill
- interview-synthesisSkill
- prd-reviewSkill
- status-updateSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
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 12
Ask in rounds, one topic at a time, in this order: company, product, users, working and writing preferences, current projects.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Setup workspace
Turn the template files into the user's own workspace through a short interview. The user answers in plain language; you do all the writing.
How to run the interview
- Ask in rounds, one topic at a time, in this order: company, product, users, working and writing preferences, current projects. A few questions per round, not a wall of them.
- Plain questions a busy person can answer from memory: "What does your company sell, and to whom?", "Who do you picture when you make product decisions?", "What's a correction you find yourself giving on every AI draft?"
- Accept short answers and draft from them. Show what you wrote and ask for a yes or a fix before moving to the next topic. The user's words beat template language; keep their phrasing where it's clear.
- Skipping is fine. If the user doesn't know or doesn't care about a section, leave the template placeholder in place and move on. An honest placeholder beats invented content.
What to fill
CLAUDE.md— replace the first line with who the user actually is (role, company). Keep the file short; it's a map, not a manual.context/company.md— what the company does, how it's organized, competitors, vocabulary.context/product.md— what the product is, positioning, current strategy, key metrics (names and where they live, not live numbers).context/users.md— segments, primary persona, strongest findings.context/preferences.md— writing preferences and working preferences in the user's own words. Replace the template examples with theirs; delete examples they don't want.projects/example-project/— ask for the user's most active real project. Rename the folder to a short slug of it, fillbrief.mdfrom what they tell you, and seedtasks.mdwith their current next steps. If they'd rather start empty, leave the example in place.
Finish
Show a short summary of every file you touched. Then suggest one concrete next move: give the workspace a real task, for example /status-update or a first draft the user owes someone. Remind them once: when they correct something you got wrong, /file-feedback makes the correction permanent.
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.