aidlc-cdo

Translate client intent into emotional design briefs and gate criteria.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-cdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidlc-cdo
Source: https://github.com/CornFedKratos/s3-aidlc/tree/main/plugins/s3-aidlc/skills/aidlc-cdo
Command: npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-cdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The CDO skill ensures design intent alignment, standardization, and governance across all UI features by producing emotional design briefs, enforcing the design system, and guiding gate processes.

Core Features & Use Cases

  • Emotional design briefs created before UI work to align the client's feel with implementation.
  • Design gates and KB documentation to capture decisions, exceptions, and evolutions of the design system.
  • Accessibility and token-driven design enforcement across features from concept to deployment.

Quick Start

Draft the emotional design brief and accompanying Figma mockup plan for a new UI surface.

Frequently Asked Questions about aidlc-cdo

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

FAQPage Schema
How do I create an emotional design brief for a new UI feature?

An emotional design brief aligns a client's desired feel with implementation by translating intent into repeatable gate criteria before UI work begins. It ensures standardization and design system compliance from ideation to deployment.

What are design gates and how do they enforce a design system?

Design gates are checkpoint processes that enforce design system compliance and accessibility across UI features. They capture decisions, exceptions, and system evolutions within a knowledge base throughout the development lifecycle.

How do I maintain design system documentation and accessibility standards?

You maintain design system documentation by recording decisions and gate exceptions in a comprehensive knowledge base. This ensures accessibility and token-driven design rules are consistently enforced across all features.

Can I use this to manage design tokens from concept to deployment?

Yes, the skill enforces token-driven design across the entire UI feature lifecycle from concept to deployment. It satisfies requirements for design tokens and guides the evolution of the design system through structured gates.

What is the best way to align client feel with UI implementation rules?

The best way to align client feel with implementation is drafting an emotional design brief before UI work. This translates client intent into repeatable rules that govern design identity and system compliance.