teach-impeccable

Store project design guidelines in the AI config file for future sessions.

Updated May 15, 2026
One-click install
npx skills add https://github.com/nachopalmeri/agents-system --skill teach-impeccable-nachopalmeri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/nachopalmeri/agents-system/tree/main/.agents/skills/teach-impeccable
Command: npx skills add https://github.com/nachopalmeri/agents-system --skill teach-impeccable-nachopalmeri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and persists project design context to seed AI behavior across sessions, eliminating drift in product design decisions.

Core Features & Use Cases

  • One-time capture of design goals, brand voice, typography, tokens, and constraints.
  • Persists context in the AI config so future prompts automatically align with established guidelines.
  • Use Case: at project kickoff, collect design context and seed it for all subsequent interactions and decisions.

Quick Start

Run the teach-impeccable skill to collect design context and save it to the AI config for persistent guidelines.

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 across AI sessions?

To persist design guidelines across AI sessions, you can capture your project's brand voice, typography, and tokens once, saving them directly into the AI config file to seed context for all future interactions.

Why does my AI generated UI drift from my original brand design context?

AI generated UI drifts from brand design context when guidelines are not persisted. Centralizing design rules in the AI config file seeds consistent behavior and eliminates drift in future product decisions.

What is the best way to establish UX design rules for ongoing AI interactions?

The best way to establish UX design rules for ongoing AI interactions is to collect your constraints during project kickoff and save them to the AI config, ensuring all subsequent prompts automatically align.

When do I need to capture project design tokens for persistent context?

You need to capture project design tokens for persistent context during initial project setup or whenever establishing brand and UX design rules, ensuring future sessions automatically align with your goals.

Does saving design context to an AI config file eliminate manual prompting for brand voice?

Saving design context to an AI config file eliminates manual prompting for brand voice by storing guidelines centrally, which automatically seeds persistent context and aligns future prompts with established rules.