Extract best practices

Author: mylanconnolly

usage-rules.md

@@ -10,28 +10,4 @@ SPDX-License-Identifier: MIT
 
 AshPostgres is the PostgreSQL data layer for Ash Framework. It's the most fully-featured Ash data layer and should be your default choice unless you have specific requirements for another data layer. Any PostgreSQL version higher than 13 is fully supported.
 
-## Best Practices
-
-1. **Organize migrations**: Run `mix ash.codegen` after each meaningful set of resource changes with a descriptive name:
-   ```bash
-   mix ash.codegen --name add_user_roles
-   mix ash.codegen --name implement_post_tagging
-   ```
-
-2. **Use check constraints for domain invariants**: Enforce data integrity at the database level:
-   ```elixir
-   check_constraints do
-     check_constraint :valid_status, check: "status IN ('pending', 'active', 'completed')"
-     check_constraint :positive_balance, check: "balance >= 0"
-   end
-   ```
-
-3. **Use custom statements for schema-only changes**: If you need to add database objects not directly tied to resources:
-   ```elixir
-   custom_statements do
-     statement "CREATE EXTENSION IF NOT EXISTS \"pgcrypto\""
-     statement "CREATE INDEX users_search_idx ON users USING gin(search_vector)"
-   end
-   ```
-
 Remember that using AshPostgres provides a full-featured PostgreSQL data layer for your Ash application, giving you both the structure and declarative approach of Ash along with the power and flexibility of PostgreSQL.

usage-rules/best_practices.md

@@ -0,0 +1,29 @@
+<!--
+SPDX-FileCopyrightText: 2020 Zach Daniel
+
+SPDX-License-Identifier: MIT
+-->
+
+# Best Practices
+
+1. **Organize migrations**: Run `mix ash.codegen` after each meaningful set of resource changes with a descriptive name:
+   ```bash
+   mix ash.codegen --name add_user_roles
+   mix ash.codegen --name implement_post_tagging
+   ```
+
+2. **Use check constraints for domain invariants**: Enforce data integrity at the database level:
+   ```elixir
+   check_constraints do
+     check_constraint :valid_status, check: "status IN ('pending', 'active', 'completed')"
+     check_constraint :positive_balance, check: "balance >= 0"
+   end
+   ```
+
+3. **Use custom statements for schema-only changes**: If you need to add database objects not directly tied to resources:
+   ```elixir
+   custom_statements do
+     statement "CREATE EXTENSION IF NOT EXISTS \"pgcrypto\""
+     statement "CREATE INDEX users_search_idx ON users USING gin(search_vector)"
+   end
+   ```