* feat(sidebar): add onboarding guide * docs(guide): clarify tag search casing * docs(guide): clarify workflow save copy * docs(guide): refine sidebar visuals * docs(guide): refresh save snapshot visual * docs(guide): refresh load snapshot visual * docs(guide): refresh module save visual * docs(guide): use real sidebar screenshot * docs(guide): render sidebar overview screenshot directly * docs(guide): soften sidebar overview annotations * docs(guide): clarify nodes action bar callout * docs(guide): clarify workflow action bar callout * docs(guide): simplify sidebar overview markers * docs(guide): align sidebar overview intro * docs(guide): use real snapshot recipe screenshots * docs(guide): simplify project workflow diagram * docs(guide): make function cards scannable * docs(guide): sketch module recipe icon focus * docs(guide): use real icon screenshot for module recipe * docs(guide): add cropped workflow action screenshot * docs(guide): use full toolbar screenshot for module recipe * docs(guide): use real search screenshot * docs(guide): use real node search screenshot * docs(guide): standardize screenshot recipe cards * docs(guide): tighten recipe callout styling * docs: require visual QA for UI work * docs(guide): address pass-2 review nits
1.1 KiB
1.1 KiB
ComfyUI-Koolook Codex Instructions
Required Project Context
Read CLAUDE.md before making substantive changes. It contains the
project-specific workflow, dev-sync rules, release rules, and sidebar
maintenance notes.
Visual QA Is Mandatory For UI Work
For any change that affects rendered UI, guide pages, screenshots, CSS/layout, onboarding docs, or browser-visible behavior:
- Do not rely on CSS coordinates, source inspection, or user screenshots alone.
- Open the changed page/app in a browser-rendered environment that Codex can screenshot.
- If a
file://guide page is blocked by browser tooling, serve the repo over local HTTP instead, for example:python3 -m http.server <port>from the repo root, then openhttp://127.0.0.1:<port>/.... - Take a rendered screenshot after the change and inspect the actual visual result before committing or pushing.
- If visual verification is blocked, say that clearly and do not present the UI change as ready unless the user explicitly waives visual QA.
This is especially important for overlays, icon highlights, responsive layout, text fitting, and visual guide pages.