Take an untyped or loosely typed module and give it precise types: unions, boundaries, strict mode, no any.
Choose a real module with any, string-typed enums or unchecked JSON. Model its data with discriminated unions and literal types, add schema parsing at its boundaries, enable strict for it, and remove every any and cast. Keep behaviour identical, proven by tests or snapshots.
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.
Components, state, effects and data — learned by building a real interface and refactoring it as it grows.
Build interactive React interfaces with sensible state, few effects and components that stay small.
Skills: Composing components with props and children, Choosing where state lives, Using effects only for synchronisation, Fetching and caching data, Testing components
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
Take one manual process from map to live automation with error handling, a manual fallback and a measured saving.
Choose a recurring process. Map it from three real examples, build the automation one block at a time, add error routing and idempotency, test three samples and one deliberate failure, and run it live for two weeks with a log of runs, failures and time saved.
Configure instructions, three projects and a saved-prompt file for your real work, then measure the time saved over a week.
Write custom instructions, create three projects for your three most recurring areas of work with files and instructions, and keep a file of five saved prompts with variables. Use the setup for a week and log time saved per task and edits made.
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
Time 6hClaude Code
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