[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74F734T6J96G5M2CJSWBCEH":3,"skill-same:01M74F734T6J96G5M2CJSWBCEH":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M74F734T6J96G5M2CJSWBCEH","api-design",null,"Design or review an HTTP\u002FREST\u002FGraphQL API for versioning, pagination, error shapes, idempotency, auth, status codes, cache headers, and breaking-change management. Use when asked to \"design an API\", \"shape the endpoints\", \"design the schema\", \"add a new endpoint\", \"review this API\", or when building\u002Fmodifying a public or internal HTTP surface. HTTP-specific complement to `design-an-interface`.","open-gsd\u002Fgsd-pi","open-gsd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286935422?v=4","01M74F5F0MKW0B81YZHRVJMMWR","Open GSD","01M74F5F1782D325EYEM5GNXNC",1369,"MIT","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fapi-design\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: api-design\ndescription: Design or review an HTTP\u002FREST\u002FGraphQL API for versioning, pagination, error shapes, idempotency, auth, status codes, cache headers, and breaking-change management. Use when asked to \"design an API\", \"shape the endpoints\", \"design the schema\", \"add a new endpoint\", \"review this API\", or when building\u002Fmodifying a public or internal HTTP surface. HTTP-specific complement to `design-an-interface`.\n---\n\n\u003Cobjective>\nShape an HTTP or GraphQL API so callers get predictable, evolvable, and honest semantics. The deliverable is a concrete endpoint\u002Fschema sketch with: URL or operation names, method\u002Fverb, request shape, response shape, error shape, auth model, pagination strategy, and versioning stance. Optimize for \"clients that exist in 2 years\" over \"client that's easy to write today\".\n\u003C\u002Fobjective>\n\n\u003Ccontext>\ngsd-pi has `design-an-interface` for general module-interface design; this skill is the HTTP\u002FGraphQL specialization. REST and GraphQL carry baggage — status codes, verbs, nullability, pagination — that a generic interface-design discussion glosses over.\n\nInvocation points:\n\n- Adding a new public API endpoint\n- Redesigning an internal API boundary between services\n- Code review of a PR that introduces HTTP handlers\n- A slice whose acceptance criteria include \"the API works\"\n- A GraphQL schema change\n\u003C\u002Fcontext>\n\n\u003Ccore_principle>\n**CALLERS OUTLIVE YOUR ASSUMPTIONS.** An API you ship today has to keep working when your internals change, when the mobile app version two is still in use, and when a third party integrates against it. Design for extension, not just for the current caller.\n\n**HONEST STATUS CODES.** 200 OK with `{\"error\": \"not found\"}` is a lie. 404 says not found. Use the HTTP semantics the protocol offers — HTTP clients, caches, and intermediaries rely on them.\n\n**PAGINATION IS NON-OPTIONAL.** Any list endpoint that doesn't paginate will eventually get a request for \"all records\" that kills your database.\n\u003C\u002Fcore_principle>\n\n\u003Cprocess>\n\n## Step 1: Gather the contract\n\nAnswer, or ask (one round, 1–3 questions):\n\n1. **Who are the callers?** Internal service \u002F mobile app \u002F public third-party \u002F same-repo frontend.\n2. **What's the versioning stance?** None \u002F URL-path (`\u002Fv1\u002F`) \u002F header-based \u002F GraphQL schema evolution.\n3. **Auth model?** Public \u002F API key \u002F OAuth \u002F session cookie \u002F mTLS \u002F none-but-internal-only.\n4. **Idempotency expectation?** Is a retry safe? Required?\n5. **Consistency model?** Read-your-writes, eventual, serializable?\n\n## Step 2: Resource and operation naming\n\n### REST\n\n- Nouns not verbs in URLs: `POST \u002Fusers`, not `POST \u002FcreateUser`.\n- Plural resources: `\u002Fusers\u002F42`, not `\u002Fuser\u002F42`.\n- Nested only when the relationship is hierarchical and the child has no independent identity: `\u002Fusers\u002F42\u002Fsessions\u002F3`. Otherwise flat: `\u002Fsessions\u002F3?userId=42`.\n- Use subresources for actions that don't fit CRUD: `POST \u002Fusers\u002F42:deactivate` (colon syntax) or `POST \u002Fusers\u002F42\u002Factions\u002Fdeactivate`.\n\n### GraphQL\n\n- Queries are nouns; mutations are verbs: `user(id)`, `createUser(input)`, `deactivateUser(id)`.\n- Group related mutations under an input type: `createUser(input: CreateUserInput!)`.\n- Return the affected object plus any derived\u002Fcomputed fields from mutations — lets clients avoid a refetch.\n\n## Step 3: Methods and status codes\n\n### REST\n\n| Method | Intent | Idempotent? | Default success |\n|---|---|---|---|\n| GET | Read | Yes | 200, or 304 if conditional |\n| POST | Create or non-idempotent action | No | 201 with `Location` on create, 200 on action |\n| PUT | Replace (full-object) | Yes | 200 with body, or 204 |\n| PATCH | Partial update | No (usually) | 200 with body |\n| DELETE | Remove | Yes | 204 |\n\nErrors:\n\n- 400: caller screwed up the request shape\n- 401: no\u002Finvalid auth\n- 403: authed but not allowed\n- 404: resource doesn't exist\n- 409: conflict (version mismatch, unique constraint)\n- 410: gone (vs 404 when the resource previously existed and you want to signal that)\n- 422: validation failed\n- 429: rate-limited — include `Retry-After`\n- 500: genuinely unexpected server error\n- 503: service down or overloaded — include `Retry-After`\n\nNever 200-with-error-body. Never 500 for a 4xx cause.\n\n### GraphQL\n\n- Top-level errors (`errors[]`) for transport-level failures. Domain errors (validation, not-found, forbidden) go in the typed return — use a union or result type.\n- Partial results are expected; design the schema so `null` on a field is meaningful, not a signal of generic failure.\n\n## Step 4: Pagination\n\n- **Cursor-based by default.** Opaque cursor string, `limit`, return `nextCursor` when more exists. Scales, stable under writes.\n- **Offset-based only when:** dataset is small, user needs jump-to-page semantics (admin tables), and you're willing to accept stability drift.\n- **Never \"return everything\"** as default. Put a hard upper bound on `limit` (e.g., 200).\n- GraphQL: use Relay-style connections (`edges`, `pageInfo`) if the ecosystem expects it; otherwise a simpler `{items, nextCursor}` is fine.\n\n## Step 5: Error shape\n\nStandardize one shape and use it everywhere. Example REST:\n\n```json\n{\n  \"error\": {\n    \"code\": \"user_not_found\",\n    \"message\": \"No user with id 42\",\n    \"details\": { \"userId\": 42 },\n    \"requestId\": \"req_abc123\"\n  }\n}\n```\n\n- `code` is machine-readable; stable; documented.\n- `message` is human-readable; can change.\n- `details` carries structured context.\n- `requestId` lets callers report bugs.\n\nErrors don't leak stack traces, file paths, or internal queries.\n\n## Step 6: Idempotency, caching, concurrency\n\n- **Idempotency keys** for POST operations that mustn't double-execute on retry. Caller passes `Idempotency-Key: \u003Cuuid>`; server dedupes for a window.\n- **ETags** for GET + conditional updates (`If-Match` on PUT\u002FPATCH).\n- **Cache-Control** on GETs that are safely cacheable.\n- **Optimistic concurrency:** when multiple writers collide, 409 with the current state. Don't silently clobber.\n\n## Step 7: Versioning and evolution\n\n- **Additive changes are free:** new optional fields, new endpoints, new optional query params.\n- **Breaking changes need a plan:** path-versioned (`\u002Fv2\u002F`), sunset headers on `\u002Fv1\u002F`, deprecation window communicated. Or, for GraphQL, `@deprecated` on fields with a migration note.\n- **Document the contract:** OpenAPI\u002FGraphQL SDL. Keep it in the repo. Make it part of the PR that introduces the change.\n\n## Step 8: Review or write it up\n\nIf this is a review, produce findings in the same shape as `security-review` \u002F `review` — file:line, category, recommendation.\n\nIf this is a new design, produce:\n\n```markdown\n## \u003CAPI name>\n\n### Scope\n\u003Cwhat the API is for, who calls it>\n\n### Endpoints \u002F Operations\n- `POST \u002Fusers` — create user. Request: `{email, name}`. Response 201: `{id, email, name, createdAt}` + `Location: \u002Fusers\u002F\u003Cid>`. Errors: 409 email taken, 422 invalid.\n- ...\n\n### Auth\n\u003Cmodel + where to put the credential>\n\n### Pagination\n\u003Ccursor shape, max limit>\n\n### Error shape\n\u003Cone canonical shape>\n\n### Idempotency \u002F concurrency\n\u003Crules>\n\n### Versioning\n\u003Cstance + how breaking changes will be handled>\n\n### OpenAPI \u002F SDL\n\u003Clink or inline>\n```\n\nSave architectural decisions with `gsd_decision_save`; it renders `.gsd\u002FDECISIONS.md`.\n\n\u003C\u002Fprocess>\n\n\u003Canti_patterns>\n\n- **200 OK with `{\"error\": \"...\"}`.** Lies to caches, proxies, retry libraries.\n- **Unbounded list endpoints.** `GET \u002Fusers` without a `limit` cap will bite you.\n- **Offset pagination at scale.** Drifts under writes; slow at high offsets.\n- **Free-form error messages with no code.** Machine callers can't branch on prose.\n- **Breaking changes in-place.** Callers break; versioning exists for a reason.\n- **Ignoring idempotency on retriable POSTs.** Double-charges, duplicate records.\n- **Auth checks at the handler only, not the service layer.** Defense in depth.\n\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\n\n- [ ] Every endpoint\u002Foperation has named request, response, and error shapes.\n- [ ] Status codes match HTTP semantics — no 200-with-error.\n- [ ] List endpoints paginate; max limit is documented.\n- [ ] A single error shape is used everywhere, with a machine-readable code.\n- [ ] Versioning stance is stated — even if the answer is \"additive only for now.\"\n- [ ] OpenAPI\u002FSDL reflects the design and lives in the repo.\n- [ ] Decisions are saved with `gsd_decision_save`.\n\n\u003C\u002Fsuccess_criteria>\n","\u003Cobjective>\nShape an HTTP or GraphQL API so callers get predictable, evolvable, and honest semantics. The deliverable is a concrete endpoint\u002Fschema sketch with: URL or operation names, method\u002Fverb, request shape, response shape, error shape, auth model, pagination strategy, and versioning stance. Optimize for \"clients that exist in 2 years\" over \"client that's easy to write today\".\n\u003C\u002Fobjective>\n\n\u003Ccontext>\ngsd-pi has `design-an-interface` for general module-interface design; this skill is the HTTP\u002FGraphQL specialization. REST and GraphQL carry baggage — status codes, verbs, nullability, pagination — that a generic interface-design discussion glosses over.\n\nInvocation points:\n\n- Adding a new public API endpoint\n- Redesigning an internal API boundary between services\n- Code review of a PR that introduces HTTP handlers\n- A slice whose acceptance criteria include \"the API works\"\n- A GraphQL schema change\n\u003C\u002Fcontext>\n\n\u003Ccore_principle>\n**CALLERS OUTLIVE YOUR ASSUMPTIONS.** An API you ship today has to keep working when your internals change, when the mobile app version two is still in use, and when a third party integrates against it. Design for extension, not just for the current caller.\n\n**HONEST STATUS CODES.** 200 OK with `{\"error\": \"not found\"}` is a lie. 404 says not found. Use the HTTP semantics the protocol offers — HTTP clients, caches, and intermediaries rely on them.\n\n**PAGINATION IS NON-OPTIONAL.** Any list endpoint that doesn't paginate will eventually get a request for \"all records\" that kills your database.\n\u003C\u002Fcore_principle>\n\n\u003Cprocess>\n\n## Step 1: Gather the contract\n\nAnswer, or ask (one round, 1–3 questions):\n\n1. **Who are the callers?** Internal service \u002F mobile app \u002F public third-party \u002F same-repo frontend.\n2. **What's the versioning stance?** None \u002F URL-path (`\u002Fv1\u002F`) \u002F header-based \u002F GraphQL schema evolution.\n3. **Auth model?** Public \u002F API key \u002F OAuth \u002F session cookie \u002F mTLS \u002F none-but-internal-only.\n4. **Idempotency expectation?** Is a retry safe? Required?\n5. **Consistency model?** Read-your-writes, eventual, serializable?\n\n## Step 2: Resource and operation naming\n\n### REST\n\n- Nouns not verbs in URLs: `POST \u002Fusers`, not `POST \u002FcreateUser`.\n- Plural resources: `\u002Fusers\u002F42`, not `\u002Fuser\u002F42`.\n- Nested only when the relationship is hierarchical and the child has no independent identity: `\u002Fusers\u002F42\u002Fsessions\u002F3`. Otherwise flat: `\u002Fsessions\u002F3?userId=42`.\n- Use subresources for actions that don't fit CRUD: `POST \u002Fusers\u002F42:deactivate` (colon syntax) or `POST \u002Fusers\u002F42\u002Factions\u002Fdeactivate`.\n\n### GraphQL\n\n- Queries are nouns; mutations are verbs: `user(id)`, `createUser(input)`, `deactivateUser(id)`.\n- Group related mutations under an input type: `createUser(input: CreateUserInput!)`.\n- Return the affected object plus any derived\u002Fcomputed fields from mutations — lets clients avoid a refetch.\n\n## Step 3: Methods and status codes\n\n### REST\n\n| Method | Intent | Idempotent? | Default success |\n|---|---|---|---|\n| GET | Read | Yes | 200, or 304 if conditional |\n| POST | Create or non-idempotent action | No | 201 with `Location` on create, 200 on action |\n| PUT | Replace (full-object) | Yes | 200 with body, or 204 |\n| PATCH | Partial update | No (usually) | 200 with body |\n| DELETE | Remove | Yes | 204 |\n\nErrors:\n\n- 400: caller screwed up the request shape\n- 401: no\u002Finvalid auth\n- 403: authed but not allowed\n- 404: resource doesn't exist\n- 409: conflict (version mismatch, unique constraint)\n- 410: gone (vs 404 when the resource previously existed and you want to signal that)\n- 422: validation failed\n- 429: rate-limited — include `Retry-After`\n- 500: genuinely unexpected server error\n- 503: service down or overloaded — include `Retry-After`\n\nNever 200-with-error-body. Never 500 for a 4xx cause.\n\n### GraphQL\n\n- Top-level errors (`errors[]`) for transport-level failures. Domain errors (validation, not-found, forbidden) go in the typed return — use a union or result type.\n- Partial results are expected; design the schema so `null` on a field is meaningful, not a signal of generic failure.\n\n## Step 4: Pagination\n\n- **Cursor-based by default.** Opaque cursor string, `limit`, return `nextCursor` when more exists. Scales, stable under writes.\n- **Offset-based only when:** dataset is small, user needs jump-to-page semantics (admin tables), and you're willing to accept stability drift.\n- **Never \"return everything\"** as default. Put a hard upper bound on `limit` (e.g., 200).\n- GraphQL: use Relay-style connections (`edges`, `pageInfo`) if the ecosystem expects it; otherwise a simpler `{items, nextCursor}` is fine.\n\n## Step 5: Error shape\n\nStandardize one shape and use it everywhere. Example REST:\n\n```json\n{\n  \"error\": {\n    \"code\": \"user_not_found\",\n    \"message\": \"No user with id 42\",\n    \"details\": { \"userId\": 42 },\n    \"requestId\": \"req_abc123\"\n  }\n}\n```\n\n- `code` is machine-readable; stable; documented.\n- `message` is human-readable; can change.\n- `details` carries structured context.\n- `requestId` lets callers report bugs.\n\nErrors don't leak stack traces, file paths, or internal queries.\n\n## Step 6: Idempotency, caching, concurrency\n\n- **Idempotency keys** for POST operations that mustn't double-execute on retry. Caller passes `Idempotency-Key: \u003Cuuid>`; server dedupes for a window.\n- **ETags** for GET + conditional updates (`If-Match` on PUT\u002FPATCH).\n- **Cache-Control** on GETs that are safely cacheable.\n- **Optimistic concurrency:** when multiple writers collide, 409 with the current state. Don't silently clobber.\n\n## Step 7: Versioning and evolution\n\n- **Additive changes are free:** new optional fields, new endpoints, new optional query params.\n- **Breaking changes need a plan:** path-versioned (`\u002Fv2\u002F`), sunset headers on `\u002Fv1\u002F`, deprecation window communicated. Or, for GraphQL, `@deprecated` on fields with a migration note.\n- **Document the contract:** OpenAPI\u002FGraphQL SDL. Keep it in the repo. Make it part of the PR that introduces the change.\n\n## Step 8: Review or write it up\n\nIf this is a review, produce findings in the same shape as `security-review` \u002F `review` — file:line, category, recommendation.\n\nIf this is a new design, produce:\n\n```markdown\n## \u003CAPI name>\n\n### Scope\n\u003Cwhat the API is for, who calls it>\n\n### Endpoints \u002F Operations\n- `POST \u002Fusers` — create user. Request: `{email, name}`. Response 201: `{id, email, name, createdAt}` + `Location: \u002Fusers\u002F\u003Cid>`. Errors: 409 email taken, 422 invalid.\n- ...\n\n### Auth\n\u003Cmodel + where to put the credential>\n\n### Pagination\n\u003Ccursor shape, max limit>\n\n### Error shape\n\u003Cone canonical shape>\n\n### Idempotency \u002F concurrency\n\u003Crules>\n\n### Versioning\n\u003Cstance + how breaking changes will be handled>\n\n### OpenAPI \u002F SDL\n\u003Clink or inline>\n```\n\nSave architectural decisions with `gsd_decision_save`; it renders `.gsd\u002FDECISIONS.md`.\n\n\u003C\u002Fprocess>\n\n\u003Canti_patterns>\n\n- **200 OK with `{\"error\": \"...\"}`.** Lies to caches, proxies, retry libraries.\n- **Unbounded list endpoints.** `GET \u002Fusers` without a `limit` cap will bite you.\n- **Offset pagination at scale.** Drifts under writes; slow at high offsets.\n- **Free-form error messages with no code.** Machine callers can't branch on prose.\n- **Breaking changes in-place.** Callers break; versioning exists for a reason.\n- **Ignoring idempotency on retriable POSTs.** Double-charges, duplicate records.\n- **Auth checks at the handler only, not the service layer.** Defense in depth.\n\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\n\n- [ ] Every endpoint\u002Foperation has named request, response, and error shapes.\n- [ ] Status codes match HTTP semantics — no 200-with-error.\n- [ ] List endpoints paginate; max limit is documented.\n- [ ] A single error shape is used everywhere, with a machine-readable code.\n- [ ] Versioning stance is stated — even if the answer is \"additive only for now.\"\n- [ ] OpenAPI\u002FSDL reflects the design and lives in the repo.\n- [ ] Decisions are saved with `gsd_decision_save`.\n\n\u003C\u002Fsuccess_criteria>\n",{"name":5,"description":7},"main","c0bc9c4e7e0a8581aeac3af397031dc3a63d012e","src\u002Fresources\u002Fskills\u002Fapi-design",118,"https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi","https:\u002F\u002Fwww.opengsd.net","https:\u002F\u002Fgithub.com\u002Fopen-gsd","opengsd.net","Most AI coding setups rot as the context window fills. Open GSD keeps the context clean, the work verified, and the git history honest — ship more, worry less.","2026-11-15 00:38:19",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add open-gsd\u002Fgsd-pi --skill api-design",{"tool":40,"command":41},"bunx","bunx skills add open-gsd\u002Fgsd-pi --skill api-design",{"tool":43,"command":44},"pnpm","pnpm dlx skills add open-gsd\u002Fgsd-pi --skill api-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fapi-design\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M74FAXPHS0QT1S067QDKYDBX","write-milestone-brief","Synthesize the current conversation into a milestone brief (PRD). Saves it as the milestone CONTEXT (`gsd_summary_save`) by default, or files a GitHub issue only with explicit user confirmation. Use when asked to \"turn this into a PRD\", \"draft a milestone brief\", \"capture this context\", \"write it up\", or when enough has been discussed to commit the plan to paper. Does not interview — it synthesizes what is already known.","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fwrite-milestone-brief\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M74FATJT7WZX5CSSG8RJDCF1","write-docs","Collaborative authoring workflow for proposals, technical specs, decision docs, READMEs, ADRs, and long-form prose that must work for fresh readers. Three stages: gather context, iterate on structure, reader-test for a stranger. Use when asked to \"write the docs\", \"draft a proposal\", \"write a spec\", \"write an RFC\", \"write the README\", or when a doc must be understandable without this session's context.","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fwrite-docs\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M74FAQ8HKNVGCZ5ZBHW03A76","web-quality-audit","Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to \"audit my site\", \"review web quality\", \"run lighthouse audit\", \"check page quality\", or \"optimize my website\".","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fweb-quality-audit\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M74FAMZ7WP4RPAG20F448MVF","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M74FAHYM672GKGGS8KMY9CKC","verify-before-complete","Block completion claims until verification evidence has been produced in the current message. Use before marking a task\u002Fslice\u002Fmilestone complete, before creating a commit or PR, before saying \"it works\" or \"tests pass\", and any time you are about to claim work is done. The rule is: evidence before claims, always — running the verification must happen now, not \"earlier in the session\". Fresh output or no claim.","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fverify-before-complete\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M74FADG78GX090P4YE5ZHR2A","userinterface-wiki","UI\u002FUX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fuserinterface-wiki\u002FSKILL.md",[],[]]