- 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 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
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 폴더 링크를 보내면 설치합니다.