Skip to content

JasonColapietro/suede-creator-skills / skills/suede-reverse-engineer-anyone

suede-reverse-engineer-anyone

Verified

Use when asked "how did X grow", "reverse engineer their marketing", "what made this artist blow up", or "map their funnel". Suede reverse-engineers any company, creator, artist, founder brand, app, or launch from dated public evidence: a one-source growth curve, a log of every move, funnel and content patterns, hidden signals, the user's gap, and ranked plays routed to the Suede skill that runs each one. NOT FOR: a current-state competitor snapshot (use suede-competitor-profiling), publishing comparison pages (use suede-competitors), or why one post traveled (use suede-social).

references/play-routing.md

View on GitHub
# Play Routing

Every play names the Suede skill that runs it and, for repeat work, the loop that keeps it going. Use this table to route each one. Write the play's prompt so it opens with that skill (`$suede-...`) and passes along the teardown's specifics: the formula, the page family, the evidence link, the metric.

## Contents
- Routing table: search, AI, and site
- Routing table: paid, social, and creators
- Routing table: product, lifecycle, and revenue
- Routing table: music and creator releases
- Routing table: weak spots and Funnel Hack
- Loops and the monthly watch
- Plays that don't transfer
- Writing the prompt
- Example

---

## Routing Table: Search, AI, and Site

| What the teardown found | Skill that runs it | Loop that keeps it going (`$suede-marketing-loops`) |
|---|---|---|
| A page family carrying non-brand traffic (templates, integrations, use cases, locations) | `$suede-programmatic-seo` | The programmatic-SEO quality loop |
| Comparison or alternative pages ranking | `$suede-competitors` | The keyword-gap loop |
| Glossary, guides, or a blog driving traffic | `$suede-content-strategy`, then `$suede-copy` | The content-calendar refill loop |
| Named and cited first in AI answers | `$suede-ai-seo` | The AI-citation watch loop |
| Links from many domains to one asset | `$suede-seo-audit` (link gap and internal links), `$suede-public-relations` (earned coverage) | The backlink-prospecting loop |
| A free tool or calculator earning traffic | `$suede-free-tools` | One-off build |
| Technical or schema advantages on key pages | `$suede-seo-audit` | The ranking-drop watch loop |
| A landing or launch page that converts | `$suede-site-alchemy` | The landing-page regression loop |
| A positioning shift that came before growth (Stage 5 headline history) | `$suede-product-marketing` for positioning, `$suede-copy` for the homepage | The competitor-watch loop |
| A lead magnet or gated asset | `$suede-lead-magnets` | The lead-capture-asset loop |
| Directory and marketplace listings | `$suede-directory-submissions` | The directory-submission loop |
| App store page changes that lined up with installs | `$suede-aso` | One-off test, then the experiment-backlog loop |

## Routing Table: Paid, Social, and Creators

| What the teardown found | Skill that runs it | Loop |
|---|---|---|
| Long-running ads on a network (45+ days) | `$suede-ads` for structure, `$suede-ad-creative` for creative | The daily-creative-drop loop, the ad-fatigue loop |
| Founder or artist posts with numbers or behind-the-scenes driving reach | `$suede-social` | The content-repurposing loop |
| A content format or formula winning on a channel (Stage 6) | `$suede-social` for posts and short-form scripts, `$suede-video` for production | The content-repurposing loop |
| Short clips feeding long-form guides or courses | `$suede-clip-to-guide` | The content-repurposing loop |
| A consistent visual house style (thumbnails, covers, artwork) | `$suede-image` | One-off template build |
| Creators teaching or using the product or song | `$suede-influencer-outreach` | The social-listening loop |
| Newsletter, podcast, or video sponsorships (Stage 5) | `$suede-influencer-outreach` | The social-listening loop |
| Press or podcast runs | `$suede-public-relations` | The newsjacking loop |
| An editorial content engine (many sourced pieces per week) | `$suede-newsroom` | The content-calendar refill loop |
| Community threads or a Discord driving sign-ups or fans | `$suede-community-marketing` | The community-engagement loop |
| Events, meetups, listening parties, or conference sponsorships | `$suede-community-marketing` for the event program, `$suede-marketing-plan` for the calendar | Per event |
| Partner, integration, or collaboration listings | `$suede-co-marketing` | The partner-pipeline loop |
| A launch, launch week, or launch-platform spike | `$suede-marketing-plan` for sequencing, `$suede-public-relations` for coverage | The campaign-postmortem loop |

## Routing Table: Product, Lifecycle, and Revenue

| What the teardown found | Skill that runs it | Loop |
|---|---|---|
| Fast first result, light sign-up | `$suede-onboarding`, `$suede-site-alchemy` (the sign-up page) | The onboarding drop-off loop |
| A "made with" badge or shared-output loop | `$suede-referrals` (loop design), `$suede-site-alchemy` (the landing step) | The referral-nudge loop |
| An affiliate or referral program | `$suede-referrals` | The referral-nudge loop |
| A review campaign (Stage 5 review spike) | `$suede-referrals` (review program) | The review-site-management loop |
| A pricing or packaging change that lined up with growth | `$suede-pricing` | The pricing-page-experiment loop |
| A trial or credit model that converts | `$suede-paywalls` | The trial-conversion loop |
| Lifecycle email or in-app nudges | `$suede-emails` | The lifecycle-email-refresh loop |
| An onboarding email sequence that converts (Stage 3) | `$suede-emails` | The lifecycle-email-refresh loop |
| SMS flows with compliant opt-in | `$suede-sms` | The lifecycle-email-refresh loop |
| Save offers in the cancel flow (Stage 3) | `$suede-churn-prevention` | The churn-signal loop |
| Outbound to a defined account list | `$suede-prospecting`, `$suede-cold-email` | One-off list, then the experiment-backlog loop |
| A fast, well-run sales process (Stage 3) | `$suede-sales-enablement`, `$suede-revops` | One-off build |
| Bundles, guarantees, or offer stacks | `$suede-offers` | The pricing-page-experiment loop |
| A metric the user can't measure today | `$suede-analytics` (events), `$suede-attribution` (source credit) | The tracking-QA loop |
| A plan that sequences several plays | `$suede-marketing-plan` | The weekly-marketing-review loop |
| A/B tests seen in their funnel | `$suede-ab-testing` | The experiment-backlog loop |

## Routing Table: Music and Creator Releases

| What the teardown found | Skill that runs it | Loop |
|---|---|---|
| A release rollout (announce, tease, launch, follow-up) that lined up with growth | `$suede-campaign-in-a-box` | The campaign-postmortem loop |
| Release cadence that compounded (singles every N weeks, versions, waterfall) | `$suede-campaign-in-a-box` for the plan, `$suede-social` for the posts | The content-calendar refill loop |
| Clean metadata, credits, and artwork across releases | `$suede-release-linter` (check the user's release folder before delivery) | Per release |
| Sync placements that moved the curve | `$suede-sync-packaging` | Per pitch |
| Licensing, splits, or samples the user would need cleared before copying a play | `$suede-rights-passport` | Per release |
| Pre-save, newsletter, or fan-club capture | `$suede-lead-magnets`, `$suede-emails` | The lead-capture-asset loop |
| Merch bundles and presales | `$suede-offers` | The pricing-page-experiment loop |
| Playlist or press features | `$suede-public-relations` | The newsjacking loop |
| A fan community with rituals | `$suede-community-marketing` | The community-engagement loop |

## Routing Table: Weak Spots and Funnel Hack

| What the teardown found | Skill that runs it | Loop |
|---|---|---|
| A complaint theme the user solves | `$suede-competitors` (alternative page), `$suede-product-marketing` (positioning) | The keyword-gap loop |
| Price pain after their price rise | `$suede-offers` (switching offer), `$suede-pricing` | One-off offer |
| Objections in reviews and switching posts | `$suede-sales-enablement` (battle card), `$suede-customer-research` | Refresh with Watch mode |
| Voice of customer from their reviews | `$suede-customer-research` | The voice-of-customer loop |
| A deeper snapshot of one rival's positioning, pricing, features | `$suede-competitor-profiling` | The competitor-watch loop |
| Coupon or lifetime-deal distribution (Stage 5) | `$suede-offers` | One-off test |
| An order bump, upsell, or downsell sequence | `$suede-offers`, `$suede-site-alchemy` | The pricing-page-experiment loop |
| An abandoned-cart or abandoned-opt-in flow | `$suede-emails`, `$suede-sms` | The lifecycle-email-refresh loop |
| A quiz or webinar funnel | `$suede-lead-magnets`, `$suede-site-alchemy` | The lead-capture-asset loop |
| Conquesting ads on competitor names | `$suede-ads`, `$suede-competitors` | The paid-search query-mining loop |
| Swipe file of hooks, headlines, subject lines | `$suede-copy`, `$suede-ad-creative` | The monthly-creative-retro loop |
| An industry-specific play from `industry-signals.md` | The skill that section names | The loop that play needs, if any |

There is no separate link-building skill: link work goes to `$suede-seo-audit` (link gap, internal links, technical fixes) or `$suede-public-relations` (earned coverage and mentions).

## Loops and the Monthly Watch

Use `$suede-marketing-loops` to schedule any loop named above, with the teardown's files as its state.

**The monthly growth-move watch loop** keeps a teardown alive. Author it in `$suede-marketing-loops`, modeled on its competitor-watch loop, at a monthly cadence:

1. Re-collect the Stage 1 and Stage 5 signals (page scripts, pricing and headline captures, sitemap families, DNS, certificate logs, job board, reviews, ad libraries, paid promotion sweep, last month's posts, new interviews). Write a fresh `moves.csv`.
2. Diff against last month's log:
   ```bash
   node <skill-dir>/scripts/timeline.mjs diff --old teardowns/<target-slug>/moves-YYYY-MM.csv --new teardowns/<target-slug>/moves.csv --out teardowns/<target-slug>/new-moves.csv
   ```
3. Report only meaningful new moves (a new ad network, page family, loop, pricing change, content format, release pattern, hiring burst in one channel, complaint theme), plus any launch radar flag from `hidden-signals.md`. "No new moves" is the usual result.
4. For each new move, say whether it changes a play and which Suede skill takes it.
5. **State:** the dated move logs in `teardowns/<target-slug>/`. **Stop:** when the user ends the watch or the target goes quiet for three months.

## Plays That Don't Transfer

Some plays worked because of something the user doesn't have: a large round, an existing audience, a famous founder or feature artist, a label budget, a platform deal, a viral moment someone else made. Those go in plays to skip, with the reason. Every play also needs its metric tracked; if the user can't measure it today, add a `$suede-analytics` step to the prompt.

## Writing the Prompt

A good prompt gives the skill everything it would otherwise ask for:

1. **The skill:** "Use $suede-programmatic-seo."
2. **The evidence:** what the target did, its label, and the link.
3. **The user's version:** the specific asset, scaled to the user's stage.
4. **The formula or house style** from Stage 6, for content plays.
5. **The metric** and when to check it.

## Example

> Use $suede-programmatic-seo. Acme's `/templates/*` family (480 pages, Observed in Wayback CDX, pulled 2026-10-30) carried about 41% of their non-brand search traffic (Semrush estimate, pulled 2026-10-30), and it existed four months before their growth inflection. We have 12 template pages. Plan a template page family for our invoicing product: the template types our customers search for, the page structure, the data each page needs, and internal links from our pricing and features pages. Start with the 20 highest-volume template keywords. Track impressions for `/templates/` in Search Console weekly, and check at 60 days.

> Use $suede-campaign-in-a-box. [Artist]'s last three singles each ran a 21-day rollout: a 15-second hook clip on day 1, a lyric card on day 7, a pre-save push on day 14, and a live version 10 days after release (Observed, links in `moves.csv`). Each rollout sat inside a cluster with +9 to +14 pp lift in monthly listeners (one tracker, pulled 2026-11-01). Plan the same four-beat rollout for our next single, scaled to two posts a week. Track pre-saves and day-7 streams, and check 14 days after release.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall