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.
Review an existing content series plan against the standard a strong content creator who plans, scripts and repurposes with an assistant would hold it to, then return an improved version.
Fill in: {{theme}}, {{pieces}}, {{format}}, {{outcome}}, {{draft}}
Plan a series of connected pieces around one theme with an arc, so each piece builds on the last.
Plan a series of connected pieces around one theme with an arc, so each piece builds on the last. Written for creators work: the context, steps and output format are fixed so results come back in the same shape every time.
Fill in: {{theme}}, {{pieces}}, {{format}}, {{outcome}}
Produce several distinct sponsorship proposal options so the best can be chosen or tested, each built on a different angle rather than reworded copies.
Fill in: {{channel}}, {{numbers}}, {{packages}}, {{sponsor}}
Review an existing sponsorship proposal against the standard a strong content creator who plans, scripts and repurposes with an assistant would hold it to, then return an improved version.
Fill in: {{channel}}, {{numbers}}, {{packages}}, {{sponsor}}, {{draft}}
Write a sponsorship proposal for a creator channel with honest numbers, packages and deliverables.
Write a sponsorship proposal for a creator channel with honest numbers, packages and deliverables. Written for creators work: the context, steps and output format are fixed so results come back in the same shape every time.
Fill in: {{channel}}, {{numbers}}, {{packages}}, {{sponsor}}
Produce several distinct usability test script options so the best can be chosen or tested, each built on a different angle rather than reworded copies.
Fill in: {{task}}, {{participants}}, {{length}}, {{questions}}
Review an existing usability test script against the standard a strong product designer who uses an assistant for critique, copy and structure would hold it to, then return an improved version.
Fill in: {{task}}, {{participants}}, {{length}}, {{questions}}, {{draft}}
Write a moderated usability test script for a task with tasks, prompts and what to observe.
Write a moderated usability test script for a task with tasks, prompts and what to observe. Written for designers work: the context, steps and output format are fixed so results come back in the same shape every time.
Fill in: {{task}}, {{participants}}, {{length}}, {{questions}}
Produce several distinct design system component spec options so the best can be chosen or tested, each built on a different angle rather than reworded copies.
Fill in: {{component}}, {{variants}}, {{props}}, {{behaviour}}
Review an existing design system component spec against the standard a strong product designer who uses an assistant for critique, copy and structure would hold it to, then return an improved version.
Fill in: {{component}}, {{variants}}, {{props}}, {{behaviour}}, {{draft}}
Specify a UI component so engineers can build it once and designers use it consistently.
Specify a UI component so engineers can build it once and designers use it consistently. Written for designers work: the context, steps and output format are fixed so results come back in the same shape every time.
Fill in: {{component}}, {{variants}}, {{props}}, {{behaviour}}
Produce several distinct accessibility review options so the best can be chosen or tested, each built on a different angle rather than reworded copies.
Fill in: {{screen}}, {{standard}}, {{components}}, {{known}}
Review an existing accessibility review against the standard a strong product designer who uses an assistant for critique, copy and structure would hold it to, then return an improved version.
Fill in: {{screen}}, {{standard}}, {{components}}, {{known}}, {{draft}}
Review a screen's structure and copy for accessibility and list fixes with the standard each addresses.
Review a screen's structure and copy for accessibility and list fixes with the standard each addresses. Written for designers work: the context, steps and output format are fixed so results come back in the same shape every time.
Fill in: {{screen}}, {{standard}}, {{components}}, {{known}}
Review an existing design critique against the standard a strong product designer who uses an assistant for critique, copy and structure would hold it to, then return an improved version.
Fill in: {{screen}}, {{goal}}, {{principles}}, {{users}}, {{draft}}
Critique a screen against usability principles and return specific, prioritised recommendations with a concrete fix for each issue.
Critique a screen against usability principles and return specific, prioritised recommendations with a concrete fix for each issue. Written for designers work: the context, steps and output format are fixed so results come back in the same shape every time.
Fill in: {{screen}}, {{goal}}, {{principles}}, {{users}}
Review an existing incident postmortem against the standard a strong working developer who uses an assistant for design, docs and debugging beyond the editor would hold it to, then return an improved version.
Fill in: {{timeline}}, {{impact}}, {{cause}}, {{fixes}}, {{draft}}
Write a blameless postmortem that explains what happened, why the system allowed it, and what changes.
Write a blameless postmortem that explains what happened, why the system allowed it, and what changes. Written for developers work: the context, steps and output format are fixed so results come back in the same shape every time.
Fill in: {{timeline}}, {{impact}}, {{cause}}, {{fixes}}
Produce several distinct architecture decision record options so the best can be chosen or tested, each built on a different angle rather than reworded copies.
Fill in: {{decision}}, {{context}}, {{alternatives}}, {{consequences}}
Review an existing architecture decision record against the standard a strong working developer who uses an assistant for design, docs and debugging beyond the editor would hold it to, then return an improved version.
Fill in: {{decision}}, {{context}}, {{alternatives}}, {{consequences}}, {{draft}}
Write an ADR that captures a technical decision, its context, alternatives and consequences.
Write an ADR that captures a technical decision, its context, alternatives and consequences. Written for developers work: the context, steps and output format are fixed so results come back in the same shape every time.
Fill in: {{decision}}, {{context}}, {{alternatives}}, {{consequences}}
Variables 4ClaudeChatGPT
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