onex

Add Better Auth plus a Neon Postgres database to a Next.js App Router app using raw SQL — no ORM. Scaffolds a raw-SQL migration runner (`yarn db:migrate`) and an idempotent admin seeder (`yarn db:seed`), wires email+password / passwordless magic-link / email-OTP authentication via Resend, builds a compact login / sign-up / forgot-password dialog with the logo top-centered, and updates `.env.example`. Asks at run time whether to add Google/LinkedIn OAuth and SMS OTP as extra login methods, and whether the app is a multi-tenant SaaS (Better Auth organization model + seeded org). Use when the user says "/onex:add-auth-db", "add auth and a database", "set up Better Auth with Neon", "add login to this app", "scaffold authentication", or wants authentication + Postgres without an ORM.

Brainstorm gaps, loopholes, and improvement ideas across an entire module or app, reviewed through a product manager's lens. Always confirms scope first by asking which module to review (with a detected list to pick from) unless the user already named one. Returns a thematic, severity-marked, continuously-numbered list and ends with a prioritized "top 5 this week" pick, then offers to phase implementation. Use when the user says "ideate", "ideate on X", "what are we missing", "review this as a PM", "what could we improve", "brainstorm gaps", "loopholes in this", "what's next on this module/app", or asks for a numbered list of refinements at the module or product level. Do NOT use for bug fixes, one-line changes, pure code reviews, or architectural decisions — this is product-thinking scope at the module/app level, not engineering scope.

Audit and rewrite content to remove AI writing patterns ("AI-isms") that make text sound machine-generated. Flags em dashes, hollow intensifiers, vocabulary tells (delve, leverage, robust, harness, etc.), template phrases, hashtag stuffing, chatbot artifacts, copula avoidance, synonym cycling, and structural uniformity — then rewrites for human voice. Supports a detect-only mode that flags patterns without rewriting, and context profiles (`linkedin`, `blog`, `technical-blog`, `investor-email`, `docs`, `casual`) that adjust rule strictness. Use when the user says "/onex:rewrite", "rewrite this", "remove AI-isms", "clean up AI writing", "make this sound less like AI", "edit for AI patterns", "audit my writing", "humanize this", or "flag AI tells".

Set up a modern AI agent on top of the six protocols that define how it connects to tools, other agents, suppliers, payments, the UI, and the user — MCP (Model Context Protocol, tools), A2A (Agent-to-Agent, discovery + delegation), UCP (Universal Commerce Protocol, supplier discovery + structured orders), AP2 (Agent Payments Protocol, typed mandates for bounded spend), A2UI (Agent-to-User Interface, interactive UI primitives), and AGUI (event streaming from agent to frontend). Confirms scope first by asking which agent framework — Claude Agent SDK or OpenAI Agent SDK — whether the agent has a commerce segment (gates UCP + AP2), whether it has a user-facing UI (gates A2UI + AGUI), whether it delegates to or is discoverable by other agents (gates A2A), runtime / language, greenfield vs existing repo, and identity / auth posture. Writes a detailed plan to `docs/agent-setup-plan.md` with concrete setup steps, code stubs, env vars, and verification steps per protocol — then offers to scaffold each protocol, one commit at a time, in dependency order. Use when the user says "/onex:setup-agent", "set up an agent", "scaffold an AI agent", "wire up the agent protocols", "add MCP / A2A / UCP / AP2 / A2UI / AGUI", "build a commerce agent", "make this app agentic", "set up agent tools", or asks how to wire up the modern agent protocols.

Style the OAuth / social sign-in buttons of a Next.js app's auth UI — which official provider icons and brand colors to use (Google, LinkedIn, Apple, GitHub, Microsoft), where the buttons sit on the login page and in the auth dialog, and the exact button layout, sizing, hover/pending/error states, and accessibility. Use when the user says "/onex:style-auth-ui", "style the login buttons", "style the auth UI", "add a Google/LinkedIn/Apple button", "fix the OAuth buttons", "the social buttons look off", "lay out the social login", or asks how third-party sign-in buttons should look or where they belong.