mozaiks: Skill for Claude Code

Before starting: git fetch origin && gh pr list --state open && git log origin/main --oneline -3 — if another agent has an open PR touching the same files you need, wait for it to merge, then branch from fresh origin/main.

Use this skill when a change touches AppGenerator specifically.

Typical triggers:

• factory_app/workflows/AppGenerator/**
• AppGenerator agents or prompts
• AppBuildPlan shape or validation
• structured_outputs.yaml
• factory_app/build_context/AppGenerator/file_contracts.yaml
• factory_app/build_context/AppGenerator/domain_catalogs.yaml
• factory_app/build_context/AppGenerator/module_archetypes.yaml
• tools/app_build_plan.py
• tools/assemble_app_tasks.py
• shared generated UI contract checks used by AppGenerator
• module, page, or data contract generation behavior
• managed-capability or external-adapter planning
• app-owned facade module patterns
• AppGenerator-specific tests or fixtures

Inspect first:

• factory_app/workflows/AppGenerator/agents.yaml
• factory_app/workflows/AppGenerator/structured_outputs.yaml
• factory_app/workflows/AppGenerator/middleware.yaml
• factory_app/workflows/AppGenerator/transition_graph.yaml
• factory_app/workflows/AppGenerator/context_variables.yaml
• factory_app/build_context/AppGenerator/file_contracts.yaml
• factory_app/build_context/AppGenerator/domain_catalogs.yaml
• factory_app/build_context/AppGenerator/module_archetypes.yaml
• factory_app/workflows/AppGenerator/tools/app_build_plan.py
• factory_app/workflows/AppGenerator/tools/assemble_app_tasks.py
• factory_app/workflows/_shared/generated_ui_contract.py

Catalog placement rule:

• AppGenerator prompt catalogs live only under factory_app/build_context/AppGenerator/.
• AppGenerator runtime workflow files live under factory_app/workflows/AppGenerator/.
• Hooks resolve factory build-context paths through factory_app.workflows._shared.hook_utils.workflow_context_path().
• Do not recreate factory_app/workflows/_shared/catalogs/.
• Do not add static prompt catalog values to context_variables.yaml; context variables are runtime/session state.
• the narrowest relevant AppGenerator tests before editing:
  • tests/test_appgenerator_module_contracts.py
  • tests/test_appgenerator_canonical_generation.py
  • tests/test_appgenerator_persistence_alignment.py
  • tests/test_appgenerator_validate_wiring.py
  • tests/test_appgenerator_ui_quality_gate.py
  • tests/test_appgenerator_component_drift_guard.py
  • tests/test_appgenerator_managed_capability_smoke.py
  • tests/test_appgenerator_generated_page_binding.py
• inspect upstream build-sequence context only when the AppGenerator change depends on upstream inputs or assumptions from ValueEngine, ThemeCapture, DesignDocs, or AgentGenerator

Core truth:

• AppGenerator is the final app-bundle generation workflow inside the broader factory workflow_sequence.
• It consumes upstream outputs from earlier build workflows.
• It does not own product strategy, concept formation, brand discovery, or workflow generation.
• It emits canonical app workspace artifacts.
• It must respect the canonical app structure and the platform's current runtime contracts.
• It must respect factory_app/build_context/AppGenerator/file_contracts.yaml.
• It must not invent runtime contracts unsupported by the platform.
• It must not generate provider-owned managed capability internals.
• It should keep persistent app UI schema-first unless the bounded custom route contract is explicitly required.

Boundary rules:

• Do not treat AppGenerator as the whole build system.
• Do not change workflow_sequence composition from this skill; use factory-build-workflow-change when the change widens into extension_registry.json, transitions, entrypoints, or cross-workflow build composition.
• Do not generate backend/models.py or backend/models/*.py.
• Do not generate contracts/subscriptions.yaml as the canonical reaction contract.
• Do not generate flat root manifests when the canonical contract uses contracts/.
• Do not generate app/capability_packs/.
• Do not generate transport.py or duplicate runtime transport infrastructure.
• Do not bind pages directly to managed-capability internals; use the app-owned facade module pattern.
• Do not hardcode provider-specific or private product examples into OSS guidance, tests, or fixtures.
• Do not assume ctx.db; use the canonical persistence model and ctx.persistence.collection(module_id, collection_name).
• Do not generate local visual primitive clones or raw persistent-page React when the shipped schema and primitive contracts can represent the surface.