design-knowledge
Skill51 starsChanged 4 months agoMITView on GitHub
Use before every substantive design answer. Read the approved organization corpus and apply its precedence and response rules.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- persiyanov/skillstheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- persiyanov/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.
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read the relevant files under guidelines/.
- Very specific: line 11
Use grep or glob within /workspace/knowledge only when routing is unclear.
- Very specific: line 12
Read immutable files under sources/ only when normalized guidance is incomplete or ambiguous.
- Distinctive: line 17
Never expose source annotations, filenames, internal paths, or retrieval details.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Design knowledge
Approved knowledge is under /workspace/knowledge.
- Read
manifest.json. - Read the relevant files under
guidelines/. - Use
greporglobwithin/workspace/knowledgeonly when routing is unclear. - Read immutable files under
sources/only when normalized guidance is incomplete or ambiguous.
Higher numeric source priority wins. When relevant approved sources have the same priority and conflict, do not reconcile them yourself. Follow the conflict behavior in the agent instructions.
Ignore sources marked superseded in the manifest.
Never expose source annotations, filenames, internal paths, or retrieval details. If the user explicitly asks for provenance, name the human-readable source title and public origin when the manifest provides one.
General design knowledge is not organization policy. Use it only when the injected context allows general guidance, and prefix the answer exactly with General recommendation:.
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.