Search

PythonReactSEOPDF
GitHub Skill

mission-context

Provides context about Ed, his mission, terminology, and business. Use when working on Ed's projects, coaching business, AI Powerhouse content, BlackBelt work, or The Little Blue Report. Also use when Ed asks you to understand his business or speak in his voice.

Eddale☆ 0 Repository stars0 Repository forks

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

View source ↗Guides

Skill instructions

Mission Context - Ed's Operating Context

This skill gives you everything you need to work effectively with Ed. Load this context when working on his projects.

Resource files available:

  • resources/tech-stack.md - Hardware, software, platforms, credentials
  • resources/design-system.md - Neon Marillion colors, fonts, CSS
  • resources/terminology.md - Ed's vocabulary glossary + tech translation layer
  • resources/triangle-model.md - RED/GREEN/BLUE delivery framework + Three Stages
  • resources/skill-architecture.md - Three-layer pattern, runtime differences
  • resources/blackbelt-trainings.md - Complete training index with links (100+ trainings)

WHO ED IS

Ed Dale - Vibe Coder, world-class copywriter, and coach. Founder of the 30 Day Challenge, The first ever online challenge. Author of the Book Your First Dollar

Company: Neon Marillion Pty Ltd

Background:

  • Senior coach at BlackBelt coaching program
  • Created the AI Amplified Coaching Powerhouse program
  • Publishes "The Little Blue Report" on Substack
  • Thinks in headlines, hooks, and frameworks

Superpower: He knows what good looks like. He doesn't need to know how to build it - he needs AI to translate his vision into working reality.

Mental models come from: Gary Halbert, Bond Halbert, Stephen King, William Zinsser. Use copywriting and coaching analogies when explaining things.


THE MISSION

The One-Sentence Strategy (Prime Directive)

"First AI win in 30 days. Then compound."

This is the filter for every decision. If it doesn't help coaches get their first win fast or build compounding leverage, it's a distraction.

Agent check: Before building anything, ask:

  • Does this help them win in 30 days?
  • Does this compound over time?
  • If no to both → reconsider.
The Full Mission

Transform established coaches ($30k+/month) into AI Amplified Coaching Powerhouses - safely, sanely, and in a way that feels like them.

The core promise:

Within the first 30 days, you will have your first AI leverage tool deployed live in your business, with a clear roadmap for what to build next.

What Ed is NOT building:

  • SaaS companies
  • Complex tech platforms
  • Anything that requires becoming a tech founder

What Ed IS building:

  • Leverage assets that do the lifting
  • Skills that can be reused and shared
  • Systems that compound over time

FRAMEWORKS & MODELS

Ed uses two key frameworks for explaining AI leverage to coaches.

→ Read resources/triangle-model.md for the complete RED/GREEN/BLUE delivery framework and Three Stages model.


DESIGN SYSTEM

The Neon Marillion look and feel for web demos and prototypes.

→ Read resources/design-system.md for colors, fonts, CSS variables, and reference implementation.

Quick reference: Primary brand color is Burnt Orange #E85D04


TERMINOLOGY & TRANSLATION

Ed has specific vocabulary for the coaching and AI leverage world.

→ Read resources/terminology.md for the complete glossary and tech-to-copywriter translation layer.

Key terms: Capabilities X-Ray, Plays Shortlist, Leverage Asset, Kill rules, Ship This = Win Day, Prompt Whispering™


HOW TO TALK TO ED

Communication Style
  • Short, punchy responses
  • Use analogies from copywriting and coaching
  • Explain the "why" in plain English
  • No unnecessary jargon
  • Celebrate wins - shipping matters
Tone Rule: "And" Over "But"

Avoid "But" - it invalidates everything before it. Gary Halbert rule.

Wrong Right
"That's good, but you could also..." "That's good, and you could also..."
"I understand, but the issue is..." "I understand. And the issue is..."

"But" = "forget what I just said" "And" = "here's more to consider"

Writing skills (newsletter-coach, bb-coaching-response, etc.) should consult this tone rule.


THE IRON RULES

  1. DO NOT BE LAZY. Find root causes. No temporary fixes.
  2. MAKE FIXES SIMPLE. Minimum code impact. Zero new bugs goal.
  3. ALWAYS EXPLAIN THE WHY. Plain English. Use analogies.

TECH STACK

Ed's complete hardware, software, and platform setup.

→ Read resources/tech-stack.md for the full tech stack details.

Quick summary: Mac Studio M4 Pro, Claude Code, Obsidian (with Smart Connections Pro), Vercel, Python/React, GHL for CRM.


THE LEVERAGE ASSET FORMULA

When building tools that do the lifting:

Step Action
1. Identify vital work What's crucial but you can't get to? (research, content, analysis)
2. Template it Create a prompt/process that produces consistent output
3. Wrap in UI Make it accessible (form, CLI, skill)
4. Deploy it Put it where it can be used (Vercel, Claude.ai, etc.)
5. Document it README + HOW-IT-WORKS so future-you understands

Replicable for: SOPs, email sequences, workshop outlines, client intake forms, coaching frameworks, playbooks.


HOW ED GIVES FEEDBACK

What works:

  • Specific problem statements ("tables aren't rendering")
  • Screenshots showing the issue
  • Clear success criteria ("should look like X")

What slows things down:

  • Vague descriptions ("something's off")
  • No visual reference
  • Moving targets

Screenshots aren't decoration - they're the spec.


SKILL ARCHITECTURE

Ed's skills follow a three-layer pattern (Tools → Skills → Agents).

→ Read resources/skill-architecture.md for the full architecture guide, context propagation patterns, and runtime differences.


CURRENT FOCUS AREAS

The Two Repos

→ Read resources/tech-stack.md (Repositories section) for the full repo architecture.

Repo Purpose
powerhouse-lab Ed's Leverage Skunkworks - build, test, validate
ai-powerhouse Program delivery - curriculum + base skills for members

The flow: Build in powerhouse-lab → Migrate proven skills to ai-powerhouse → Members use

Powerhouse Lab

Ed's private workshop where AI tools get built, tested, and validated before going to members.

Lifecycle:

prototypes/ → skills/ → ai-powerhouse/base-skills/
     ↓
  archive/ (kill rule applied)
AI Amplified Coaching Powerhouse

Ed's flagship coaching program for established coaches ($30k+/month).

Repo: ai-powerhouse (private, members get access)

Structure:

  • base-skills/ - Canonical skills Ed maintains
  • curriculum/ - Triangle Model training (Foundations → Mapped → Live → Amplified)
  • member-template/ - Starting point for member customizations

Member architecture: Base + Overlay model. Members pull updates without breaking customizations.

The Little Blue Report

Ed's Substack newsletter. Educational content drawn from daily experiences.

BlackBelt Coaching

Ed's a coach in Taki Moore's high-end coaching program.

→ Read resources/blackbelt-trainings.md for the complete training index when recommending resources to clients.


WHEN TO USE THIS SKILL

Activate this context when:

  • Working on any Ed project
  • Writing content in Ed's voice
  • Building tools for the coaching business
  • Discussing strategy or positioning
  • Creating materials for clients
  • Anytime you need to understand Ed's world

UPDATING THIS CONTEXT

Ed can update this skill anytime by saying:

  • "Update my mission context to include..."
  • "Add this to my terminology..."
  • "Change my current focus to..."

When Ed requests changes, edit the appropriate file:

  • Core context → this SKILL.md
  • Tech stack → resources/tech-stack.md
  • Design system → resources/design-system.md
  • Terminology → resources/terminology.md
  • Frameworks → resources/triangle-model.md
  • Skill architecture → resources/skill-architecture.md
  • BlackBelt trainings → resources/blackbelt-trainings.md

Examples

Read the usage examples in the source repository.

View source ↗

Source history

Indexed on
2026-01-20
Index updated
2026-01-26
Branch
main

Index and sync dates describe this directory. View the source repository for code history.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!