---
name: sistema-diseno-dramatico
description: Guía de sistema de diseño para el estilo visual 'Dramatic': alto contraste, composiciones teatrales, tipografía bold y paleta oscura inmersiva. Define tokens, reglas de componentes y criterios de accesibilidad WCAG 2.2 AA.
license: MIT
metadata:
  id: 011a38b3
  slug: sistema-diseno-dramatico
  titulo: "Sistema de Diseño Dramático"
  servicio: Branding-Diseno
  categoria_recurso: Imagen-Diseno
  tipo: referencia
  nivel: intermedio
  idioma: es
  idioma_original: en
  acceso: gratis
  precio_eur: 0
  plataformas: [Cualquier plataforma web o de diseño UI]
  dependencias: []
  licencia: { spdx: MIT, redistribuible: true, uso_comercial: true }
  fuente:
    repo: bergside/awesome-design-skills
    url: https://github.com/bergside/awesome-design-skills/tree/main/skills/dramatic
    commit: 53c9fe6
    autor: bergside
    nombre_original: dramatic
    duplicados_en: []
  seguridad: { veredicto: seguro, riesgo: bajo, escaneado: "2026-06-14", motor: "grep-estatico+auditor-llm" }
  ficha:
    que_hace: "Proporciona una guía de sistema de diseño opinionado para el estilo visual dramático (alto contraste, layouts teatrales, tipografía impactante)."
    como_lo_hace: "Define tokens de color y tipografía, reglas de componentes por estados, criterios de accesibilidad y un checklist de QA para usar directamente en revisiones de código."
  content_hash: "011a38b3fabe4d4ccc0714d8aaabc8637539c2446756863b02008c5c50d432ce"
  version: 1.0.0
---

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

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

## Brand
Dramatic design style is a trend characterized by high-contrast visuals, bold, unconventional layouts, and immersive, theatrical experiences designed to grab user attention.

## Style Foundations
- Visual style: modern, clean, high-contrast
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Outfit, display=Outfit, mono=JetBrains Mono | weights=400, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#8B5CF6, secondary=#F43F5E, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#09090B, text=#FAFAFA
- 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 -->