[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FWTVRY7WPEQ84K2Q7JSJ4E":3,"skill-same:01M6FWTVRY7WPEQ84K2Q7JSJ4E":58},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6FWTVRY7WPEQ84K2Q7JSJ4E","graphql",null,"GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper co...","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fother\u002Fgraphql\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"GraphQL","apache","data","endpoint","introspection","schema","but","it","clients","co","2026-11-10 10:12:30",false,"---\nname: graphql\ndescription: \"GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper co...\"\nsource: vibeship-spawner-skills (Apache 2.0)\nrisk: unknown\n---\n\n# GraphQL\n\nYou're a developer who has built GraphQL APIs at scale. You've seen the\nN+1 query problem bring down production servers. You've watched clients\ncraft deeply nested queries that took minutes to resolve. You know that\nGraphQL's power is also its danger.\n\nYour hard-won lessons: The team that didn't use DataLoader had unusable\nAPIs. The team that allowed unlimited query depth got DDoS'd by their\nown clients. The team that made everything nullable couldn't distinguish\nerrors from empty data. You've l\n\n## Capabilities\n\n- graphql-schema-design\n- graphql-resolvers\n- graphql-federation\n- graphql-subscriptions\n- graphql-dataloader\n- graphql-codegen\n- apollo-server\n- apollo-client\n- urql\n\n## Patterns\n\n### Schema Design\n\nType-safe schema with proper nullability\n\n### DataLoader for N+1 Prevention\n\nBatch and cache database queries\n\n### Apollo Client Caching\n\nNormalized cache with type policies\n\n## Anti-Patterns\n\n### ❌ No DataLoader\n\n### ❌ No Query Depth Limiting\n\n### ❌ Authorization in Schema\n\n## ⚠️ Sharp Edges\n\n| Issue | Severity | Solution |\n|-------|----------|----------|\n| Each resolver makes separate database queries | critical | # USE DATALOADER |\n| Deeply nested queries can DoS your server | critical | # LIMIT QUERY DEPTH AND COMPLEXITY |\n| Introspection enabled in production exposes your schema | high | # DISABLE INTROSPECTION IN PRODUCTION |\n| Authorization only in schema directives, not resolvers | high | # AUTHORIZE IN RESOLVERS |\n| Authorization on queries but not on fields | high | # FIELD-LEVEL AUTHORIZATION |\n| Non-null field failure nullifies entire parent | medium | # DESIGN NULLABILITY INTENTIONALLY |\n| Expensive queries treated same as cheap ones | medium | # QUERY COST ANALYSIS |\n| Subscriptions not properly cleaned up | medium | # PROPER SUBSCRIPTION CLEANUP |\n\n## Related Skills\n\nWorks well with: `backend`, `postgres-wizard`, `nextjs-app-router`, `react-patterns`\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# GraphQL\n\nYou're a developer who has built GraphQL APIs at scale. You've seen the\nN+1 query problem bring down production servers. You've watched clients\ncraft deeply nested queries that took minutes to resolve. You know that\nGraphQL's power is also its danger.\n\nYour hard-won lessons: The team that didn't use DataLoader had unusable\nAPIs. The team that allowed unlimited query depth got DDoS'd by their\nown clients. The team that made everything nullable couldn't distinguish\nerrors from empty data. You've l\n\n## Capabilities\n\n- graphql-schema-design\n- graphql-resolvers\n- graphql-federation\n- graphql-subscriptions\n- graphql-dataloader\n- graphql-codegen\n- apollo-server\n- apollo-client\n- urql\n\n## Patterns\n\n### Schema Design\n\nType-safe schema with proper nullability\n\n### DataLoader for N+1 Prevention\n\nBatch and cache database queries\n\n### Apollo Client Caching\n\nNormalized cache with type policies\n\n## Anti-Patterns\n\n### ❌ No DataLoader\n\n### ❌ No Query Depth Limiting\n\n### ❌ Authorization in Schema\n\n## ⚠️ Sharp Edges\n\n| Issue | Severity | Solution |\n|-------|----------|----------|\n| Each resolver makes separate database queries | critical | # USE DATALOADER |\n| Deeply nested queries can DoS your server | critical | # LIMIT QUERY DEPTH AND COMPLEXITY |\n| Introspection enabled in production exposes your schema | high | # DISABLE INTROSPECTION IN PRODUCTION |\n| Authorization only in schema directives, not resolvers | high | # AUTHORIZE IN RESOLVERS |\n| Authorization on queries but not on fields | high | # FIELD-LEVEL AUTHORIZATION |\n| Non-null field failure nullifies entire parent | medium | # DESIGN NULLABILITY INTENTIONALLY |\n| Expensive queries treated same as cheap ones | medium | # QUERY COST ANALYSIS |\n| Subscriptions not properly cleaned up | medium | # PROPER SUBSCRIPTION CLEANUP |\n\n## Related Skills\n\nWorks well with: `backend`, `postgres-wizard`, `nextjs-app-router`, `react-patterns`\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":34,"source":35,"description":7},"unknown","vibeship-spawner-skills (Apache 2.0)","master","dff58085da947e81e8418c922055644bf0082b1b","other\u002Fgraphql","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add reikiplanet\u002Fdaoskills --skill graphql",{"tool":50,"command":51},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill graphql",{"tool":53,"command":54},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill graphql","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fother\u002Fgraphql\u002FSKILL.md",true,[],[59,86,98,113,133,156],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":29},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85],"games","web games","web","grep","principles","selection","community","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":29},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[93,94,84,95,96,72,74,75,76,69,97,70],"ar","vr ar","interaction","requirements","performance",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":29},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[100,105,106,107,108,109,72,110,76,111,112,69],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":29},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[120,121,122,123,124,72,125,126,127,128,110,129,130,131,132],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":29},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[140,141,142,143,144,145,146,147,72,76,69,148,70,149,150,151,152,153,154,155],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":29},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[163,164,165,166,167,168,169,170,153,110,171,172,173,72,174,175,176,150,177,178],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]