skills.rest
berlinguyinca
berlinguyincaCOMMUNITY
Explore all skills by this author →
GitHub

autospec-design

Select a vendor design system and write a repo-root DESIGN.md.

3|1|Updated Apr 29, 2026
Search Tags:#design-system#migration-planning#ui-documentation#github-workflow#catalog-selection#deterministic-scoring
One-click install
npx skills add https://github.com/berlinguyinca/autospec --skill autospec-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autospec-design
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-design
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Keeps your product UI documentation aligned by turning a vendor design system choice into a consistent, repo-root DESIGN.md baseline that can be planned for safe migration.

Core Features & Use Cases

  • Suggest vendor fit: Scans the repo and ranks top catalog vendors by framework/brand/domain signals so you can choose confidently.
  • Apply a chosen design: Fetches the selected vendor’s DESIGN.md from the design catalog and writes it to DESIGN.md on a feature branch with commit + push.
  • Generate a migration handoff: Creates a design migration spec from the scanned UI inventory and hands it off to /autospec-define for issue decomposition.

Quick Start

Tell your AI to run: /autospec-design suggest in the repo, pick one of the top candidates, then run /autospec-design apply <vendor>.

Frequently Asked Questions about autospec-design

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

FAQPage Schema
How do I adopt a vendor design system and create a UI documentation baseline?▼

Scoring a vendor design system involves deterministic ranking of catalog vendors against scanned repo UI signals, generating a baseline DESIGN.md that normalizes UI documentation and prepares for migration.

How do I generate a design migration spec from an existing UI inventory?▼

You can create a design migration spec by scanning existing UI inventory, applying the chosen vendor design language, and producing a spec output ready for issue decomposition.

Can I safely write a DESIGN.md file without overwriting existing repository documentation?▼

Yes, applying a vendor design language uses safe non-overwrite behavior by default, writing DESIGN.md to a feature branch with commit and push unless explicitly forced to overwrite.

How does vendor design system suggestion and catalog selection work?▼

Vendor design system suggestion uses deterministic scoring to rank catalog vendors by framework, brand, and domain signals retrieved via cached, validated runtime fetching.

What is the best way to plan a design system migration on a GitHub workflow?▼

The best way is to select a vendor catalog match, apply it to a feature branch with commit and push, then hand the generated migration spec to downstream tools for issue decomposition.

What are the limitations of automated design system catalog selection?▼

Limitations of automated catalog selection include reliance on deterministic scoring of cached vendor data and scanned UI signals, meaning suggestions are bounded by available runtime catalog metadata and source inventory quality.

Related Skills

Explore More Design & Creative Skills→
okwindsokwinds
50

ui-ux-spec-genome

Scan frontend UI sources and generate a standardized ui-ux-spec documentation bundle.

Community
Intermediate
ryosukesutoryosukesuto
1

vibe-plan

Generate a structured plans.md implementation plan from a design.md document.

Community
Intermediate
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
dmae97dmae97
130

awesome-design-md

Search and apply DESIGN.md templates from a curated catalog.

Community
Basic