Ship your second Pennywise feature using Claude Code, from plan to working, on your own. Then document it in Cowork. Graded on process, not polish.

Time: 60 to 90 minutes. Stuck more than 15 minutes is a WhatsApp question, not a solo struggle.

Pick one feature

• Search and filter expenses by name or category
• A budget limit per category, with an alert when you go over
• Export the monthly summary as a PDF
• A chart of spend over the last six months
• Recurring expense detection (same payee, same amount, monthly)

Or propose your own. Rule of thumb: pick something Lovable would struggle to do cleanly.

How to do it

1. Start with the Plan prompt. Read the plan, correct it, then say go.
2. Build one step at a time. Review each diff before you approve it.
3. Hit a break and fix it with the Debug prompt.
4. Write a one-page PRD for your feature in Cowork.
5. Create your first Claude Code skill. Save your plan-first method as a reusable skill so you never have to re-type it. Ask Claude Code using the prompt below. Then use it on your next change by typing /new-feature.
6. Write and publish a LinkedIn post about what you built, using the Cowork copy prompt below. Actually post it, do not just draft it.

Create a skill called new-feature that always plans before writing code, builds one step at a time, and shows me the diff before each step. Save it as a SKILL.md in this project.

Write a short LinkedIn post announcing that I just built [your feature] into my own expense app, Pennywise, during a bootcamp using Claude Code, and that I also saved my build method as a reusable Claude Code skill. Voice: direct, warm, first person, no hype, no em dashes. Structure: a one-line hook, two or three lines on what I built and why it was satisfying, one line on what I learned about directing an AI agent, and a soft invitation to follow along. Under 120 words, give me two versions.

Definition of done