11 October 2026 · Frontend workflow source check
Need a new design, or proof the current one works?
If the screen already has a visual direction, write the release checks before adding a design skill. Name the route, expected interaction, relevant widths, and failure states. Then run the checks on the rendered app. This is a task-fit recommendation, not a measured outcome comparison.
Choose the work
| Problem | Start with | Do not assume |
|---|---|---|
| No approved visual target for a new or substantially redesigned surface. | Frontend App Builder is a conditional concept-first path if Image Gen, approval, and browser comparison are available. | A polished concept is a release test. |
| A working frontend has a specific bug or change to verify. | Define the expected state and consider Frontend Testing & Debugging for its target-flow browser loop. | One screenshot or passing build covers every state. |
| A reusable template or product surface is being shipped. | Write your own acceptance checks for the surfaces buyers will use. Test the render and interactions against them. | A skill chooses your quality bar for you. |
What the sources establish
The pinned Frontend App Builder instructions call for Image Gen concepts before code except for a user opt-out or a small fix inside an existing design system. They require comparison between the accepted concept and a browser render. The current Frontend Testing & Debugging file instead starts with an entry route, action or state, and expected rendered result; it calls for page, console, screenshot, and interaction checks. These are author instructions, not evidence that either workflow improves a result.
A developer starting a large business project asked which skills or practices actually prevent regressions. A template seller reported using a written definition of done covering responsive widths, console errors, keyboard use, contrast, reduced motion, and packaging checks. The seller also sells the templates, so the output and productivity claims are self-reported. Neither post compares these two skills.
Decision and limits
Use a concept skill when the visual target is the unresolved decision. Use a targeted QA workflow when the target exists and a rendered behavior must be checked. For repeated template releases, make the acceptance criteria project-specific before either route. We did not install a skill, run a browser, inspect the seller's templates, or measure time, defects, sales, or visitor behavior. The QA file is on mutable main.