Skip to main content
prompt GP ChatGPT

Phoenix App taste — ChatGPT, Claude.ai, Claude Code prompt

Phoenix App taste — a prompt for ChatGPT, Claude.ai, and Claude Code that enforces engineering standards for Elixir and Phoenix applications. It defines architectural patterns, database operations, and testing strategies.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Phoenix App taste does

This prompt provides a set of engineering principles for building Elixir and Phoenix applications. It enforces grouping business logic into contexts, using LiveView for interactive pages, and validating input with Ecto changesets.

The guidelines cover background job management with Oban, secret handling via config/runtime.exs, and testing strategies using DataCase. For Claude Code users, the prompt is referenced via the .claude/commands/prompts.csv.md file.

What it helps with

  • Maintain architectural boundaries between contexts
  • Prevent N+1 database queries
  • Configure background jobs using Oban
  • Validate input data with Ecto

Example prompts for the agent

  • Apply Phoenix App taste engineering principles to this project
  • Review the module architecture against Phoenix App taste guidelines

How to install Phoenix App taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Phoenix App taste

What does Phoenix App taste do?

It is a prompt containing best practices for Elixir and Phoenix development to maintain code and architectural quality.

How to install Phoenix App taste in Claude Code?

Add the prompt reference to your .claude/commands/prompts.csv.md file.

What technologies does this prompt cover?

It covers Phoenix, Ecto, Oban, LiveView, Telemetry, and Docker releases.

Source text

prompts.csv · CC0-1.0
# Phoenix App taste of a pragmatic Elixir engineer
- Start new projects on the latest stable Elixir and Phoenix releases, and pin Erlang/OTP and Elixir versions in .tool-versions. Confidence: 0.85
- Group business logic into Phoenix contexts with small public APIs, and never call Repo directly from controllers or LiveViews. Confidence: 0.90
- Keep contexts from reaching into each other's schemas, and talk across boundaries through public context functions. Confidence: 0.80
- Use LiveView for interactive pages by default and add JavaScript hooks only for things the browser must do itself. Confidence: 0.80
- Build UI from function components with declared attrs and slots instead of large shared templates. Confidence: 0.85
- Validate all input with Ecto changesets and keep separate changesets for different actions like registration and profile updates. Confidence: 0.90
- Lean on database constraints with unique_constraint and foreign_key_constraint instead of check-then-insert code. Confidence: 0.95
- Preload associations explicitly in context functions, and never let a template trigger an N+1 query. Confidence: 0.85
- Use Ecto.Multi or Repo.transaction for multi-step writes so partial failures roll back cleanly. Confidence: 0.85
- Write reversible migrations, and split long-running data backfills into separate tasks rather than schema migrations. Confidence: 0.85
- Read runtime settings and secrets in config/runtime.exs from environment variables, never in compile-time config. Confidence: 0.95
- Run background work with Oban backed by Postgres, with unique jobs and retries, instead of bare Task.start calls. Confidence: 0.85
- Put long-lived processes under a supervisor with a clear restart strategy and let them crash instead of rescuing every error. Confidence: 0.90
- Avoid GenServers as a place to hold data the database already owns; use them for real concurrency or coordination. Confidence: 0.80
- Return tagged tuples like {:ok, value} and {:error, reason} from context functions and handle them with with blocks. Confidence: 0.90
- Use PubSub for live updates between LiveViews and keep the broadcast topic names defined in one module. Confidence: 0.75
- Generate auth with phx.gen.auth and extend it, rather than building login and session handling from scratch. Confidence: 0.80
- Format code with mix format and run Credo and Dialyzer in CI so style and type issues fail the build. Confidence: 0.80
- Test contexts with DataCase and the SQL sandbox, and test LiveViews with Phoenix.LiveViewTest instead of a browser. Confidence: 0.85
- Emit metrics through Telemetry and watch them in LiveDashboard and an external metrics backend in production. Confidence: 0.75
- Ship releases built with mix release inside a small Docker image, and run migrations from a release command. Confidence: 0.80
- Cluster nodes with dns_cluster or libcluster only when the app really needs distributed PubSub or presence. Confidence: 0.70

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Backend and APIs →

From the same set218

The whole set →
WebAssembly Module taste WebAssembly Module taste — a system prompt for ChatGPT, Claude.ai, and Claude Code that establishes architectural standards for WebAssembly development. It guides developers on performance and safety best practices. GP ChatGPT ★ 178,201repo stars Incident Response taste The Incident Response taste prompt for ChatGPT sets out how a calm on-call engineer can handle incidents. It calls for early declaration and coordinated response before the root cause is known. GP ChatGPT ★ 178,201repo stars Nix Dev Environment taste Nix Dev Environment taste — a prompt for ChatGPT configures reproducible Nix development environments with locked dependencies and container builds. GP ChatGPT ★ 178,201repo stars Astro Content Site taste The Astro Content Site taste ChatGPT prompt sets out development rules for content sites built with Astro. It covers rendering, images, SEO, and CI checks. GP ChatGPT ★ 178,201repo stars gRPC Service taste The gRPC Service taste prompt for ChatGPT sets design guidelines for gRPC services. It covers .proto schemas, RPC methods, errors, and calls between services. GP ChatGPT ★ 178,201repo stars Spring Boot Service taste ChatGPT prompt Spring Boot Service taste defines architecture standards for Java backend engineering. GP ChatGPT ★ 178,201repo stars Full-Text Search taste Full-Text Search taste — a prompt for ChatGPT that sets out principles for building full-text search. It covers indexing, ranking, access control, and result delivery. GP ChatGPT ★ 178,201repo stars .NET Web API taste .NET Web API taste — a prompt for ChatGPT defines .NET Web API standards for a pragmatic C# engineer. Runs during backend design and code generation. GP ChatGPT ★ 178,201repo stars

Project sponsors

Companies that keep this analytics open