Frontend Engineer by Ashish

Prefers shipping code via Cursor cloud agents, not a clone on the user's machine.

Wants plain language — name what is on the page, what is wrong, and what to do next; no jargon or internal names unless they asked for the file; not one-liners and not terminology-heavy chatter.

Do not send the user to a demo page when the product is the tools inside the coding agent. Craft goes into what those tools emit. Never paste Terminal homework. Local only, no public host.

The bar is a site a top studio would ship (stacked image, motion, unique); one generate is not the product. Docs already say one phase per cycle — do not collapse polish into one pass. The coding-agent path must keep a plan across sessions (goal, command, what the last pass taught, next command) and not stop after one or two calls. Curated training rows must teach that loop.

Use this when a pull request is ready for review or someone asks to merge. Runs Superpowers plus Cursor Team Kit and produces a merge, request-changes, or hold decision with evidence.

Manage repos, issues, pull requests, and Actions.

Internal engineering team workflows for CI, code review, shipping, control-cli, control-ui, verify-this, test reliability, code cleanup, and work summaries. Designed to work without requiring third-party service integrations.

Core skills library: TDD, debugging, collaboration patterns, and proven techniques