EasyPlatform design-good

[Design] Create an immersive design

install

source · Clone the upstream repo

git clone https://github.com/duc01226/EasyPlatform

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/duc01226/EasyPlatform "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/design-good" ~/.claude/skills/duc01226-easyplatform-design-good && rm -rf "$T"

manifest: .claude/skills/design-good/SKILL.md

source content

[IMPORTANT] Use
TaskCreate
to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip.

Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.

AI Mistake Prevention — Failure modes to avoid on every task:

Check downstream references before deleting. Deleting components causes documentation and code staleness cascades. Map all referencing files before removal.

Verify AI-generated content against actual code. AI hallucinates APIs, class names, and method signatures. Always grep to confirm existence before documenting or referencing.

Trace full dependency chain after edits. Changing a definition misses downstream variables and consumers derived from it. Always trace the full chain.

Trace ALL code paths when verifying correctness. Confirming code exists is not confirming it executes. Always trace early exits, error branches, and conditional skips — not just happy path.

When debugging, ask "whose responsibility?" before fixing. Trace whether bug is in caller (wrong data) or callee (wrong handling). Fix at responsible layer — never patch symptom site.

Assume existing values are intentional — ask WHY before changing. Before changing any constant, limit, flag, or pattern: read comments, check git blame, examine surrounding code.

Verify ALL affected outputs, not just the first. Changes touching multiple stacks require verifying EVERY output. One green check is not all green checks.

Holistic-first debugging — resist nearest-attention trap. When investigating any failure, list EVERY precondition first (config, env vars, DB names, endpoints, DI registrations, data preconditions), then verify each against evidence before forming any code-layer hypothesis.

Surgical changes — apply the diff test. Bug fix: every changed line must trace directly to the bug. Don't restyle or improve adjacent code. Enhancement task: implement improvements AND announce them explicitly.

Surface ambiguity before coding — don't pick silently. If request has multiple interpretations, present each with effort estimate and ask. Never assume all-records, file-based, or more complex path.

Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: <tasks>$ARGUMENTS</tasks>

Skill Variant: Variant of design skills — immersive, high-quality design.

Quick Summary

Goal: Create an immersive, high-quality UI design with deep design research and refinement.

Workflow:

Research — Comprehensive
```
ui-ux-pro-max
```
searches across all domains
Design — Use
```
ui-ux-designer
```
subagent with detailed brief
Refine — Iterate on feedback, verify with
```
ai-multimodal
```
Document — Update design guidelines if needed

Key Rules:

Always activate
```
ui-ux-pro-max
```
FIRST for design intelligence
Higher quality bar than
```
/design-fast
```
— iterate on details
Use
```
ai-multimodal
```
for generating and reviewing visual assets

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Required Skills (Priority Order)

ui-ux-pro-max
- Design intelligence database (ALWAYS ACTIVATE FIRST)
frontend-design
- Screenshot analysis and design replication

Ensure token efficiency while maintaining high quality.

Workflow:

FIRST: Run

ui-ux-pro-max

searches to gather design intelligence:

python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<product-type>" --domain product
python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<style-keywords>" --domain style
python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<mood>" --domain typography
python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<industry>" --domain color

Use
```
researcher
```
subagent to research about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
Use
```
ui-ux-designer
```
subagent to implement the design step by step based on the research.
If user doesn't specify, create the design in pure HTML/CSS/JS.
Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
If user approves the changes, update the
```
./docs/design-guidelines.md
```
docs if needed.

Important Notes:

ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.
Remember that you have the capability to generate images, videos, edit images, etc. with
```
ai-multimodal
```
skills for image generation. Use them to create the design with real assets.
Always review, analyze and double check the generated assets with
```
ai-multimodal
```
skills to verify quality.
Use
```
media-processing
```
skill (RMBG) to remove background from generated assets if needed.
Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
Maintain and update
```
./docs/design-guidelines.md
```
docs if needed.

Closing Reminders

MANDATORY IMPORTANT MUST ATTENTION break work into small todo tasks using
```
TaskCreate
```
BEFORE starting
MANDATORY IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
MANDATORY IMPORTANT MUST ATTENTION cite
```
file:line
```
evidence for every claim (confidence >80% to act)
MANDATORY IMPORTANT MUST ATTENTION add a final review todo task to verify work quality
MUST ATTENTION apply critical thinking — every claim needs traced proof, confidence >80% to act. Anti-hallucination: never present guess as fact.
MUST ATTENTION apply AI mistake prevention — holistic-first debugging, fix at responsible layer, surface ambiguity before coding, re-read files after compaction.