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.
Automate checks, deploys and scheduled jobs next to the code.
GitHub Actions runs workflows on repository events and schedules, with a marketplace of actions and hosted runners; it is the default place for CI, release automation and nightly jobs when the code lives on GitHub.
Build stale branch cleanup as a GitHub Actions automation: list merged or abandoned branches weekly and delete those over ninety days old after a warning.
Build preview deployment comment with checks as a GitHub Actions automation: on every pull request, post the preview URL with the results of the key checks in one comment.
Use Copilot completions and chat for the boilerplate and stay in charge of the design.
Copilot completes code as you type and offers a chat that understands the open files and, with the right setup, the repository; it is strongest on repetitive code and tests, weakest on architecture and anything it cannot see.
Use Cursor's inline edits, chat with codebase context and agent mode without losing control of the diff.
Cursor is an editor with the model wired into inline edits, a chat that can read your codebase, and an agent mode that makes multi-file changes; its value is speed on changes you already understand, and its risk is accepting diffs you did not read.
Build nightly dependency audit summary as a GitHub Actions automation: summarise new vulnerability advisories for your dependencies into an actionable morning note.
Build aI review comment on every PR as a GitHub Actions automation: post an assistant review comment on each pull request with ranked findings and the test result.
Build a feature with an assistant by writing the failing test first, so the assistant's code has something to be right against.
When: Any feature small enough to describe in one paragraph.
1. Describe and point
2. Run the failing test
Steps 5Tools Claude Code, Cursor or similar, Your test runnerClaude CodeCursor
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