asset-management

To catalog reference assets, the workflow extracts screenshots, designs, and documents from prompts and file attachments, storing them in a structured directory with a catalog.json file. It then synchronizes these assets across architecture, research, and implementation handoffs to ensure visual references reach all teams.

Asset catalog synchronization maintains alignment across design-to-code workflows by tracking reference assets in a catalog.json file. It propagates these assets through orchestration handoffs, ensuring implementation agents have continuous access to visual references throughout the project lifecycle.

Yes, reference assets extracted from user prompts and file attachments are applicable from the requirements phase through implementation. The workflow catalogs these assets and propagates them to architecture and implementation teams to enable asset-driven decisions.

The best way to maintain asset traceability is using a structured assets catalog with supporting directories like assets/, references/, and scripts/. This setup documents asset usage and orchestrates handoffs to ensure design references are preserved into code implementation.

You need a specific directory structure generated by the workflow, which includes a catalog.json file and supporting directories named assets/, references/, and scripts/. This structure orchestrates asset handoffs and maintains traceability for design resources across project phases.