bundles/sales/skills/traffic-architect/SKILL.md
Design traffic strategy, build Dream 100 list, or plan audience acquisition using Traffic Secrets principles. Activates for "build my traffic plan," "create my Dream 100," or traffic acquisition planning.
npx skillsauth add shipshitdev/library traffic-architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design traffic strategies using Traffic Secrets principles: Dream 100, Work In vs. Buy In, traffic temperature, and audience ownership.
Brunson's Core Principle: "Your customers are already congregating. Find the watering holes."
Core Components:
| Category | What to Find | How Many | |----------|--------------|----------| | Influencers | People they follow | 25 | | Podcasts | Shows they listen to | 25 | | Channels | YouTube, newsletters | 15 | | Communities | Groups, forums, subreddits | 15 | | Publications | Blogs, sites they read | 10 | | Events | Conferences, meetups | 10 |
| Situation | Recommendation | |-----------|----------------| | Pre-revenue | Work In (validate first) | | <$5K/mo | Work In primary | | $5K-20K/mo | Work In + test Buy In | | >$20K/mo | Mix based on CAC/LTV | | Proven funnel | Buy In to scale |
| Temp | Strategy | Content | |------|----------|---------| | Cold | Value-first, no selling | How-to, guides, lead magnets | | Warm | Low-ticket offers | Tripwires, webinars, case studies | | Hot | Direct offers | Sales pages, booking pages |
Ask:
| Skill | When to Use |
|-------|-------------|
| traffic-validator | Validate strategy |
| funnel-architect | Design funnel |
| channel-validator | Validate channel focus |
| copy-validator | Validate hooks |
For detailed execution workflow, templates, and 90-day plans: Load ${CLAUDE_SKILL_DIR}/references/full-guide.md when the user asks for step-by-step execution, campaign templates, or a 90-day plan.
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.