Vibe coding
AI-assisted building with planning, review, versioning, and responsibility.
My approach
Vibe coding helps me turn an idea into a working prototype quickly, but quality comes from the system around the generation: a clear outcome, small changes, code review, security checks, testing, documentation, and a reversible release.
Planning with advanced models
I ask a capable model to question the product brief, compare architectures, map data flow, identify failure states, and draft acceptance tests before code generation. I own the decisions and verify the proposed libraries, permissions, and implementation.
3D image project
The 3D image project taught me to define audience and composition first, prototype with small assets, test loading and responsive behavior, organize original files, and review accessibility text and performance before release.
Changelogs and code changes
Every change has one clear purpose, a readable diff, preflight tests, a version and changelog entry, and postflight evidence. Preflight drafts the expected wiki changes; postflight updates the project article with what actually shipped, how it was verified, limitations, and lessons. Small changes are easier to understand, secure, reverse, and learn from.
Versioning, UI and UX
Versioning names the delivered state. UI defines the visible controls and layout. UX covers the entire journey from the first interaction through success or recovery. I treat all three as one quality standard rather than separate polish steps.