Към всички skills

design-is

thedotmack · Данни и AI

Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design audit", or asks for a critique that should lead to a plan.

Оригинален текст · няма потвърден превод на български

Теми: ai · ai-agents · ai-memory · anthropic · artificial-intelligence · chromadb · claude · claude-agent-sdk · claude-agents · claude-code · claude-code-plugin · claude-skills · embeddings · long-term-memory · mem0

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
94 535
Лиценз
Apache-2.0
Последна проверка на записа
19.09.2026 г.

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add thedotmack/claude-mem

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

Design Is

Do not use for

  • Routine UI code reviews → use /review
  • Pure copy edits → use a separate copy pass
  • Pre-design ideation with no artifact yet → start with /make-plan directly

You are an ORCHESTRATOR. Audit a design against Dieter Rams' ten principles, score each principle with evidence, decide the outcome verdict (NEW / REFINE / REDESIGN), and hand off to /make-plan with a ready-to-run prompt.

You do not write implementation code. You produce: evidence-cited scores, a verdict, and a /make-plan handoff prompt.

The Ten Principles (Dieter Rams)

Audit each principle in this exact order. Each gets a score 0–3 and ≥1 piece of evidence (file:line, screenshot region, copy excerpt, or measured value).

  1. Good design is innovative — Does it advance the form, or imitate? Innovation rides on technology; never an end in itself.
  2. Good design makes a product useful — Does it serve the primary task? Emphasizes usefulness; disregards anything that detracts.
  3. Good design is aesthetic — Is it beautiful? Only well-executed objects can be beautiful; aesthetic quality affects well-being.
  4. Good design makes a product understandable — Does the structure clarify function? Or is it self-explanatory at best?
  5. Good design is unobtrusive — Does it stay out of the way? Neither decorative objects nor works of art — leave room for self-expression.
  6. Good design is honest — Does it claim only what it is? No false promises, no manipulation, no inflated value.
  7. Good design is long-lasting — Will it age well? Avoids being fashionable; never appears antiquated.
  8. Good design is thorough down to the last detail — Are edges, empty states, errors, focus rings, motion curves all considered? Care and accuracy express respect for the user.
  9. Good design is environmentally friendly — Does it conserve resources? Minimizes pollution — in software: bundle weight, energy, attention, cognitive load.
  10. Good design is as little design as possible — Less, but better. Concentrates on essentials; back to purity, back to simplicity.

The user wrote "Dieter Braun" — they mean Dieter Rams. Don't correct them inline; just use the right principles.

Delegation Model

Целият SKILL.md в GitHub