[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FCTPVNT1SNWEWSJ2KN0SC0":3,"skill-same:01M7FCTPVNT1SNWEWSJ2KN0SC0":193},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7FCTPVNT1SNWEWSJ2KN0SC0","supabase-postgres-best-practices",null,"Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector\u002Fsemantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.","ayusht26\u002Fgym_logger","ayusht26","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F215128900?v=4","01M7FCSVM931J6N4M8T0QQRKZJ","Ayush Tiwari","01M7FCSVMY80CJP65JPF1R2YGC",0,"MIT","https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: supabase-postgres-best-practices\ndescription: \"Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector\u002Fsemantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.\"\nlicense: MIT\nmetadata:\n  author: supabase\n  version: \"1.1.1\"\n  organization: Supabase\n  date: January 2026\n  abstract: Comprehensive Postgres performance optimization guide for developers using Supabase and Postgres. Contains performance rules across 8 categories, prioritized by impact from critical (query performance, connection management) to incremental (advanced features). Each rule includes detailed explanations, incorrect vs. correct SQL examples, query plan analysis, and specific performance metrics to guide automated optimization and code generation.\n---\n\n# Supabase Postgres Best Practices\n\nComprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design.\n\n## When to Apply\n\nReference these guidelines when:\n- Writing SQL queries or designing schemas\n- Implementing indexes or query optimization\n- Reviewing database performance issues\n- Configuring connection pooling or scaling\n- Optimizing for Postgres-specific features\n- Working with Row-Level Security (RLS)\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | Query Performance | CRITICAL | `query-` |\n| 2 | Connection Management | CRITICAL | `conn-` |\n| 3 | Security & RLS | CRITICAL | `security-` |\n| 4 | Schema Design | HIGH | `schema-` |\n| 5 | Concurrency & Locking | MEDIUM-HIGH | `lock-` |\n| 6 | Data Access Patterns | MEDIUM | `data-` |\n| 7 | Monitoring & Diagnostics | LOW-MEDIUM | `monitor-` |\n| 8 | Advanced Features | LOW | `advanced-` |\n\n## How to Use\n\nRead individual rule files for detailed explanations and SQL examples:\n\n```\nreferences\u002Fquery-missing-indexes.md\nreferences\u002Fquery-partial-indexes.md\nreferences\u002F_sections.md\n```\n\nEach rule file contains:\n- Brief explanation of why it matters\n- Incorrect SQL example with explanation\n- Correct SQL example with explanation\n- Optional EXPLAIN output or metrics\n- Additional context and references\n- Supabase-specific notes (when applicable)\n\n## References\n\n- https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002F\n- https:\u002F\u002Fsupabase.com\u002Fdocs\n- https:\u002F\u002Fwiki.postgresql.org\u002Fwiki\u002FPerformance_Optimization\n- https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Foverview\n- https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Frow-level-security\n","# Supabase Postgres Best Practices\n\nComprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design.\n\n## When to Apply\n\nReference these guidelines when:\n- Writing SQL queries or designing schemas\n- Implementing indexes or query optimization\n- Reviewing database performance issues\n- Configuring connection pooling or scaling\n- Optimizing for Postgres-specific features\n- Working with Row-Level Security (RLS)\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | Query Performance | CRITICAL | `query-` |\n| 2 | Connection Management | CRITICAL | `conn-` |\n| 3 | Security & RLS | CRITICAL | `security-` |\n| 4 | Schema Design | HIGH | `schema-` |\n| 5 | Concurrency & Locking | MEDIUM-HIGH | `lock-` |\n| 6 | Data Access Patterns | MEDIUM | `data-` |\n| 7 | Monitoring & Diagnostics | LOW-MEDIUM | `monitor-` |\n| 8 | Advanced Features | LOW | `advanced-` |\n\n## How to Use\n\nRead individual rule files for detailed explanations and SQL examples:\n\n```\nreferences\u002Fquery-missing-indexes.md\nreferences\u002Fquery-partial-indexes.md\nreferences\u002F_sections.md\n```\n\nEach rule file contains:\n- Brief explanation of why it matters\n- Incorrect SQL example with explanation\n- Correct SQL example with explanation\n- Optional EXPLAIN output or metrics\n- Additional context and references\n- Supabase-specific notes (when applicable)\n\n## References\n\n- https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002F\n- https:\u002F\u002Fsupabase.com\u002Fdocs\n- https:\u002F\u002Fwiki.postgresql.org\u002Fwiki\u002FPerformance_Optimization\n- https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Foverview\n- https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Frow-level-security\n",{"name":5,"license":15,"metadata":24,"description":7},{"date":25,"author":26,"version":27,"abstract":28,"organization":29},"January 2026","supabase","1.1.1","Comprehensive Postgres performance optimization guide for developers using Supabase and Postgres. Contains performance rules across 8 categories, prioritized by impact from critical (query performance, connection management) to incremental (advanced features). Each rule includes detailed explanations, incorrect vs. correct SQL examples, query plan analysis, and specific performance metrics to guide automated optimization and code generation.","Supabase","main","14ebae85ed3b878ea57bf4f918184a37d519434a",".agents\u002Fskills\u002Fsupabase-postgres-best-practices","https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger","https:\u002F\u002Fgymlogger-tau.vercel.app","https:\u002F\u002Fgithub.com\u002Fayusht26","Full-stack developer | GenAI enthusiast | Open-source builder","2026-10-22 21:48:12",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add ayusht26\u002Fgym_logger --skill supabase-postgres-best-practices",{"tool":44,"command":45},"bunx","bunx skills add ayusht26\u002Fgym_logger --skill supabase-postgres-best-practices",{"tool":47,"command":48},"pnpm","pnpm dlx skills add ayusht26\u002Fgym_logger --skill supabase-postgres-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",true,[52,58,62,66,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142,145,149,153,157,161,165,169,173,177,181,185,189],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"CHANGELOG.md","REFERENCE","参考文档",5684,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002FCHANGELOG.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002F_contributing.md",4113,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002F_contributing.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002F_sections.md",1682,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002F_sections.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002F_template.md",1040,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002F_template.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fadvanced-full-text-search.md",1468,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fadvanced-full-text-search.md",{"path":75,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fadvanced-jsonb-indexing.md",1444,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fadvanced-jsonb-indexing.md",{"path":79,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fconn-idle-timeout.md",1282,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fconn-idle-timeout.md",{"path":83,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fconn-limits.md",1325,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fconn-limits.md",{"path":87,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fconn-pooling.md",1382,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fconn-pooling.md",{"path":91,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fconn-prepared-statements.md",1529,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fconn-prepared-statements.md",{"path":95,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fdata-batch-inserts.md",1287,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fdata-batch-inserts.md",{"path":99,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fdata-n-plus-one.md",1361,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fdata-n-plus-one.md",{"path":103,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fdata-pagination.md",1358,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fdata-pagination.md",{"path":107,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fdata-upsert.md",1390,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fdata-upsert.md",{"path":111,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Flock-advisory.md",1531,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Flock-advisory.md",{"path":115,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Flock-deadlock-prevention.md",1855,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Flock-deadlock-prevention.md",{"path":119,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Flock-short-transactions.md",1350,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Flock-short-transactions.md",{"path":123,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Flock-skip-locked.md",1353,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Flock-skip-locked.md",{"path":127,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fmonitor-explain-analyze.md",1441,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fmonitor-explain-analyze.md",{"path":131,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fmonitor-pg-stat-statements.md",1418,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fmonitor-pg-stat-statements.md",{"path":135,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fmonitor-vacuum-analyze.md",1506,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fmonitor-vacuum-analyze.md",{"path":139,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fquery-composite-indexes.md",1454,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fquery-composite-indexes.md",{"path":143,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":96,"sourceHtmlUrl":144},"references\u002Fquery-covering-indexes.md","https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fquery-covering-indexes.md",{"path":146,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":147,"sourceHtmlUrl":148},"references\u002Fquery-index-types.md",1521,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fquery-index-types.md",{"path":150,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":151,"sourceHtmlUrl":152},"references\u002Fquery-missing-indexes.md",1218,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fquery-missing-indexes.md",{"path":154,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":155,"sourceHtmlUrl":156},"references\u002Fquery-partial-indexes.md",1347,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fquery-partial-indexes.md",{"path":158,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":159,"sourceHtmlUrl":160},"references\u002Fschema-constraints.md",1880,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fschema-constraints.md",{"path":162,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":163,"sourceHtmlUrl":164},"references\u002Fschema-data-types.md",1453,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fschema-data-types.md",{"path":166,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":167,"sourceHtmlUrl":168},"references\u002Fschema-foreign-key-indexes.md",1679,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fschema-foreign-key-indexes.md",{"path":170,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":171,"sourceHtmlUrl":172},"references\u002Fschema-lowercase-identifiers.md",1728,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fschema-lowercase-identifiers.md",{"path":174,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":175,"sourceHtmlUrl":176},"references\u002Fschema-partitioning.md",1548,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fschema-partitioning.md",{"path":178,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":179,"sourceHtmlUrl":180},"references\u002Fschema-primary-keys.md",1821,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fschema-primary-keys.md",{"path":182,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":183,"sourceHtmlUrl":184},"references\u002Fsecurity-privileges.md",1566,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fsecurity-privileges.md",{"path":186,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":187,"sourceHtmlUrl":188},"references\u002Fsecurity-rls-basics.md",1372,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fsecurity-rls-basics.md",{"path":190,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":191,"sourceHtmlUrl":192},"references\u002Fsecurity-rls-performance.md",2103,"https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002Freferences\u002Fsecurity-rls-performance.md",[194,201,210,215],{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":19},"01M7FCW6A6E6379DPNCZ694W1Y","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.aider-desk\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":205,"licenseFileUrl":206,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":19},"01M7FCVX440WMZ01QF4PNGR5VS","frontend-design","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.aider-desk\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.aider-desk\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":211,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":214,"publishedAt":19},"01M7FCV73MR390ZXEEEHJ2T99T","https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":216,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":205,"licenseFileUrl":217,"sourceHtmlUrl":218,"categories":219,"keywords":220,"publishedAt":19},"01M7FCTEZ4RAR2W2KJ0DGXNQ72","https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fayusht26\u002Fgym_logger\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[]]