ads-dna
Brand DNA extractor for paid advertising. Scans a website URL to extract visual identity, tone of voice, color palette, typography, and imagery style. Outputs brand-profile.json to the current directory. Run before /ads create or /ads generate for brand-consistent creative. Triggers on: brand DNA, brand profile, extract brand, brand identity, brand colors, what is the brand voice, analyze brand, brand style guide.
Hainrixz · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Hainrixz/claude-ads --skill ads-dna技能说明
name: ads-dna description: "Brand DNA extractor for paid advertising. Scans a website URL to extract visual identity, tone of voice, color palette, typography, and imagery style. Outputs brand-profile.json to the current directory. Run before /ads create or /ads generate for brand-consistent creative. Triggers on: brand DNA, brand profile, extract brand, brand identity, brand colors, what is the brand voice, analyze brand, brand style guide." user-invokable: false
Ads DNA: Brand DNA Extractor
Extracts brand identity from a website and saves it as brand-profile.json
for use by /ads create, /ads generate, and /ads photoshoot.
Quick Reference
| Command | What it does |
|---|---|
/ads dna <url> | Full brand extraction → brand-profile.json |
/ads dna https://acme.com --quick | Fast extraction (homepage only) |
Process
Step 1: Collect URL
If the user hasn't provided a URL, ask:
"What website URL should I analyze for brand DNA? (e.g. https://yoursite.com)"
Step 2: Fetch Pages
Use the WebFetch tool to retrieve each page. For each URL, use this fetch prompt:
"Return all visible text content, the full contents of any
<style>blocks, inlinestyle=attributes,<meta>tags, Google Fonts@importURLs, and anyog:imagevalues found on this page."
Fetch in this order:
- Homepage (
<url>) - About page: try
<url>/about, then<url>/about-us, then<url>/our-story - Product/Services page: try
<url>/product, then<url>/products, then<url>/services
If --quick flag was provided: fetch the homepage only; skip steps 2 and 3.
If a secondary page returns a 404 or redirect error, continue with fewer pages and note: "Secondary pages unavailable; extraction based on homepage only. Confidence may be lower."
Step 2b: Capture Brand Screenshots
After fetching pages, capture 3 screenshots for comprehensive brand anchoring.
These serve as visual style references during /ads generate; the same approach
Pomelli uses to anchor ad images to the actual brand aesthetic.
Capture the following:
- Homepage hero section (above the fold):
python ~/.claude/skills/ads/scripts/capture_screenshot.py [url]
Saves: ./brand-screenshots/{domain}_homepage.png
- Product or services page:
python ~/.claude/skills/ads/scripts/capture_screenshot.py [url]/products
Saves: ./brand-screenshots/{domain}_product.png
- About page (brand personality):
python ~/.claude/skills/ads/scripts/capture_screenshot.py [url]/about
Saves: ./brand-screenshots/{domain}_about.png
If a page is not found or returns an error, skip it gracefully and continue with the remaining pages.
If --quick flag was provided: skip screenshot capture entirely.
If capture fails (Playwright not installed, network error, JS-heavy SPA that times out):
- Log:
"Screenshot capture skipped; run: python3 -m playwright install chromium" - Continue without screenshots
- Do NOT set the
screenshotsfield in brand-profile.json
Step 3: Extract Brand Elements
From the fetched HTML, extract:
Colors:
og:imagemeta tag → analyze dominant colors (note 2-3 prominent hex values)- CSS
background-coloronbody,header,.hero,.btn-primary - CSS
coloronh1,h2,.btn - CSS
border-colororbackgroundon.cta,.button - Identify: primary (most prominent brand color), secondary (supporting colors), background, text
Typography:
@import url(https://fonts.googleapis.com/...)→ extract font names from URL path- CSS
font-familyonh1,h2,body,.headline - If Google Fonts URL contains
family=Inter:wght@..., heading_font = "Inter"
Voice: Analyze hero headline, subheadline, About page intro, and CTA button text. Score each axis 1-10 using these heuristics:
| Signal | Score direction |
|---|---|
| Uses "you/your" frequently | formal_casual → casual (+2) |
| Uses technical jargon | expert_accessible → expert (-2) |
| Short punchy sentences (≤8 words) | bold_subtle → bold (+2) |
| Data/stats in hero | rational_emotional → rational (-2) |
| "Transform", "revolutionize", "disrupt" | traditional_innovative → innovative (+2) |
| Customer testimonials lead | rational_emotional → emotional (+2) |
| Industry awards, "trusted by X" | traditional_innovative → traditional (-1) |
Confidence Scoring
Each voice axis gets a confidence rating based on signal count:
- High (3+ signals): strong evidence for axis position
- Medium (2 signals): moderate evidence, may need validation
- Low (1 signal): weak evidence, treat as estimate
Also extract structured data when available: schema.org markup, Open Graph tags (og:title, og:description, og:image), Twitter Card metadata.
Imagery style (from og:image and any visible hero image descriptions):
- Photography vs. illustration vs. flat design
- Subject matter (people, product, abstract, data)
- Composition style (clean/minimal vs. busy/editorial)
Forbidden elements (infer from brand positioning):
- Enterprise/B2B brands → add "cheesy stock photos", "consumer lifestyle imagery"
- Healthcare → add "unqualified medical claims", "before/after imagery"
- Finance → add "get rich quick imagery", "unrealistic wealth displays"
- Consumer brands → usually no forbidden elements
Step 4: Build brand-profile.json
Read ~/.claude/skills/ads/references/brand-dna-template.md for the exact schema.
Construct the JSON object following the schema precisely. Use null for any
field that cannot be confidently extracted; do not guess.
Example of a low-confidence field:
"typography": {
"heading_font": null,
"body_font": "system-ui",
"pairing_descriptor": "system default (Google Fonts not detected)"
}
Step 5: Write brand-profile.json
Wr
阅读完整来源 ↗