--- name: match-assets description: "Match indexed brand assets to calendar posts and assign each post its creative mode (anchor-compose, enhance-extend, style-referenced, pure-creative). Triggers on \"/match-assets\", \"match assets\", \"which photos for which posts\", \"assign creative modes\", \"pair assets to the calendar\", or right after parse-calendar and before compose-creative. Reads the asset index; posts with no suitable asset are flagged rather than force-matched." argument-hint: "--brand --month " effort: high user-invocable: true --- # /socialforge:match-assets — Asset Matcher Match brand assets to parsed calendar posts using the multi-factor scoring algorithm. Assigns one of 4 creative modes per post. ## Context efficiency Asset-heavy skill. **Grep before Read** the asset catalog (`${CLAUDE_PLUGIN_DATA}/socialforge/brands//asset-index.json`) — never list the asset directory. Reference generated images / videos by path, not by loading metadata. Brand profile loads once per session. ## Prerequisites - Calendar parsed (calendar-data.json exists) - Asset index built (asset-index.json exists) If either is missing, prompt: "Run `/socialforge:parse-calendar` first, then `/socialforge:index-assets`." ## The Matching Algorithm For each post, calculate a multi-factor score against every indexed asset: | Factor | Weight | What It Measures | |--------|--------|------------------| | Tag Overlap | 30% | Post keywords vs asset tags | | Suitability Match | 25% | Asset's "suitable_for" vs post context | | Content Bucket Match | 20% | Does asset suit this content bucket? | | Crop Feasibility | 15% | Can asset be cropped to all required platform ratios? | | Freshness | 10% | Favours assets not already used this month | **Freshness factor:** scored as `1 - penalty` and weighted at 10% alongside the other four factors (the five weights sum to 1.00). Penalty by prior uses this month: 0 uses = 0.00 | 1 use = 0.15 | 2 uses = 0.40 | 3+ uses = 0.70. Reusing an asset within the same week adds a further 0.50 to the penalty (capped at 1.00). ## Creative Mode Assignment | Score Range | Recommended Mode | |-------------|-----------------| | > 0.8 | ANCHOR_COMPOSE or ENHANCE_EXTEND | | 0.5 - 0.8 | ENHANCE_EXTEND or STYLE_REFERENCED | | 0.3 - 0.5 | STYLE_REFERENCED | | < 0.3 | PURE_CREATIVE | Also selects 2-5 style reference images per post (always fed to AI generation alongside prompts). ## Process 1. Load calendar-data.json and asset-index.json 2. For each post: extract keywords → score all assets → rank → assign mode 3. Select style references per post 4. Generate coverage report ## Coverage Report ``` Asset Matching Complete: 28 posts ANCHOR_COMPOSE: 8 posts (direct brand asset matches) ENHANCE_EXTEND: 5 posts (asset needs enhancement) STYLE_REFERENCED: 9 posts (AI gen guided by brand DNA) PURE_CREATIVE: 4 posts (full AI generation) CAROUSEL_TEMPLATE: 2 posts (HTML template rendering) Asset gaps: 3 posts flagged — P07, P14, P22 Top used assets: asset_012 (3 posts), asset_005 (2 posts) ``` The gap flag is a boolean (`gap_flag`), raised when a HERO or HUB post's best asset scores below 0.3. It marks which posts need attention; it does not explain which kind of asset is missing — inspect the flagged posts to decide what to shoot or upload. 5. Present for user confirmation — user can override any match 6. Save to `output/{brand}/{YYYY-MM}/asset-matches.json` ## User Override Overrides are conversational, not flags — `match_assets.py` accepts only `--brand` and `--month`. Adjustments are made at the confirmation step (step 5) and written back to asset-matches.json. For any post, user can: - Accept the recommendation - Select a different asset: "Use asset_015 for P07" - Change creative mode: "Make P14 PURE_CREATIVE instead" - Upload a new asset on the spot - Skip: "I'll handle P22 manually" ## Timeout & Fallback - Per-post matching: 5-second timeout. If an asset index is very large (500+ images), process in batches. - Show progress: `[12/28] Matching Post P12 — best match: asset_023 (score: 0.74, STYLE_REFERENCED)`