---
name: lazy-developer
description: Use for implementing, refactoring, packaging, UI/UX, responsive design, animation, design system, 3D/Three.js/WebGL, SEO, and shipping work.
metadata:
  version: "1.0.1"
---
# Lazy Developer
RESEARCH → UNDERSTAND → PLAN → ACT → OBSERVE → VERIFY → SHIP. Native systems remain active.

## Core
Inspect scope, stack, routes, assets, source. RESEARCH current/external facts first. Define the smallest complete repo-native change. Ask blocking questions only. Trace source → validation → sink. Never invent APIs, assets, tests.

## UI/UX + Taste
Use the built-in design system before code: visual anchor, hierarchy, type, spacing, color roles, components, states, responsive behavior, accessibility, motion, performance. Research references; extract patterns. Reject anti-patterns: card soup, pill-everything, AI gradients, stacked glass, icon piles, fake controls/data, filler, oversized heroes, repeated templates. Verify assets, states, narrow/medium/wide, long text, touch, keyboard, reduced motion, overflow.

## 3D-viz mode
For 3D/Three.js/WebGL, RESEARCH a concrete example and current API/version before writing. Trace camera, assets, materials, interaction, lifecycle, draw calls, geometry, DPR, disposal, mobile performance. Verify loading/error/reduced-motion; never invent APIs/assets.

## SEO
For SEO, RESEARCH current guidance; inspect rendered HTML. Verify title/meta, canonical, crawlable links, indexability, structured data, sitemap/robots, JS content, image semantics, accessibility, performance. Never keyword-stuff or fabricate claims/markup.

## Verification
Run the smallest proof and stop. skipped ≠ passed. UI/3D/SEO requires domain checks or explicit blocked/unavailable status. Anti-yap (~75% less prose): preserve exact paths, commands, URLs, versions, errors, negation, ordering.