Update template files: rename postgresql to postgres

skills/postgres-best-practices/rules/_contributing.md

@@ -1,6 +1,6 @@
-# Writing Guidelines for PostgreSQL Rules
+# Writing Guidelines for Postgres Rules
 
-This document provides guidelines for creating effective PostgreSQL best
+This document provides guidelines for creating effective Postgres best
 practice rules that work well with AI agents and LLMs.
 
 ## Key Principles
@@ -150,7 +150,7 @@ const posts = await db.query("SELECT * FROM posts WHERE user_id = ANY($1)", [
 ````
 
 **Balance:** ~10% of content should be Supabase-specific. Core rules should work
-on any PostgreSQL.
+on any Postgres.
 
 ---
 
@@ -158,16 +158,16 @@ on any PostgreSQL.
 
 **Primary Sources:**
 
-- Official PostgreSQL documentation
+- Official Postgres documentation
 - Supabase documentation
-- PostgreSQL wiki
+- Postgres wiki
 - Established blogs (2ndQuadrant, Crunchy Data)
 
 **Format:**
 
 ```markdown
 Reference:
-[PostgreSQL Indexes](https://www.postgresql.org/docs/current/indexes.html)
+[Postgres Indexes](https://www.postgresql.org/docs/current/indexes.html)
 ```
 
 ---

skills/postgres-best-practices/rules/_sections.md

@@ -1,14 +1,14 @@
 # Section Definitions
 
-This file defines the rule categories for PostgreSQL best practices. Rules are automatically assigned to sections based on their filename prefix.
+This file defines the rule categories for Postgres best practices. Rules are automatically assigned to sections based on their filename prefix.
 
-Take the examples below as pure demonstrative. Replace each section with the actual rule categories for PostgreSQL best practices.
+Take the examples below as pure demonstrative. Replace each section with the actual rule categories for Postgres best practices.
 
 ---
 
 ## 1. Query Performance (query)
 **Impact:** CRITICAL
-**Description:** Slow queries, missing indexes, inefficient query plans. The most common source of PostgreSQL performance issues.
+**Description:** Slow queries, missing indexes, inefficient query plans. The most common source of Postgres performance issues.
 
 ## 2. Connection Management (conn)
 **Impact:** CRITICAL
@@ -36,4 +36,4 @@ Take the examples below as pure demonstrative. Replace each section with the act
 
 ## 8. Advanced Features (advanced)
 **Impact:** LOW
-**Description:** Full-text search, JSONB optimization, PostGIS, extensions, and advanced PostgreSQL features.
+**Description:** Full-text search, JSONB optimization, PostGIS, extensions, and advanced Postgres features.

skills/postgres-best-practices/rules/_template.md

@@ -31,4 +31,4 @@ SELECT * FROM users WHERE email = 'user@example.com' AND deleted_at IS NULL;
 
 [Optional: Additional context, edge cases, or trade-offs]
 
-Reference: [PostgreSQL Docs](https://www.postgresql.org/docs/current/)
+Reference: [Postgres Docs](https://www.postgresql.org/docs/current/)