taste

Name: taste
Availability: InStock
Author: edupazogle

Enforce AXA Canopée design tokens and route UI design tasks to sub-skills.

Updated Aug 27, 2026

Search Tags:#design tokens #ui design #brand compliance #accessibility audit #image to code #frontend aesthetics

Ready to run

npx skills add https://github.com/edupazogle/agentic_cockpit --skill taste-edupazogle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: taste
Source: https://github.com/edupazogle/agentic_cockpit/tree/main/.agents/skills/taste
Command: npx skills add https://github.com/edupazogle/agentic_cockpit --skill taste-edupazogle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents generic, inconsistent UI visuals by enforcing an AXA Canopée token-driven design system and providing a clear routing flow for common design tasks.

Core Features & Use Cases

Token-first design rule: Forces every visual change to use AXA Canopée design tokens, never invented colors, fonts, or spacing values.
Sub-skill selection catalog: Routes requests to specialized design instructions (brand kit, frontend polish, production-ready output, specific aesthetics, and image-to-code).
Quality and safety guardrails: Requires accessibility (a11y) checks and bans placeholder/low-effort “AI slop” aesthetics.

Quick Start

Tell the AI you want AXA Canopée-token compliant visual design for your UI, including whether you need brand kit setup, frontend taste polish, full production output, or image-to-code conversion.

Frequently Asked Questions about taste

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

FAQPage Schema

How do I enforce design tokens for consistent UI design?▼

To enforce design tokens for consistent UI design, apply a token-first rule that restricts visual changes to approved design system values, preventing invented colors, fonts, or spacing. This ensures strict brand compliance across all frontend aesthetics.

What is the best way to convert an image to code while maintaining brand compliance?▼

Converting an image to code while maintaining brand compliance requires routing visual references through a deterministic token-driven design system. This process translates visual elements into frontend-ready output using strictly enforced, pre-defined design tokens instead of arbitrary values.

How does an accessibility audit work during UI component design?▼

An accessibility audit during UI component design works by enforcing mandatory a11y checks alongside token-driven visual decisions. This guardrail prevents low-effort aesthetics and ensures frontend output meets accessibility standards before production.

Can I use custom fonts and colors for my UI redesign?▼

No, you cannot use custom invented fonts and colors for your UI redesign. The system requires strict no-invention design rules, forcing every visual change to apply specific design tokens to maintain brand compliance and eliminate generic aesthetics.

Does this design token approach support full production-ready UI output?▼

Yes, this design token approach supports full production-ready UI output. It routes requests through specialized sub-skills for frontend polish and production output, ensuring visual references are translated into frontend-ready code using deterministic token-first rules.