メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when auth changes could create drift between runtime, env keys, mocks, UI copy, and docs.
Use when deciding where new files belong and how module boundaries should be preserved.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.
| name | i-teach-impeccable |
| description | 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. |
| user-invokable | true |
Gather design context for this project, then persist it for all future sessions.
Before asking questions, thoroughly scan the project to discover what you can:
Note what you've learned and what remains unclear.
ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase:
Skip questions where the answer is already clear from the codebase exploration.
Synthesize your findings and the user's answers into a ## Design Context section:
## 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 .github/copilot-instructions.md in the project root. If the file exists, append or update the Design Context section.
Confirm completion and summarize the key design principles that will now guide all future work.