[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H957Z6ADDNETGHH4G6RKX9":3,"skill-same:01M6H957Z6ADDNETGHH4G6RKX9":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6H957Z6ADDNETGHH4G6RKX9","supabase-schema-from-requirements",null,"Execute Supabase primary workflow: Schema from Requirements.\nUse when Starting a new project with defined data requirements,\nRefactoring an existing schema based on new features, or Creating migrations from specification documents.\nTrigger with phrases like \"supabase schema from requirements\",\n\"generate database schema with supabase\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fsupabase-pack\u002Fskills\u002Fsupabase-schema-from-requirements\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"supabase schema from requirements","supabase","requirements","schema","migrations","Existing","with","trigger","io","database schema","project","specification","codex","use","Bash","database","code","generate","documents","workflow","2026-11-10 10:12:30",false,"---\nname: supabase-schema-from-requirements\ndescription: |\n  Execute Supabase primary workflow: Schema from Requirements.\n  Use when Starting a new project with defined data requirements,\n  Refactoring an existing schema based on new features, or Creating migrations from specification documents.\n  Trigger with phrases like \"supabase schema from requirements\",\n  \"generate database schema with supabase\".\nallowed-tools: Read, Write, Edit, Bash(npm:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Supabase Schema from Requirements\n\n## Overview\nGenerate Supabase database schema from natural language requirements. This is the primary workflow for starting new Supabase projects. Translating business requirements directly into a well-structured Postgres schema with Row Level Security policies, appropriate indexes, and foreign key constraints is one of the highest-leverage activities in the early stages of a project. A well-designed schema is far cheaper to iterate on before data is in production than after.\n\n## Prerequisites\n- Completed `supabase-install-auth` setup\n- Understanding of Supabase core concepts\n- Valid API credentials configured\n\n## Instructions\n\n### Step 1: Initialize\nParse the natural language requirements into a structured entity list. Identify the main entities, their attributes, the relationships between them (one-to-one, one-to-many, many-to-many), and the access control rules that determine who can see or modify each entity. Clarify any ambiguous requirements before generating SQL to avoid costly schema revisions later.\n\n```typescript\n\u002F\u002F Step 1 implementation\n```\n\n### Step 2: Execute\nGenerate the SQL migration file that creates the tables, defines foreign key constraints, adds appropriate indexes on foreign keys and frequently filtered columns, and sets up Row Level Security policies matching the identified access control rules. Review the generated schema for normalization issues and verify that the RLS policies correctly implement the intent of the requirements.\n\n```typescript\n\u002F\u002F Step 2 implementation\n```\n\n### Step 3: Finalize\nApply the migration to your Supabase project and run integration tests that exercise each RLS policy with different user roles to confirm access control behaves as specified. Document the schema design decisions, particularly any denormalization choices made for performance reasons, so future maintainers understand the rationale.\n\n```typescript\n\u002F\u002F Step 3 implementation\n```\n\n## Output\n- Structured entity model derived from natural language requirements\n- SQL migration creating tables, indexes, and RLS policies\n- Verified schema with passing integration tests for each access control rule\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Error 1 | Cause | Solution |\n| Error 2 | Cause | Solution |\n\n## Examples\n\n### Complete Workflow\n```typescript\n\u002F\u002F Complete workflow example\n```\n\n### Common Variations\n- Variation 1: Description\n- Variation 2: Description\n\n## Resources\n- [Supabase Documentation](https:\u002F\u002Fsupabase.com\u002Fdocs)\n- [Supabase API Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fapi)\n\n## Next Steps\nFor secondary workflow, see `supabase-auth-storage-realtime-core`.","# Supabase Schema from Requirements\n\n## Overview\nGenerate Supabase database schema from natural language requirements. This is the primary workflow for starting new Supabase projects. Translating business requirements directly into a well-structured Postgres schema with Row Level Security policies, appropriate indexes, and foreign key constraints is one of the highest-leverage activities in the early stages of a project. A well-designed schema is far cheaper to iterate on before data is in production than after.\n\n## Prerequisites\n- Completed `supabase-install-auth` setup\n- Understanding of Supabase core concepts\n- Valid API credentials configured\n\n## Instructions\n\n### Step 1: Initialize\nParse the natural language requirements into a structured entity list. Identify the main entities, their attributes, the relationships between them (one-to-one, one-to-many, many-to-many), and the access control rules that determine who can see or modify each entity. Clarify any ambiguous requirements before generating SQL to avoid costly schema revisions later.\n\n```typescript\n\u002F\u002F Step 1 implementation\n```\n\n### Step 2: Execute\nGenerate the SQL migration file that creates the tables, defines foreign key constraints, adds appropriate indexes on foreign keys and frequently filtered columns, and sets up Row Level Security policies matching the identified access control rules. Review the generated schema for normalization issues and verify that the RLS policies correctly implement the intent of the requirements.\n\n```typescript\n\u002F\u002F Step 2 implementation\n```\n\n### Step 3: Finalize\nApply the migration to your Supabase project and run integration tests that exercise each RLS policy with different user roles to confirm access control behaves as specified. Document the schema design decisions, particularly any denormalization choices made for performance reasons, so future maintainers understand the rationale.\n\n```typescript\n\u002F\u002F Step 3 implementation\n```\n\n## Output\n- Structured entity model derived from natural language requirements\n- SQL migration creating tables, indexes, and RLS policies\n- Verified schema with passing integration tests for each access control rule\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Error 1 | Cause | Solution |\n| Error 2 | Cause | Solution |\n\n## Examples\n\n### Complete Workflow\n```typescript\n\u002F\u002F Complete workflow example\n```\n\n### Common Variations\n- Variation 1: Description\n- Variation 2: Description\n\n## Resources\n- [Supabase Documentation](https:\u002F\u002Fsupabase.com\u002Fdocs)\n- [Supabase API Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fapi)\n\n## Next Steps\nFor secondary workflow, see `supabase-auth-storage-realtime-core`.",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Supabase primary workflow: Schema from Requirements.\nUse when Starting a new project with defined data requirements,\nRefactoring an existing schema based on new features, or Creating migrations from specification documents.\nTrigger with phrases like \"supabase schema from requirements\",\n\"generate database schema with supabase\".\n","Read, Write, Edit, Bash(npm:*), Grep","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fsupabase-pack\u002Fskills\u002Fsupabase-schema-from-requirements",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add micsapp\u002Fmicstec-skills --skill supabase-schema-from-requirements",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill supabase-schema-from-requirements",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill supabase-schema-from-requirements","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fsupabase-pack\u002Fskills\u002Fsupabase-schema-from-requirements\u002FSKILL.md",true,[],[70,107,136,156,176,200],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":86,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[76,81],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":121,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[113,114,117,120],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":115,"categoryName":116,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":118,"categoryName":119,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[122,123,124,125,88,126,34,127,128,129,130,131,96,97,103,132,133,104,134,135],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[142],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[144,145,146,147,88,91,96,97,148,31,149,150,151,152,153,104,154,155,135,106],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":164,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[162,163],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[165,147,166,96,150,167,88,122,168,169,170,171,97,172,104,173,174,175,105,106],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[183,184,185,124,186,187,188,189,96,190,191,192,193,194,195,28,196,197,198,199],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project work","token","line","sprints",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[202,207,208,209,210,211,212,31,213,214],"npm","js","calculate","node","math","user","compute","errors"]