ヴィンテージなUIを作る（vintage）

---
name: vintage
description: 1950s-1990s nostalgia with skeuomorphic touches, grainy textures, retro color palettes, and pixel-style typography.
license: MIT
metadata:
  author: typeui.sh
---

<!-- TYPEUI_SH_MANAGED_START -->
# Vintage Design System Skill (Universal)

## Mission
You are an expert design-system guideline author for Vintage.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.

## Brand
Vintage design style revives aesthetics from the 1950s–1990s, blending nostalgia with modern functionality through skeuomorphic elements, grainy textures, and retro color palettes

## Style Foundations
- Visual style: clean, vintage, retro
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Silkscreen, display=Silkscreen, mono=JetBrains Mono | weights=400, 700
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#008080, secondary=#C0C0C0, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#C0C0C0, text=#000000
- Spacing scale: 4/8/12/16/24/32


## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states

## Writing Tone
concise, confident, helpful

## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit

## Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels

## Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.

## Guideline Authoring Workflow
1. Restate the design intent in one sentence before proposing rules.
2. Define tokens and foundational constraints before component-level guidance.
3. Specify component anatomy, states, variants, and interaction behavior.
4. Include accessibility acceptance criteria and content-writing expectations.
5. Add anti-patterns and migration notes for existing inconsistent UI.
6. End with a QA checklist that can be executed in code review.

## Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist

## Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).

## Quality Gates
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
- Every accessibility statement must be testable in implementation.
- Prefer system consistency over one-off local optimizations.
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.

## Example Constraint Language
- Use "must" for non-negotiable rules and "should" for recommendations.
- Pair every do-rule with at least one concrete don't-example.
- If introducing a new pattern, include migration guidance for existing components.

<!-- TYPEUI_SH_MANAGED_END -->

---

# DESIGN.md

---
name: Vintage
colors:
  primary: "#008080"
  secondary: "#C0C0C0"
  success: "#16A34A"
  warning: "#D97706"
  danger: "#DC2626"
  surface: "#C0C0C0"
  text: "#000000"
  neutral: "#C0C0C0"
typography:
  h1:
    fontFamily: "Silkscreen"
    fontSize: 2rem
  body-md:
    fontFamily: "Silkscreen"
    fontSize: 1rem
  label-caps:
    fontFamily: "JetBrains Mono"
    fontSize: 0.75rem
  sourceScale: "12/14/16/20/24/32"
  weights: "400, 700"
rounded:
  sm: 4px
  md: 8px
spacing:
  sm: 4px
  md: 8px
  sourceScale: "4/8/12/16/24/32"
---

## Overview

1950s-1990s nostalgia with skeuomorphic touches, grainy textures, retro color palettes, and pixel-style typography.

## Style Foundations

- **Visual style:** clean, vintage, retro
- **Typography scale:** 12/14/16/20/24/32
- **Typography fonts:** primary=Silkscreen, display=Silkscreen, mono=JetBrains Mono
- **Typography weights:** 400, 700
- **Color palette:** primary, neutral, success, warning, danger
- **Spacing scale:** 4/8/12/16/24/32

## Colors

- **Primary (#008080):** Token from style foundations.
- **Secondary (#C0C0C0):** Token from style foundations.
- **Success (#16A34A):** Token from style foundations.
- **Warning (#D97706):** Token from style foundations.
- **Danger (#DC2626):** Token from style foundations.
- **Surface (#C0C0C0):** Token from style foundations.
- **Text (#000000):** Token from style foundations.
- **Neutral (#C0C0C0):** Derived from the surface token for official format compatibility.

---

## 出典

このスキルは公開されているものを、ライセンスに従って転載したものです。
本文は原文のまま、改変していません（SKILL.md と DESIGN.md を続けて綴じてあります）。

- 作者: typeui.sh
- 出典: https://github.com/bergside/awesome-design-skills/tree/main/skills/vintage
- 収録: https://github.com/bergside/awesome-design-skills
- ライセンス: MIT License

最新版は出典元を確認してください。