agentic-design-frontend-design

# agentic-design-frontend-design This repo skill name is the default producer subagent for subagent-authored prototype bundle production. It may discuss design, diagnose design issues, and explain frontend decisions, but trigger-owned artifact production stays under `agentic-prototype-trigger`. ## Artifact-Producing Redirect Policy Artifact-producing prototype create, regenerate, refine, critique repair, or selected-element modification requests must redirect to `agentic-prototype-trigger`. Direct use of this skill is allowed only for non-artifact design discussion, design diagnosis, or explanation. Direct use must not write `staging_bundle_root`, canonical bundle, manifest, asset-index, phase metadata, or Git commits. Any Artifact-producing prototype request received here must redirect to `agentic-prototype-trigger`. The trigger normalizes producer-facing operations as `create_new` for new prototype work, `regenerate` for rerun generation, and `refine_existing` for critique repair, selected-element modification, or focused revision. ## Required Producer Input Contract The producer subagent must receive: - `orchestrator: agentic-prototype-trigger` - `producer.execution: subagent` - `operation: create_new | regenerate | refine_existing` - `prototype_production_run_id` - `idempotency_key` - `phase_id` - `prototype_id` - `source_spec_ref` - `staging_bundle_root` - `run_state_ref` - `Design Resource Palette` - `design_skill_palette.allowed[]` - `design_skill_palette.activated[]` - `design_skill_palette.skipped[]` - `active_design_system` - `selected_design_template` - `craft_refs` - `source_refs` - allowed write file list The design palette contract must preserve repo skill name entries for each activated or skipped helper so the trigger can validate the exact Design Resource Palette selection. If any required field is missing, return blocked questions and do not write bundle files. The allowed write file list is limited to: - `staging_bundle_root/index.html` - `staging_bundle_root/pages/*.html` - `staging_bundle_root/assets/styles.css` - `staging_bundle_root/assets/interactions.js` - `staging_bundle_root/assets/mock-data.json` - `staging_bundle_root/agentic-design-frontend-design-report.yaml` ## Required Outputs Write only under `staging_bundle_root`: - `index.html` - `pages/*.html` - `assets/styles.css` - `assets/interactions.js` - `assets/mock-data.json` - `agentic-design-frontend-design-report.yaml` The report must include `kind: agentic-design-frontend-design-subagent-handoff`, `prototype_production_run_id`, `request_digest`, `operation`, `status`, `entrypoint`, `files_written`, `pages`, `design_inputs`, `design_skill_palette`, `quality_evidence`, `implementation_notes`, and `blocked_reason`. The producer must reuse the existing report schema. Do not invent a second report schema or rename the existing contract fields. Keep `design_inputs.active_design_system`, `design_inputs.selected_design_template`, and `quality_evidence.design_quality` in the handoff report exactly as named so the trigger and lint/critic tooling can read them without adapters. For structured asset refinement, write evidence into the existing `agentic-design-frontend-design-report.yaml`: `design_inputs.refinement_context` must echo the structured context, and `implementation_notes.refinement_evidence` must summarize affected pages, preserved source refs, preserved operation refs, and unchanged page ids. The producer subagent must not directly edit canonical formal assets. `quality_evidence.design_quality` must carry the producer-side evidence needed by the quality gate, including `cloned_exemplar_id`. If the producer cannot prove the reused exemplar clone, return a blocked result that preserves the same report schema and makes the failure machine-readable, for example with `exemplar_clone_missing` in blocked diagnostics or notes. ## Forbidden Actions - Artifact-producing prototype request handling that bypasses trigger ownership. - Do not write files outside `staging_bundle_root`. - Direct calls must redirect to `agentic-prototype-trigger`. - The producer subagent must not write canonical bundle. - The producer subagent must not write manifest. - The producer subagent must not write asset-index. - Do not write phase metadata or perform Git commits. ## Verification - Confirm the request includes all required trigger fields before writing. - Confirm outputs are limited to the allowed write file list. - Confirm blocked responses omit bundle writes when any required field is missing.