File language: Not specified
25 Ways to Work Better with AI
Install 25 slash commands in your coding agent with one line.
에반Free
Skill overview
Does AI give you different results every time?
One slash command.
25 commands Matt Pocock uses daily in his own projects.
The same workflow in Claude Code, Cursor or Codex.
Does this happen every week?
AI writes code quickly.
But ask it to do the same thing twice and the output looks different.
-
01It's 2 AM. You've asked for the same thing five times.
One version has oversized functions, another makes up variable names, another omits tests. Same prompt, different result.
-
02Friday afternoon. You reopen last week's code.
Two functions do the same job. Change one router line and two other screens break. Your codebase got this tangled in a week.
-
03You started without a PRD and only discovered the mismatch after building it.
“It works, but is this what we wanted?” The conversation starts over. Another thirty minutes gone.
The model isn't the missing piece. The way you ask.
Standardize how you ask AI
with one slash command.
npx skills@latest add mattpocock/skills
Install once. Enable only the commands you need.
Sound engineering habits,
one slash away.
Ask questions for thirty minutes before starting.
/grill-with-docs
Invoke it and the AI asks first.
“Who uses this?” “What happens to existing data?” “How should failure look?” It won't write code until these questions are answered. That time shapes half the result.
Tests first. Code second.
/tdd
runs a red → green → refactor loop.
Write a failing test, then the minimum code to pass it. One slice at a time, with a consistent structure.
Clean up the codebase every few days.
/improve-codebase-architecture
Run
every few days to find duplicated functions and structures where one change breaks another part. Even a few days can make a noticeable difference.
25 slash commands.
MIT-licensed open source. The installer lets you choose only what you need.
/setup-matt-pocock-skills
Be sure to include
engineering/ — 10 for coding /grill-with-docs Ask clarifying questions + automatically build a domain glossary /tdd Red-green-refactor loop /diagnose Reproduce, narrow down, form a hypothesis, instrument, and fix /triage Triage issues with a state machine /to-prd Turn a conversation into a concise PRD and file it as an issue /to-issues Break a PRD into small GitHub issues /zoom-out Ask for an explanation of the overall flow first /prototype A throwaway branch that leaves the main code untouched /improve-codebase-… Clean up the structure every few days /setup-matt-pocock-skills One-time setup productivity/ — 4 that also help with non-coding work /grill-me Ask questions for 30 minutes before starting the work /handoff Hand off the current conversation to another agent /caveman Cut tokens by 75% when AI responses get too long /write-a-skill Create a new skill with the same structure misc/ — 4 for occasional needs /git-guardrails-… Block dangerous Git commands in advance /setup-pre-commit Set up Husky pre-commit hooks automatically /scaffold-exercises Generate a practice-problem folder automatically /migrate-to-shoehorn Migrate tests to `as` type assertions + personal/, in-progress/, deprecated/ — 7 more for personal use
From installation to your first task.
The first five minutes. For another project, repeat only step one.
Paste npx skills@latest add mattpocock/skills into your terminal to launch the wizard. Select the commands and agent: Claude Code, Cursor or Codex.
/setup-matt-pocock-skills Run it once. It asks where to track issues, how to name triage labels and where to save new documents. Those settings persist for the repository.
Don't jump straight into code for a new feature. /grill-with-docs Start here. The AI begins by asking questions.
When building, use /tdd. For a stubborn bug, use /diagnose. If the overall structure is too complex, use /zoom-out.
/improve-codebase-architecture Run it every few days. Even a short interval can noticeably improve the codebase.
Frequently asked questions.
npx skills@latest add mattpocock/skills Paste one line to launch the installer and select the commands you want. To uninstall, delete the relevant files from the installation folder, usually .claude/commands/). It doesn't change system settings.
/grill-with-docs, /tdd, /diagnose, /to-prd four commands. /setup-matt-pocock-skills Be sure to include
aihero.dev a newsletter reaching nearly 60,000 developers weekly. He's also known for Total TypeScript. This collection contains tools he uses in his daily projects, with real workflows rather than marketing demos.
/grill-me, /handoff, /caveman can be used more broadly. It makes no promises of passing assessments, revenue or guaranteed results.
“The AI went off track again.”
Make the output more consistent.
npx skills@latest add mattpocock/skills
Q&A 0
No questions yet.
From purchase to your first result
Check what you need in the guide, then start a first task with your own materials.
Open the guide for your skill
Open the guide from the payment confirmation or your library, and check the accounts and materials you need.
Get the skill and follow its setup guide
Open the skill source link and follow the accompanying setup instructions.
Try a small task with your own materials
Start with one topic or item. Describe the result you want and check whether it works for your needs.
Ask in the skill room if you get stuck
Share the task, the step where you got stuck, and any error message in the buyer community. You can return to the guide from your library.
Example first request
“I’d like to try a first task with 25 Ways to Work Better with AI. Tell me what materials and setup I need, then help me start with a small task.”
Purchase information
Before you buy
- Materials
Skill source link
Open purchased materials from your library.
- Requirements
You need an AI agent and an account to run the skill.
Check the product description for supported agents and required services.
- Additional costs
External AI services may have separate subscription or usage fees.
Ask the seller about required plans and expected usage before buying.
Warranty and support
Review the tested environment and support period.
- Tested environment
- Tested with Claude Code and Codex. Operation with other agents or CLIs is not guaranteed.
- Free patch period
- One year from upload (2026-05-13), through 2027-05-13. If model or CLI changes break the skill during this period, we will fix it at no charge.
- Access period
- Available to download immediately after payment, and available to download and view again in your library for 11 months from the payment date. Download and viewing access ends after this period.
- If we cannot fix it
- If we cannot fix it within the free patch period, we refund an amount proportional to the remaining period.
- Last verified
- 2026-10-29(skill's last updated date)