When using Ox Alpha for frontend UI, providing actionable browser, animation, and aesthetic tools first, then having the model read reference sites, is usually more reusable than simply asking it to “make a beautiful page.”
Suitable tasks: Marketing pages, Hero sections, animation prototypes, and frontend tasks that require browser-based review and verification.
Unsuitable tasks: Treating one visual result as proof of general design ability, or publishing generated code directly without review.
Applicable model version: Ox Alpha; the original post gives no version snapshot.
Applicable clients, agents, or APIs: OpenCode; the comments also mention Playwright CLI, GSAP, and reference sites.
Recommended reasoning levels and parameters: Not disclosed; fix the Harness, tool permissions, and timeouts first.
The original post does not publish a complete verbatim prompt. The following is a reusable workflow compiled from the post and comments and should not be cited as the original prompt:
1. Integrate Ox Alpha into a reversible frontend repository, and prepare Playwright CLI, GSAP, and the project's existing UI/animation tools.
2. First have the model read the project structure, existing components, and constraints; then have it use Playwright to open a public reference site and record its layout, copy, spacing, animation timeline, and interaction states.
3. Explicitly require that the reference site be used only to analyze information architecture and visual language, without copying brand assets, copy, or source code.
4. Implement a runnable Hero section first, then ask the model to check it in a browser on desktop and mobile, fixing overflow, interaction issues, and console errors.
5. Save screenshots, console errors, test results, and the diff for each change; add animations or details only after the previous round passes.
6. Finally, have a human review readability, keyboard operation, animation fallbacks, and differences from the reference site.The poster said they entered a prompt in OpenCode, the model stopped multiple times midway, and they eventually completed the Hero section after about 2–3 hours of repeatedly continuing the conversation. The commenter suggested adding GSAP, Playwright CLI, taste.md, and an accessible design reference. The original post does not publish the prompt text, repository, original screenshot files, or test logs.
“Better tools + reasoning” is the comment author's experience-based summary, not a controlled comparative experiment.
Whether the reference site can be viewed correctly by the model depends on the client's browser tools and permissions; providing only a link does not mean the model saw the page.
Visual quality, code correctness, and animation accessibility should be evaluated separately.
Ox Alpha