πŸš€ Spring into AI Competition

A 5-week, ship-every-week competition where participants build real AI projects, publish what they learn, and compete on reps.

What is this?

Welcome to the AI Build Sprint β€” a 5-week competition where the point is to get embarrassed, put yourself ONLINE, and realize we're all figuring this out in realtime.

The rules are simple on purpose: build β†’ publish β†’ score β†’ repeat.

Winners will be based solely on total points. In the event of a tie, a vibe-coded random spinner will determine the winner (recorded on video). Please don't make Eric vibe code your victory. Win in an unquestionable way.

πŸ† How to Win

At the end of the competition, the winner is simply: Whoever has the most points.

No judges. No vibes. Just points.

Medals will be provided to the top three winners.

πŸ“… Competition Schedule

Each week follows this rhythm:

DayEvent
Monday 8:00 AM CTTheme drops
Mon 8:00 AM β†’ Sun 11:59 PMBuild window
Sunday 11:59 PM CTSubmission deadline
Monday 12:00 PM CTScoreboard update
Monday 12:05 PM CTSlacker board + coffee debts declared

🧭 Week-by-Week Archive

The rules page stays focused on the competition mechanics, but the live archive now preserves the theme prompts in order so builders can start with the right weekly context before reading the submissions.

WeekTheme PromptBuild Window
Week 1 Data Visualization & Interactions Feb 9–15, 2026
Week 2 Tools for AI Tools Feb 16–22, 2026
Week 3 Interactive Tutorials Feb 23–Mar 1, 2026
Week 4 Soundwave β€” Transmission of Identity Through Sound Mar 2–5, 2026

πŸ“Š Scoring System

Base Points (Per Published Piece)

5
LinkedIn Post
15
YouTube Video
(β‰₯ 5 minutes)
2
Personal Blog Post
2
Substack Post

Note: You can publish on multiple channels and earn points on each. Points multiply by what you ship. Ship 2 apps and post 2 LinkedIn posts? That's 20 points!

Multipliers

Code Release Multipliers

0Γ—
No public release
(nullified)
1Γ—
Public repo
2Γ—
Hosted app + public repo

Bonus Points

  • +10 points β€” Reference any competitor's post, video, app, or code
  • +10 points β€” Build clearly operates inside the week's theme

⚠️ Slacker Board & Accountability

If you do not deliver in a given week:
  • You owe everyone in the group a coffee
  • You get added to the Slacker Board for that week

No drama. Just accountability. Maybe a lot of name calling.

πŸ“‹ Repo Requirements

  • Public repo β€” Private repos do not qualify (score 0)
  • README.md at root with: what it is, how to run it, link to live app
  • Screenshot required β€” At least one screenshot of the app in action

🎬 YouTube Requirements

  • Your channel has your FIRST or LAST name in the channel name
  • Minimum length: 5 minutes
  • Picture-in-picture required for full video β€” camera visible entire time
  • If PiP drops out for more than single digit % of video β†’ 0 points

πŸš€ What Counts as "Hosted"

A build earns the 2Γ— multiplier when: public GitHub repo meets all requirements AND app is hosted online with publicly accessible URL.

Ready to Compete?

This is a reps competition: ship in public, learn fast, and build momentum.

Follow on Substack

πŸ“€ How to Submit

Every time you publish something, send it to Eric (link(s)). He'll coordinate scoring and make sure everyone is seeing each other's work.

If it's not shared, it won't be scored.

🎯 Submissions

Week 1: Data Visualization & Interactions

The kickoff week asked builders to make data visible, add a meaningful interaction, and publish the lesson in public. Start with the Week 1 theme prompt, then browse the submitted builds in the build log.

ChartSlice OpenClaw Analyzer SkyStats β€” airplane visualizations Crypto Dashboard

Week 2: Tools for AI Tools

Build something designed for AI to use, not humans. Read the Week 2 theme prompt before browsing the submissions.

πŸ₯‡ Crypto Market Agent Skill β€” Jake Strait

Open-source Agent Skill that gives AI coding assistants live crypto market data. Works with Claude Code, Cursor, Copilot, Codex, and 20+ other tools.

"JSON output instead of pretty tables. --help flags instead of UI. Decision trees instead of menus. When your user is an AI, simplicity wins."

πŸ“š Got Questions?

Check the FAQ for common questions, tips, and practical guidance.

View FAQ & Tips