Skip to content
Skills Library
Design & UX · Planning

interface-craft

/interface-craft

Use when a visible product interface needs design judgment, including UI mockups during brainstorming, landing and marketing pages, visual direction exploration, reviewing an existing screen, or refining a prototype that feels generic or inconsistent.

Author
innei ↗
Repository
ryugi ↗
Licence
MIT
Last repository change
14.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 14.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a visible product interface needs design judgment, including UI mockups during brainstorming, landing and marketing pages, visual direction exploration, reviewing an existing screen, or refining a prototype that feels generic or inconsistent.

Original author description

Use when a visible product interface needs design judgment, including UI mockups during brainstorming, landing and marketing pages, visual direction exploration, reviewing an existing screen, or refining a prototype that feels generic or inconsistent.

How it works

  1. Pick the mode
  2. The five lenses
  3. Values only where nothing exists
  4. Audit before judging
  5. Fix in ordered passes
  6. Check what can fail
Original SKILL.md headings · 64 lines, 785 words
SKILL.md preview
---
name: interface-craft
description: Use when a visible product interface needs design judgment, including UI mockups during brainstorming, landing and marketing pages, visual direction exploration, reviewing an existing screen, or refining a prototype that feels generic or inconsistent.
---

# Interface Craft

A design technique, not a mandatory extra phase. Two halves, in order: set a direction from the product, then check the screen against things that can fail. Nothing here is a house style; the project's system and accepted decisions outrank every default below.

**Integration:** Project design system and explicit decisions take priority. Ryugi:brainstorming owns requirements and approval; ryugi:artifacts owns visual presentation; ryugi:verifying owns the human verdict for built UI. This skill adds **no new approval gate**.

## Pick the mode

| Mode       | When                                                                      | What to do                                                                                             |
| ---------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Create** | A new surface or a new visual direction, especially with no design system | Write the five direction lines, then apply [tokens](references/tokens.md) and the passes while drawing |
| **Repair** | An existing screen, with defects or with a request to improve it          | Audit with [signs](references/signs.md), report findings with locations, fix only the agreed scope     |
| **Edit**   | One exact visual change is specified                                      | Make that change. No audit, no direction, no questions                                                 |

Not a UI task: backend work, architecture diagrams, pure copy, generic documents that happen to have a visual format.

Landing pages, marketing and pricing pages, onboarding, empty states, settings and emails are product interfaces too; use this skill for them.

## The five lenses

Infer from the product, brief, current screen and user decisions. Read [direction](references/direction.md) when deriving a new direction; it contains the shape of the answer and one worked example.

1. **Product:** Who uses this interface, for which job, under what conditions?
2. **Character:** Which two or three specific qualities should it communicate? Reject _modern_, _clean_, _premium_, _sleek_: they describe every template.
3. **World:** What materials, places, objects or metaphors actually belong to this product? This sets the tint of the neutrals, the accent and the visual.
4. **Moments:** Where does richness concentrate? One or two places where the product itself is shown well; not a mandatory hero.
5. **Signature:** One small repeatable detail only this product would have. Omit it rather than invent one.

Write these five lines before drawing or editing. They are decisions, not questions for your human partner.

## Values only where nothing exists

The project's tokens, brand and accepted direction win. When they do not exist, [tokens](references/tokens.md) gives starting values: a 4px spacing grid, nested radius math, a type scale, three text roles, one accent, one easing curve. Adapt the tint and accent from the **World**; never copy an example palette verbatim.

## Audit before judging

Read [signs](references/signs.md) and list what you find, one line each, as `location — sign — fix`. Classify each finding:

- **Objective defect** — clipped or covered text, overlap, broken alignment, contrast below 4.5:1, a control that does not work.
- **Design hypothesis** — hierarchy, density, or a missing moment. Worth proposing, not fixing unasked.
- **Preference** — taste. Never a bug.

If the screen is already effective, say so and stop, with at most two or three exact refinements. Do not redesign to justify the skill.

## Fix in ordered passes

Read [evaluation](references/evaluation.md). Apply one pass across the whole screen before starting the next, in this order: **spacing → color → icons → copy → type → layout → details → visuals → motion.** Spacing first because it changes how everything reads; copy before type and layout because headline length decides size and position; visuals and motion last because they must fit a screen that already works.

## Check what can fail

Render the result when the screen is code that can be rendered, at least at desktop width and one narrow width. At most three renders per run. Compare the render with the audit list and with the direction; a claim about visual quality without a render is unverified, so say so.

- [ ] Every audit finding is answered, and each fix names its location
- [ ] No text is covered, clipped or overlapped at either width
- [ ] Spacing values sit on the scale, and equal things have equal sizes
- [ ] One neutral ramp, three text roles, one accent with readable contrast
- [ ] Figures use tabular numbers and one format across the screen
- [ ] No prices, logos, customer names or claims that the user did not supply
- [ ] Nothing from the signs list survives in the touched area
- [ ] **Name-swap test:** if another product's name replaced this one, would the screen still fit? If yes, push the copy, visual and signature detail harder

Adapted from [Unslop by Damir Sokolovsky](https://github.com/heydamir/unslop) (CC BY 4.0): the audit signs and token tables derive from it, generalized to creation, review and design-system-aware workflows.
Files in this package (5)
  • SKILL.md 5 KB
  • references/direction.md 3 KB
  • references/evaluation.md 4 KB
  • references/signs.md 9 KB
  • references/tokens.md 7 KB

Versions

RepositoryScoreLicence
This page · innei/ryugi100MIT
ios3kov/codex-skills100MIT
The-Utopia-Studio/skills100Apache-2.0
mikemoller/premium-ui90MIT
cbrock84/headcount90MIT

Database snapshot: 13.11.2026 · package version 9e94d460e11f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100interface-design
    Craft-first interface design for dashboards, admin panels, SaaS apps, tools, settings pages, data interfaces, and interactive products. Use when designing, building, reviewing, auditing, or refining product UI where visual craft, layout hierarchy, tokens, states, visual…
  • 100reviewing-interface-quality
    Use when asked to review, critique, audit, or improve an existing user interface — "review this UI", "why does this look generic", "make this more polished", "design feedback", "does this look AI-generated", "audit this page". Also use as the final gate before shipping any…
  • 100nuxt-frontend-design
    Build or polish Nuxt UI v4+ pages and design systems. Use for landing pages, dashboards, tokens, motion, or generic-looking UX.
  • 100design-craft
    Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique. Use for new screens, landing pages, redesigns, typography/layout work, or UI that feels generic or AI-generated. For small fixes, preserve…
  • 100distinctive-ui
    Creative-director workflow for designing or redesigning an interface with an identity that could only belong to THIS product — not a generic AI template. Runs the full phased process (intake → brief → three art directions → build → real-browser visual review → honest handover)…
  • 90interface-design
    Craft-first 介面設計基礎,用於儀表板、後台、管理介面、工具與資料密集型產品 UI。設計或檢視這類介面的版面層級、間距節奏、深度策略、色彩角色、狀態覆蓋、設計系統一致性時使用。搭配 init / extract / audit / status 指令與 .interface-design/system.md token 檔運作。不處理行銷頁、landing page、品牌視覺,那些另找設計工具。

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.