47-design-review-global
Use when a finished DESIGN needs scoring and feedback — brand consistency, hierarchy plus readability plus accessibility, conversion elements, and platform fit, 10 points each, with per-issue feedback in issue, why, and how-to-fix form and a verdict of approve, minor fix, or redo. Trigger on 'design review', 'review this design', 'score this creative', 'is this design good', 'brand check on this banner', 'can we ship this or not'. Also use when the user just sends an image and asks for thoughts. Not for — reviewing copy and briefs, see `62-marketing-review-global`; writing the brief before production, see `42-image-brief-global`; the brand rules being checked against, see `46-brand-guideline-global`.
git clone --depth 1 https://github.com/minhnv0807/ai-business-skills /tmp/47-design-review-global && cp -r /tmp/47-design-review-global/skills/en/47-design-review-global ~/.claude/skills/47-design-review-globalSKILL.md
# Design Review (Global) Reviewing design is not about liking it. It is checking whether the design does its job. Beautiful work that does not convert has failed. Converting work that breaks the brand has also failed. Feedback must be specific enough for the designer to act without asking. ## Information gathering Read the brand guideline (`46-brand-guideline-global`) and the originating brief. If information is missing, ask up to 4 questions: 1. **What is being reviewed?** File, screenshot, or share link — and what type (social post, ad banner, carousel, landing page, email)? 2. **Objective and funnel stage?** Awareness, trust, or conversion — TOFU, MOFU, or BOFU? 3. **Which channel does it run on?** Meta, TikTok, Instagram, LinkedIn, Pinterest, email, or website? 4. **Which brand guideline applies?** If none exists, the brand section can only be scored loosely — propose running `46-brand-guideline-global` first. ## Principles 1. **Feedback specific enough to fix without a follow-up.** "It doesn't feel right" is not feedback. 2. **Separate must-fix (blocker) from should-fix (suggestion).** 3. **Never reject on personal taste** — every deduction cites a checklist item. 4. **Review within 24 hours.** Do not let a designer wait and block the workflow. 5. **Once approved, do not reopen** after the designer exports. 6. **If more than 50% needs rebuilding, rewrite the brief** instead of looping revisions. ## Workflow ### 1. Look at the whole thing first (3 seconds) View it as a real user would — do not zoom into detail yet. Answer two questions: within three seconds, is it clear what this design is saying? Where does the eye land first? ### 2. Score the 4 criteria groups Each group is worth 10 points, 40 total. Score against the checklist below; deduct in proportion to the impact of each failure. ### 3. Write feedback in the standard format Every issue is written as **[Issue] -> [Why it is wrong] -> [Exactly how to fix it]**. ### 4. Give a verdict and an action summary State the verdict, list fixes in priority order, and name the condition for approval. ## Output structure ```markdown # Design Review — [Asset name] — [date] ## Quick verdict | Criterion | Assessment | Note | |-----------|-----------|------| | On brand? | OK / Warning / Fail | | | Clear hierarchy? | OK / Warning / Fail | | | Readable on mobile? | OK / Warning / Fail | | | Meets the objective? | OK / Warning / Fail | | ## Total: [X/40] | Group | Score | Assessment | |-------|-------|-----------| | A. Brand consistency | /10 | | | B. Hierarchy, readability, accessibility | /10 | | | C. Conversion elements | /10 | | | D. Platform fit | /10 | | Verdict: APPROVE / MINOR FIX (fix per notes, no re-review needed) / REDO [section] (reason) ## A. Brand consistency [/10] - [ ] Logo uses the right version, position, and clear space - [ ] Colors match the brand palette exactly (not a near-match with the wrong value) - [ ] Fonts are [heading font] / [body font] - [ ] Visual tone matches the brand personality - [ ] No element violates a guideline do or don't - [ ] No generic stock imagery diluting the brand Issue: [issue] -> [why] -> [how to fix] ## B. Hierarchy, readability, accessibility [/10] - [ ] One clear focal point — no competing centers of attention - [ ] Logical reading order: headline -> subhead -> body -> CTA - [ ] The most important element carries enough visual weight (size, color, contrast) - [ ] The headline is readable in three seconds - [ ] Body type is at least 14px and readable on a phone - [ ] Text contrast meets WCAG AA: 4.5:1 for body, 3:1 for large text (24px+, or 18.66px+ bold) - [ ] Icons and meaningful graphics meet 3:1 contrast; meaning is never carried by color alone - [ ] Alt text is drafted and ready for the post or email; video has captions - [ ] Not overloaded — three messages maximum, enough negative space - [ ] Spacing is consistent (8px grid); no typos, broken glyphs, or missing characters Issue: [issue] -> [why] -> [how to fix] ## C. Conversion elements [/10] - [ ] CTA stands out, contrasts with its ground, uses a verb plus a benefit - [ ] USP or offer is explicit (at BOFU the viewer knows exactly what they get) - [ ] Trust elements present where needed: figures, testimonial, badge - [ ] Urgency or scarcity present if the campaign requires it, and genuinely true - [ ] The hook is strong enough (at TOFU, it stops the scroll in about 1.5 seconds) - [ ] Claims are substantiated; disclosures present where required Issue: [issue] -> [why] -> [how to fix] ## D. Platform fit [/10] - [ ] Dimensions match the channel spec - [ ] Safe zones respected — text and CTA are not covered by UI or cropped - [ ] Mobile-friendly (readable at 375px width) - [ ] File size and format correct (JPG/PNG/MP4/PDF) - [ ] Overlay text kept light enough not to crowd the frame - [ ] Email: 600px width, CTA button at least 44px tall Issue: [issue] -> [why] -> [how to fix] ## Action summary Keep: [element] — [why it works] Fix now (must fix): 1. [issue] -> [fix] -> [deadline] Consider (should fix): 1. [suggestion] -> [reason] Approve when: [specific condition] ``` ## Platform spec quick reference | Channel | Dimensions | Safe zone | |---------|-----------|-----------| | Meta Feed (FB/IG) | 1080x1080 (1:1) / 1080x1350 (4:5) | 20px each edge | | Meta Story / Reels | 1080x1920 (9:16) | 250px top / 250px bottom | | TikTok / Reels | 1080x1920 (9:16) | 150px top / 300px bottom, ~140px right | | LinkedIn | 1200x627 (1.91:1) | 40px each edge | | Pinterest | 1000x1500 (2:3) | 60px each edge | | YouTube thumbnail | 1280x720 (16:9) | avoid the bottom-right timestamp overlay | | Email header | 600x200 | 10px each edge | | Landing page hero | 1440px desktop / 375px mobile | headline and CTA visible without scrolling | ## Decision rules - Any group below 5/10 means REDO that group — do not approve overall. - Brand failures (group A) are blockers: a high total does not rescue an off-brand asset. - Accessibility failures at bo
Ke hoach Fullstack Marketing — master skill tong hop chien luoc, noi dung, trien khai, hieu suat, va timeline. Goi cac skill con de hoan thien output.
Use when the user needs an overall marketing plan for a period — objectives, segments, positioning, channel mix, content direction, budget, timeline, KPIs, and a risk matrix, adapted to US, EU, SEA, or LATAM. Trigger on 'marketing plan', 'marketing strategy for next year', 'go-to-market roadmap', 'plan for Q3', 'we have no marketing plan', 'where should we spend next quarter'. Also use when a founder only says the business needs to grow and has no idea which channel to start with. Not for — one specific campaign, see `02-campaign-brief-global`; working backward from a revenue goal to spend, see `10-reverse-kpi-global`; splitting a budget across channels and months, see `61-budget-planning-global`; taking a brand new product to market, see `59-go-to-market-global`.
Use when the user needs a monthly or weekly content calendar — posting schedule per channel, funnel ratio, content pillars, repurposing matrix, and an owner per slot. Trigger on 'content calendar', 'posting schedule', 'what should we post this month', 'editorial calendar', 'social media plan', 'we post randomly with no plan'. Also use when the user only says the team keeps running out of things to post. Not for — the brief for one specific post, see `36-content-brief-global`; the caption text itself, see `37-social-caption-global`; deciding next period content from last period data, see `40-next-content-plan-global`; a paid campaign timeline, see `02-campaign-brief-global`.
Lich noi dung thang — len lich dang bai da kenh voi ti le pheu, content pillar, repurposing matrix, va scoring tieu chi.
Brief chien dich marketing — 9 phan day du tu Context den Risk, bao gom creative direction, RACI, budget allocation theo phase, va auto-trigger cac skill lien quan.
Use when a specific campaign needs a brief the whole team can execute from — context, objective, audience, core message, creative direction, channels, deliverables, week-by-week timeline, approval gates, and risks. Trigger on 'campaign brief', 'creative brief', 'launch brief', 'brief the team on this campaign', 'we are running a promo next month', 'what is the plan for this campaign'. Also use when the user describes a promotion out loud and asks for something the team can actually run. Not for — the whole period plan, see `00-marketing-plan-global`; the list of design files needed, see `41-campaign-asset-list-global`; assigning work to one person, see `64-team-brief-global`; a new product launch sequence, see `59-go-to-market-global`.
Danh gia hieu suat marketing — audit performance ads va organic, chan doan root cause, de xuat toi uu voi action plan 48h va checklist hang tuan.
Use when marketing numbers look bad and the user needs to know WHY — layered root-cause diagnosis across tracking, delivery, creative, landing page, offer, and audience quality, 5-Whys, regional benchmarks for US, EU, SEA, and LATAM, and a 48-hour action plan. Covers dropshipping ROAS and BE-ROAS. Trigger on 'why is CPA so high', 'my ads are not converting', 'ROAS dropped', 'we are burning budget', 'performance is bad this month', 'diagnose the funnel'. Also use when the user pastes a screenshot of numbers with no question attached. Not for — auditing account configuration and scoring health, see `21-ads-audit-global`; writing a report someone else reads, see `07-marketing-report-global`; turning a raw export into insight, see `13-data-analysis-global`.