ash_feedback

Create or manage Architecture Decision Records (ADRs) in docs/decisions/

Use this skill working with Ash Framework or any of its extensions. Always consult this when making any domain changes, features or fixes.

Record a development session summary in the project devlog

Run E2E browser tests via Tidewave browser_eval against the running Phoenix dev server

Inspect LiveView state (assigns, components) via Phoenix.LiveView.Debug in project_eval

Morning briefing — where we left off, what to work on today. Fast, compact report from canonical sources.

Manage plan lifecycle — list plans, mark completed/abandoned, move between directories

Review changed code for Elixir/Ash/Phoenix best practices, anti-patterns, and idiomatic style — then fix issues found

Review an implementation plan against Elixir/Phoenix/Ash best practices, anti-patterns, and GsNet project rules

Update project documentation after completing work

Systematically close a coding session — commit check, memory update, plan sync, docs, handoff summary