creative-mechanics
A library of creative mechanics — the structural patterns that define how an ad constructs meaning between its hook, visuals, and narrative. Use this whenever designing ad concepts, briefing creative, or trying to explain why a specific ad works beyond just its hook or format. Trigger when a user describes an ad they saw and wants to understand or replicate what made it work, when building a creative concept from a messaging angle, or when execution needs more than a hook and a format — it needs a structural idea. Creative mechanics sit between hooks and visual formats in the Creative Strategy Engine: hooks say what, formats show how, mechanics define the cognitive or emotional mechanism that makes the concept land. Always pair with Hook Writing for opening line execution and Hook Tactics for tactic classification.
What this skill does
# Creative Mechanics
Creative mechanics are the **structural patterns that define how an ad creates meaning.**
They are not hooks (what you say) and not visual formats (what it looks like). They are the underlying mechanism — the cognitive or emotional move the ad makes that causes the viewer to feel something, conclude something, or remember something.
**The same mechanic can be executed across multiple visual formats.**
The Implied Answer works as a lifestyle video, a static image, a talking head, or a carousel. The mechanic travels. The format is just the vessel.
---
## Where Mechanics Sit in the Creative Stack
```
Messaging Angle (Creative Strategy Engine)
↓
Creative Mechanic ← YOU ARE HERE
↓
Hook (Hook Writing + Hook Tactics)
↓
Visual Format
```
The messaging angle defines the **core truth.**
The mechanic defines **how the ad makes the viewer arrive at that truth.**
The hook is the **opening line that triggers the mechanic.**
The visual format is **the production structure that delivers it.**
---
## How to Use This
1. Start with your messaging angle from the Creative Strategy Engine
2. Ask: *how do I want the viewer to arrive at this truth?* — that's your mechanic
3. Select the mechanic that best serves the awareness stage and persona
4. Write the hook that opens the mechanic (Hook Writing)
5. Choose the visual format that best executes it
---
## The Mechanic Library
---
### The Implied Answer
**What it is:** The hook poses a question that sounds like mild judgment, confusion, or curiosity. The visuals silently answer it with an aspirational truth. No one states the answer out loud — the viewer concludes it themselves.
**Why it works:** Self-conclusions bypass ad skepticism. When the viewer connects the dots themselves, the insight lands as their own thought, not a brand claim.
**Awareness stage fit:** Unaware, Problem-Aware — works best when the viewer doesn't yet know they want the product. The question meets them where they are; the visual shows them where they could be.
**Structure:**
- Hook = question that sounds like an observation someone would make about the customer
- Visual = the silent answer (the product's world, without explanation)
- Brand never states the connection
**Example:**
- Hook: *"Why do you always stay home?"*
- Visual: Guy hanging incredible artwork all over a beautiful apartment
- Implied truth: *His home is so good he doesn't need to leave*
- Brand: Art/home decor
**More examples by category:**
- Sleep brand → *"Why does she never want to go out anymore?"* / visual of an incredible bedroom setup
- Home gym → *"Why does he never go to the gym?"* / visual of an insane home gym mid-workout
- Coffee brand → *"Why does she always wake up before everyone?"* / visual of a perfect quiet morning ritual
---
### The Social Witness
**What it is:** Someone other than the customer notices the change. A compliment, a double-take, an unsolicited "what are you doing differently?" The product's impact is validated through a third party's reaction — not a claim, not a review, not a before/after.
**Why it works:** Third-party validation is more believable than self-reported results. It also implies the change is *visible enough that other people notice* — which raises the stakes of not having the product.
**Note:** This is often a secondary mechanic layered onto another. The artwork ad uses Implied Answer as the primary mechanic and Social Witness as the secondary — "why do you always stay home" implies someone noticed the behavioral change.
**Awareness stage fit:** Problem-Aware, Product-Aware — works well when the viewer already knows they have the problem and needs to believe the product actually works.
**Structure:**
- Setup: Customer living their normal life, not talking about the product
- Witness moment: Someone else notices and comments
- Reaction: Customer's response is low-key, not a sales pitch
- Product appears naturally as the obvious explanation
**Example:**
- Hair growth serum
- Scene: Woman at work, colleague stops her in hallway
- Witness: *"Wait — did you do something different? Your hair looks incredible."*
- Reaction: She just smiles
- Product shown at end, no voiceover
---
### The Overheard Conversation
**What it is:** The ad is framed as something you weren't supposed to see — a text thread, a DM, a group chat, a conversation between friends. It feels like eavesdropping, not advertising.
**Why it works:** Removes the "this is an ad" filter entirely. Viewers process it as social content, not branded content. The informal framing also makes claims feel more credible — friends don't use marketing language with each other.
**Awareness stage fit:** Unaware, Problem-Aware — especially effective for reaching people who don't know they have the problem yet, because it mimics how people actually discover products (through friends, not ads).
**Structure:**
- Frame: text thread, DM, comment section, or overheard dialogue
- Trigger: one person mentions a problem or asks a question
- Resolution: the other person casually recommends the product
- No brand voiceover, no formal CTA — ends like a real conversation would
**Example:**
- Gut health supplement
- Opens on iMessage thread
- Friend 1: *"okay don't judge me but I've been using this probiotic"*
- Friend 2: *"omg which one"*
- Friend 1 screenshots the product
- Ad ends
---
### The Reframe
**What it is:** Opens by validating a belief the viewer already holds — something they've been told, something they've tried, something that makes logical sense. Then flips the frame entirely. The product isn't the hero. The new perspective is.
**Why it works:** Viewers share things that changed how they think, not things that sold them something. The Reframe manufactures that "I never thought about it that way" moment, which drives both conversion and organic sharing.
**Not to be confused with the Contrarian hook tactic.** A Contrarian hook flips a belief in the opening line. The Reframe builds to the flip as the structural point of the entire concept — it's architecture, not just an opening.
**Awareness stage fit:** Problem-Aware, Solution-Aware — works best when the viewer has already tried things that didn't work and needs a new explanation for why.
**Structure:**
- Open: validate the conventional wisdom ("you've been told X")
- Middle: show that they've been doing everything right by that logic
- Flip: reveal the real problem is something else entirely
- Resolution: product solves the *real* problem, not the assumed one
**Example:**
- Sleep tracking app
- Open: *"You've been told you just need 8 hours of sleep"*
- Middle: shows person doing everything right — in bed on time, no screens, etc.
- Flip: *"The problem was never the hours. It was the quality."*
- Product: the thing that finally explains why they're still exhausted
---
### The Borrowed Enemy
**What it is:** The ad describes a problem, an ingredient, a feeling, or an experience that is *obviously* caused by a specific competitor — without ever naming them. The viewer makes the connection themselves.
**Why it works:** Naming a competitor triggers defensiveness and legal risk. Not naming them but making the reference unmistakable lets the viewer do the conquesting themselves — and again, self-conclusions land harder than stated claims.
**Awareness stage fit:** Solution-Aware, Product-Aware — most effective when the viewer is already shopping and comparing options, and has likely already experienced the competitor's product.
**Structure:**
- Describe the problem in vivid, specific, recognizable detail
- Use language that *only applies* to the competitor's product (specific ingredients, form factor, feeling, side effect)
- Never name them
- Position your product as the natural alternative
**Example:**
- Clean energy drink
- *"That jittery crash feeling... ingredients you can't pronounce... wondering what you just put in your body"*
- Every Red Bull drinker knows exactly wRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".