---
summary: The architectural and program design skills Flow ships, and what each one does.
---

# Skills

Flow ships skills for architectural and program design. They give your coding agent one way to design each part of an AdonisJS app, so it writes consistent code instead of inventing a pattern for each task. Your codebase stays easy to reason about, and simpler to review.

Flow ships with the following 11 skills today, and adds more as apps need them.

## flow-schema-design

Your agent uses this skill when it writes or changes a migration or a model. It decides how to handle soft deletes, constraints, enums, money, polymorphic relations and JSON columns, and how to change a table that already has rows.

## flow-cruddy-controllers

Your agent uses this skill when it adds or changes a route or a controller. It decides which controller and which method each action goes to: a resource controller with the RESTful methods, or a single action controller.

This skill has a separate version for Inertia + React, Inertia + Vue, JSON APIs and Edge templates. Flow installs the version that matches the stack you choose when you run `npx @adonisplus/flow install`.

## flow-response-design

Your agent uses this skill when it writes or changes a controller action that renders a page or returns JSON. It decides the page props or the API payload, the transformer that builds them, and the relations to preload.

Like `flow-cruddy-controllers`, this skill has a separate version for each stack.

## flow-validation-layers

Your agent uses this skill when it writes or changes a validator, or any check on incoming data. It decides where each check goes: the validator, a guard that needs a loaded record, or a database constraint.

## flow-access-control

Your agent uses this skill when it writes code that reads or writes records that belong to users, tenants or organisations. It decides the scope of each query, the authorization check on each record, and the limit on list endpoints and bulk writes.

## flow-code-placement

Your agent uses this skill when it adds a helper, a service, a utils file, or code that more than one place uses. It decides where the code goes: the class that needs it, a model method, a service, or a pattern object.

## flow-pattern-object-design

Your agent uses this skill when it writes a class that holds one value, a class with only static methods, or functions that work on the same value. It turns them into one class that holds the value and its operations.

## flow-design-tests

Your agent uses this skill when it writes or changes a test. It decides which tests to write for an HTTP request, a console command, a queued job or an event listener, what each test checks, and what it fakes.

## flow-apply

Applies a feature pack to your app. It copies the pack's code into your app, fits it around your existing code, and runs the pack's tests. Your agent never starts this skill on its own. You start it with the name of a pack, for example `/flow-apply passkeys`. See [Feature packs](/docs/feature-packs).

## flow-code-review

Reviews a pull request, a branch or a folder with your app's review lenses. Your agent uses it when you ask for a review, and the CI job uses it on every pull request. See [Lenses](/docs/flow/reviews/lenses).

## flow-code-re-review

Reviews a pull request again after new commits. It checks the earlier review comments, then reviews only the new changes. Only the CI job uses it.
