Usage rules appear not to offer guidance for using any backpex features and doesn't follow usage_rules file-naming standard (usage-rules.md)

[em-jones]

Describe the bug
As I understand it, usage-rules.md are meant to describe how the dependency itself is used (backpex, in this case) - e.g. ash's usage rules

As it stands, the usage rules are describing how Backpex's dependencies (phoenix, elixir, etc.) are used while not offering guidance WRT how backpex aught be used by agents to produce admin dashboards.

To Reproduce
Steps to reproduce the behavior:

1. Go to usage-rules.md
2. CTRL+f search for "backpex" and find no mentions of any patterns/practices relevant specifically to using backpex

Expected behavior

• usage_rules.md is renamed to usage-rules.md
• Follows usage_rules package authors guidance to provide backpex specific patterns

[Flo0807]

Hey!

Backpex does not yet provide a file that describes how Backpex itself is used. The usage_rules.md file you mentioned is meant to help us develop Backpex. The same applies to the AGENTS.md and CLAUDE.md files.

We are mixing different use cases here:

• LLM context files for developing Backpex (used by maintainers) - already present (usage_rules.md, AGENTS.md, and CLAUDE.md).
• A file that instructs LLMs on how to build Backpex applications for developers who install Backpex (not available yet).

I understand that this is confusing, and we will work on improving it. One solution is to rename the usage_rules.md file into something more internal.

Providing LLM context for developers who install and work with Backpex as an admin panel is a great idea. We are going to work on this, too.