agentleFS
Sign inStart free
refpathrefpath/chatgpt-team/.agents/skills/stack-phoenix-liveview/SKILL.md

stack-phoenix-liveview

Skill0 starsChanged 2 months agoMITView on GitHub

Implement and validate Phoenix and LiveView changes with attention to server/client state, navigation, events, reconnect behavior, accessibility, and repository-native tests.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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:

    Keep authorization at the repository's established server-side boundary.

    line 13
  2. Distinctive:

    Keep assigns intentional and avoid retaining large/unbounded state without need.

    line 14
  3. Distinctive:

    Treat LiveView events, params, patches/navigate behavior, async work, uploads, and reconnects according to the project's existing patterns.

    line 15
  4. Distinctive:

    Avoid introducing client-side JavaScript when normal LiveView semantics solve the problem cleanly.

    line 17
  5. Very specific:

    Prefer the repository's Phoenix/LiveView tests for deterministic behavior.

    line 21
  6. Distinctive:

    Do not assume a database, asset tool, or server command.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 and LiveView

Apply this skill only when the repository actually uses Phoenix or LiveView.

Implementation

  • Inspect router, endpoint, LiveView/component boundaries, hooks/assets, and test helpers before editing.
  • Keep authorization at the repository's established server-side boundary; do not rely on hidden UI for access control.
  • Keep assigns intentional and avoid retaining large/unbounded state without need.
  • Treat LiveView events, params, patches/navigate behavior, async work, uploads, and reconnects according to the project's existing patterns.
  • Preserve semantic HTML, labels, focus behavior, keyboard access, and progressive/error states.
  • Avoid introducing client-side JavaScript when normal LiveView semantics solve the problem cleanly; likewise, do not force LiveView for behavior the project already handles client-side.

Validation

Prefer the repository's Phoenix/LiveView tests for deterministic behavior. For user-visible changes also run the ui-validation skill against the real application.

When relevant, validate:

  • initial server-rendered state;
  • event handling and validation errors;
  • live navigation/patches;
  • loading/async states;
  • reconnect/recovery behavior;
  • browser console failures from hooks/assets;
  • responsive rendering.

Do not assume a database, asset tool, or server command; read the repository instructions first.

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.

Check your setup, free