teach-impeccable

Gather project design context and persist guidelines to the AI configuration.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Ikki-Group/erp --skill teach-impeccable-ikki-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/Ikki-Group/erp/tree/main/.agents/skills/teach-impeccable
Command: npx skills add https://github.com/Ikki-Group/erp --skill teach-impeccable-ikki-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams capture design context for a project and persist it to the AI configuration so recommendations stay aligned with brand and UX goals across sessions.

Core Features & Use Cases

  • Gather project design context, including brand attributes, design tokens, and accessibility considerations.
  • Persist guidelines to the AI config for consistent guidance in future sessions and across team members.
  • Use during onboarding and design refreshes to align design decisions with established guidelines.

Quick Start

Run this skill once to gather your design context and persist guidelines in your AI config for future sessions.

Frequently Asked Questions about teach-impeccable

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

FAQPage Schema
How do I persist design guidelines in AI config for consistent UX recommendations?

To persist design guidelines, this Skill scans your codebase to gather design context and writes a design-context file to the AI config, ensuring future recommendations align with brand, accessibility, and UX goals.

What is the best way to capture brand attributes and design tokens during project onboarding?

The best way to capture brand attributes during onboarding is running this Skill once to extract design context, including design tokens and accessibility considerations, and save it for ongoing guidance.

Do I need external dependencies to scan my codebase for design context?

You do not need external dependencies to scan your codebase for design context; this Skill operates using only the existing environment to gather guidelines and write them to the AI configuration.

Can I use this to align design decisions with established accessibility considerations across teams?

You can align design decisions across teams because this Skill persists project guidelines to the AI config, enabling consistent application of accessibility considerations for all team members in future sessions.

When should I run a design context capture to update my AI configuration?

You should run a design context capture during project onboarding or design refreshes to update your AI configuration, ensuring that evolving brand guidelines and UX goals remain persistent across sessions.