Skip to content

oliver-kriska/claude-elixir-phoenix / targets/codex/skills/phx-quick

phx-quick

Verified

Implement small Phoenix changes without planning — add validations; Use for single-file edits under 50 lines.

Quick Mode

Skip the planning ceremony. Get working code fast.

Usage

$elixir-phoenix:phx-quick Add pagination to posts
$elixir-phoenix:phx-quick Fix the login redirect bug
$elixir-phoenix:phx-quick Add CSV export to reports

Arguments

$ARGUMENTS = What to implement

How It Differs

Normal ModeQuick Mode
Spawn research agentsNo agents
Create plan documentMental model only
Parallel reviewOptional single review
Multiple iterationsSingle pass

Workflow

  1. Understand - Read the files the change touches
  2. Implement - Write code directly
  3. Verify - Quick compile check
  4. Done - No ceremony

Iron Laws

  1. NEVER skip verification — run mix compile --warnings-as-errors after every change, even in quick mode
  2. DO NOT touch files outside the stated scope — quick mode means minimal blast radius; if a fix requires changes across multiple domains, escalate to $elixir-phoenix:phx-plan
  3. NEVER bypass security checks for speed — auth, input validation, and XSS rules apply regardless of change size

Rules in Quick Mode

Still Enforced (Iron Laws)

  • ✓ No process without runtime reason
  • ✓ No DB in mount
  • ✓ Security basics (no SQL injection, etc.)
  • ✓ Run mix format

Skipped

  • ✗ Parallel agent research
  • ✗ Written plan document
  • ✗ Multiple review passes
  • ✗ Documentation updates

When to Use

Good for:

  • Bug fixes with clear solution
  • Small features (<100 lines)
  • Refactoring with tests
  • Adding fields/columns
  • UI tweaks

Not for:

  • New authentication flows
  • Payment integration
  • Data migrations
  • Architectural changes
  • Anything touching security

Quick Patterns

Add Field

/quick Add phone field to users

→ Migration + schema + changeset + form field

Fix Bug

/quick Fix: posts not showing for admin users

→ Find issue + fix + verify

Add Endpoint

/quick Add GET /api/health endpoint

→ Route + controller + response

Escape Hatch

If quick mode hits complexity:

This needs more planning. Switching to normal mode.
Run $elixir-phoenix:phx-plan [task] for full analysis.

Verification

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.

Example Session

User: $elixir-phoenix: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.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall