# Agentic Design Enterprise System Producer

> Producer skill activated by agentic-prototype-trigger for enterprise-system prototype workflows; writes staged HTML/CSS/JS bundles using seed UI stack detection, tiered exemplars, and strict handoff evidence.

- Skill: `dolphinai2026/agentic-design-enterprise-system-producer` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add dolphinai2026/agentic-design-enterprise-system-producer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dolphinai2026/agentic-design-enterprise-system-producer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: dolphinai2026 (https://skillmd.com/u/dolphinai2026)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dolphinai2026/agentic-design-enterprise-system-producer

---


# agentic-design-enterprise-system-producer

Default activation owner: `agentic-prototype-trigger`.

This skill is a producer, not a compatibility shim and not a design-advice helper. It writes staged prototype files only when `agentic-prototype-trigger` dispatches it with strict producer fields. The primary artifact may be a framework-native staged source tree when the seed target identifies a framework stack.

## Required Producer Input Contract

The producer subagent must receive:

- `orchestrator: agentic-prototype-trigger`
- `producer.execution: subagent`
- `producer.skill_name: agentic-design-enterprise-system-producer`
- `producer.producer_kind: enterprise-system`
- `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`
- `producer_selection`
- `detected_ui_stack`
- `seed_parity`
- `exemplar_resolution`
- `enterprise_pattern`
- `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`
- `structured_asset_payload`
- `structured_asset_payload.system_blueprint`
- `seed_generation_target`
- allowed write file list

If any required field is missing, return a blocked handoff report and do not write bundle files.

When system-home generation is requested by `structured_asset_payload.system_pages[]`, system-home mock bindings, or `seed_generation_target.seed_system_home_exemplar_ref`, the packet must additionally include `structured_asset_payload.system_pages[]`, `structured_asset_payload.mock_data_contract`, `seed_system_home_exemplar_ref`, and `exemplar_reuse_policy`; missing conditional system-home fields must block only that system-home dispatch. Object-only page-set packets remain valid without these system-home-only fields.

System-home dispatch packets must preserve the upstream `system_blueprint`, `system_pages[]`, and `mock_data_contract` exactly as supplied by `agentic-prototype-trigger`. The producer may use `seed_system_home_exemplar_ref` only according to `exemplar_reuse_policy`; for FS3 that policy is layout and interaction grammar only. Do not copy exemplar metrics, records, object names, routes, or workflow semantics into the generated prototype unless those facts already exist in the structured payload.

FS3 extends the existing enterprise producer with `system-home` support. There is no dashboard producer, and `dashboard` must not be emitted as a page role, route role, page-set role, skill kind, or producer kind. Dashboard concepts are allowed only as block semantics such as `dashboard-kpi` inside a `system-home` page.

## Built-In Enterprise Exemplars

P0A built-in exemplars are:

- `record-list`
- `record-form`
- `approval-queue`

Use seed exemplars first when they are close enough. Use built-in exemplars only when seed exemplars are missing or not close enough. Use `model_generated.enterprise-layout` when neither seed nor built-in exemplars are close enough.

## Enterprise Operational Surface Contract

Enterprise business pages must expose the operational surface a generated implementation can consume. Form-like pages are not allowed to collapse into isolated create/edit forms: include a record list or queue context, searchable filters, create entry point, row-actions, a detail-panel or detail-drawer, and a workflow-indicator when the business object has state transitions or approvals.

When multiple pages are generated, each page must carry distinct business structure and copy. Reusing the same table/form shell with changed headings is a blocking quality issue reported as `prototype_duplicate_page_structure`.

## Required Outputs

Write only under `staging_bundle_root`.

Framework-native mode is allowed only when `seed_generation_target` proves a Vue + Vite + vue-router + Element Plus shell with high-confidence seed detection evidence and seed exemplar page-set metadata. When unsupported, write only a blocked `handoff-report.yaml`; do not write `framework-native/` files and do not set `primary_artifact_mode: framework-native`.

Framework-native mode also requires all peer structured assets in `structured_asset_payload`: `system-blueprint`, `business-object`, `business-flow`, and `page-interaction`. If any peer structured asset is missing, write only a blocked `handoff-report.yaml` with reason `producer_structured_assets_missing`; do not write `framework-native/` files and do not set `primary_artifact_mode: framework-native`.

Supported framework-native mode writes:

- `framework-native/frontend/src/pages/<object-code>/*.vue` for Vue seed targets
- `framework-native/frontend/src/router/object-page-set.routes.ts`
- `html-review/index.html`
- `handoff-report.yaml`

Task 3 extends the deterministic framework-native producer output contract to include `framework-native/frontend/src/pages/system/SystemHome.vue`, `framework-native/frontend/src/router/system-home.routes.ts`, `framework-native/frontend/src/mock/prototype-mock-data.ts`, and `html-review/pages/system-home.html` when system-home is generated. Until that Task 3 producer implementation is present, this Task 2 contract requires prompt/readiness and handoff evidence to preserve those system-home inputs without claiming the deterministic producer path has emitted those files.

The supported handoff report must include `primary_artifact_mode: framework-native`, `producer`, `seed_generation_target`, `structured_asset_payload`, object-code page metadata, system-home page metadata, mock data contract evidence, the router artifact path, and relative artifact paths. `html-review/index.html` is a secondary review mirror; the framework-native source tree is the primary artifact.

Legacy HTML bundle mode writes:

- `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`, `producer`, `producer_selection`, `design_inputs.detected_ui_stack`, `design_inputs.seed_parity`, `design_inputs.exemplar_resolution`, `design_inputs.enterprise_pattern`, `design_inputs.selected_design_template`, `quality_evidence.design_quality.cloned_exemplar_id`, and `quality_evidence.design_quality.enterprise_producer`.

## Forbidden Actions

- Do not bypass `agentic-prototype-trigger`.
- Do not write files outside `staging_bundle_root`.
- The producer subagent must not write canonical bundle.
- The producer subagent must not write manifest.
- The producer subagent must not write asset-index.
- The producer subagent must not write final `prototype-manifest.yaml`, global `asset-index.yaml`, or any repository asset-index directly.
- Do not write phase metadata or perform Git commits.