If “build me a beautiful UI” were a complete brief, this series would be a shorter list. The miss these repositories target is small: the wrong easing, a phone layout that still behaves like a desktop site, a landing page any company could publish, a color described in words and never stored as a value.
Those are the decisions that make a generated interface feel generic. The next three repositories write down a designer’s habits, a refusal of the default page, and a file an agent can read exactly.
What they add is encoded expertise. Encoding it does not retire the person who knows whether it applies.
-
Skills for Designers and Engineers. Emil Kowalski’s guidance on animation choices, including places that should stay still, plus performance, mobile behavior, and a pass that tries to break the UI with long names, empty lists, and awkward data. The repository is explicit that these skills come from practice and that an agent does not replace that practice.
-
Hallmark. Page structure, visual direction, anti-pattern review, and redesign. The README describes forty-eight themes, and a custom direction when you decline the catalog. The gates file lists 39 Floor gates, 50 Reflex gates, and 26 Finish checks. The Floor includes contrast, focus, and reduced motion. Clearing that list is not a complete usability or accessibility assessment.
/hallmark auditreports. It does not ship the product for you. -
Google DESIGN.md. A format specification published under google-labs-code: exact tokens, plus prose for why those values exist, with a linter, a diff, and exporters for Tailwind and W3C design tokens. Awesome DESIGN.md is a separate project, a collection of site analyses written as DESIGN.md files. This repository does not turn those analyses into official brand systems, and it is not Google’s corporate design system. One document does not hold every product decision. The spec is marked alpha.
Use craft guidance when the details feel unfinished. Use Hallmark when the risk is the same landing page in a new palette. Use a token file when the agent needs the value and the reason, and a person still decides what the product is for.
Review starting point, not a release standard:
- Does it fit the user’s task and the product’s design system?
- Does it work across the required devices and browsers?
- Can people use it with a keyboard and reduced motion?
- Have you checked loading, empty, error, and long-content states?
- Have you reviewed performance, dependencies, and licensing?
Exact values make an agent consistent. Your team still decides whether the product is the right one.
Source: github.com/emilkowalski/skills — README. github.com/Nutlope/hallmark — README and skills/hallmark/references/gates.md (39 Floor, 50 Reflex, 26 Finish). github.com/google-labs-code/design.md — README. Retrieved 23 October 2026.
#AgentSkills #ProductDesign #DesignSystems