🏆 WEEKLY COMP #8: THE WILDCARD 🏆

Matthew Creamer

10h • 💰 Competitions

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️

Pick your cohort. Technical, Business, or Creator. Your call.

----

📋 THE CHALLENGE

You are the client this week.

No fictional Marcus. No fictional Sarah. No fictional Devon. Pick a real problem in your own life or work. Build the folder-based specialist you wish you had.

This is the capstone of Month 2. The challenge flips. Instead of building for someone else, you write your own brief and solve it for yourself.

----

🎯 THE TWIST

The hard part isn't building. The hard part is scoping.

Picking the right problem is harder than solving the wrong one. Most people pick problems that are too small or too vague. The skill this week is treating yourself like a real client.

Be specific about what's broken. Be specific about what you need. Don't pick "I want to be more productive." Pick "I waste two hours every Sunday night writing the same kind of LinkedIn carousel posts and I need a folder that handles 80% of the draft work so I can focus on the hook and the visuals."

That's a real brief. Specific problem. Specific scope. Specific desired output.

----

🗂️ TWO DELIVERABLES THIS WEEK

This is the only week with two pieces:

1️⃣ Your own client brief. 250 words or less. Describe the problem you're solving for yourself. Treat yourself like a real client. What's broken? What have you already tried? What do you need?

2️⃣ The folder system that solves it. Same structure as every week:

📄 identity.md
📐 rules.md
💬 examples.md
📚 reference/
📖 README.md

Your brief lives at the top of the repo as brief.md so judges can read it before they look at the folder.

----

🔥 THE ANGLE THIS WEEK

Anyone can follow a brief. Writing your own, then solving it, then shipping it as a usable folder is a portfolio piece that demonstrates judgment, not just execution.

This is the skill that separates "AI hobbyist" from "AI builder." Anyone can prompt their way through a problem someone else handed them. Scoping a problem, designing the solution, and shipping it as a system is what real work looks like. 💪

----

💼 WHY THIS LANDS ON YOUR RESUME

Every previous week has been "I built X using interpretable context methodology." This week is different. This week is "I identified a real problem in my own work, scoped the solution, and shipped it as a folder-based system."

That's not a build exercise. That's a case study. Hiring managers eat case studies for breakfast. 🚀

Win or lose, you walk out with something you'd be proud to link from your LinkedIn AND a tool you'll actually use in your own life.

----

📝 HOW TO SUBMIT

Drop a public GitHub repo link in the comments. Make sure brief.md is at the top of the repo. Plus 2-3 sentences in the comment summarizing what you built and who it's for (you).

----

⚖️ JUDGING

Jake, Matt, and the mods. Four things we're looking at:

✅ Is the brief a real problem worth solving? (Specificity wins. Vague briefs lose.)

✅ Does the folder actually solve what the brief says it solves?

✅ Is the methodology clean?

✅ Could a stranger use this and benefit?

----

🎟️ WHO CAN ENTER

Premium and VIP members only. No exceptions.

🆓 Free members watching this thinking "I could win that"? You're probably right. This week's prize is a free Lyceum seat. That's the same program biz owners pay full price to access. Upgrade to Premium and you're in the running.

----

📅 DATES

⏰ Submit by: Sunday, June 28th, 11:59 PM EST

🎉 Winner announced: Following week

----

⚙️ HEADS UP ON THE COMP RHYTHM

Starting after this comp, we're moving to an every-other-week cadence. More time to judge means better feedback for everyone, not just the winner. Same prizes, more depth on the read.

----

🚀 One last thing.

Month 2 wraps with this one. Coach. Researcher. Operator. Wildcard. Four weeks. Four different specialists. Four portfolio pieces.

Anyone who's entered all four walks out with a body of work that demonstrates real range. That's not a Skool flex. That's the kind of portfolio that lands interviews.

LFG 🚀

10 comments