Build the browsing interface for a content library: list, search, filters, detail view, bookmarks — with data from a query library and tests for the key flows.
Build a React interface that lists resources, filters them by type and difficulty, searches by title, opens a detail view, and lets a user bookmark. Data comes from a mock API through a query library. Write tests for filtering, searching and bookmarking.
Build a small app where signed-in members browse resources, save bookmarks and see only what their plan covers.
Build an app with a public resource list (server-rendered), sign-in, an account area protected on the server, a server action to bookmark, and a plan check that hides full content from members without access. Deploy it with previews.
Build a real, data-backed app with the App Router: routing, server components, data, actions, auth and deployment.
Build and deploy a Next.js application with server components, server actions, a database and protected routes.
Skills: App Router layouts and routes, Server versus client components, Data fetching and caching, Server actions and forms, Deployment with environment variables
Prepare a real repository so Claude Code can work in it safely: conventions, tests, checks and a release script, proven by one test-first feature.
Take a repository you own. Write CLAUDE.md, ensure the test command runs green, add a release-check script that prints an evidence table, then implement one small feature test-first with the tool and ship it with the table in the pull request.
From first session to a repeatable workflow: orientation, test-first changes, review and release.
Use Claude Code to make verified changes to a real codebase with tests, reviews and evidence.
Skills: Writing a CLAUDE.md that steers the tool, Running test-first changes, Reviewing diffs the tool proposes, Keeping the tool inside safe boundaries
Set up a Claude project that reviews contracts against your checklist and produces a referenced summary, tested on three real contracts.
Build a project whose instructions define a review checklist (payment, termination, liability, IP, renewal), an output format with section references and quotes, and a rule that ambiguous clauses are quoted and listed for a lawyer. Test on three contracts; verify every reference.
From a single tool call to a budgeted, evaluated, approval-gated agent that can be left running.
Design, build, evaluate and operate a tool-using agent with side effects gated by a person.
Skills: Defining tools with schemas and failure returns, Writing a system prompt as a contract, Enforcing budgets in code, Building an evaluation set, Gating side effects
Build five reusable prompts for one role's recurring tasks, each with variables, a reference run and a ten-case test set.
Choose one role (support, sales, marketing, ops). Identify its five most repeated writing tasks. For each, produce a prompt template with variables, a filled reference run, and a ten-case test set with rubrics and a recorded pass rate. Deliver as a folder someone in that role could use on Monday.
The four architectural decisions every agent forces and how to make them for a first production agent.
Agent frameworks differ in surface but force the same four decisions: how the loop ends, how tools fail, where state lives, and who approves side effects. This guide makes each decision for a first production agent and explains the trade-off.
Design onboarding so a new user reaches the product's first valuable moment in the first session.
Half of new signups reach first value in session one.
Step 1: Define first value precisely
Step 2: Map the current path
Steps 5Deliverables 3
Instant delivery after paymentLicence stated on every productRe-download anytime from My LibrarySecure checkout — Polar or FungiesNew products every week
Instant delivery after paymentLicence stated on every productRe-download anytime from My LibrarySecure checkout — Polar or FungiesNew products every week
