The one-page brief format that lets a designer or writer produce assets without a meeting, and what each section is for.
A brief exists so that someone else can make the assets correctly the first time. Most briefs are either a paragraph of hope or a deck nobody reads. This guide sets out a one-page format where every section answers a question the maker would otherwise have to ask.
How to produce listing images that show the real product clearly, consistently, and in the formats marketplaces want.
Listing images decide whether a buyer reads the rest. This guide covers the two cases a store meets — screenshots of digital products and photographs of physical ones — with the rules that keep every image honest, consistent and usable across platforms.
Build help article suggestion on ticket close as a n8n automation: when a ticket closes, suggest the help article that would have answered it, and log the gap if none exists.
Trigger: Help desk ticket status changes to closed.
Use feed validation tools to catch listing data errors before a marketplace or ad platform rejects the feed.
Marketplaces and shopping ads ingest a product feed — a file of titles, prices, availability, images and identifiers — and reject items with missing or malformed fields; a validator checks the feed against the platform's rules before submission so rejections are fixed in bulk rather than one email at a time.
Produce four pieces on a weekly system with hooks, structure, honest titles, repurposing and a monthly review.
Plan four pieces with three hook options each, timed outlines and reuse plans. Record and edit each on the fixed weekly schedule. Publish with titles under sixty characters and thumbnails under four words. Produce three clips and a newsletter section per piece. Review weekly and write a one-page monthly review with retention by piece and one change.
Model, texture, light and render one product in three views, and export it for the web.
Choose a real product with a reference. Model it at scale with clean topology, unwrap it, build its materials, light it with a studio setup, render three views (hero, detail, in-context), and export a glTF that opens correctly in a web viewer.
Build a themed spawn area, a resource pack that supports its theme, and a plugin that welcomes players and points them to the rules — packaged for a server to install.
Plan and build a spawn with a clear silhouette, palette and landscaping; create a resource pack that changes three textures and a sound to match; write a plugin with a /rules command, a permission, configurable messages and a join greeting with persistent join counts. Package all three with READMEs and versions.
Build a complete shop resource: configurable locations and items, a NUI menu, server-validated purchases through the framework, and a documented release.
Build a shop resource with locations and items in a shared config, a marker and prompt near each location, a NUI menu, a server purchase handler that validates distance, price and balance through one framework wrapper, rate limiting and logging on the handler, and a README, config, version and changelog. Test on staging with a modified client attempting bad purchases.
Lua scripting for FiveM: resource structure, client and server, events, framework integration, UI and release.
Write, structure and release FiveM resources with correct client-server separation, secure events and a framework integration that does not break on update.
Skills: Resource manifest and structure, Client versus server code, Events and security, Framework integration, NUI basics and release packaging
Rewrite ten listings, fix delivery and policies, build support snippets and macros, run one review cycle and one retention action — and measure.
For a real or realistic store: rewrite the ten best-selling listings to the buyer's-questions structure with spec blocks, set delivery to a library with logged downloads and quotable policies at checkout, build ten snippets and five macros, run one monthly review clustering with listing fixes shipped, and launch one retention email measured by cohort.
Position a product, commit to two channels, run one campaign and an email programme for a quarter, and produce three monthly reviews.
For a real product: write the positioning statement from customer language with proof, choose two channels on evidence with a metric each, launch the email programme with a promise and welcome sequence, run one campaign from a one-page brief with tagged links, and produce three monthly reviews with fair comparisons and caveats.
Take a real business question end to end: definition, profile, query with reconciliation, chart, one-page write-up, and a review by a sceptic.
Choose a question someone in your business actually asks. Write the metric definition and get it agreed. Profile the data and write notes. Build the query with a reconciliation check. Produce one chart with the finding as its title and a caveat beneath. Write the one-page analysis and have a sceptical colleague review it; record their questions and revise.
From a business question to a chart with a caveat, with definitions, checks and a write-up that survives scrutiny.
Answer business questions from data with defined metrics, reconciled queries, honest charts and a one-page write-up.
Skills: Turning questions into metric definitions, Profiling and cleaning data, SQL and spreadsheet aggregation, Chart choice and annotation, Writing up with caveats
Implement the money, customer, work and risk systems for a real small business and run them for one month.
For a real business (yours or a client's), set up lean bookkeeping with a close checklist, invoicing with a reminder ladder, a thirteen-week cash sheet, a CRM with five stages and a weekly review, one task list, a file structure, three procedures, tested backups, a password manager with offboarding, and a compliance calendar. Run everything for one month and write a one-page review.
Design a three-step checkout with every state and all its copy, then run a usability test and revise.
Design a checkout flow: cart review, details, confirmation. Define each screen's job and primary action, build hierarchy in greyscale first, design all five states per screen, write all copy to the rules, then test with five people and revise the top three findings.
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.
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.
Milestone 1: Set up
Milestone 2: Test
Claude
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
