teach-impeccable

Collect project design context and persist it to an AI configuration file.

Updated Feb 27, 2025
One-click install
npx skills add https://github.com/tuanemuy/dotfiles --skill teach-impeccable-tuanemuy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/tuanemuy/dotfiles/tree/main/config/claude/skills/teach-impeccable
Command: npx skills add https://github.com/tuanemuy/dotfiles --skill teach-impeccable-tuanemuy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

プロジェクトのデザインコンテキストを収集し、今後のセッションで再利用できる形でAI設定ファイルへ永続化します。これにより、一度の実行で持続的なデザインガイドラインが確立されます。

Core Features & Use Cases

  • デザインコンテキストの収集: README、設定ファイル、既存のデザイン要素、ブランド資産、デザイントークン等をスキャンして要点を抽出します。
  • 永続化: 発見事項をAI設定ファイルに保存し、以後の全セッションで再利用可能にします。
  • 学習と明確化: 不明点を文書化し、後での検討・補足に備えます。

Quick Start

Run this skill to collect the project's design context and persist it to the AI config for all 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 context and brand assets for AI-assisted development?

You can capture design context by scanning codebases, documents, and brand assets, then persisting the findings into an AI configuration file to ensure consistent design guidelines across all future sessions.

What is the best way to maintain design token consistency across multiple AI sessions?

Maintaining design token consistency is achieved by extracting tokens during an initial discovery scan and saving them directly into a durable AI config file, which automatically applies these rules to ongoing sessions.

How does capturing design context into an AI config file work?

Capturing design context works through a single-run workflow that scans README files, existing design elements, and brand assets, outputting a structured Design Context file while documenting unknowns for later clarification.

Do I need existing design documentation to extract UX research context?

You do not need strictly formatted documentation; the skill scans available codebases, onboarding documents, and brand assets to extract the UX research context and structure it into a reusable guide.

What happens to unclear design elements found during the codebase scan?

When the scan encounters unclear design elements, it records these questions within the structured Design Context file, ensuring unresolved items are documented for later review and clarification.

Can I use this design context capture for ongoing project onboarding?

Yes, the captured design context is persisted for ongoing sessions, meaning any new onboarding workflow will automatically reference the established AI configuration to maintain strict design consistency.