# Per-Project Workflow Template **Purpose:** When starting a new image creation project, copy this template into the project folder and fill it in. This customizes the general pipeline for the specific style, brand, and deliverables of each engagement. --- ## How to Use 1. Copy this file to `projects//IMAGE-WORKFLOW.md` 2. Fill in all sections before generating any images 3. This becomes the single source of truth for the project's visual direction 4. Anton uses the project-specific criteria from §3 in every review 5. Tatiana uses the style guide from §2 in every prompt --- ## 1. Project Brief ``` PROJECT NAME: [e.g., Bonanzo Bank Pitch] CLIENT/AUDIENCE: [who sees this] DELIVERABLES: [e.g., 12 slide illustrations, 16:9 landscape, 2K resolution] DEADLINE: [date] STYLE DIRECTION: [1-sentence summary — e.g., "Colin Ozawa vinyl toy aesthetic"] ``` ### Deliverable List | # | Name | Description | Status | |---|------|-------------|--------| | 1 | [Slide/Asset name] | [Brief description of what it shows] | ⏳ | | 2 | ... | ... | ... | --- ## 2. Style Guide *Tatiana fills this section after analyzing reference material. This is the project's visual bible.* ### Reference Artist/Style - **Name:** [artist name or style description] - **Why this style:** [how it serves the project's message] - **Key references:** [paths to primary reference images] ### Visual DNA (What Makes This Style THIS Style) - **Forms & Shapes:** [e.g., rounded, angular, organic, geometric] - **Proportions:** [e.g., oversized heads, elongated limbs, realistic] - **Surface/Material:** [e.g., matte vinyl, glossy ceramic, watercolor, flat vector] - **Color Palette:** [specific colors or color rules] - **Lighting:** [e.g., soft studio, dramatic shadows, flat/even] - **Backgrounds:** [e.g., solid color, gradient, environmental, none] - **Character Design:** [if applicable — body type, face style, clothing approach] ### Must-Haves (Non-Negotiable Elements) - [ ] [e.g., "Solid color backgrounds, never gradients"] - [ ] [e.g., "Characters always wear sunglasses"] - [ ] [e.g., "Matte plastic finish on all surfaces"] ### Must-Avoids (Known Problem Areas) - [ ] [e.g., "No individual fingers — use mitt/blob hands"] - [ ] [e.g., "No text in images — model renders it badly"] - [ ] [e.g., "No busy backgrounds — dilutes the style"] ### Prompt Template *The base prompt structure that Tatiana uses for this project. Every generation starts from this and adds task-specific details.* ``` [Base prompt template goes here after Tatiana's analysis] ``` ### Prompt Modifiers *Reusable fragments for common adjustments within this project:* | Modifier | When to Use | Prompt Fragment | |----------|-------------|-----------------| | [e.g., "More personality"] | [Character looks too generic] | [e.g., "EXPRESSIVE FEATURES: styled hair, accessories, attitude"] | | [e.g., "Simpler composition"] | [Too busy for slide readability] | [e.g., "clean composition, single focal point, negative space"] | --- ## 3. Project-Specific Critique Criteria *These get added to Anton's universal rubric for this project.* ``` PROJECT-SPECIFIC CRITERIA (1-10 each): □ [Criteria 1]: [description — e.g., "Hand/appendage accuracy"] □ [Criteria 2]: [description — e.g., "Brand color usage"] □ [Criteria 3]: [description — e.g., "Toy/collectible aesthetic maintained"] ``` ### Known Model Limitations for This Style *Document specific generation model weaknesses that affect this project:* | Issue | Severity | Best Mitigation | |-------|----------|-----------------| | [e.g., "Fingers despite 'no fingers' prompt"] | High | [e.g., "Use 'smooth rounded stump hands' or 'LEGO mitten' framing"] | | [e.g., "Adds gradients to backgrounds"] | Medium | [e.g., "Post-process with background flattening script"] | --- ## 4. Reference Image Library ### Setup Checklist - [ ] Create `projects//references/` directory - [ ] Collect 2-3 primary reference images - [ ] Add supplementary references for specific elements - [ ] Tatiana completes style analysis and writes style-guide.md - [ ] First 2-3 approved outputs added as self-references ### Directory Structure ``` projects//references/ ├── style-guide.md — Tatiana's style analysis (detailed) ├── primary/ — 2-3 key reference images ├── supplementary/ — Additional context images ├── approved/ — Our approved outputs (become refs for consistency) └── prompt-log.md — What prompts produced what (successes + failures) ``` ### Reference Usage Rules - **First 2-3 tasks:** Use primary references + style guide - **After first approvals:** Add best approved output as additional reference input - **Dual reference input:** Always pass both original style ref AND best previous output to the model - **Max references per generation:** 3 (more causes confusion in most models) --- ## 5. Project Task Flow ### Starting a New Task 1. **Kitt** creates Discord thread: `🎨 [Project] — [Task Name]` 2. **Kitt** posts the creative brief (from §1 deliverable list) 3. **Erica** routes to Tatiana with style guide reference 4. **Tatiana** crafts prompt using project template + task specifics 5. **Erica** executes generation 6. **Anton** reviews against universal + project-specific rubric 7. Loop 4-6 until APPROVED (max 5 iterations) 8. **Kitt** final check → deliver to Assaf ### Style Lock Protocol After the first 2-3 tasks are approved: 1. Tatiana confirms the prompt template is stable 2. Anton confirms style scores are consistent (>8/10) 3. Kitt declares "style locked" — remaining tasks can be batched in parallel 4. Any task that deviates from locked style gets flagged, not auto-approved ### Handoff Between Sequential and Parallel | Phase | Tasks | Mode | Why | |-------|-------|------|-----| | Style calibration | First 2-3 | Sequential | Need approval gates to dial in style | | Production | Remaining | Parallel (2-3 concurrent) | Style locked, efficiency matters | | Revisions | As needed | Sequential | Each revision is specific | --- ## 6. Version & File Management ### Naming Convention ``` YYYY-MM-DD---v.png ``` Examples: - `2026-02-03-bonanzo-slide02-shift-v1.png` - `2026-02-03-whitespace-hero-banner-v3.png` ### Approved Finals - Move to `projects//finals/` - Keep only the approved version, delete iterations - Record final version number in the deliverable list (§1) ### Cleanup Protocol (End of Project) - Archive approved finals - Delete all draft/iteration files - Preserve: style guide, references, prompt log, project workflow doc - Log total iterations, time, and quality metrics --- ## 7. Project Retrospective (Fill at End) ### Metrics | Metric | Result | |--------|--------| | Total tasks | | | Total iterations | | | First-pass approval rate | | | Average iterations per task | | | Total project time | | | Pipeline violations | | ### What Worked - ### What Didn't - ### Style-Specific Learnings *Prompt tricks, model limitations, and workarounds discovered during this project. Feed back into general prompt-patterns.md if universally applicable.* - ### Updates to General Pipeline *If this project revealed gaps in the general process, document them here for review.* - --- *This template works with the General Image Creation Pipeline plan. The general plan defines the process; this template adapts it per engagement.*