Flow with Matt Pocock's skills
On this page
This recipe is for you if you use Matt Pocock's skills and want to use Flow in the same app.
How they differ
Section titled "How they differ"Matt's skills are about how you work. You talk through a change with your agent, turn it into a spec and tickets, and build each ticket. They work with any framework.
Flow is about AdonisJS. It gives your agent accurate docs for the framework and its packages, and design skills that settle each choice the AdonisJS way. The team behind AdonisJS maintains both.
The skills you will use
Section titled "The skills you will use"You will use Matt's skills for the steps of your work:
/grill-with-docsasks you questions about a change until you and your agent agree on it./to-specturns the conversation into a spec./to-ticketsbreaks the spec into tickets./implementbuilds one ticket and then reviews it./implement-specbuilds all the tickets of a spec.
Point Matt's skills at Flow
Section titled "Point Matt's skills at Flow"Paste this prompt into your coding agent, in the root of your project. It adds one ADR, and asks before it commits anything.
Most of Matt's skills read the ADRs of your project when they design and build a change, for example /grill-with-docs, /to-spec, /to-tickets and /implement. The ADR tells them to read the Flow docs and use the Flow skills first. In /grill-with-docs, your agent then gives you the answer of a Flow skill and does not ask you the question.
Reviewing your work
Section titled "Reviewing your work"/implement ends with Matt's code-review skill. It checks that the implementation sticks to the spec.
The Flow review is separate. Use it to review a diff or a pull request after you build. Run npx @adonisplus/flow review on your branch, or let it review each pull request on GitHub. See Local reviews and GitHub setup.