hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-design
hyper-design
Verified[Hyper] Use this skill when the user wants interface design work that must not look AI-generated - designing a new screen, page, or component, restyling an existing UI, building faux product UI for a hero, feature card, or demo, or auditing, cleaning, or verifying generic template patterns in an interface - driven by a written design direction, a numeric craft floor, static detection, and evidence-separated review, with briefs and reports saved under `.hyper/design/[slug]/`. Do not use it for backend or data work with no visual surface, accessibility-only or performance-only QA, brand strategy with no interface, or a reusable skill folder.
rules/design-direction.md
View on GitHub# Design Direction
Read in `design`, `restyle`, `mockup`, and `brief-only` before the first token or markup. This file owns the brief, the visitor mode, the reference, the token plan, the rejected alternative, and the anti-convergence checks. The result is saved as `.hyper/design/<slug>/brief.md` using `assets/design-brief-template.ko.md`.
## 1. Why Direction Comes First
A model asked for "a nice page" samples the most common page it has seen. Adjectives such as "modern, clean, premium" describe a region of that distribution, not a point in it; banning one default moves the output to the next default. The fix is to decide, in writing, before markup: who this is for, what it must do, what it looks like by reference to something specific, and which obvious option was rejected.
## 2. Brief Sentence
Write one sentence, and list the unknowns beside it:
> This [surface] helps [audience] do [task] in [situation]; it keeps [confirmed identity, data, and behavior]; [unknowns] are unverified.
Read the inputs in the order of `references/context-signals.md`. A user's own words about the look outrank everything in this file.
## 3. Visitor Mode
Choose one from the surface, not from the product:
| Mode | The visitor wants to | Ambition shows as |
|---|---|---|
| Persuade | be convinced to act (landing, pricing, signup) | one memorable idea, strong hierarchy, real proof |
| Operate | get a task done repeatedly (dashboard, settings, admin, forms) | precision, density that fits the data, familiar patterns, fast feedback |
| Read | understand content (docs, articles, reports) | measure, rhythm, typographic hierarchy, quiet chrome |
| Experience | enjoy or explore (portfolio, campaign, media) | an authored moment, motion or imagery with a cause |
Default to `Operate` for application UI. An Operate screen made "expressive" is a failure, not ambition.
## 4. Reference
Name one specific reference that carries the direction, with what to take from it:
- good: "a printed train timetable: tabular figures, hairline rules, one signal color reserved for delays"
- good: "the product's own onboarding illustration style and its existing 6px radius"
- weak: "minimal and modern", "like Linear", "Apple-like"
A product's existing system is always the first reference in `restyle`. Copying a famous product's look is not a direction; it lands on a different median. Never reproduce a third-party brand's logo, mark, or proprietary assets.
## 5. Token Plan
Convert the direction into named values before markup, in the project's styling system. Minimum set:
| Group | Decide |
|---|---|
| Color | neutral ramp (canvas, surface, raised, line, text strong/default/muted), one accent with its on-color, status colors; each text pair's contrast |
| Type | one or two families with fixed jobs and a reason tied to the reference; a role scale (display, heading levels, body, small, label) with size, line height, weight, tracking |
| Space | one scale (4px-based or the platform's own); section, group, and element gaps |
| Shape | a radius scale tied to element size; nested radius = outer radius minus padding |
| Depth | at most a few elevation steps; borders or shadows, chosen once |
| Motion | duration ladder and easing per job; what never animates |
| Icons | one set, one stroke weight, one size per context |
In `restyle`, map the existing tokens first and change the fewest tokens that move the whole surface. In a component-library project, edit the library's tokens before touching components. Values come from `rules/craft-floor.md` where the floor sets a number.
## 6. Layout Plan and States
- Give every section a job: hook, explain, prove, explore, convert, navigate, or operate. A section with no job is removed.
- Order content by importance; let hierarchy come from size, weight, space, and position before boxes and color.
- List the states the surface has and how each looks: default, hover, focus-visible, active, disabled, loading, empty, error, success, offline. A design that shows only the happy path is not done.
- Use real content or clearly marked placeholders; never invent proof.
## 7. Rejected Alternative
Record at least one obvious option that was considered and rejected, with the reason ("a three-card feature row, rejected: the product has one primary feature and two minor ones"). A brief with no rejected option has not made a decision.
## 8. Anti-Convergence Check
Before building, answer in `brief.md`:
1. Would this same plan be produced for any other product in this category? If yes, change the plan where the product differs.
2. Is any choice here a known default (see `references/anti-pattern-catalog.md`, including the second-wave defaults: cream background with an italic serif display, bento grid as the escape, emerald as the "safe" accent)? If yes, keep it only with a reason from the brief or the reference.
3. Does every expressive element (a gradient, a glow, a motion, an illustration) have a job from the brief? If not, remove it.
Removing a default must not produce an empty or lifeless result: keep feedback motion, real states, and hierarchy alive.
## 9. Korean Interfaces
When the product language is Korean, the plan also states the Hangul font stack, body size, line height, and line-breaking rule from `rules/craft-floor.md` §6.
## 10. Design Read, Dials, and Levers
Removing defaults leaves a void; liveliness is added on purpose. Before markup, write one Design Read line in `brief.md`:
> Reading this as: [page kind] for [audience], in a [visual language] style, visitor mode [mode], dials ENERGY [1-3] / RHYTHM [1-3] / MOTION [1-3].
| Dial | 1 (calm) | 2 (balanced) | 3 (bold) | It answers |
|---|---|---|---|---|
| ENERGY | quiet public-service or tool screen | confident product marketing | portfolio or campaign | How hard does the design say hello? |
| RHYTHM | uniform, predictable grid | consistent with a few breaks | asymmetric, mixed compositions | How much do sections differ? |
| MOTION | hover and state feedback only | transitions and one reveal | authored choreography | How much motion, and why? |
Three levels are used because a reviewer can check "uniform or varied" but cannot check "6 or 7". Starting points by visitor mode: Operate and Read 1 / 1 / 1, Persuade 2 / 2 / 1, Experience 3 / 3 / 2. A `DESIGN.md` line such as `Dial: ENERGY 2 / RHYTHM 3 / MOTION 1` is used as written.
Hit the dials with these levers:
- **One focal point per screen:** exactly one element is clearly the most important; the rest defer to it.
- **Hierarchical contrast:** size, weight, and color differ on purpose, not at random.
- **Whitespace as structure:** space separates groups and sets rhythm; it is never leftover.
- **One deliberate accent:** one color or gesture at the key moment. Zero accents is sterile; an accent everywhere is a default.
- **One identity motif:** one specific, repeated pattern, gesture, or typographic voice that makes the screen belong to this product.
How the dials are set:
1. Direction exists (`DESIGN.md`, a brand guide, the existing product in `restyle`, or a brief with mood): infer the dials from it.
2. Direction is open on a new product and the user can be asked: ask exactly one decisive question (for example "closer to a calm tool or to an expressive campaign?"), never a list of questions.
3. No direction and no chance to ask: label the result "draft without direction", use ENERGY 1 / RHYTHM 1 / MOTION 1, and do not present it as a deliverable.
Never fall back silently to a neutral, sterile default: flat near-white, thin gray borders, small radius, a generic font, and no identity is a failure, not a safe result.
## 11. Decision Reasons
Before calling the design done, write one line in `brief.md` for each major decision: color, layout, typography, spacing, containers (cards or not), and every illustration or icon set. A decision whose reason does not fit in one line is revisited. "It is the default" or "it looks modern" is not a reason. The swap test closes the list: if the logo and product name were swapped out, the design must still read as this product.
When `DESIGN.md`, a brand guide, or a user sample asks for a pattern that `rules/delivery-gate.md` forbids or caps, name the element and the line, ask once, and record the answer here. A bold palette or an unusual typeface is identity and is never questioned.
## Sources
> Checked 2026-11-07.
| Claim | Source |
|---|---|
| Models converge on statistically common choices, and banning one default moves them to another | <https://claude.com/resources/articles/improving-frontend-design-through-skills> (Anthropic, 2025-11-12) |
| Plan first, check "would this be produced for any similar page", and the brief's own words win | <https://github.com/anthropics/skills> (`frontend-design`, commit `2c5958e`) (Apache-2.0) |
| Design Read line, the three dials and their levers, "draft without direction" with dials 1 / 1 / 1, one decisive question, the sterile default as a failure, one-line decision reasons, the swap test, and the conflict protocol for a brief that asks for a named pattern | <https://github.com/miqdadbadjuber/anti-slop> (commit `9504989`, `antislop/SKILL.md` Part 3, R-31, R-37; MIT). The starting dials per visitor mode are this package's mapping. |
| Visitor modes Persuade, Operate, Read, Experience, chosen from the surface | <https://github.com/pbakaus/impeccable/tree/687bc381bc9091bf252c0a05303640561014a425/.agent/skills/impeccable> (Apache-2.0) |
| A specific reference carries more than adjectives; tokens and ordered sections for a `DESIGN.md` | <https://github.com/google-labs-code/design.md/tree/1ed38aa9dd4451b9039f9aeb9ed1d2579edafddf> (Apache-2.0) |
| Section jobs and a recorded rejected alternative | <https://github.com/changeroa/StyleGallery> |
| Editing a few library tokens changes the look of every screen | <https://freedesignmd.com/blog/shadcn-looks-generic> (2026-04-28) |
| Second-wave defaults: cream, italic serif, bento, emerald | <https://github.com/febbhav/signs-of-ai-design/tree/854b46f18dee5cc174d45cec8cd4f3142fe46984> (CC BY-SA 4.0), <https://solodesign.cc/blog/ai-design-slop-the-tells/> |
### Evidence grade
The procedure is this package's synthesis. The mechanism (convergence on common choices) is stated by a model vendor without a public measurement; the sources agree on the order of steps, not on a single checklist.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |