A brief is a complete assignment.
Not a vague prompt. Not a tutorial checklist. A real-world project broken into the pieces you need to start, finish, and explain what you built.
Free sections below. Premium marked where it unlocks more.
Inside a brief, section by section
One sample throughout: a Web brief at Intermediate level. A neighborhood tool library for makers and neighbors. Same product, every section explained.
The statement
One sentence. No guessing.
- What
- Every brief opens with a single line: what you are building, who it is for, and the job they need done.
- Why
- That sentence is your north star. When you get stuck mid-build, you come back to it and decide what still serves the user.
From the sample brief
You are building a neighborhood tool library for makers and neighbors who are borrowing shared tools without chasing texts.
Project stack
Your tools, named on purpose.
- What
- The stack lists the languages and frameworks you should use, with a short reason for each choice.
- Why
- Vague prompts waste hours. When the brief says Next.js and TypeScript, you open those tools and start. No translating from "a modern frontend framework."
From the sample brief
- TypeScriptTyped models for inventory, holds, and member eligibility.
- Next.jsApp Router for browse, reserve, and pickup confirmation flows.
- ReactInteractive inventory grid with optimistic hold updates.
Context
The world before you write code.
- What
- A short scene that explains the situation: who is struggling, what is broken today, and what "better" looks like.
- Why
- Features without context become busywork. Context gives you empathy and constraints, so every screen you ship has a reason to exist.
From the sample brief
A volunteer-run tool library needs a calm web app so members can see what's available this weekend, place a hold, and know when to pick up, without a spreadsheet and a group chat.
Requirements
What to ship. In order.
- What
- Concrete outcomes, often with steps. These are the must-haves that make the product usable, not a wishlist of nice-to-haves.
- Why
- A blank canvas invites thrashing. Clear requirements let you plan a weekend, a week, or a sprint, and know when the core is done.
From the sample brief
- 01
Browse tools by category with live availability and a clear hold window.
- Filter by category and pickup neighborhood.
- Show next available date when an item is out.
- Confirm a hold with pickup instructions in one screen.
- 02
Let stewards mark items returned and resolve overdue holds.
- 03
Keep the experience usable on a phone at the shed door.
Insights
The non-obvious truths.
- What
- A few sharp observations about the problem space: what users actually care about, and what usually goes wrong.
- Why
- Tutorials teach syntax. Insights teach taste. They help you make product decisions that feel intentional in a portfolio case study later.
From the sample brief
- Availability beats catalog size. People quit when they can’t tell if a drill is free.
- Pickup windows reduce no-shows more than longer hold times.
Design direction
PremiumHow it should feel, not just work.
- What
- Visual tone, layout priorities, and a named color token palette with hex values and semantic roles.
- Why
- Function alone rarely reads as finished work. Design direction turns a working demo into something you can show with pride, and write about with specifics.
From the sample brief
Warm, civic, and low-chrome. Prioritize scannable inventory cards, high-contrast status chips, and a pickup confirmation that feels like a paper receipt, not a SaaS dashboard.
- ink#1C1917 · Primary text
- paper#F5F0E8 · Page background
- signal#0F766E · Available / success
- hold#B45309 · On hold / warning
Success criteria
PremiumDone means observable.
- What
- Three user-facing outcomes that prove the brief is truly finished, not just "code exists."
- Why
- Without a finish line, side projects drift forever. Success criteria give you a test you can demo, and a story you can tell in interviews.
From the sample brief
- A new member can place a hold on an available tool in under two minutes.
- Stewards can clear a return and free the item without leaving the inventory view.
- Overdue holds are visible without opening each tool’s detail page.
Stretch goals
PremiumWhen the core is solid, go further.
- What
- Three advanced upgrades that would genuinely elevate the project, with specific technologies named.
- Why
- Stretch goals keep ambitious builders moving without bloating the first version. Ship the requirements first. Earn the extras.
From the sample brief
- SMS pickup reminders via a Twilio webhook when a hold window opens.
- QR check-in at the shed that marks the item as checked out.
- A public waitlist that auto-offers the next person when a hold expires.
Around the brief
The sections above are the document. These are the product habits that make generating the next one feel natural.
Matched to your level
Beginner through seasoned. Scope and complexity flex so the brief stretches you without burying you.
Every practice lane
Web, Software, Systems, Design, and Mobile. Free includes the full curated toolkit. Premium unlocks custom tools beyond the catalog.
Built for the portfolio write-up
Problem, audience, stack choices, and outcomes live in the brief. When you finish, the case study is already half written.
Start with no account
Take the quiz and generate your first brief free. Sign up when you want history across devices.
You already know how to build. You need something worth building.
Five questions. One brief. Free to start. When you want design direction, success criteria, and stretch goals on every generation, Premium is one upgrade away.