project-room
Skill1 starsChanged 23 days agoApache-2.0View on GitHub
Use when changing anything on the Work page, project views, chat threads, or run representation in SC Prism — the founder's no-black-box standard for how project work must be shown
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Uuriko/project-roomtheir own version, first seen Oct 25, 2026
- jobottinkwork/claude-skillstheir own version, first seen Oct 8, 2026
- ridermw/my-skillstheir own version, first seen Sep 10, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Uuriko/project-room★ 2same name
- jobottinkwork/claude-skills★ 0same name
- ridermw/my-skills★ 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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 19
Every file the room mentions must be reachable from the room (reveal/open).
- Distinctive: line 21
If a change cannot meet the bar honestly (data doesn't exist in spans), say so in the PR/commit rather than faking a line.
≈ “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
The project-room standard (Sukhdeep, 2026-08-29)
Load docs/superpowers/specs/2026-08-29-project-room-design.md and hold every
Work-page change to it. The short form:
- A project is a separate ROOM: own chat, own folder access, own file details, unmistakable switching.
- The work lives IN the chat — inline, scrollable, seat-attributed action lines derived ONLY from engine span records (never invented).
- Attribution is three-part or it's not done: agent name · AI brand · action. "Opus is doing this thing" fails the bar.
- The privacy line renders in the room: vault/MCP arguments never appear; 🔒 withheld and ⛔ blocked are part of the story.
- Every file the room mentions must be reachable from the room (reveal/open).
If a change cannot meet the bar honestly (data doesn't exist in spans), say so in the PR/commit rather than faking a line.
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.

