crussella0129

Structured five-phase workflow (Research → Plan → Build → Test → Loop) for long-horizon coding tasks. Use when the user runs /sprint-loop, asks to start a sprint, continue a sprint loop, run an iteration, work in numbered sprints, or invokes phrases like "sprint loop", "start a sprint", "continue the loop", or "next sprint". Also use when a project root contains a `sprints/` directory and the user asks to resume work.

Structured five-phase workflow (Research → Plan → Build → Test → Loop) for long-horizon coding tasks. Trigger when the user mentions sprint loops, starting a sprint, continuing a sprint, or when the project root contains a `sprints/` directory.

Structured five-phase workflow (Research → Plan → Build → Test → Loop) that translates Antigravity's native Planning Mode into the Sprint Loops cross-harness schema.

Execution rules and a visual-quality bar for all front-end work in an Astro + SolidJS + TypeScript codebase. Use this skill for ANY task that touches the UI or front-end files — creating or editing pages and components (.astro, .tsx), styles, forms, search/filter features, toggles, client state, animations, or front-end tests — even when the request never names the frameworks ("add a page", "wire up this form", "make it look better"). Also trigger on front-end symptoms: an element that renders but does nothing when clicked, layout shift while loading, janky motion, build/SSR errors like "window is not defined", or state that falls out of sync between components on a page. Always use it when refactoring or reviewing front-end code, especially anything written with React idioms (useState/useEffect, destructured props, className). Not for backend APIs, CI/tooling config, or React/Vue/Next codebases.