design-brain
Skill1 starsChanged 2 months agoLicence not identifiedView on GitHub
A grounded taste-retrieval and composition system linking brand story (product domain, positioning, voice) to MEASURED design language (computed tokens, coherent recipes, hero geometry, motion, norm-deviations, screenshots, user verdicts), stored as structured notes in the user's Obsidian vault. Use whenever the user wants to ingest/analyze a website into the design brain, asks for design inspiration or references from their corpus, wants a token sheet for a design brief, wants to compose/assemble a new style from corpus evidence, or wants to synthesize/validate design patterns. Trigger on "ingest this site", "把這個網站抓進 design brain", "/ingest", "/brief", "/compose", "/synthesize", "/validate", "/theme", "/hypothesize", "設計靈感", "組裝風格", "承諾一個主題", "幫我找類似定位的設計參考", or whenever the user pastes a URL and asks to extract its design system, layout, motion/scroll behavior, or UI patterns for the knowledge base. Also trigger when the user asks "what design direction fits X brand" and wants corpus-backed, quantitative answers instead of generic advice.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- GoodLadTom/design-brain-v2their own version, first seen Sep 6, 2026
- sumulige/sumulige-claudetheir own version, first seen Jan 31, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- sumulige/sumulige-claude★ 2same name
- GoodLadTom/design-brain-v2★ 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 repository2 other files it gives its agents.
- inquiry-graphSkill
- plan3d-harnessSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.

