- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add rizqinrr/viserys-agent --skill get-design -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add rizqinrr/viserys-agent --skill get-design -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add rizqinrr/viserys-agent --skill get-design -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add rizqinrr/viserys-agent --skill get-design -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/rizqinrr/viserys-agent/tree/HEAD/skills/get-designVom Herausgeber
Run a product-grounded UI design workflow. The goal is not merely polished CSS: it is an interface with a clear job, a recognizable visual point of view, content that carries the design, hierarchy that reflects user priorities, and interaction states that work in the real usage scene.
For new users, get-design acts as an interactive design partner: it asks targeted questions about the product feel, audience, and constraints, derivations of anti-AI-slop visual systems, and outputs a concrete, executable docs/design.md (or design.md) specification covering design tokens, layouts, component states, and accessibility standards.
This skill is a native Viserys adaptation of the Impeccable design playbook and anti-slop catalog. It contains no runtime dependency on Impeccable, its CLI, hooks, binaries, or external detector. The rulebook is advisory evidence; a deliberate choice can override a default when the product brief, brand, platform, or accessibility requirement earns it.
docs/design.md.docs/design.md.When NOT to use: Pure backend changes, non-visual CLI tools, or algorithmic database work with no user-facing interface.
Choose the route from the user's request. If the request is ambiguous, ask before editing. Load routing for mode selection and the context-aware menu. Load the complete anti-AI-slop catalog for every mode, including new, shape, critique, audit, focused refinements, document, and extract; it is the baseline before any design decision, edit, critique, or audit. For deep review use critique or audit; for a focused refinement use the matching section in focused playbooks.
Natural Language & Visual Guidance: Converse in the user's language (Indonesian or English). If the user says "saya buta desain, tolong arahkan" (I don't know design, please guide me), do not ask them for hex codes or typography scale ratios. Present 2–3 cohesive visual archetypes (e.g. Utilitarian High-Density, Modern Clean Monochrome, or Warm Crafted) with concrete explanations of why each fits their audience.
Strict Anti-AI-Slop Standard: Deliberately reject category clichés: no purple/cyan gradient text, no floating cards with massive blur shadows, no identical 3-card repetition, and no giant rounded pills eating up dense screen real estate.
Complete State Lifecycles: Never output a design that only looks good in a static screenshot. Every interactive element in docs/design.md must document its full state lifecycle (Default, Hover, Focus-visible ring, Active, Disabled, Loading skeleton, Empty state, and Error flash).
Context → establish product truth, audience, task, platform, constraints, existing visual authority, and the evidence available.
Direction → choose the surface mode and visual direction before implementation.
Build → implement the chosen direction as a coherent system, not as disconnected decorations.
Inspect → review the whole path at representative viewports and states.
Finish → fix the highest-impact issues, verify again once, and document durable system decisions.
new or shapePRODUCT.md, DESIGN.md, surface briefs, existing tokens, components, copy, assets, and neighboring flows when present.shape, present the direction and stop before implementation. If building, continue with the chosen direction.critiqueQuestions skipped: fewer than 3 priority issues.auditpolishlayout: fix spatial hierarchy, rhythm, grouping, density, optical alignment, and responsive composition.typeset: fix type character, hierarchy, measure, line-height, weight, wrapping, localization expansion, and font loading.colorize: establish palette roles, contrast, semantic states, theme behavior, and intentional color at page scale.animate: add one or a few purposeful moments tied to state, relationship, or feedback; preserve reduced motion and visible defaults.bolder: amplify a bland but coherent design without replacing its product truth.quieter: reduce noise, competing emphasis, glow, decoration, and unnecessary motion while retaining personality.distill: remove clutter, duplicate explanation, redundant chrome, and competing actions.clarify: rewrite labels, instructions, errors, empty states, and calls to action around the user's next decision.adapt: preserve the world while adapting composition, interaction, and density to another viewport or platform.harden: handle loading, empty, error, success, disabled, permission, offline, slow, long-content, missing-content, and localization states.onboard: design first-run, activation, empty-state, and learning-by-doing flows around the first useful result.optimize: measure and improve UI performance without adding speculative micro-optimizations.delight: add a product-specific, useful moment rather than decorative novelty.overdrive: push ambition only when the brief permits it; keep performance, clarity, accessibility, and product truth intact.documentDESIGN.md only after checking whether one already exists. If it exists, ask whether to refresh, overwrite, or merge.extractdocs/design.md SpecificationWhen completing a design interview or visual direction pass, commit the agreed direction to docs/design.md (or design.md) so downstream task planning has a concrete reference:
# Design Specification: [Product/Surface Name]
## 1. Visual Thesis & Audience
- **Product Job:** <What user task does this surface accomplish?>
- **Audience & Scene:** <Who is using this, and in what context?>
- **Aesthetic Thesis:** <What default templates or AI clichés does this design refuse?>
## 2. Design Tokens & Visual World
- **Color Palette:**
- Surface & Background: <tokens, contrast verified>
- Text & Hierarchy: <primary text, muted text with >= 4.5:1 contrast>
- Brand & Semantic: <primary action, error, warning, success>
- **Typography:**
- Display & Headings: <font family, scale, weights>
- Body & Labels: <font family, line height, measure 65-75 chars>
- **Spacing & Elevation:** <modular spacing scale, single depth strategy, border radii>
## 3. Layout & Responsive Breakpoints
- **Mobile (375px):** <single column, bottom-anchored or thumb-friendly controls, touch targets >= 44px>
- **Tablet (768px):** <adaptive grid, responsive navigation>
- **Desktop (1280px+):** <full composition, generous negative space>
## 4. Component Hierarchy & Interactive States
- State coverage: default, hover, focus-visible (high contrast outline), active, disabled, loading, empty, and error.
## 5. Micro-Interactions & Motion
- Purposeful transitions (150-250ms ease-out), full `@media (prefers-reduced-motion)` fallback.
## 6. Accessibility & Performance Bar
- WCAG 2.1 AA compliant, full keyboard tab order, font preloading, layout shift prevention (CLS).
Every UI route must account for default, hover, focus-visible, active, disabled, loading, error, empty, success, and permission states where relevant. Verify keyboard focus, semantic structure, screen-reader names, contrast, responsive composition, touch targets, overflow, console errors, image loading, and reduced motion.
DESIGN.md; task-specific strategy remains in a surface brief.../../references/accessibility-checklist.md for the shared accessibility baseline.This skill is a native Viserys adaptation of the Impeccable design guidance and anti-pattern catalog by Paul Bakaus, derived from https://github.com/pbakaus/impeccable and https://impeccable.style/. The upstream work is Apache-2.0 licensed. Viserys does not include the upstream runtime, binary, hooks, detector, or extension.
Interviews users on UI/UX aesthetics, establishes bespoke visual direction, removes generic AI aesthetics, and produces a complete design specification document at docs/design.md. Use when a user asks
---name: get-designdescription: Interviews users on UI/UX aesthetics, establishes bespoke visual direction, removes generic AI aesthetics, and…---# skills/get-design/SKILL.mdÜbersicht
Interviews users on UI/UX aesthetics, establishes bespoke visual direction, removes generic AI aesthetics, and produces a complete design specification document at docs/design.md. Use when a user asks to design a UI, dashboard, landing page, or mobile app, establish visual direction, critique AI slop, or specify UI components, color palettes, typography, responsive layouts, accessibility, and interaction states.
FAQ
Laden Sie skills/get-design/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/rizqinrr/viserys-agent.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.