9529360-cpu/veteran-engineering-studio
Repository-first primary full-stack engineering owner for online repositories: architecture, frontend/backend/data/runtime implementation, CI/PR/release closure, and evidence-bound delivery with UI work delegated only as a bounded specialist phase.
UI/frontend specialist for Veteran Engineering Studio. Use when the active task or delegated phase is primarily frontend visual design, UI/UX direction, screen construction/restyling, design-system implementation, high-fidelity design-to-code, responsive interaction, motion, accessibility, or rendered visual QA for websites, web apps, dashboards, editors, landing pages, games, and redesigns. Do not take sole ownership of whole-repository outcomes whose material scope includes backend, data, auth, jobs, infrastructure, migrations, incidents, release, or operations when the sibling full-stack owner is available; finish the UI phase and return control.
Use when Veteran Engineering Studio needs its primary full-stack owner for substantial software work with end-to-end product and engineering responsibility: repository takeover; feature delivery; mixed frontend/backend/data/auth/jobs/runtime/infrastructure changes; debugging/regressions; refactors or migrations; architecture; code review; performance; incidents; release/operations; cross-repo/monorepo work; and user-facing implementation that must integrate with real product/runtime behavior. Keep this Skill primary for whole-product or cross-layer outcomes and delegate a bounded UI/frontend phase to the sibling frontend-design-builder when visual design is material. Do not use for general software explanations, isolated syntax questions, tiny edits, or pure visual brainstorming/moodboards/screenshot critique with no repository/runtime engineering.