Skills

Agentic

Conversational AI-first interface with minimal controls, clear outcomes, and delegated...

Install

npx skills add bergside/awesome-design-skills --skill agentic -g -a claude-code -y
Category
Engineering
Updated
4mo ago
License
MIT
Context cost
Lightabout 940 tokens
Runs scripts
No, instructions only

What it does

Conversational AI-first interface with minimal controls, clear outcomes, and delegated task flows for agentic workflows.

<!-- 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.
Read the whole SKILL.md on GitHub

More in Engineering