jg-brainstorm
Think an idea through before planning, with options, tradeoffs, and a recommended direction.
Agent Skills for professional development
Brainstorm, plan, build, review, and ship changes with the skills professional software developers use on real projects. Workflow skills run only when you call them. Implicit skills load on their own when a task touches their stack.
npx skills add jesusgraterol/jg-skills --skill "*" -y
/jg-brainstorm Should we rate-limit the public API per account?/jg-plan /jg-execute auto The skills
Explicit skills state exactly what they may change. Implicit skills add the stack-specific standards your agent needs on top of your repository's coding instructions.
Agree on what to build before any code changes.
Think an idea through before planning, with options, tradeoffs, and a recommended direction.
Ask about the decisions that are yours, then write an implementation-ready plan for approval.
Challenge a plan before approval and surface material risks, gaps, and decisions.
Split a plan into ordered, reviewable milestones when it has real implementation boundaries.
Turn the approved plan into verified code.
Build an agreed task or plan, supervised by default, or with auto to review and push each milestone.
Find the cause of a bug before fixing it, then fix it with a regression test that fails first.
Stop at the nearest safe point, report where things stand, and wait until you say continue.
Turn a task into a few checked shell commands, explain each one, and run the one you pick.
Check the finished change, then publish it.
Weigh outside input and earlier sessions.
Assess feedback independently and recommend what to adopt, reject, or adjust.
Find a named Claude Code or Codex session and answer questions from its latest decisions.
Loaded by your agent when a task touches their stack.
Accessibility, responsive layout, themes, forms, motion, and design-system reuse for Tailwind CSS.
Components, render performance, React 19 APIs, routing, hydration, client data, and tests for React.
Manifests, install prompts, service worker updates, caching, and push for progressive web apps.
Metadata, canonicals, sitemaps, robots, structured data, and social previews for public sites.
Icon drawing, outlined logo text, file shape, brand colors, exports, and optimization for SVG.
Templates, fonts, exact sizes, formats, and repeatable renders for images made with Playwright.
Modules, schema validation, configuration, logging, lifecycle, and tests for NestJS.
Naming, constraints, queries, transactions, pools, timeouts, and migrations for PostgreSQL.
Key names, expiry, scanning, round trips, data structures, and locks for Redis.
Cross-platform paths, safe filesystem access, processes, and CLIs for Node.js scripts.
Package selection, local API documentation, and consumer integration for JG Packages.
Exports, dependency ranges, tarball tests, versioning, and trusted publishing for npm packages.
Task graphs, cache inputs, filters, and workspace dependencies for Turborepo and pnpm.
Shell choice, script structure, quoting, safety, and verification for bash and sh on Linux.
Compose services, healthchecks, secrets, ports, image tags, and Dockerfile structure for Docker.
A single check workflow, permissions, timeouts, caching, and action pinning for GitHub Actions.
Strictness, metadata, error handling, formats, and composition for Zod 4 schemas.
Deterministic waits, timeouts, retries, and repeat runs for Vitest and Playwright.
How it works
Agree on what to build before any code changes.
/jg-brainstormAgree on a direction.
/jg-planSave it as a plan you approve.
/jg-challenge-planOptionalFind gaps before you approve.
/jg-breakdownOptionalSplit a large plan into milestones.
Turn the approved plan into verified code.
/jg-execute/jg-execute autoBuild and check one milestone, then stop.
Build each remaining milestone in turn.
For each milestone
/jg-debugOptionalFind a bug's cause, then fix it test-first.
/jg-pauseOptionalStop at a safe point, then pick up later.
/jg-commandOptionalPick a checked command and run it.
Check the finished change, then publish it.
/jg-reviewCheck the change before it ships.
/jg-pushCommit and push the task's files.
You run these when you are ready.
Install
Run the commands from your repository's root. The skills live in the project, so you can commit them and share the same workflow with your team.
Needs Node.js. Explicit-only and implicit loading are verified with Claude Code and Codex.
Update refreshes only the skills you already have. To add skills released since you installed, run the install command again.
npx skills add jesusgraterol/jg-skills --skill "*" -y
npx skills update -p jg-brainstorm jg-plan jg-challenge-plan jg-breakdown jg-execute jg-debug jg-pause jg-command jg-review jg-push jg-feedback jg-session jg-frontend jg-react jg-pwa jg-seo jg-svg jg-graphics jg-nestjs jg-postgres jg-redis jg-node jg-packages jg-npm-package jg-monorepo jg-bash jg-docker jg-ci jg-zod jg-testing
npx skills remove jg-brainstorm jg-plan jg-challenge-plan jg-breakdown jg-execute jg-debug jg-pause jg-command jg-review jg-push jg-feedback jg-session jg-frontend jg-react jg-pwa jg-seo jg-svg jg-graphics jg-nestjs jg-postgres jg-redis jg-node jg-packages jg-npm-package jg-monorepo jg-bash jg-docker jg-ci jg-zod jg-testing
Agentic Coding
The skills run the workflow. Your repository's AGENTS.md sets the standards each one applies, and Agentic Coding has a starting point either way.
AGENTS.mdSets the standardsjg-skillsRuns the workflowA neutral AGENTS.md for new or existing repositories, ready to copy or download.
agenticcoding.jesusgraterol.dev
A prompt that improves your AGENTS.md without losing what it already knows about your project.
agenticcoding.jesusgraterol.dev
jg-packages
Use reusable helpers alongside your project's own code. The jg-packages skill helps your agent choose a suitable package and verify its installed API.
Set your project's standards.
Guide the work.
Provide reusable code.
Credits
A few ideas in these skills are adapted from other open-source collections and rewritten in our own words.
by Jesse Vincent
Fixing only blocking findings, checking acceptance criteria first, and a three-attempt stop rule.
by Addy Osmani
Labeling review findings by severity, and listing what was noticed but deliberately left alone.
by Lauren Tan
Proving a change works on the real path, and never weakening a check just to get it through.
by Matt Pocock
Milestones that fit one context window, batched questions, and the debugging loop in jg-debug.