design

Creates and maintains a repository-local DESIGN.md for UI/UX and frontend decisions.

Updated May 26, 2026
One-click install
npx skills add https://github.com/koasis89/ite-ai-agent --skill design-koasis89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/koasis89/ite-ai-agent/tree/main/plugins/oh-my-codex/skills/design
Command: npx skills add https://github.com/koasis89/ite-ai-agent --skill design-koasis89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to create and maintain a design source of truth, ensuring consistency and clarity in UI/UX and frontend decision-making.

Core Features & Use Cases

  • Design Discovery: Identifies existing design context within the repository.
  • Interview for Missing Context: Gathers necessary information for design decisions.
  • Create/Refresh DESIGN.md: Generates or updates the repository's DESIGN.md document.
  • Decision Contract: Serves as a reference for UI/UX/frontend work.
  • Use Cases: Ideal for product, UI/UX, frontend, or design-system decisions requiring a durable source of truth.

Quick Start

Run the design skill with the $design command to initiate the design workflow.

Frequently Asked Questions about design

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

FAQPage Schema
How do I establish a durable design source of truth for frontend decisions?

Create a repository-local `DESIGN.md` document to serve as a durable design source of truth for UI/UX and frontend decisions. It identifies existing repository context and conducts interviews for missing information to maintain consistency.

What is the best way to document UI/UX design decisions in a repository?

Generate a `DESIGN.md` file as a decision contract for UI/UX work. This Skill scans repository evidence and gathers missing context through interviews to create a structured reference for product and design-system workflows.

Can I use this approach for design-system workflows without prior documentation?

Yes, this approach supports design-system workflows lacking prior documentation. The Skill performs design discovery to identify existing repository context, and if missing, conducts interviews to gather necessary information for establishing the source of truth.

How does a design discovery workflow handle missing UI/UX context?

A design discovery workflow handles missing UI/UX context by conducting targeted interviews to gather necessary information. It integrates these answers with existing repository evidence to refresh or create the `DESIGN.md` decision contract.

When do I need a `DESIGN.md` file for product and frontend development?

You need a `DESIGN.md` file for product and frontend development when requiring a durable decision contract to maintain consistency. It is ideal for workflows needing a central source of truth to guide ongoing UI/UX and design-system decisions.