agentleFS
MindrallyMindrally/skills/phoenix/SKILL.md

phoenix

Skill275 starsChanged 35 days agoApache-2.0View on GitHub

Phoenix framework development guidelines covering LiveView, Ecto, real-time features, and best practices for building scalable web applications with Elixir.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write concise, idiomatic Elixir code with accurate examples

    line 15
  2. Distinctive:

    Follow Phoenix conventions and established best practices

    line 16
  3. Very specific:

    Use meaningful variable and function names (e.g., user_signed_in?, calculate_total)

    line 19
  4. Distinctive:

    Use snake_case for files, functions, and variables

    line 24
  5. Distinctive:

    Use PascalCase for module names

    line 25
  6. Distinctive:

    Follow the Elixir Style Guide

    line 36
  7. Distinctive:

    Use single quotes for charlists, double quotes for strings

    line 38
  8. Distinctive:

    Use LiveView for real-time, dynamic interactions

    line 49
  9. Distinctive:

    Follow RESTful routing conventions

    line 62
  10. Distinctive:

    Use GenServers for stateful processes and background work

    line 64
  11. Distinctive:

    Write comprehensive ExUnit tests

    line 69
  12. Distinctive:

    Use ExMachina for test data generation

    line 71

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Phoenix Framework Development

You are an expert in Elixir, Phoenix, PostgreSQL, LiveView, and Tailwind CSS.

Code Style and Structure

  • Write concise, idiomatic Elixir code with accurate examples
  • Follow Phoenix conventions and established best practices
  • Leverage functional programming patterns and immutability principles
  • Favor higher-order functions and recursion over imperative loops
  • Use meaningful variable and function names (e.g., user_signed_in?, calculate_total)
  • Organize files per Phoenix conventions: controllers, contexts, views, schemas

Naming Standards

  • Use snake_case for files, functions, and variables
  • Use PascalCase for module names
  • Adhere to Phoenix naming conventions for contexts, schemas, and controllers

Elixir and Phoenix Implementation

  • Utilize pattern matching and guards effectively
  • Leverage Phoenix's built-in functions and macros
  • Apply Ecto proficiently for database operations

Syntax and Formatting

  • Follow the Elixir Style Guide
  • Chain functions with the pipe operator |>
  • Use single quotes for charlists, double quotes for strings

Error Handling

  • Embrace the "let it crash" philosophy with supervisor trees
  • Log errors properly and provide user-friendly messaging
  • Validate data through Ecto changesets
  • Display appropriate flash messages for controller errors

UI and Styling

  • Use LiveView for real-time, dynamic interactions
  • Implement responsive design with Tailwind CSS
  • Employ view helpers to maintain DRY templates

Performance Optimization

  • Index databases effectively
  • Cache strategically (ETS, Redis)
  • Prevent N+1 queries using preload, joins, or select
  • Optimize database queries for efficient data retrieval

Architecture Patterns

  • Follow RESTful routing conventions
  • Organize functionality within contexts
  • Use GenServers for stateful processes and background work
  • Deploy Tasks for concurrent, isolated operations

Testing

  • Write comprehensive ExUnit tests
  • Practice TDD (Test-Driven Development)
  • Use ExMachina for test data generation

Security

  • Implement authentication and authorization (Guardian, Pow)
  • Validate strong parameters in controllers
  • Defend against XSS, CSRF, and SQL injection vulnerabilities

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.