appgenerator-change

Review AppGenerator changes against canonical app-bundle contracts and UI quality gates.

14|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill appgenerator-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: appgenerator-change
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/appgenerator-change
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill appgenerator-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review and implement changes to AppGenerator prompts and contract enforcement without breaking canonical app-bundle generation behavior or runtime expectations.

Core Features & Use Cases

  • AppGenerator-focused change review: Update prompts, structured outputs, file contracts, and assembly guidance specifically when the change touches AppGenerator behavior.
  • Contract and UI quality gate protection: Preserve schema-first persistence and canonical runtime boundaries while maintaining generated UI quality checks.
  • Targeted inspection and testing: Follow the recommended inspection paths and run the narrowest AppGenerator test slices relevant to the edited contracts or wiring.

Quick Start

Ask the AI to review or implement the change described in "change summary or file path" while adhering to AppGenerator boundaries and updating the matching contracts and tests.

Frequently Asked Questions about appgenerator-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update app generator prompts without breaking contract validation?

To update app generator prompts safely, enforce file contract ownership rules and validate AppBuildPlan structures to preserve canonical app-bundle generation behavior and UI quality gates.

What is the best way to maintain UI quality gates during app-bundle assembly updates?

Maintaining UI quality gates during app-bundle assembly requires strict adherence to current runtime contracts and schema-first persistence boundaries while applying targeted test impact analysis to the modified modules.

How do I validate module page intent changes against runtime contracts?

Validate module page intent changes by checking persistence alignment and file contract ownership boundaries, ensuring the modifications do not violate established workflow sequencing or AppGenerator responsibilities.

When do I need to run test impact analysis for AppBuildPlan modifications?

Run test impact analysis for AppBuildPlan modifications whenever changes touch generated artifact structures or prompt engineering outputs, executing the narrowest test slices relevant to the edited contracts.

Can I modify file contract ownership rules without affecting generated artifact structure?

Modifying file contract ownership rules requires reviewing AppGenerator boundaries and persistence alignment to prevent breaking the generated artifact structure or canonical app-bundle assembly guidance.