delight
by pbakausUse the delight skill to add tasteful UI polish, micro-interactions, and personality to success, loading, empty, and onboarding states without hurting usability or focus.
This skill scores 68/100, which means it is listable but best framed as a moderately useful, caution-level install for users who want guided interface delight work. The repository gives enough workflow substance to help an agent act with less guesswork than a generic prompt, but users should expect some dependence on the broader impeccable skill and limited standalone operational support.
- Clear trigger language for delight, polish, micro-interactions, and memorable interface improvements.
- Concrete workflow coverage for finding delight opportunities across success, empty, loading, achievement, interaction, error, and easter egg states.
- Strong context sensitivity: explicitly asks for brand personality, audience, and appropriate tone before proposing changes.
- Relies on invoking $impeccable and a context-gathering protocol, so it is not fully standalone.
- No scripts, references, resources, or install command are provided, which reduces onboarding clarity for directory users.
Overview of delight skill
What delight is for
The delight skill helps you add small, intentional moments of joy to interfaces without turning them into distractions. It is best for UI work where the core flow already works and you want the product to feel more memorable, human, or brand-aligned. The real job-to-be-done is not “make it cute”; it is “improve the experience at moments users already notice.”
When it fits best
Use the delight skill for success states, onboarding, empty states, loading moments, hover feedback, and subtle motion or copy that reinforces personality. It is especially useful for delight for UI Design when you need tasteful polish that still respects usability, accessibility, and product seriousness.
What makes it different
This skill is decision-oriented: it asks where delight helps, what kind of personality fits the domain, and where extra flourish would get in the way. The most important differentiator is restraint. delight is meant to amplify an interface, not layer on decoration everywhere.
How to Use delight skill
Install and load context
Use delight install in your skill manager or add the GitHub skill from pbakaus/impeccable under .codex/skills/delight. Start with SKILL.md, since this repo has no extra scripts or reference folders to fill in the gaps. The install decision is simple: if you need a promptable guide for UI delight choices, this skill is directly relevant.
Give the skill a real design target
The delight skill works best when you provide a target screen, flow, or state instead of a vague request like “make it nicer.” Include the UI type, audience, tone, and constraints. Stronger input looks like: “Add delight to a B2B settings save flow for enterprise admins; keep it calm, fast, and accessible.” That gives the model enough context to choose appropriate motion, copy, and interaction details.
Follow a practical workflow
A good delight usage pattern is: identify the user moment, decide whether delight is appropriate, then choose one or two enhancements that support the brand. Read SKILL.md first to understand the mandatory preparation and the “Delight Principles” and “Delight Amplifies, Never Blocks” guidance. If you are deciding whether to adopt the skill, that file is the only one you need to judge fit quickly.
Write prompts that trigger better output
The delight guide works better when your prompt names the state, the emotion, and the boundary. For example: “Design a delightful empty state for a project dashboard aimed at first-time users. Make it warm but not playful, and avoid anything that slows task creation.” That is better than asking for “nice micro-interactions,” because it forces the skill to solve a real interface problem.
delight skill FAQ
Is delight only for playful products?
No. delight is useful for serious products too, as long as the personality stays appropriate. In enterprise, fintech, or healthcare, delight often means clarity, reassurance, and subtle motion rather than humor or novelty.
How is this different from a normal prompt?
A normal prompt may produce generic “add animation” suggestions. The delight skill adds a workflow: identify where delight belongs, check the domain tone, and avoid blocking the core task. That usually produces more usable output for product teams and UI designers.
Do I need design experience to use it?
No, but you do need a concrete UI target. Beginners get better results when they describe one screen or one state at a time. If you only say “improve the app,” the output will be broader and less actionable.
When should I not use delight?
Skip it when the main problem is broken usability, missing content, or unclear flow. If the interface needs structure before personality, delight is the wrong first step. It is also a poor fit when the product must stay fully neutral and minimal.
How to Improve delight skill
Start with the highest-value moment
The best results come from targeting one place where users already feel something: success, waiting, first use, or recovery from an error. Be explicit about which moment matters most, because the skill should not spread effort evenly across the whole UI.
Provide stronger constraints
Tell the skill what must stay unchanged: layout, hierarchy, accessibility, performance, or brand tone. For delight for UI Design, the most common failure mode is overdoing motion or personality in a context that needs trust or speed. Clear constraints help the skill choose tasteful, implementable ideas.
Iterate from rough to refined
Use the first output to pick the direction, then narrow it with follow-up prompts like “make it more subtle,” “reduce novelty,” or “make it friendlier for a professional audience.” This is where delight usage becomes effective: the first pass identifies opportunities, and the next pass calibrates intensity.
Ask for concrete outputs
If you want actionable work, request exact states, copy examples, motion ideas, or interaction rules rather than abstract inspiration. The delight skill is strongest when you ask it to turn a broad goal into specific UI decisions that can be reviewed, built, and tested.