Every skill you need to deliver a world-class founder experience. One command. Immediate output. The system handles the complexity. You bring the care.
Skills live in a secure database. Your team interacts through Claude Code. The prompt content never leaves the server.
5 visual skills (Strategy Deck, Landing Page Build, Workshop Deck, Waterfall Visual, Ad Creative Builder) now use a two-step process. Step 1 generates structured JSON content via MCP. Step 2 renders that JSON into a shared HTML template and deploys to Vercel locally. This eliminates truncation, reduces token usage by 73%, and lets template updates apply to all future builds automatically.
The skill content never enters your session. The edge function reads it from the database, calls Claude server-side, and returns only the finished output. Per-user API keys. Every call logged with token counts and cost estimates. Rate limited to 100 calls/hour.
Visual skills no longer generate raw HTML. They generate structured JSON, then render it into shared templates that enforce brand consistency automatically.
Templates live in the velocity-templates GitHub repo. The build script (build.js) injects founder data into templates.
Templates use CSS custom properties for brand colors — every founder's page looks like THEIR brand, not ours.
Template updates apply to all future builds automatically.
Full technical docs: See SKILLS-ARCHITECTURE.md in the velocity-templates repo for the complete specification, JSON schemas, and template development guide.
Two steps. Everything is distributed automatically by the context sync system.
Don sends you a single-use bootstrap URL. Run it in your terminal:
curl -sL "https://<bootstrap-url>" | bash
One command sets up everything: context sync, 46 Velocity skills via MCP, credential vault access, Claude Code hooks, remote control, and shell aliases. The token is single-use and expires in 48 hours.
Already onboarded but need skills? Run: curl -sL "https://yhvssclmrddiowlccvjc.supabase.co/functions/v1/operator-bootstrap?mode=skills-only" | bash
Open Claude Code and run /start. This reads your context files, checks journal freshness, and reports status. You're ready to use any skill.
# Ask Claude to run any skill
Run velocity-brand-positioning for Kaylor Betts
# Or use the two-step process for visual skills
Run velocity-brand-strategy-deck for Kaylor Betts
# Then render with the template
/velocity-build
API keys are managed automatically. Your key is embedded in the bootstrap command and stored securely at ~/.fos_credentials (chmod 600). You never need to copy or paste keys. If you need a key reissued, contact Don.
New to the skills system? Here's the fastest path to delivering value.
The golden rule: the more context you feed the skills (Fathom transcripts, intake data, prior deliverables, website URL), the more specific and personalized the output. Feed them everything.
New architecture: Visual skills (decks, landing pages, infographics, ad creatives) are now a two-step process: content generation via MCP, then local rendering + deployment. This is faster, more reliable, and never truncates.
Run this on every deliverable before the founder sees it. Check each item. The progress bar tracks your readiness.
Every one of these has happened. None of them should happen again.
The live reveal IS the experience. Never drop a PDF in Slack. Always walk through it on a call. Record on Fathom.
The Fathom transcript is 60% of the voice weight. Without it, the output is generic. Always wait for the Deep Dive transcript before generating Phase 1 deliverables.
Read every deliverable out loud before presenting. If there are brackets, placeholders, or AI-smell language ("unlock your potential"), fix it. One bad deliverable erases ten good ones.
"Designer of companies," "systems over hustle," "peace, profit, purpose" — these are Matt's phrases. Each founder gets their own voice pulled from their transcript.
The scorecard uses THREE sources: form data + your live profile notes + independent research. If you only use the form, the founder will know you didn't look at their stuff.
The review call feedback becomes the amendment brief. If you don't record it, you have to ask the founder to repeat themselves. That breaks trust.
Don't dump 5 deliverables at once. Present them one by one. Celebrate each one. Make them feel the quality. The pace should feel luxurious, not rushed.
Every skill Matt has built. Organized by delivery phase.
Brand Positioning + Content GPS + 200 Hooks — full brand foundation in one run
Content Waterfall + Lead Magnet + Email Sequence + 30 days social content
Offer Stack + Sales Deck + VSL + Landing Page + Ad Creatives — full monetization engine
Landing Page + Workshop + Org Chart + Leadership Blueprint — full conversion infrastructure
16-dimension brand analysis
Custom 60-min call script
12-part brand strategy
Extended competitive analysis
Interactive Vercel presentation
Content OS + 200 hooks
14 posts + 3 lead magnets
14 platform-native tweets
Visual designs for X
10 slide-by-slide scripts
HTML 1080x1350 production
Stories content pack
5 LinkedIn infographics
1 anchor to 22+ assets
Shareable HTML infographic
Master map + ManyChat
Full scripts with retention
10-min conversion weapon
Reels, Shorts, TikTok
Conversion-optimized
5 welcome + 4 FOMO
Subject line generator
Pricing + objections
10-25 page PDFs
SMS campaigns
Discovery call scripts
16-section copy
Live HTML on Vercel
46-slide with close
Live slide deck
Team + hiring roadmap
Per-prospect presentation
Org systems document
Every skill, what it produces, and the format it delivers in. Use this to set founder expectations.
Every luxury experience has a plan for the unexpected. Here is yours. The way you handle these moments defines whether a founder tells one friend or ten.
This is not about the form. They're either overwhelmed by the commitment they just made, or life got in the way. Your job is to make it feel effortless, not to add pressure.
"Hey [Name], just checking in. No rush on the form. If it helps, most founders knock it out in about 15 minutes with a coffee. And honestly, even partial answers give us enough to start building something incredible for you. Whenever you're ready, we're here."
After 7 days with no response, Matt or the CSM reaches out directly. Never let a new founder go silent in the first week.
This is not a failure. This is the process working. The first draft is the starting point, not the finish line. The magic is in how you respond.
"Thank you for being honest. That's exactly what I need. Walk me through what feels off and what you'd change. I'm going to take your exact words and feed them back into the system, and the next version will feel like you wrote it yourself."
Record the feedback on Fathom. Run the skill again with their feedback transcript as additional context. One round of amendments resolves 95% of issues. Never take it personally.
This is rare but it happens. The transcript is the #1 input for everything. Without it, the deliverables will be generic.
Immediately write down everything you remember from the call. Key phrases they used. Stories they told. Their energy when describing their ICP. Then schedule a 30-minute follow-up: "I want to make sure we captured everything perfectly. Can we do a quick 30 minutes to go deeper on a few things?" They'll appreciate the thoroughness.
Prevention: always verify Fathom is recording in the first 30 seconds of every call. Check the indicator light. Say "just confirming our recording is running."
They signed up for a brand machine, not more work. If they feel overwhelmed, the pacing is wrong.
"I hear you, and I want to be clear: you don't need to do anything with all of this right now. Our job is to build. Your job is to show up for the review calls and tell us what feels right. That's it. We'll handle the complexity. You handle the taste."
Slow down. Present one deliverable per call instead of three. Let them absorb the quality. The pace should feel luxurious, not efficient.
If you could swap the founder's name and it still works, the skill didn't have enough context.
Re-run the skill. This time, include: the full Fathom transcript (not just notes), the Brand Positioning Doc, 3-5 of their best-performing social posts, and their website URL. The more context, the more specific the output. If it's still generic after all that context, the Fathom call didn't go deep enough. Schedule a 30-minute follow-up focused on voice and stories.
Silence is not rejection. It's usually one of three things: they're busy, they're overwhelmed, or they've hit a personal wall. Your response sets the tone.
"Hey [Name], just wanted you to know we're still here and building. No pressure at all. When you're ready to pick back up, everything will be waiting for you exactly where we left off. And if anything changed on your end that I should know about, I'm always a message away."
After 10 days, escalate to Matt. A personal WhatsApp from Matt re-engages 90% of silent founders. The message: "Hey, just checking in. You good?"
The measure of a luxury experience is not how it performs when everything goes right. It's how it recovers when something goes wrong. Every recovery is an opportunity to create a story the founder tells for years.
The Velocity Standard
Every email in the founder journey. Click copy. Personalize the brackets. Send.