메뉴
Use when UI changes must be proven safe across breakpoints using baseline and diff workflows. AE.LTD visual quality gate for release confidence.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Diligence-grade product and technical analysis for the ae.ltd proof-agent concept, including comparison against Cursor and Omnara, MVP and production architecture, red-team review, and build-vs-buy evaluation. Use when Codex needs to create or critique PRDs, tech specs, competitive diligence, leadership memos, or multi-agent evaluation packs for agent-runtime, demo-agent, or proof-agent products.
Use when creating or upgrading CLAUDE.md instructions and selecting the right template baseline for repo size, architecture, and team constraints. AE.LTD template decision workflow.
Use when coding decisions depend on current library/framework APIs and you need version-accurate docs before implementation. AE.LTD workflow tuned for fast, verifiable doc grounding.
Use when scaffolding or extending MCP servers, adding tools/resources/prompts, or hardening MCP tool schemas and handlers. AE.LTD workflow tuned for production-ready MCP delivery.
Use when unit tests look green but confidence is low and mutation testing is needed to expose weak assertions. AE.LTD workflow for targeted mutation runs and actionable test hardening.
Use when converting plain-language automation goals into production-ready n8n workflow JSON with retries, error paths, and credential-safe placeholders. AE.LTD automation blueprint workflow.
| name | ae-ltd-visual-regression-forge |
| description | Use when UI changes must be proven safe across breakpoints using baseline and diff workflows. AE.LTD visual quality gate for release confidence. |
Proves UI changes are safe across breakpoints using baseline and diff workflows. Visual quality gate for release confidence. Niche gem source: visual-regression plugin from awesome-claude-code-toolkit.
User: "Did my CSS change break anything?"
→ Define scope → Capture baseline → Run diff → Report pass/fail
Define snapshot scope. Pick critical pages/components and three base viewports: mobile, tablet, desktop.
Capture clean baselines. Wait for network idle and mask dynamic regions.
Capture current state with matching settings. Use identical viewport/device/browser settings for comparability.
Run diff and classify. Compute pixel deltas and mark pass/warn/fail against threshold.
Convert failures into actionable fixes. Map each diff to CSS/layout/asset causes and patch.