teach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Best use case
teach-impeccable is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Teams using teach-impeccable should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/teach-impeccable/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How teach-impeccable Compares
| Feature / Agent | teach-impeccable | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Gather design context for this project, then persist it for all future sessions. ## Step 1: Explore the Codebase Before asking questions, thoroughly scan the project to discover what you can: - **README and docs**: Project purpose, target audience, any stated goals - **Package.json / config files**: Tech stack, dependencies, existing design libraries - **Existing components**: Current design patterns, spacing, typography in use - **Brand assets**: Logos, favicons, color values already defined - **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales - **Any style guides or brand documentation** Note what you've learned and what remains unclear. ## Step 2: Ask UX-Focused Questions STOP and call the AskUserQuestion tool to clarify. Focus only on what you couldn't infer from the codebase: ### Users & Purpose - Who uses this? What's their context when using it? - What job are they trying to get done? - What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) ### Brand & Personality - How would you describe the brand personality in 3 words? - Any reference sites or apps that capture the right feel? What specifically about them? - What should this explicitly NOT look like? Any anti-references? ### Aesthetic Preferences - Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) - Light mode, dark mode, or both? - Any colors that must be used or avoided? ### Accessibility & Inclusion - Specific accessibility requirements? (WCAG level, known user needs) - Considerations for reduced motion, color blindness, or other accommodations? Skip questions where the answer is already clear from the codebase exploration. ## Step 3: Write Design Context Synthesize your findings and the user's answers into a `## Design Context` section: ```markdown ## Design Context ### Users [Who they are, their context, the job to be done] ### Brand Personality [Voice, tone, 3-word personality, emotional goals] ### Aesthetic Direction [Visual tone, references, anti-references, theme] ### Design Principles [3-5 principles derived from the conversation that should guide all design decisions] ``` Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. Then STOP and call the AskUserQuestion tool to clarify. whether they'd also like the Design Context appended to CLAUDE.md. If yes, append or update the section there as well. Confirm completion and summarize the key design principles that will now guide all future work.
Related Skills
typescript-performance
Comprehensive TypeScript performance analysis and optimization. Use when users report slow TypeScript compilation, slow editor experience, or want to investigate TypeScript performance issues. This skill provides diagnostic tools, trace analysis workflows, and optimization strategies. Key triggers include mentions of slow builds, type-checking delays, tsc performance, editor lag with TypeScript, or requests to analyze/improve TypeScript performance. Always prioritize data-driven analysis using --extendedDiagnostics, --generateTrace, and TS Server logs before making optimization recommendations.
watch-ci
CI を監視し、失敗したら自律的に修正してパスするまでループするスキル。push 後・PR 作成後・rebase 後に CI が通るか確認したいとき、CI が落ちていたら直してほしいとき、CI の結果を待ちたいときに使う。「CI 監視して」「CI が通るまで待って」「CI 直して」「push したので CI を見ておいて」など、CI の状態確認・自動修正が必要な場面では必ずこのスキルを呼び出すこと。
vue-style-guide
Vue を書くときは基本的に参考にしてください。 個人的に気に入っている ubgeeei 氏の Vue.js のスタイルガイドです。
vitess
Vitess best practices, query optimization, and connection troubleshooting for PlanetScale Vitess databases. Load when working with Vitess databases, sharding, VSchema configuration, keyspace management, or MySQL scaling issues.
triage-pr-reviews
Triages unresolved PR review comments using gh-pr-reviews. Analyzes code context and classifies each comment as Agree / Partially Agree / Disagree. Walks through each comment one-by-one, asking the user what action to take. Use when the user wants to triage, review, or analyze unresolved PR comments.
terraform-test
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution.
terraform-style-guide
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
terraform-stacks
Comprehensive guide for working with HashiCorp Terraform Stacks. Use when creating, modifying, or validating Terraform Stack configurations (.tfcomponent.hcl, .tfdeploy.hcl files), working with stack components and deployments from local modules, public registry, or private registry sources, managing multi-region or multi-environment infrastructure, or troubleshooting Terraform Stacks syntax and structure.
stacked-pr
依存関係のある複数の PR を管理・同期するためのスキル。stacked PR のカスケード rebase、PR 間の依存検出、base branch 管理、CI の上流優先修正を行う。PR が別の PR に依存している状況全般で使う — cascade rebase、スタック sync、依存先 PR 更新後のメンテ、PR チェーンの整合性確認などをするときなど。
smart-compact
セッションのコンテキストを分析し、重要な情報を保持するためのプロンプトを生成して /compact コマンドの実行を支援するスキル。コンテキストウィンドウが逼迫してきた時や、セッションを整理したい時に使用。
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
semgrep
Run Semgrep static analysis scans and create custom detection rules. Use when asked to scan code with Semgrep, find security vulnerabilities, write custom YAML rules, or detect specific bug patterns. IMPORTANT: Also use this skill when users ask to 'scan for bugs', 'check code quality', 'find vulnerabilities', 'static analysis', 'lint for security', 'audit this code', or want to enforce coding standards — even if they don't mention Semgrep by name. Semgrep is the right tool for pattern-based code scanning across 30+ languages.