- name
SKILL.md
Файл навыка остаётся в репозитории издателя.
Вставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add Innei/ryugi --skill interface-craft -a cursor -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add Innei/ryugi --skill interface-craft -a claude-code -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add Innei/ryugi --skill interface-craft -a codex -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add Innei/ryugi --skill interface-craft -a grok -yОтправьте скопированное сообщение в чат Grok Bot. Бот загрузит этот SKILL.md с GitHub и добавит его к навыкам, общим для всех ваших ботов.
Install this skill: https://github.com/Innei/ryugi/tree/HEAD/skills/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.
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.
Infer from the product, brief, current screen and user decisions. Read direction when deriving a new direction; it contains the shape of the answer and one worked example.
Write these five lines before drawing or editing. They are decisions, not questions for your human partner.
The project's tokens, brand and accepted direction win. When they do not exist, tokens 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.
Read signs and list what you find, one line each, as location — sign — fix. Classify each finding:
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.
Read evaluation. 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.
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.
Adapted from Unslop by Damir Sokolovsky (CC BY 4.0): the audit signs and token tables derive from it, generalized to creation, review and design-system-aware workflows.
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 refin
---name: interface-craftdescription: Use when a visible product interface needs design judgment, including UI mockups during brainstorming, landing…---# skills/interface-craft/SKILL.mdОбзор
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.
FAQ
Скачайте skills/interface-craft/SKILL.md у издателя или скопируйте путь и откройте репозиторий. PlugMCP только показывает навык в каталоге и не хранит файл.
Издатель хранит его в https://github.com/Innei/ryugi.
Claude, Cursor, Codex и Grok Build могут читать SKILL.md, который вы добавляете из репозитория издателя. Grok Bot устанавливает его, когда вы отправляете в чат ссылку на папку навыка на GitHub.