wiseiodev

Interactive guide for hand-shaping a reference feature in a greenfield repo. Use on day 1 of a new project to seed quality gates and canonical patterns before agents take over. Triggers on /bootstrap, "bootstrap a reference feature", "scaffold a canonical pattern".

Set up or operate per-feature Neon database branches for Drizzle projects. Use when schema-changing branches, agents, or worktrees need isolated databases, branch work should use db:push, feature branches must not commit generated migrations, and production migrations should be generated and applied only after merge.

Set up or tighten a repo's preferred quality-gate toolchain. Use when the user invokes /setup-quality, asks to add Biome, Vitest, Commitlint, Lefthook, pnpm scripts, Turbo quality gates, GitHub Actions CI, or wants the preferred quality setup applied to a project.

Break a PRD into ordered tracer-bullet slice specs. Use when a PRD exists and you need a queue of specs ready for plan-gate. Triggers on /decompose, "decompose this PRD", "break this into slices".

Run implementation phase against an approved plan. Use after /plan has been approved by the human. Triggers on /implement, "implement the plan", "code this up", "execute the plan".

Generate an implementation plan from a locked per-task spec, gated by human approval before any code is written. Use after the spec exists and before implementation. Triggers on /plan, "make a plan", "draft a plan for this spec".

Run anti-overengineering review on the current diff. Invoke after self-QA is green and before opening a PR. Triggers on /review, "review for overengineering", "check the diff for overeng".

Open a per-task spec scaffold from the canonical template, prefilled with reasonable defaults. Use when starting a new slice that needs a spec written. Triggers on /spec, "draft a spec", "spec this slice".

Execute exactly one Linear issue end-to-end with branch safety, repo-discovered gates, self-QA, adversarial review, decision logging, single-source report and PR-body rendering, Ready PR creation, and autonomous post-PR review-comment handling. Use when the user says /ship, ship issue, ship Linear issue work, or asks to complete a specific Linear issue such as ENG-123; reject GitHub issues, plan phases, and vague next-work requests.

Per-feature Neon database branch for each git branch in a Drizzle + Vercel project. Schema changes use `db:push` (no migration files on feature branches); migrations are auto-generated and validated post-merge against a throwaway prod clone, then applied to prod with deploy gated on success. Use when setting up or operating a project where multiple agents/worktrees need isolated DB schemas without conflicting migration files. Triggers on "isolated db branches", "neon branching", "per-branch database", "db isolation", "drizzle migration conflict", "neon worktree", "/isolated-db-branches".

Execute one implementation slice end-to-end from either (1) a PRD plus plan plus phase, where PRD and plan may be files or GitHub issues, (2) a GitHub PRD issue plus optional work issue, or (3) a Linear issue with its project/docs as PRD context. Use when the user says "/work", "do work", "do issue work", "do linear work", asks to implement a planned phase, asks to pick/execute the next GitHub slice from a PRD, or asks to complete a Linear issue. Always includes dependency intake, clarifications, feature branch, implementation, mandatory gates, adversarial review, Playwright self-QA or fallback evidence, local conventional commit, 2-page HTML report, opening the report, pushing the branch, and opening a Ready PR whose body mirrors the report.

Run a multi-round adversarial code review with two independent AI reviewers that cross-examine each other's findings. Iterates until only nitpicks remain (max 3 rounds). Use when you want deep, debate-style review that catches issues a single pass misses. Triggers on "adversarial review", "debate review", "cross-review", "deep review".

Review and resolve unresolved GitHub PR review threads. Use when the user wants to process PR comments, address requested changes, triage reviewer feedback, reply to invalid feedback, push fixes to the PR branch, and resolve review threads safely. Adapts quality gates to the repository instead of assuming a fixed package manager or test suite.

Analyze text readability with Flesch-Kincaid, Gunning Fog, SMOG, and other metrics. Returns objective scores with interpretation and recommendations.

Write a technical retrospective grounded in artifacts the user can verify — commits, PRs, ADRs, tests, logs. Use only when the user has a specific past incident with concrete evidence to cite. Refuses to fabricate stages when evidence is missing. Triggers on "engineering retrospective", "lessons-learned article", "technical postmortem write-up", or "blog post about a bug, incident, or fix".

Log accomplishments, solved problems, learnings, and milestones to Obsidian daily notes via the Obsidian CLI. Also answers questions about the Obsidian CLI. Triggers on "/log", "log accomplishment", "log what I did", "work log", "obsidian cli", "daily note", or when user wants to record something noteworthy they did.

Use when managing stacked branch workflows with DubStack, including create/modify, navigation, sync/restack, submit, PR opening, and recovery.

Use when managing stacked branch workflows with DubStack, including create/modify, navigation, sync/restack, submit, PR opening, and recovery.

Use when the user wants fully autonomous delivery in this repo from a clear task through implementation, verification, review, and PR follow-through.

Use when changing AI-generated branch, commit, or PR metadata for DubStack flow, or when adding new local Evalite coverage for those outputs.

Use when turning staged changes into a DubStack branch, commit, and submitted PR stack with clear naming and user confirmation.

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

Generate copy-ready X or LinkedIn posts for a published Rage AI score. Use when the user asks to share or draft a social post from Rage AI stats.

Show the shared Rage AI leaderboard. Use when the user asks to view Rage AI rankings.

Preview and optionally publish aggregate Rage AI leaderboard stats. Use when the user asks to publish Rage AI stats.

Scan local Claude and Codex transcripts for private Rage AI stats. Use when the user asks to scan, refresh, or set up Rage AI local stats.

Show local Rage AI stats without publishing. Use when the user asks for their local rage/frustration/swear stats.

Plan cycle scope and identify risks using Linear entities

Agent playbook for Linear issue triage and prioritization

Use the Linear CLI for agent-friendly Linear issue workflows

Use when turning staged changes into a DubStack branch, commit, and submitted PR stack with clear naming and user confirmation.

Use when managing stacked branch workflows with DubStack, including create/modify, navigation, sync/restack, submit, PR opening, and recovery.

Use when integrating @wiseiodev/dubs-auth in a Next.js App Router app with Better Auth, Stripe subscriptions, and Drizzle schema wiring, including CLI scaffolding, route setup, env validation, billing portal, webhook sync, and client auth UX.

Bulletproof React architecture patterns for scalable, maintainable applications. Covers feature-based project structure, component patterns, state management boundaries, API layer design, error handling, security, and testing strategies. Use when structuring a React project, designing application architecture, organizing features, or when the user asks about React project structure or scalable patterns.