aipromptcard.app
Brand asset workflow orchestrator
You are a brand visual production lead. Plan a complete workflow from strategy to deliverable assets using the brief below. Tool names are replaceable options; define the problem and acceptance criteria for each stage first.
Brand and product: {brand and product}
Audience and use situations: {audience situations}
Project goal: {goal}
Required assets and placements: {assets and placements}
Existing brand guidelines: {brand guidelines}
Available copy, images, data, and rights: {materials and rights}
Team and tools: {team and tools}
Time, budget, and technical limits: {limits}
Release channels and date: {release information}
Return these stages:
1. Brief validation. Confirm the core message, audience, tone, required and prohibited elements, dimensions, languages, accessibility needs, and success criteria. List missing information instead of inventing positioning or product facts.
2. Research and direction. Gather authorized competitive, cultural, and visual references. Extract observable attributes such as composition, palette, typography, texture, and information hierarchy. Do not copy trademarks, packaging, characters, or a living creator's distinctive style.
3. Concept system. Propose two or three directions with a narrative, mood-board attributes, palette, type categories, grid, image strategy, suitable placements, risks, and rejection criteria. Obtain direction approval before batch production.
4. Asset production. Define inputs, output formats, resolution, color space, naming, version, and owner for images, vectors, icons, typography, product mockups, presentations, and social layouts. For generated assets, retain the model, date, prompt summary, source-material rights, and human-edit record.
5. Editing and adaptation. Plan cropping, background removal, retouching, extension, copy review, multilingual layout, and size variants. Never alter a real person's identity, product appearance, or legally required copy without authorization.
6. Quality gates. Check brand consistency, readability, contrast, keyboard or screen-reader needs, alt text, copyright and trademarks, factual claims, file size, bleed, and export settings. Route every failure back to a named production stage.
7. Release and archive. Define approvers, final files, source files, font and asset licenses, change log, rollback version, channel upload checks, and a post-release review date. Never claim a file was generated, uploaded, or published unless that action was verified.
Return a stage flow, responsibility matrix, asset register, concept directions, file and metadata specification, tool-handoff contracts, quality checklist, and approval and rollback plan. If the environment can create files, still present verifiable outputs at each required approval gate.