- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add smokeeaasd/flawless-ui-ux --skill skill-2.0.0 -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add smokeeaasd/flawless-ui-ux --skill skill-2.0.0 -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add smokeeaasd/flawless-ui-ux --skill skill-2.0.0 -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add smokeeaasd/flawless-ui-ux --skill skill-2.0.0 -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/smokeeaasd/flawless-ui-ux/tree/HEAD/tests/fixtures/skill-2.0.0From the publisher
Translate product intent into specific visual decisions. Quality combines functioning behavior, accessibility, identity, and finish. Build richness through hierarchy, proportions, rhythm, imagery, and detail suited to the product.
Use the requested platform and stack, preserving appropriate navigation, input, and accessibility conventions. Examples do not prescribe a sector, device, or aesthetic.
Inspect the requested target, surrounding components, content, and available assets. Establish what the user needs to understand or do, what may change, and which facts and behaviors must remain. Ask only when an unresolved fact materially changes the scope, identity, or outcome.
Reuse relevant product and design documentation before reopening decisions. For continuity across tasks, consult project context; keep useful decisions in Markdown using the project's existing documents. Small interventions do not require new records.
Make a coherent composition from the actual material: choose what leads, how supporting information relates, and how the main action works. Select typography, color, density, imagery, and detail together, considering readability at the intended viewing scale from the start. Carry that treatment through the whole target. A short brief still permits confident design choices; routine work can proceed without a written brief, concept presentation, or separate planning artifact.
Use the project's stack and implement the requested behavior. Add interface elements because the task needs them, rather than creating extra product features to fill a conventional layout.
For new interfaces and broad redesigns, read Direction and apply its essential composition exploration before implementation. Use it for other new visual-direction decisions as needed. For focused existing work, the entry point and project context may suffice. Otherwise read the relevant section below when it answers a concrete question; this table is not a reading sequence. Reuse material already read.
Observe the primary task, affected states, and relevant device/window sizes and input methods with available tools. Check hierarchy, readable content, navigation, and clipping as well as calculations and controls.
Before delivering a creation or redesign, read and perform the final pattern pass on the completed target. For refinement, apply its affected checks within the authorized scope. Inspect actual copy and icons in source even when rendering is unavailable; correct observed repetition rather than merely claiming a review.
Measure contrast against actual backgrounds. Run relevant project checks and meaningful tests; repeat affected checks after corrections. If rendering is unavailable, continue useful source work and state the limit. Static checks cannot establish visual quality.
When the local CLI covers the target sources or browser-rendered interface, use executable inspection for scoped evidence and verification. Native widgets need suitable platform/project tools; an empty web scan does not verify native behavior. Read actual coverage; contextual signals still require judgment.
Finish when the requested result is complete and material issues within scope are resolved, or report the specific blocker. Preserve explicit choices and product facts; identify sample data and never invent credibility claims. Report the result, checks actually performed, and remaining limits concisely.
Create, redesign, refine, or review web, native mobile, and desktop interfaces with product-specific visual design and usable interactions.
---name: flawless-ui-uxdescription: Create, redesign, refine, or review web, native mobile, and desktop interfaces with product-specific visual…---# tests/fixtures/skill-2.0.0/SKILL.mdFAQ
Download tests/fixtures/skill-2.0.0/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/smokeeaasd/flawless-ui-ux.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.