docs: update all documentation and add AI tooling configs
- Rewrite README.md with current architecture, features and stack - Update docs/API.md with all current endpoints (corporate, BI, client 360) - Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL - Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente) - Add docs/INDEX.md documentation index - Add PROJETO.md comprehensive project reference - Add BI-CCC-Implementation-Guide.md - Include AI agent configs (.claude, .agents, .gemini, _bmad) - Add netbird VPN configuration - Add status report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,111 @@
|
||||
---
|
||||
name: 'step-01-load-context'
|
||||
description: 'Load motion content requirements including what needs to move, where, and why'
|
||||
nextStepFile: './step-02-inventory.md'
|
||||
---
|
||||
|
||||
# Step 1: Load Context
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Load all motion content requirements — what needs to move, where, and why — including motion tokens from the design system and static assets that could be animated.
|
||||
|
||||
## 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 loading motion content context
|
||||
- ✅ 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 motion design expertise, user brings project specifics
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on loading and summarizing motion content context
|
||||
- 🚫 FORBIDDEN to generate motion content or select styles in this step
|
||||
- 💬 Identify all motion content types: hero animations, product demos, micro-interactions, background video, explainers
|
||||
- 📋 Present clear context summary before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document context summary
|
||||
- 🚫 FORBIDDEN to skip any context source
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Page specifications, design system motion tokens, existing visual assets
|
||||
- Focus: Loading all motion content requirements
|
||||
- Limits: Do not start generating — just load context
|
||||
- Dependencies: Page specifications must exist
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Load Motion Requirements
|
||||
|
||||
From page specs: hero animations, product demonstrations, micro-interactions, background video, explainer sequences.
|
||||
|
||||
### 2. Load Motion Tokens
|
||||
|
||||
From design system: duration scale, easing curves, transition types.
|
||||
|
||||
### 3. Load Visual Assets
|
||||
|
||||
Check for static assets that motion builds upon: images needing animation, UI components needing state transitions, illustrations that could be animated.
|
||||
|
||||
### 4. Present Context Summary
|
||||
|
||||
```
|
||||
Video/Motion Context:
|
||||
- Motion assets needed: [count]
|
||||
- Types: [hero, product demo, micro-interaction, background, explainer]
|
||||
- Duration range: [shortest] to [longest]
|
||||
- Existing static assets to animate: [count]
|
||||
- Full video productions: [count]
|
||||
```
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save context, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-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 context is summarized will you load {nextStepFile} to begin building the motion content inventory.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All motion requirements identified from specs
|
||||
- Motion tokens loaded
|
||||
- Visual assets checked for animation potential
|
||||
- Context summary presented
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Starting generation without context
|
||||
- Missing motion content types
|
||||
- Not checking existing visual assets
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,104 @@
|
||||
---
|
||||
name: 'step-02-inventory'
|
||||
description: 'Catalog all motion content needed with type, duration, complexity, and format requirements'
|
||||
nextStepFile: './step-03-select-style.md'
|
||||
---
|
||||
|
||||
# Step 2: Asset Inventory
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Catalog all motion content needed with type, duration, complexity level, format requirements, and file size targets — letting the user select generation scope.
|
||||
|
||||
## 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 organizing motion content inventory
|
||||
- ✅ 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 motion production expertise, user brings scope decisions
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on cataloging motion content with technical requirements
|
||||
- 🚫 FORBIDDEN to generate motion content in this step
|
||||
- 💬 Categorize by complexity: Simple (CSS/SVG), Medium (Lottie), Complex (video), Generated (AI)
|
||||
- 📋 Include format and file size targets
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document inventory with technical requirements
|
||||
- 🚫 FORBIDDEN to proceed without user scope selection
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Motion context from Step 1
|
||||
- Focus: Organizing motion content into generation-ready inventory
|
||||
- Limits: Do not generate — just catalog
|
||||
- Dependencies: Context from Step 1
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Build Motion Asset Catalog
|
||||
|
||||
Table: asset name, page, type, duration, format (MP4/WebM, CSS/Lottie, SVG anim).
|
||||
|
||||
### 2. Categorize by Complexity
|
||||
|
||||
[S] Simple (CSS/SVG, <10KB), [M] Medium (Lottie, <50KB), [C] Complex (video, <10MB), [G] Generated (AI video, <2MB).
|
||||
|
||||
### 3. Document Technical Requirements
|
||||
|
||||
Format, use case, and file size target per complexity level.
|
||||
|
||||
### 4. Present Inventory with Scope Options
|
||||
|
||||
Show counts per complexity level, total motion assets. Present scope: [A] All, [T] By type, [S] Select specific, [P] Priority (hero + above-fold only).
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save inventory and scope, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-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 scope is confirmed will you load {nextStepFile} to begin selecting motion style.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All motion assets cataloged with technical requirements
|
||||
- Complexity levels assigned
|
||||
- File size targets documented
|
||||
- User selected scope
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Starting generation without inventory
|
||||
- Missing complexity categorization
|
||||
- Not including file size targets
|
||||
- Not waiting for user scope selection
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,109 @@
|
||||
---
|
||||
name: 'step-03-select-style'
|
||||
description: 'Define motion personality, timing parameters, and video visual treatment'
|
||||
nextStepFile: './step-04-generate.md'
|
||||
---
|
||||
|
||||
# Step 3: Select Style
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Define the motion style — personality (subtle/fluid/energetic/precise), timing parameters, video visual treatment, and color direction — so all motion content feels cohesive.
|
||||
|
||||
## 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 motion 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 motion design expertise, user brings brand preferences
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on defining motion style parameters
|
||||
- 🚫 FORBIDDEN to generate motion content in this step
|
||||
- 💬 Set timing parameters based on personality selection
|
||||
- 📋 Confirm complete style configuration before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document complete motion style configuration
|
||||
- 🚫 FORBIDDEN to proceed without confirmed style
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Motion inventory (Step 2), design system motion tokens
|
||||
- Focus: Defining motion style parameters
|
||||
- Limits: Do not generate — just define style
|
||||
- Dependencies: Inventory and scope from Step 2
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Select Motion Personality
|
||||
|
||||
[S] Subtle (corporate, medical), [F] Fluid (wellness, lifestyle), [E] Energetic (startup, gaming), [P] Precise (engineering, SaaS).
|
||||
|
||||
### 2. Configure Timing Parameters
|
||||
|
||||
Based on personality: base duration, easing curve, stagger delay, loop delay.
|
||||
|
||||
### 3. Select Video Treatment (for produced/generated video)
|
||||
|
||||
[C] Cinematic (shallow DOF, color graded), [D] Documentary (natural, handheld), [M] Motion design (graphics-driven), [A] Abstract (textures, ambient).
|
||||
|
||||
### 4. Define Color and Lighting
|
||||
|
||||
Match brand palette, dark/light preference, contrast level for overlaid text.
|
||||
|
||||
### 5. Confirm Style
|
||||
|
||||
Present: personality, timing parameters, video treatment, color direction.
|
||||
|
||||
### 6. 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](#6-present-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 generating motion content.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Motion personality selected
|
||||
- Timing parameters configured
|
||||
- Video treatment selected
|
||||
- Color direction defined
|
||||
- Complete style confirmed
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Generating without defined style
|
||||
- Not configuring timing parameters
|
||||
- Skipping video treatment selection
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,112 @@
|
||||
---
|
||||
name: 'step-04-generate'
|
||||
description: 'Generate video and motion assets using appropriate tools per complexity level'
|
||||
nextStepFile: './step-05-review.md'
|
||||
---
|
||||
|
||||
# Step 4: Generate Motion Content
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Generate video and motion assets, routing each to the appropriate tool based on complexity level — CSS/SVG for simple, Lottie for medium, video production for complex, AI generation for generated.
|
||||
|
||||
## 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 executing motion content generation
|
||||
- ✅ 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 multi-format motion production expertise, user brings approval decisions
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Route each asset to the correct tool based on complexity
|
||||
- 🚫 FORBIDDEN to use wrong tool for complexity level
|
||||
- 💬 Preview each in context (how it looks on the page)
|
||||
- 📋 Track progress across all complexity levels
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Track progress per complexity group
|
||||
- 📖 Use reference frames from approved static images for AI video
|
||||
- 🚫 FORBIDDEN to skip preview and timing check per asset
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Inventory (Step 2), style (Step 3)
|
||||
- Focus: Generating motion content with correct tools
|
||||
- Limits: Generate only — full review in Step 5
|
||||
- Dependencies: Confirmed style and scoped inventory
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Route by Complexity
|
||||
|
||||
- Simple (CSS/SVG): Generate keyframe animations, SVG with SMIL/CSS animation
|
||||
- Medium (Lottie): Describe animation for After Effects/Lottie, generate Lottie JSON if MCP supports
|
||||
- Complex (video): Storyboard, shot list, guide to production
|
||||
- AI Generated: Craft video generation prompts with reference frames
|
||||
|
||||
### 2. Build Prompts (AI Generated)
|
||||
|
||||
Include: duration, subject, movement, mood, style keywords, color palette, dimensions, FPS, loop preference, reference frame.
|
||||
|
||||
### 3. Select Service
|
||||
|
||||
For AI video: [G] Generate via MCP, [E] Export prompts. For CSS/SVG: [C] Generate code, [S] Spec document.
|
||||
|
||||
### 4. Generate and Preview
|
||||
|
||||
For each: generate/create, preview in page context, check timing and feel, iterate if needed.
|
||||
|
||||
### 5. Track Progress
|
||||
|
||||
Display progress per complexity group with counts.
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save generated motion content, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-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 all scoped motion content is generated will you load {nextStepFile} to begin reviewing the set.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Each asset routed to correct tool
|
||||
- Prompts crafted with motion style parameters
|
||||
- Preview and timing verified per asset
|
||||
- Progress tracked per complexity group
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Using wrong tool for complexity level
|
||||
- Not previewing in context
|
||||
- Skipping timing verification
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
121
_bmad/wds/workflows/6-asset-generation/steps-v/step-05-review.md
Normal file
121
_bmad/wds/workflows/6-asset-generation/steps-v/step-05-review.md
Normal file
@@ -0,0 +1,121 @@
|
||||
---
|
||||
name: 'step-05-review'
|
||||
description: 'Review all motion content for consistency, performance, and accessibility compliance'
|
||||
workflowFile: '../workflow.md'
|
||||
---
|
||||
|
||||
# Step 5: Review and Iterate
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Review all motion content for consistency, performance, accessibility compliance, and user experience quality — then save the approved motion set.
|
||||
|
||||
## 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 conducting motion quality review
|
||||
- ✅ 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 motion UX and performance expertise, user brings final approval
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Check four dimensions: consistency, performance, accessibility, UX quality
|
||||
- 🚫 FORBIDDEN to save without user approval
|
||||
- 💬 Preview in page context alongside static versions
|
||||
- 📋 Verify `prefers-reduced-motion` coverage
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Save to `{output_folder}/E-Assets/motion/`
|
||||
- 📖 Check: timing consistency, file sizes, flash rate, reduced-motion support
|
||||
- 🚫 FORBIDDEN to skip performance or accessibility checks
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All generated motion content, style configuration
|
||||
- Focus: Quality review, performance, and accessibility
|
||||
- Limits: This is the final step — focus on quality and delivery
|
||||
- Dependencies: Generated motion content from Step 4
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Preview All Motion
|
||||
|
||||
Show each: in isolation, in page context, before/after (static vs. animated).
|
||||
|
||||
### 2. Motion Consistency
|
||||
|
||||
Verify: timing consistent, easing curves match, motion direction logical, no competing animations, loops seamless.
|
||||
|
||||
### 3. Performance Check
|
||||
|
||||
Per asset: file size within target, no excessive complexity, CSS uses GPU-accelerated properties, videos compressed, lazy loading for below-fold.
|
||||
|
||||
### 4. Accessibility Check
|
||||
|
||||
Respects `prefers-reduced-motion`, no flashing (<3 per second), does not interfere with readability, video has pause/stop, alternative static content provided.
|
||||
|
||||
### 5. User Review
|
||||
|
||||
Present: [A] Approve all, [R] Regenerate specific, [T] Timing adjust, [E] Easing adjust, [C] Full page context preview, [P] Performance report.
|
||||
|
||||
### 6. Iterate
|
||||
|
||||
For flagged assets: adjust timing/easing/content, regenerate or re-code, re-preview in context.
|
||||
|
||||
### 7. Save Approved Set
|
||||
|
||||
Save to `{output_folder}/E-Assets/motion/`: `css/`, `svg/`, `lottie/`, `video/`, `motion-set-summary.md`.
|
||||
|
||||
### 8. Update Design Log
|
||||
|
||||
Record: assets created count, type breakdown, motion personality, total added weight, reduced-motion coverage.
|
||||
|
||||
### 9. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [M] Return to Activity Menu"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF M: Save set, update design log, return to Activity Menu in {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#9-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
This is the final step of the Videos/Motion workflow. When M is selected and set is saved, return to the Activity Menu.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All motion content reviewed
|
||||
- Consistency, performance, accessibility verified
|
||||
- User approved final set
|
||||
- Saved to correct locations by type
|
||||
- Design log updated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Saving without user approval
|
||||
- Skipping performance or accessibility checks
|
||||
- Not verifying reduced-motion support
|
||||
- Not updating design log
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user