gr8monk3ys
- 20 skills
- 0 followers
- 6 hours ago last updated
- ▌ Tdd · gr8monk3ys bundleTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
- ▌ To Spec · gr8monk3ysTurn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
- ▌ Grilling · gr8monk3ysGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
- ▌
- ▌ Code Review · gr8monk3ysReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
- ▌ Wizard · gr8monk3ys bundleGenerate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
- ▌ Research · gr8monk3ysInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
- ▌ Diagnosing Bugs · gr8monk3ys bundleDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
- ▌ Handoff · gr8monk3ysCompact the current conversation into a handoff document for another agent to pick up.
- ▌ Prototype · gr8monk3ys bundleBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
- ▌
- ▌ Ask Lorenzo · gr8monk3ysAsk which command or skill in this plugin fits your situation. A router over everything user-reachable — scaffolding, quality gates, delivery, and the ported workflow skills.
- ▌ API Development · gr8monk3ysWHEN to auto-invoke: Creating API routes, building endpoints, adding route.ts files, implementing REST/GraphQL APIs, adding authentication to APIs, rate limiting, API validation with Zod, handling HTTP methods (GET/POST/PUT/DELETE). WHEN NOT to invoke: Pure frontend work, styling, React components without API calls, documentation-only tasks, database migrations without API changes.
- ▌ Domain Modeling · gr8monk3ys bundleBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
- ▌ To Questionnaire · gr8monk3ysTurn a decision you can't fully answer into a questionnaire for someone else to fill in.
- ▌ Database Operations · gr8monk3ysWHEN to auto-invoke: Database schema design, creating migrations, writing SQL queries, query optimization, Supabase operations, Prisma/Drizzle schema changes, PostgreSQL tasks, RLS policies, indexes. WHEN NOT to invoke: Pure frontend work, API logic without database, styling, React components, deployment tasks.
- ▌ Writing For Agents · gr8monk3ys bundleWriting documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
- ▌ Frontend Development · gr8monk3ysWHEN to auto-invoke: Creating UI components, building React/Vue/Svelte components, Next.js pages, styling with Tailwind/CSS, state management setup, form handling, accessibility improvements, client-side interactivity. WHEN NOT to invoke: API-only work, database operations, backend logic, DevOps/deployment, pure testing without UI.
- ▌ Background Automation · gr8monk3ysWHEN to auto-invoke: Setting up recurring or self-paced tasks, watching CI or deploys, babysitting pull requests, configuring monitors, running long jobs in the background, scheduling check-ins, polling for a condition, or wiring Claude Code on the web/cloud sessions and PR activity subscriptions. WHEN NOT to invoke: One-off synchronous edits, writing application feature code, pure UI/styling work, or anything that finishes in a single turn with no waiting.
- ▌ Resolving Merge Conflicts · gr8monk3ysUse when you need to resolve an in-progress git merge/rebase conflict.