[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76P093GGFV1D3TM2Q8Z26FA":3,"skill-same:01M76P093GGFV1D3TM2Q8Z26FA":59},{"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":29,"commitSha":30,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M76P093GGFV1D3TM2Q8Z26FA","supabase-known-pitfalls",null,"Execute identify and avoid Supabase anti-patterns and common integration mistakes.\nUse when reviewing Supabase code for issues, onboarding new developers,\nor auditing existing Supabase integrations for best practices violations.\nTrigger with phrases like \"supabase mistakes\", \"supabase anti-patterns\",\n\"supabase pitfalls\", \"supabase what not to do\", \"supabase code review\".","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-known-pitfalls\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: supabase-known-pitfalls\ndescription: |\n  Execute identify and avoid Supabase anti-patterns and common integration mistakes.\n  Use when reviewing Supabase code for issues, onboarding new developers,\n  or auditing existing Supabase integrations for best practices violations.\n  Trigger with phrases like \"supabase mistakes\", \"supabase anti-patterns\",\n  \"supabase pitfalls\", \"supabase what not to do\", \"supabase code review\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Supabase Known Pitfalls\n\n## Prerequisites\n- Access to Supabase codebase for review\n- Understanding of async\u002Fawait patterns\n- Knowledge of security best practices\n- Familiarity with rate limiting concepts\n\n## Instructions\n\nSupabase anti-patterns typically cluster into three risk categories: security risks (exposing service role keys, missing RLS policies, over-privileged anon access), performance risks (N+1 queries, missing indexes, fetching more columns than needed), and reliability risks (no retry logic, synchronous auth checks in every request, missing error handling). Addressing security issues first prevents data exposure, while performance fixes have the greatest impact on user experience.\n\n### Step 1: Review for Anti-Patterns\nScan the codebase for each pitfall pattern listed in the references. Use grep or a code search tool to find all locations where Supabase client calls are made. Look specifically for service role key usage in client-side code, missing `.select()` column lists that fetch entire rows, and `await` chains that make multiple sequential queries where a single join would suffice.\n\n### Step 2: Prioritize Fixes\nAddress security issues first: any client-side exposure of the service role key or missing RLS policies on tables containing user data are critical. Then tackle performance issues that affect P95 latency. Finally, address reliability gaps like missing error handling.\n\n### Step 3: Implement Better Approach\nReplace anti-patterns with recommended patterns. Document the change in a PR description so reviewers understand why the old approach was problematic.\n\n### Step 4: Add Prevention\nSet up linting and CI checks to prevent recurrence. Add ESLint rules that flag service key usage in frontend bundles and require `.select()` calls to specify columns explicitly.\n\n## Output\n- Anti-patterns identified with severity classification\n- Security, performance, and reliability fixes implemented\n- ESLint and CI prevention measures active\n- Code quality measurably improved with documented rationale\n\n## Error Handling\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error handling.\n\n## Examples\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for detailed examples.\n\n## Resources\n- [Supabase Security Guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fsecurity)\n- [Supabase Best Practices](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fbest-practices)\n\n## Overview\n\nExecute identify and avoid Supabase anti-patterns and common integration mistakes.","# Supabase Known Pitfalls\n\n## Prerequisites\n- Access to Supabase codebase for review\n- Understanding of async\u002Fawait patterns\n- Knowledge of security best practices\n- Familiarity with rate limiting concepts\n\n## Instructions\n\nSupabase anti-patterns typically cluster into three risk categories: security risks (exposing service role keys, missing RLS policies, over-privileged anon access), performance risks (N+1 queries, missing indexes, fetching more columns than needed), and reliability risks (no retry logic, synchronous auth checks in every request, missing error handling). Addressing security issues first prevents data exposure, while performance fixes have the greatest impact on user experience.\n\n### Step 1: Review for Anti-Patterns\nScan the codebase for each pitfall pattern listed in the references. Use grep or a code search tool to find all locations where Supabase client calls are made. Look specifically for service role key usage in client-side code, missing `.select()` column lists that fetch entire rows, and `await` chains that make multiple sequential queries where a single join would suffice.\n\n### Step 2: Prioritize Fixes\nAddress security issues first: any client-side exposure of the service role key or missing RLS policies on tables containing user data are critical. Then tackle performance issues that affect P95 latency. Finally, address reliability gaps like missing error handling.\n\n### Step 3: Implement Better Approach\nReplace anti-patterns with recommended patterns. Document the change in a PR description so reviewers understand why the old approach was problematic.\n\n### Step 4: Add Prevention\nSet up linting and CI checks to prevent recurrence. Add ESLint rules that flag service key usage in frontend bundles and require `.select()` calls to specify columns explicitly.\n\n## Output\n- Anti-patterns identified with severity classification\n- Security, performance, and reliability fixes implemented\n- ESLint and CI prevention measures active\n- Code quality measurably improved with documented rationale\n\n## Error Handling\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error handling.\n\n## Examples\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for detailed examples.\n\n## Resources\n- [Supabase Security Guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fsecurity)\n- [Supabase Best Practices](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fbest-practices)\n\n## Overview\n\nExecute identify and avoid Supabase anti-patterns and common integration mistakes.",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute identify and avoid Supabase anti-patterns and common integration mistakes.\nUse when reviewing Supabase code for issues, onboarding new developers,\nor auditing existing Supabase integrations for best practices violations.\nTrigger with phrases like \"supabase mistakes\", \"supabase anti-patterns\",\n\"supabase pitfalls\", \"supabase what not to do\", \"supabase code review\".\n","Read, Grep","claude-code, codex, openclaw","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill supabase-known-pitfalls",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill supabase-known-pitfalls",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill supabase-known-pitfalls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-known-pitfalls\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Ferrors.md","REFERENCE","参考文档",320,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-known-pitfalls\u002Freferences\u002Ferrors.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fexamples.md",208,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-known-pitfalls\u002Freferences\u002Fexamples.md",[60,67,74,81,88,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]