Research note · 30 September 2026

OpenDesign’s frontend-skill entry is not the full workflow.

OpenDesign’s frontend-skill entry names an OpenAI workflow for landing pages and app UI. Its own instructions say the full workflow requires a separate upstream install. The entry links to the OpenAI skills repository without an exact skill path. It is a pointer, not the full design guidance.

Decision: Do not install this entry expecting the full OpenAI frontend workflow. Check the actual instruction file and its revision before using any copy. We are not adding the pointer as a seventeenth catalogue skill.

What changed upstream

OpenAI’s April 2026 removal commit deleted the curated frontend-skill files. A historical version at 82d2c5b contains the full art-direction and layout rules, but that is a different, old revision. We did not install it, check current Codex compatibility, or compare its output.

Why this matters

A Codex user recommended the OpenDesign entry and estimated its quality relative to another design workflow. That is a personal report, not a controlled result. We cannot tell which bytes that user installed. The name alone does not identify the instructions an agent actually followed.

For a current design task, choose one of the sixteen task-specific listings by fit and prerequisites. Every listing has a source link. None has a pool-run outcome comparison. For the Vercel React Composition Patterns listing, the example fix remains open at this check.

Next check

Record the installed file path and commit, then compare the rendered result with a careful brief on the same task. We have not performed that test.