design-to-dev
Skill0 starsChanged 7 months agoNo licenceView on GitHub
Translates Nate's design language into dev-ready prompts for Claude Code. Trigger when Nate describes a visual feeling, concept, or intention ("feels too heavy", "needs more breathing room", "should feel editorial", "like a newspaper", "more Margiela"), references a Figma layer or component, or pastes a description and wants it turned into a Claude Code prompt. Also trigger on "translate this", "how do I say this in code", "turn this into a prompt", "help me prompt Claude Code". Output both a plain-language interpretation AND a ready-to-paste Claude Code prompt.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 308,232 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.
In this repository8 other files it gives its agents.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.