add design-elevation

Author: cuellarfr

README.md

@@ -78,6 +78,15 @@ Covers the operational side of design — how teams organize work, collaborate w
 
 `12 files` · `~6,000 lines`
 
+### Design Elevation
+Transforms functional visual outputs into polished, professional designs.
+
+Systematically elevates any visual output — dashboards, presentations, reports, web pages, data visualizations — from functional to refined. Built on Tailwind CSS as the canonical design token system, structured through Alla Kholmatova's functional patterns (what users interact with) and perceptual patterns (how the design feels) framework, with data visualization principles grounded in Edward Tufte's work.
+
+**Key references:** Elevation protocol (8-phase systematic process), data visualization principles (data-ink ratio, chartjunk elimination, small multiples, micro/macro readings, layering and separation, graphical integrity), chart selection framework (9 data relationships, 20+ chart types with specific rules), Tailwind-native color systems (categorical, sequential, diverging palettes), typography scales (7 modular scales with context guidance), spacing systems, grid systems (dashboard, magazine, presentation, document), design interrogation checklist (70+ questions across typography, color, layout, data visualization), technique catalog (25+ named techniques), design exemplars (Stripe, Linear, Apple, Swiss Style).
+
+`10 files` · `~3,800 lines`
+
 ## Installation
 
 ### Install all skills
@@ -165,6 +174,8 @@ These skills synthesize material from established books, frameworks, and standar
 - **The User's Journey** (Donna Lichaw) — Narrative arc, storymapping, concept/origin/usage stories, peak-end design
 - **User Story Mapping** (Jeff Patton) — Backbone, walking skeleton, vertical slicing, release planning
 - **UX Strategy** (Jaime Levy) — Competitive analysis, value innovation, funnel design, guerrilla research
+- **The Visual Display of Quantitative Information** (Edward Tufte) — Data-ink ratio, graphical integrity, chartjunk elimination, small multiples, data density, aesthetics and technique
+- **Envisioning Information** (Edward Tufte) — Escaping flatland, micro/macro readings, layering and separation, small multiples, color and information, narratives of space and time
 - **Writing Is Designing** (Michael J. Metts & Andy Welfle) — UX writing as design, usable/useful/responsible lenses, voice and tone, content critique
 
 ### Frameworks & Methodologies
@@ -187,6 +198,7 @@ These skills synthesize material from established books, frameworks, and standar
 - **Material Design 3** (Google) — Motion system, component specs, adaptive design, color system
 - **Polaris** (Shopify), **Carbon** (IBM), **Spectrum** (Adobe), **Lightning** (Salesforce) — Real-world design system references
 - **W3C Design Tokens Community Group** — Token format specification, type system, alias syntax
+- **Tailwind CSS** — Design token system (colors, spacing, typography, shadows, border radius)
 - **WCAG 2.2** — Web Content Accessibility Guidelines (A, AA, AAA conformance levels)
 - **WebAIM** — Million report data, contrast requirements, testing tools
 

design-elevation/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: design-elevation
+description: Comprehensive design elevation system that automatically transforms functional visual outputs into polished, professional designs. Use when creating ANY visual output including presentations (pptx), spreadsheets (xlsx), dashboards, reports, HTML artifacts, PDFs, web pages, or data visualizations. Applies systematic design thinking grounded in Tailwind CSS as the canonical design token system. Structures decisions through functional patterns (what users interact with) and perceptual patterns (how the design feels), following Alla Kholmatova's design systems framework. Triggers on ALL requests for visual content creation, ensuring outputs look hand-crafted rather than template-based.
+---
+
+# Design Elevation System
+
+This skill transforms functional visual outputs into polished, professional designs by applying systematic design thinking and refinement protocols.
+
+## Design Philosophy
+
+Follow Alla Kholmatova's design systems framework: every design decision is either a **functional pattern** (what users interact with — structure, layout, components) or a **perceptual pattern** (how it feels — color, typography, spacing, motion). Both layers must be intentional.
+
+### Canonical Design Tokens: Tailwind CSS
+
+All design decisions should map to **Tailwind CSS** as the shared design language. This means:
+- Colors from Tailwind's palette (gray, blue, emerald, amber, rose, violet, etc.)
+- Spacing from Tailwind's scale (1 = 0.25rem/4px, 2 = 0.5rem/8px, 4 = 1rem/16px, etc.)
+- Typography from Tailwind's type scale (text-xs through text-9xl)
+- Border radius from Tailwind's system (rounded-sm through rounded-2xl)
+- Shadows from Tailwind's elevation (shadow-sm through shadow-2xl)
+
+When writing CSS or HTML, use Tailwind utility classes. When defining design tokens for other formats (presentations, documents), translate Tailwind values into the target medium.
+
+## Activation Protocol
+
+When creating ANY visual output:
+
+1. **Start with function** — Create a working version first
+2. **Define functional patterns** — What does the user interact with? What's the structure? Use `references/grid-systems.md`
+3. **Define perceptual patterns** — How should it feel? What's the personality? Use `references/elevation-protocol.md`
+4. **Apply interrogation** — Question every default choice using `references/design-interrogation.md`
+5. **Elevate with techniques** — Use specific moves from `references/technique-catalog.md`
+6. **Polish data visualizations** — If any charts/data, apply `references/data-visualization.md`
+7. **Final check** — Ensure output feels hand-crafted, not templated
+
+## Functional Patterns by Output Type
+
+### For Presentations (PPTX)
+- Start with information hierarchy, not decoration
+- Apply grid systems from `references/grid-systems.md`
+- One idea per slide — if it needs two ideas, it needs two slides
+- Build complexity gradually across the slide sequence
+
+### For Dashboards & Data Visualization
+- Begin with data relationships, not chart types
+- Apply Tufte's data-ink ratio from `references/data-visualization.md`
+- Structure: KPI bar → Primary chart → Supporting charts → Detail tables
+- Use small multiples over multi-series charts when comparing 4+ categories
+- Default to Tailwind's gray scale for non-data elements; reserve color for data
+
+### For Documents & Reports
+- Structure with clear typographic hierarchy
+- Apply document grids from `references/grid-systems.md`
+- Use Tailwind's type scale for consistent sizing
+
+### For Web/HTML Artifacts
+- Design with responsive grid foundations (Tailwind's grid/flex utilities)
+- Use Tailwind utility classes directly
+- Apply animation restraint — `transition-all duration-200 ease-out` as default
+
+## Perceptual Patterns
+
+### Typography Excellence
+Tailwind's type scale is the foundation. Layer these refinements:
+- Use `font-sans` (Inter/system) for UI, `font-serif` for editorial
+- Apply `tracking-tight` for display text (text-3xl and above)
+- Apply `leading-relaxed` for body text
+- Use `font-semibold` for emphasis over `font-bold` — subtler hierarchy
+- For numbers in data contexts: always `tabular-nums`
+- Refer to `references/typography-scales.md` for scale selection
+
+### Color Sophistication
+Tailwind's palette is the source of truth:
+- Build from `gray` neutrals (not pure black/white)
+- `text-gray-900` for primary text, `text-gray-500` for secondary, `text-gray-400` for tertiary
+- `bg-white` or `bg-gray-50` for backgrounds — never stark white with stark black
+- Accent color: pick ONE from Tailwind's palette (blue, emerald, violet, etc.)
+- Apply 60-30-10: 60% neutrals, 30% secondary, 10% accent
+- Refer to `references/color-systems.md` for full system
+
+### Spatial Systems
+Tailwind's spacing scale provides the rhythm:
+- Base unit: `4` (1rem / 16px) for most UI
+- Component padding: `p-4` to `p-6` (16-24px)
+- Section spacing: `py-12` to `py-20` (48-80px)
+- Gaps: `gap-4` for tight, `gap-6` for comfortable, `gap-8` for spacious
+- Use Tailwind's spacing scale exclusively — no arbitrary values
+- Refer to `references/spacing-systems.md` for patterns
+
+### Visual Refinement
+- Border radius: `rounded-lg` as default for cards, `rounded-md` for buttons
+- Borders: `border border-gray-100` for subtle card separation
+- Shadows: `shadow-sm` for cards; reserve `shadow-lg` for modals/overlays
+- Hover states: `hover:bg-gray-50` for interactive elements
+- Transitions: `transition-colors duration-150` as default
+
+## Design Exemplars
+
+Use these as **illustrations of principles**, not as the system itself. The system is Tailwind + Kholmatova's framework. These exemplars show what excellence looks like:
+
+- **Stripe**: Gradient sophistication, precise type, technical content made beautiful
+- **Linear**: Dark mode mastery, keyboard-first, minimal and precise
+- **Apple**: Scale contrasts, photography integration, restraint as premium
+- **Swiss/International Style**: Grid discipline, objective clarity, mathematical spacing
+
+Refer to `references/design-exemplars.md` for specific techniques to borrow.
+
+## Critical Design Moves (Quick Reference)
+
+### Make it feel intentional
+- Replace `#000000` with `text-gray-900`
+- Replace `#ffffff` with `bg-gray-50` for backgrounds
+- Use `rounded-lg` consistently, not mixed radii
+- Apply one spacing scale throughout
+
+### Make it feel premium
+- Generous whitespace — `p-8` or `p-12` on hero sections
+- Tight tracking on display text: `tracking-tight`
+- Colored shadows: `shadow-blue-500/10` instead of black
+- Subtle borders: `border-gray-100` instead of `border-gray-300`
+
+### Make it feel clean
+- Remove borders and use whitespace to separate
+- Reduce to 2-3 type sizes maximum per view
+- Single accent color
+- `text-gray-500` for supporting text, not smaller type
+
+### Make data feel clear
+- Title states the finding, not the chart type
+- Direct labels over legends
+- Gray out non-essential series
+- `tabular-nums` on all number columns
+- Source attribution in `text-xs text-gray-400`
+
+## Resource Loading Priority
+
+For efficiency, load resources in this order:
+1. `references/elevation-protocol.md` — Always load first
+2. `references/data-visualization.md` — Load when any data/charts involved
+3. `references/technique-catalog.md` — Load for specific techniques
+4. `references/design-interrogation.md` — Load for quality checks
+5. Context-specific references (color, typography, spacing, grids) as needed
+
+## Output Standards
+
+Every delivered visual should:
+- Use Tailwind's design tokens consistently (or their translated equivalents)
+- Show clear functional patterns (structure, hierarchy, interaction)
+- Express coherent perceptual patterns (color, type, spacing, motion)
+- Demonstrate data integrity (if data is present, follow Tufte's principles)
+- Feel intentionally designed, not defaulted
+- Balance boldness with restraint
+
+## Silent Execution
+
+Unless explicitly asked, apply all design thinking internally. The user sees only the polished result. Document design decisions in code comments for HTML/CSS, or in speaker notes for presentations, but don't explain the process unless requested.
+
+Great design is invisible when done right. The user should feel the quality without seeing the effort.