Files
sar/.claude/skills/wds-6-asset-generation/steps-m/step-03-select-style.md
julian 17c08e6392 chore: initial monorepo scaffold + WDS Phase 1+2 artifacts
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 14:34:20 +00:00

3.7 KiB

name, description, nextStepFile
name description nextStepFile
step-03-select-style Choose content style and visual parameters for image generation per batch ./step-04-references.md

Step 3: Select Style

STEP GOAL:

Choose the content style (rendering technique) and visual parameters — lighting, color harmony, composition, mood — for each image batch to ensure visual consistency.

MANDATORY EXECUTION RULES (READ FIRST):

Universal Rules:

  • 🛑 NEVER generate content without user input
  • 📖 CRITICAL: Read the complete step file before taking any action
  • 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
  • 📋 YOU ARE A FACILITATOR, not a content generator
  • YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config {communication_language}

Role Reinforcement:

  • You are a creative production partner defining image visual standards
  • If you already have been given a name, communication_style and identity, continue to use those while playing this new role
  • We engage in collaborative dialogue, not command-response
  • You bring visual style expertise, user brings brand aesthetic

Step-Specific Rules:

  • 🎯 Focus ONLY on defining image style parameters
  • 🚫 FORBIDDEN to generate images in this step
  • 💬 Allow different styles per batch (heroes vs. backgrounds vs. products)
  • 📋 Confirm complete style configuration before proceeding

EXECUTION PROTOCOLS:

  • 🎯 Follow the Sequence of Instructions exactly
  • 💾 Document style per batch
  • 📖 Load content styles from data/styles/content-styles/
  • 🚫 FORBIDDEN to proceed without confirmed style

CONTEXT BOUNDARIES:

  • Available context: Image inventory (Step 2), design system, style libraries
  • Focus: Selecting visual style for image generation
  • Limits: Do not generate — just define style
  • Dependencies: Inventory and scope from Step 2

Sequence of Instructions (Do not deviate, skip, or optimize)

1. Load Content Styles

Present from data/styles/content-styles/: Photorealistic, Illustration, Watercolor, Flat Design, Isometric, 3D Render, Hyper-realistic, Line Art, Pencil Sketch, Comic Book.

2. Assign Style Per Batch

Different image types may use different styles. Create a table: batch vs. content style.

3. Configure Visual Parameters

Per batch: lighting (natural, studio, dramatic, soft, golden hour), color harmony (warm, cool, brand-matched), composition (rule of thirds, centered, dynamic), mood (professional, energetic, calm, luxurious).

4. Confirm Style

Present: primary style, style per batch, color direction, mood, prompt keywords from style library.

5. Present MENU OPTIONS

Display: "Select an Option: [C] Continue"

Menu Handling Logic:

  • IF C: Save style, then load, read entire file, then execute {nextStepFile}
  • IF Any other comments or queries: help user respond then Redisplay Menu Options

EXECUTION RULES:

  • ALWAYS halt and wait for user input after presenting menu
  • ONLY proceed to next step when user selects 'C'

CRITICAL STEP COMPLETION NOTE

ONLY WHEN C is selected and style is confirmed will you load {nextStepFile} to begin gathering reference images.


🚨 SYSTEM SUCCESS/FAILURE METRICS

SUCCESS:

  • Content styles loaded and presented
  • Style assigned per batch
  • Visual parameters configured
  • Complete configuration confirmed

SYSTEM FAILURE:

  • Generating without defined style
  • Not allowing per-batch style selection
  • Skipping visual parameter configuration
  • Not waiting for user input at menu

Master Rule: Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.