agentleFS
doodledooddoodledood/manifest-dev/.claude/skills/design-principles/SKILL.md

design-principles

Skill78 starsChanged 5 months agoMITView on GitHub

Design principles for manifest-dev: how its maintainer wants the visual and interaction design guidance the plugin ships, and the surfaces it builds for people to look at, done, and why. Use before planning, writing, building or reviewing the design skills, their guides and instruments, or a page, canvas or draft a skill renders for a person.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use test-driven-development.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    test-driven-development

    Use when implementing any feature or bugfix, before writing implementation code

    Also in 3 projects that use this

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 23 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
  1. Distinctive:

    Before calling design work done, check it against these principles from a fresh start — a new session, or a reviewer who did not do the …

    line 12

“Common” is measured: kept by at least 6 in 10 of the 23 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Edit rule: each line is a principle with its reason and when it yields. Decisions go to the decision records, rules a check can hold go to the check, and a line is added only on a person's yes, after sharpening an existing line is ruled out.

  • Design guidance takes its direction from the artifact's subject and the person's moment — who is there, what they came to do, how long they stay — and lets that set the structure and how strong the feeling is; it ships no house style, and a guide describes how a kind of work is used or what a feeling is made of, never a look to apply by kind — catalogs pulled unrelated subjects to one look, and guidance blind to the work produced well-made artifacts arranged wrongly for it. Yields to explicit requirements, an existing design system, and a strength the request names.

Before calling design work done, check it against these principles from a fresh start — a new session, or a reviewer who did not do the work. Fix what departs unless the person chose the departure, and check again only after a fix, until a check finds none. Name each departure kept, with the principle and why.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.