🏆 WEEKLY COMP #9: THE EDITOR 🏆

Matthew Creamer

6h • 💰 Competitions

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️

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

🎯 PICK YOUR DOMAIN

The domain is yours. Pick something specific. Pick something you'd actually use.

A few sparks to get you thinking:

💻 Code review editor for a specific language and level (junior TypeScript, senior Python)
📊 Pitch deck editor for pre-seed founders
🎨 Grant application editor for arts nonprofits
📄 Resume editor for career switchers into tech
📰 Op-ed editor for policy publications
🎙️ Podcast script editor for interview shows
⚖️ Legal brief editor for civil litigation
📋 Product spec editor for early-stage PMs
🎓 Academic paper editor for one specific field

The more specific, the better. "Writing editor" is too broad. "Op-ed editor for tech policy publications targeting a policy audience" is right.

🗂️ THE METHODOLOGY

If this is your first comp, welcome. Here's what you need to know:

This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well.

Your editor is a folder with five things:

📄 identity.md (who the editor is, what work they review)
📐 rules.md (how they critique)
💬 examples.md (what good critique looks like)
📚 reference/ (style guides, checklists, frameworks the editor uses)
📖 README.md (how to use it)

Drop the folder into a Claude project. Claude becomes the editor. Reusable. Shareable. Portable.

🔥 THE ANGLE THIS WEEK

An editor is NOT a rewriter.

An editor doesn't do the work for you. An editor surfaces what's weak and pushes you to fix it. That distinction is the whole assignment this week.

When someone hands the editor a draft, the editor shouldn't produce a "fixed" version. The editor should point at the three lines that don't work, explain why, and hand it back to the writer to solve. ✍️

Generic feedback like "consider strengthening your intro" is a fail. Specific feedback like "your intro assumes the reader already knows what a Series A is, but this pub is read by generalists, so lead with the stakes instead of the jargon" is what a real editor does.

Your rules.md is where you teach the AI to critique instead of create. 💪

💼 WHY THIS LANDS ON YOUR RESUME

Reviewing work is one of the highest-leverage skills anyone can hire for. Companies pay senior people specifically to catch the mistakes junior people make.

"I built an editor that catches the mistakes junior [role] make" is a portfolio piece that lands work. It demonstrates domain expertise, systems thinking, AND judgment. 🚀

Win or lose, you walk out with something you'd be proud to link from your LinkedIn.

📐 THE BAR

Someone with no context should hand your editor a piece of work in that domain and get back feedback that actually improves it.

If the output is generic "consider strengthening your intro" style feedback, you've missed the assignment.

📝 HOW TO SUBMIT

Drop a public GitHub repo link in the comments. Plus 2-3 sentences on what your editor reviews and who it's for.

⚖️ JUDGING

Jake, Matt, and the mods, scored against a full rubric. Four things we're looking at:

✅ Does the editor actually critique? Or does it rewrite/summarize/praise?

✅ Is the domain specific enough to be useful?

✅ Is the methodology clean? Each file does one job well.

✅ README quality. Can a stranger figure this out?

🎟️ 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: Wednesday, July 22nd 11:59 PM EST

🎉 Winner announced: Following week

🚀 One last thing.

Month 3 kicks off with The Editor. Every-other-week cadence gives us more time to actually read your builds and give feedback that helps.

Different skill from the coach, the researcher, the operator. Same methodology. New portfolio piece.

LFG 🚀

10 comments

🏆 WEEKLY COMP #9: THE EDITOR 🏆