메뉴
TikTok Ads deep analysis: creative-first strategy, safe zone compliance, tracking, bidding, campaign structure, TikTok Shop, Smart+ campaigns, creative diversity for retrieval. Use when user says TikTok Ads, TikTok marketing, TikTok Shop, Spark Ads, Smart+, or USDS.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | ads-tiktok |
| description | TikTok Ads deep analysis: creative-first strategy, safe zone compliance, tracking, bidding, campaign structure, TikTok Shop, Smart+ campaigns, creative diversity for retrieval. Use when user says TikTok Ads, TikTok marketing, TikTok Shop, Spark Ads, Smart+, or USDS. |
| user-invokable | false |
| tested_date | "2026-05-17T00:00:00.000Z" |
| tested_with | claude-code v2.x |
ads/references/tiktok-audit.md for full 28-check auditads/references/benchmarks.md for TikTok-specific benchmarksads/references/platform-specs.md for creative specificationsads/references/scoring-system.md for weighted scoring algorithmTikTok is a creative-first platform. Unlike Google/Meta where targeting and bidding drive most performance, TikTok success depends primarily on creative quality.
All critical text, logos, and CTAs must be within the safe zone:
┌──────────────────────┐
│ UNSAFE (status) │ Y: 0-150px
├──────────────────────┤
│ │UNSA│
│ │FE │
│ SAFE ZONE │icon│ X: 40-940px
│ 900×1320px │ │ Y: 150-1470px
│ │ │
│ │ │ Right 140px: like/comment/share
├──────────────────────┤
│ UNSAFE (caption) │ Y: 1470-1920px
└──────────────────────┘
If e-commerce, evaluate TikTok Shop setup:
Mandatory for all Shop Ads since July 2025. Evaluate:
AI-powered creative variations generated from product URLs.
| Setting | Value |
|---|---|
| CPM | 40-60% cheaper than Meta |
| Spark Ads CTR | ~3% (vs ~2% standard) |
| Smart+ adoption | 42% of advertisers |
| Smart+ ROAS | 1.41-1.67 |
| Shop CVR | >10% |
| Available markets | 11 countries (US, UK, ID, MY, PH, SG, TH, VN, JP, KR, BR) |
| Metric | Pass | Warning | Fail |
|---|---|---|---|
| CTR (in-feed) | ≥1.0% | 0.5-1.0% | <0.5% |
| Creatives per ad group | ≥6 | 3-5 | <3 |
| Video watch time | ≥6s | 3-6s | <3s |
| Learning conversions | ≥50/week | 30-50/week | <30/week |
| Daily budget | ≥50x CPA | 20-49x CPA | <20x CPA |
| Creative age (declining) | <7 days | 7-14 days | >14 days |
TikTok Ads Health Score: XX/100 (Grade: X)
Creative Quality: XX/100 ████████░░ (30%)
Technical Setup: XX/100 ██████████ (25%)
Bidding & Budget: XX/100 ███████░░░ (20%)
Structure: XX/100 █████░░░░░ (15%)
Performance: XX/100 ████████░░ (10%)
TIKTOK-ADS-REPORT.md: Full 28-check findings with pass/warning/failBuild, secure, and package Electron desktop apps — main/preload/renderer split, contextIsolation-safe typed IPC over a preload bridge, BrowserWindow + application menu + app naming, a strict CSP, and distribution (electron-builder/Forge, productName, code signing). Use when building an Electron app, wiring IPC, hardening security, fixing the app/menu name, or packaging. Do NOT use for web-only React UI (use cleanui) or Expo/React Native.
Write an engineering tech spec (design doc / RFC) that turns an approved PRD into an implementable design. Use when turning a PRD or epic into a design doc, writing an RFC, or answering 'how should we build this'. Do NOT use for product requirements (prd-development) or recording a single architectural decision (adr).
Run a right-sized threat-modeling pass (trust boundaries, STRIDE, abuse cases) on a forming design so security decisions land before Sign-Off 2. Use when a design adds attack surface — a new endpoint, data class, integration, or authz change. Do NOT use for code-diff security review (/security-review), pentests, or compliance audits.
Build and maintain a durable automated E2E suite — Playwright for web, Maestro for Expo/React Native: stable selectors, owned test data, CI gating, and a flake policy with teeth. Use when automating the E2E journeys a test plan defines or fixing a slow/flaky suite. Do NOT use for deciding what to test (test-strategy) or unit tests (tdd).
Run a go/no-go release review producing a scored readiness report — rollout plan, observability, rollback, comms verified before shipping. Use when preparing a release/launch, a go-live checklist, a rollout plan, or 'are we ready to ship'. Do NOT use for store-submission mechanics (expo-deployment) or writing the test plan itself (test-strategy).
Define production health before launch: user-centric SLIs, SLO targets with error budgets, burn-rate alerts that page on user pain (not CPU), and a runbook per pageable alert. Use when designing SLOs, alerts, error budgets, or runbooks. Do NOT use for the go/no-go review (release-readiness) or post-incident analysis (incident-postmortem).