Agentic Prototype Design

agentic-prototype-design

This skill is a compatibility shim. It does not own prototype production workflow.

Trigger Conditions

Use this shim when older docs, users, or skills refer to agentic-prototype-design for an artifact-producing operation.

For any artifact-producing operation, call agentic-prototype-trigger with profile: general-app plus original source spec, current manifest when present, selected elements when present, and user request or critique diagnostics when present.

This compatibility shim preserves legacy guidance that referred to the general/default generator selected by agentic-prototype-trigger/rules/routing.md, but the shim itself no longer owns generation.

Required Inputs

• profile: general-app
• original source spec
• current manifest when present
• selected_elements when present
• user request when present
• critique diagnostics when present
• Read active DESIGN.md
• structured design questions in Agent Chat when upstream context is incomplete
• legacy marker expectations for data-agentic-id, data-agentic-label, data-agentic-role, and optional data-agentic-source-ref

Outputs

• A routing handoff to agentic-prototype-trigger
• Preserved agentic-design context needed for downstream request construction
• Blocked questions when source spec, manifest context, or selected_elements context is missing for the requested change
• manifest path, asset-index path, and diagnostics status remain trigger-owned downstream outputs
• shared Builder registry context and business derivation lint expectations remain downstream contract checks

Forbidden Actions

• This shim must not own prototype production workflow.
• Do not run artifact packaging from this shim.
• Do not bypass agentic-prototype-trigger for any artifact-producing operation.
• Do not commit, push, reset, rebase, stash, or delete user work as part of this skill (git_read_only tier in skills/agentic-git-sync/rules/git-permission-boundaries.md); this does not restrict other active skills' Git contracts.

Command Invocation

Call `agentic-prototype-trigger` with profile: general-app and the collected source spec / manifest / selected_elements / critique context.

# Downstream trigger-owned readiness check example:
# agentic-design prototype scan --workspace <workspace> --spec <spec>
# Downstream trigger-owned packaging / doctor example:
# agentic-design prototype doctor --workspace <workspace> --manifest <manifest>

Legacy downstream marker contract retained for compatibility:

• data-agentic-id
• data-agentic-label
• data-agentic-role
• data-agentic-source-ref
• page header, navigation, form, table, panel, card/list group, modal/drawer, and primary action groups
• deterministic from page id, role, label, and source ref

Legacy template note retained for compatibility: templates/index.yaml and templates/page.yaml are intermediate planning structures only.

Legacy output note retained for compatibility: HTML preview hub index.html, pages/*.html stay part of the downstream staged bundle and packaging contract.

Verification Commands

PYTHONPATH=python .venv/bin/pytest tests/agentic_core/test_design_skills.py -q