designer

Generate a Frontend Design Specification with architecture, tokens, and visual language.

9|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill designer-tykodev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: designer
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/design/designer
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill designer-tykodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend design projects often suffer from ambiguity between requirements and implementation. This skill generates a complete Frontend Design Specification that codifies architecture choices, design tokens, typography, color system, component structure, accessibility, and performance targets so engineers can implement with confidence.

Core Features & Use Cases

  • Produces architecture decisions, token schemas, typography rules, color strategy, spacing, and component organization.
  • Documents accessibility, performance targets, responsive behavior, and the gatekeeper workflow for design reviews.
  • Use Case: A SaaS admin panel requires a consistent design system and a gatekept handoff to the build team.

Quick Start

Provide project context and desired frontend outcomes to generate the Frontend Design Specification.

Frequently Asked Questions about designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a frontend design specification and when do I need one?

A frontend design specification codifies architecture choices, design tokens, typography, color systems, and accessibility targets. You need one to eliminate ambiguity between design requirements and engineering implementation for SaaS dashboards, admin panels, or marketing sites.

How do I create a design token system for a SaaS dashboard?

Generate a frontend design specification to define Tier-1, Tier-2, and Tier-3 design tokens. This codifies your typography rules, color strategy, and spacing variables into a structured schema for consistent UI implementation across the dashboard.

Can I document accessibility conformance and performance targets in a design handoff?

Yes, a frontend design specification documents accessibility conformance and performance targets alongside motion guidelines. It includes gatekeeper workflow artifacts for design reviews, providing engineers with clear handoff requirements for compliant implementation.

What's the best way to structure a component inventory and API for a design system?

Generate a frontend design specification to map out your component inventory and APIs. It organizes component structure alongside responsive strategies and architecture patterns, ensuring the design system scales properly across different application contexts.

Does this approach work for both marketing sites and documentation portals?

Yes, this frontend design specification approach applies to marketing sites, documentation portals, SaaS dashboards, and admin panels. It guides architecture decisions and visual language creation across diverse web application environments.

Why should I use a structured spec instead of ad hoc design handoff for admin panels?

A structured frontend design specification codifies architecture, tokens, and visual language so engineers can implement with confidence. Ad hoc handoffs often suffer from ambiguity between requirements and implementation, leading to inconsistent admin panel design systems.