Apply vintage typography and high-contrast palette rules to UI components.
npx skills add https://github.com/bergside/awesome-design-skills --skill retro-bergside
Please help me install this Agent Skill. Skill: retro Source: https://github.com/bergside/awesome-design-skills/tree/main/skills/retro Command: npx skills add https://github.com/bergside/awesome-design-skills --skill retro-bergside
Retro design guidance helps teams consistently implement vintage-inspired typography and high-contrast retro color palettes without breaking accessibility or interaction standards.
Use the retro skill to generate a complete UI guideline pass for your component set, then review the output against the token, accessibility, and QA check requirements.
High-intent search queries and answers about installing and using this skill.
To build an accessible retro UI design system, apply vintage typography and high-contrast color palette rules alongside keyboard-first interactions and visible focus-visible states. This enforces WCAG 2.2 AA compliance while standardizing component implementation.
Essential design tokens for a high-contrast vintage color palette include primary, secondary, success, warning, danger, surface, and text. These token-anchored foundations ensure consistent retro visual systems and testable quality gates.
Standardize component states for retro buttons, inputs, cards, modals, and navigation by applying opinionated do/don't constraints and explicit interaction state rules. This token-aligned approach ensures consistent spacing and labeling across your web app.
Yes, you can apply vintage typography tokens to UI components while maintaining keyboard-first accessibility by enforcing visible focus-visible states and semantic token rules. This combination meets accessibility standards without sacrificing the retro aesthetic.
The quickest way to generate UI guidelines for a retro component set is to run a complete design pass applying vintage typography and high-contrast palette rules. Review the output against token, accessibility, and QA check requirements.
High-contrast retro interface components fail accessibility quality gates when they lack explicit interaction states, visible focus-visible states, or semantic tokens. Enforce WCAG 2.2 AA expectations and keyboard-first behavior to pass do/don't compliance checks.
hulusi-tuncEstablish naming conventions for design elements, components, and tokens.
johnlindquistManage design tokens and export them to CSS, JSON, and Tailwind config.
bergsideGenerate design-system guidance for playful landing page UI with WCAG 2.2 AA constraints.
ChildoftheVibeGenerate CSS tokens and layout rules for minimalist bento-grid UI systems.
