workflows-code

Frontend code workflows guide developers through three sequential phases: implementation (writing features like forms and API calls), debugging (isolating issues in DOM manipulation and animations), and verification (browser testing before completion). This phased approach ensures consistent quality gates and reduces coordination gaps across development stages.

Mandatory browser verification enforces testing of forms, API calls, DOM manipulation, external libraries, and Webflow patterns before marking work complete. The workflow routes verification as a required checkpoint, catching issues that automated tools miss and ensuring functional correctness across user interactions.

Debugging workflows use ASCII diagrams and flowcharts to visualize troubleshooting steps, breaking complex issues into actionable sequences. Integrated checklists track progress through debugging phases, automating consistent problem-solving patterns across forms, API integrations, DOM changes, and external dependencies.

Yes. The workflow supports CDN-safe initialization patterns and handles external library integration throughout implementation and verification phases. Reference materials document safe loading practices, ensuring external dependencies don't break workflows or verification checkpoints.

The implementation phase provides automation-ready prompts, reference materials for common patterns, and structured requirements for features like login flows, form handling, and API calls. It routes setup tasks, enforces quality gates, and loads pattern libraries before moving to debugging.

Separating debugging (isolating root causes in code) from verification (confirming fixes work in the browser) prevents developers from conflating symptoms with solutions. Phase routing ensures each concern receives focused attention, reducing iteration cycles and improving diagnostic accuracy.