Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Skip the planning ceremony. Get working code fast.
/phx:quick Add pagination to posts
/phx:quick Fix the login redirect bug
/phx:quick Add CSV export to reports
$ARGUMENTS = What to implement
| Normal Mode | Quick Mode |
|---|---|
| Spawn research agents | No agents |
| Create plan document | Mental model only |
| Parallel review | Optional single review |
| Multiple iterations | Single pass |
mix compile --warnings-as-errors after every change, even in quick mode/phx:planmix formatGood for:
Not for:
/quick Add phone field to users
→ Migration + schema + changeset + form field
/quick Fix: posts not showing for admin users
→ Find issue + fix + verify
/quick Add GET /api/health endpoint
→ Route + controller + response
If quick mode hits complexity:
This needs more planning. Switching to normal mode.
Run /phx:plan [task] for full analysis.
After quick implementation:
Run mix compile --warnings-as-errors. If you touched Ecto schemas or migrations,
run mix ecto.migrate. Then run mix test test/path_test.exs for affected tests.
User: /phx:quick Add archived_at timestamp to posts
Claude:
1. Reading lib/my_app/blog/post.ex...
2. Creating migration...
# priv/repo/migrations/xxx_add_archived_at_to_posts.exs
def change do
alter table(:posts) do
add :archived_at, :utc_datetime
end
end
3. Updating schema...
# lib/my_app/blog/post.ex
field :archived_at, :utc_datetime
4. Adding to changeset...
def changeset(post, attrs) do
post
|> cast(attrs, [:title, :body, :archived_at])
...
end
5. Verifying...
$ mix compile --warnings-as-errors ✓
$ mix ecto.migrate ✓
$ mix test test/my_app/accounts_test.exs ✓
Done.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Analyze a legacy app in any language before rewriting it in Elixir: inventory, features as goals, why each mechanism exists, runtime topology, external contracts. Use to start or refresh a rewrite.
The English summary is being prepared. Showing the original description.
Design the idiomatic Elixir architecture for a rewrite: set the compatibility bar (ADR-000), consult phx specialists on open questions, then build contexts, ledger and ADRs. Use after /rewrite:analyze.
The English summary is being prepared. Showing the original description.
Ash Framework — resources, actions, policies, aggregates; Use when generating resources via mix ash.codegen, editing…
The English summary is being prepared. Showing the original description.
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
The English summary is being prepared. Showing the original description.
Compatibility alias for the Elixir/Phoenix plugin's LiveView assigns audit. Invoke explicitly with /lv:assigns.
The English summary is being prepared. Showing the original description.
Inspect LiveView socket assigns for memory bloat — missing temporary_assigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporary_assigns.
The English summary is being prepared. Showing the original description.