Impeccable UI Deep Dive
Paste the following prompt into your AI chat to install this skill:
Please follow https://skillhub.cn/install/skillhub.md to install @user_3c47cf70/impeccable-pro.
About this skill
Problem: UI work often stalls between “usable” and maintainable
Many UI Deep Dive efforts fail not because the feature is impossible, but because delivery stops at “good enough.” The material frames recurring quality traps as: works on my machine, happy-path-only logic, performance deferred, accessibility treated as optional, and documentation promised for “later.” Without a shared delivery standard, code, tests, docs, and UX details keep churning.
How it works: an Impeccable delivery loop
The skill applies a design-before-code stance and breaks UI deep-dive work into six stages:
- Design before code: clarify requirements, architecture, interfaces, edge cases, and error scenarios.
- Flawless implementation: keep naming, responsibility, error handling, and style consistent on the first pass.
- Comprehensive testing: cover public functions, edge inputs, error paths, and critical integration flows.
- Rigorous review: self-review warnings, debug code, performance, and security before requesting review.
- Perfect documentation: update
README, API docs, usage examples, and migration notes. - Perfect polish: refine error messages, loading states, accessibility, naming, and commit hygiene.
Boundary: useful for quality-sensitive delivery, not product decision-making
It fits production-grade components, high-visibility features, long-lived libraries, and showcase work. It mainly constrains engineering and UX quality; it does not set product priorities or replace design review. Use Impeccable as a ship-ready professional standard, not as indiscriminate perfectionism.
Use Cases
- Refactor high-visibility landing page components and complete design checklist items such as loading and error states.
- Prepare a design system component library for release by checking accessibility, test coverage, and API documentation.
- Self-review UI feature code before review by removing debug code, magic strings, and lint warnings.
- Harden production forms or checkout flows by adding error scenarios, performance budgets, and migration notes.
Best For
- Frontend engineers maintaining high-visibility components who need error, loading, and accessibility states ready for release.
- Design-system or shared UI library engineers who need consistent API docs, test coverage, and breaking-change notes.
- Frontend developers building portfolios or client demos who need first-draft code, tests, and polish presentable externally.
- Engineering leads protecting UI quality before deadlines who need clear criteria for what defects must not ship.
Related Skills
Automatically indexes Gradle-cached AAR/JAR dependency classes and returns library coordinates, versions, and public APIs by fully qualified name, using only the Python standard library.
Codifies AMT and YourMT3 training conventions, script patterns, hyperparameters, precision, checkpoints, and NaN safeguards.
Retrieve relevant chunks from a customer-managed PKM dataset by dataset_id and return concise, source-annotated answers.
Convert PRDs, user stories, or functional specs into prioritized test-point checklists covering functional, business-rule, boundary, exception, and non-functional dimensions.