design

Manage design context discovery and documentation into a canonical DESIGN.md file.

Updated Jul 2, 2026

Search Tags:#frontend development #design documentation #design standards #repository design #UI/UX decision-making

Ready to run

npx skills add https://github.com/JaCha00/nais2-integration-complete --skill design-jacha00

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design
Source: https://github.com/JaCha00/nais2-integration-complete/tree/main/.codex/skills/design
Command: npx skills add https://github.com/JaCha00/nais2-integration-complete --skill design-jacha00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a standardized process for maintaining a canonical design document, ensuring consistency and accuracy across all UI/UX and frontend decisions.

Core Features & Use Cases

Design Documentation: Automates the creation and maintenance of DESIGN.md for the repository.
Interviews and Evidence Review: Integrates interviews and repository evidence review to ensure all design contexts are covered.
Decision Contract: Serves as a decision contract for UI/UX and frontend work, ensuring adherence to design principles and goals.

Quick Start

Run the design skill with the $design command.

Frequently Asked Questions about design

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

FAQPage Schema

How do I maintain design documentation for frontend development?▼

Maintain design documentation by managing a canonical `DESIGN.md` file for your repository. This skill automates the discovery and interviewing process to document UI/UX contexts, ensuring your frontend development remains accurate and consistent.

What is the best way to create a design standards decision contract?▼

A design standards decision contract is created by compiling UI/UX contexts into a canonical `DESIGN.md` file. This skill interviews for missing context and reviews repository evidence to establish a single source of truth for decision-making.

How do you document existing UI/UX decisions in a code repository?▼

Document existing UI/UX decisions by reviewing repository evidence and conducting interviews for missing context. This skill processes the findings to maintain a canonical `DESIGN.md` that captures all design contexts and standards.

Can I use this design documentation skill for product and frontend development?▼

Yes, this skill is applicable to product, UI/UX, and frontend development. It maintains a canonical `DESIGN.md` document that serves as a decision contract, ensuring all design principles and goals are followed across these contexts.

What happens when design context is missing from the repository?▼

When design context is missing, the skill initiates an interview process to gather the necessary information. It then consolidates this collected data into the canonical `DESIGN.md` file to ensure complete design documentation.

Why do I need a canonical source of truth for UI/UX decision-making?▼

A canonical source of truth for UI/UX decision-making ensures design consistency and accuracy across a repository. It prevents fragmentation by serving as a binding decision contract for all related frontend work.