DESIGN.md
---
name: Agentic
colors:
primary: "#FF5701"
secondary: "#F6F6F1"
success: "#16A34A"
warning: "#D97706"
danger: "#DC2626"
surface: "#FFFFFF"
text: "#111827"
neutral: "#FFFFFF"
typography:
h1:
fontFamily: "Playfair Display"
fontSize: 2.5rem
body-md:
fontFamily: "Playfair Display"
fontSize: 1rem
label-caps:
fontFamily: "JetBrains Mono"
fontSize: 0.875rem
sourceScale: "14/16/18/24/32/40"
weights: "100, 200, 300, 400, 500, 600, 700, 800, 900"
rounded:
sm: 4px
md: 8px
spacing:
sm: 8px
md: 16px
sourceScale: "8pt baseline grid"
---
## Overview
Conversational AI-first interface with minimal controls, clear outcomes, and delegated task flows for agentic workflows.
## Style Foundations
- **Visual style:** modern, bold
- **Typography scale:** 14/16/18/24/32/40
- **Typography fonts:** primary=Playfair Display, display=Playfair Display, mono=JetBrains Mono
- **Typography weights:** 100, 200, 300, 400, 500, 600, 700, 800, 900
- **Color palette:** surface/subtle layers
- **Spacing scale:** 8pt baseline grid
## Colors
- **Primary (#FF5701):** Token from style foundations.
- **Secondary (#F6F6F1):** Token from style foundations.
- **Success (#16A34A):** Token from style foundations.
- **Warning (#D97706):** Token from style foundations.
- **Danger (#DC2626):** Token from style foundations.
- **Surface (#FFFFFF):** Token from style foundations.
- **Text (#111827):** Token from style foundations.
- **Neutral (#FFFFFF):** Derived from the surface token for official format compatibility.
SKILL.md
---
name: agentic
description: Conversational AI-first interface with minimal controls, clear outcomes, and delegated task flows for agentic workflows.
license: MIT
metadata:
author: typeui.sh
---
<!-- TYPEUI_SH_MANAGED_START -->
# Agentic Design System Skill (Universal)
## Mission
You are an expert design-system guideline author for Agentic.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
## Brand
The agentic design style emphasizes conversational interactions, clear outcomes, and minimal controls, allowing users to delegate tasks to AI instead of manually managing complex workflows.
## Style Foundations
- Visual style: modern, bold
- Typography scale: 14/16/18/24/32/40 | Fonts: primary=Playfair Display, display=Playfair Display, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: surface/subtle layers | Tokens: primary=#FF5701, secondary=#F6F6F1, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 8pt baseline grid
## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels, reduced-motion support, 44px+ touch targets, high-contrast support
## Writing Tone
concise, confident, helpful, clear, friendly, professional, action-oriented, low-jargon
## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
- design for empty/loading/error states
- ensure responsive behavior by default
- document accessibility rationale
## Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid decorative motion without purpose
- avoid ambiguous labels
- avoid mixing multiple visual metaphors
- avoid inaccessible hit areas
## 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 -->