[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RV8S2PZB0HCCRWE2C641Z":3,"skill-same:01M77RV8S2PZB0HCCRWE2C641Z":55},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77RV8S2PZB0HCCRWE2C641Z","api-design",null,"Define standards and best practices for designing secure, consistent, scalable, and maintainable APIs across all services.","panksooungman-dot\u002FAI-Web-Master","panksooungman-dot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263377190?v=4","01M77RQKZAR08JG1JSWP1MVXPV","cnbiz","01M77RQM00YBBJX4F6Y04HT8RN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fshared\u002Fapi-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: api-design\ndescription: Define standards and best practices for designing secure, consistent, scalable, and maintainable APIs across all services.\nversion: 1.0.0\nauthor: AI Business OS\nlicense: MIT\ncategory: shared\npriority: required\n---\n\n# API Design\n\n## Purpose\n\nThis skill defines API design standards that ensure consistency, usability, security, scalability, and maintainability across all services.\n\nThe goal is to create APIs that are intuitive for developers, resilient in production, and easy to evolve over time.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Designing new REST APIs\n- Designing GraphQL APIs\n- Creating internal service APIs\n- Creating public APIs\n- Reviewing API contracts\n- Versioning existing APIs\n\n---\n\n# Objectives\n\nDesign APIs that are:\n\n- Consistent\n- Predictable\n- Secure\n- Versioned\n- Scalable\n- Easy to consume\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Business Requirements\n- Product Requirements\n- User Stories\n- Data Models\n- Security Requirements\n- Integration Requirements\n\n---\n\n# API Design Principles\n\nFollow these principles:\n\n- Resource-oriented design\n- Consistent naming\n- Stateless communication\n- Idempotent operations where applicable\n- Backward compatibility\n- Explicit versioning\n\n---\n\n# Resource Design\n\nDefine:\n\n- Resources\n- Collections\n- Relationships\n- Nested Resources\n- Resource Identifiers\n\nUse nouns instead of verbs for resource names.\n\nExamples:\n\n- \u002Fusers\n- \u002Forders\n- \u002Fproducts\u002F{id}\n\n---\n\n# HTTP Methods\n\nUse methods appropriately:\n\n- GET — Retrieve resources\n- POST — Create resources\n- PUT — Replace resources\n- PATCH — Partial updates\n- DELETE — Remove resources\n\nAvoid using GET for state-changing operations.\n\n---\n\n# Request Design\n\nDocument:\n\n- Headers\n- Query Parameters\n- Path Parameters\n- Request Body\n- Validation Rules\n- Required Fields\n\nEnsure all inputs are validated.\n\n---\n\n# Response Design\n\nResponses should include:\n\n- HTTP Status Code\n- Response Body\n- Metadata\n- Pagination\n- Error Details\n\nMaintain a consistent response structure across all APIs.\n\n---\n\n# Error Handling\n\nStandardize:\n\n- Error Codes\n- Error Messages\n- Validation Errors\n- Authentication Errors\n- Authorization Errors\n- Server Errors\n\nError messages should be actionable and never expose sensitive information.\n\n---\n\n# Authentication & Security\n\nSupport:\n\n- OAuth 2.0\n- OpenID Connect\n- JWT Bearer Tokens\n- API Keys\n- Mutual TLS (where required)\n\nApply authorization checks to every protected endpoint.\n\n---\n\n# Versioning\n\nSupport:\n\n- URI Versioning\n- Header Versioning\n- Semantic Versioning\n\nDocument deprecation and migration strategies.\n\n---\n\n# Pagination & Filtering\n\nFor collections support:\n\n- Pagination\n- Sorting\n- Filtering\n- Search\n\nAvoid returning unbounded result sets.\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Resources consistently named\n- HTTP methods correctly applied\n- Request schema defined\n- Response schema defined\n- Error responses standardized\n- Security requirements implemented\n- Versioning strategy documented\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- Resources are undefined\n- API purpose is unclear\n- Security requirements are missing\n- Response format is inconsistent\n- Versioning strategy is absent\n\n---\n\n# Outputs\n\nGenerate:\n\n- API Design Specification\n- Endpoint Catalog\n- Request\u002FResponse Standards\n- Error Catalog\n- Versioning Strategy\n\n---\n\n# Rules\n\n- Prefer consistency over creativity.\n- Design APIs around resources.\n- Keep endpoints predictable.\n- Never expose internal implementation details.\n- Design for backward compatibility whenever possible.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- APIs are easy to understand\n- integrations are reliable\n- security is consistently applied\n- breaking changes are minimized\n- documentation matches implementation\n\n---\n\n# Related Skills\n\n- authentication\n- authorization\n- security\n- database\n- validation\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |","# API Design\n\n## Purpose\n\nThis skill defines API design standards that ensure consistency, usability, security, scalability, and maintainability across all services.\n\nThe goal is to create APIs that are intuitive for developers, resilient in production, and easy to evolve over time.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Designing new REST APIs\n- Designing GraphQL APIs\n- Creating internal service APIs\n- Creating public APIs\n- Reviewing API contracts\n- Versioning existing APIs\n\n---\n\n# Objectives\n\nDesign APIs that are:\n\n- Consistent\n- Predictable\n- Secure\n- Versioned\n- Scalable\n- Easy to consume\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Business Requirements\n- Product Requirements\n- User Stories\n- Data Models\n- Security Requirements\n- Integration Requirements\n\n---\n\n# API Design Principles\n\nFollow these principles:\n\n- Resource-oriented design\n- Consistent naming\n- Stateless communication\n- Idempotent operations where applicable\n- Backward compatibility\n- Explicit versioning\n\n---\n\n# Resource Design\n\nDefine:\n\n- Resources\n- Collections\n- Relationships\n- Nested Resources\n- Resource Identifiers\n\nUse nouns instead of verbs for resource names.\n\nExamples:\n\n- \u002Fusers\n- \u002Forders\n- \u002Fproducts\u002F{id}\n\n---\n\n# HTTP Methods\n\nUse methods appropriately:\n\n- GET — Retrieve resources\n- POST — Create resources\n- PUT — Replace resources\n- PATCH — Partial updates\n- DELETE — Remove resources\n\nAvoid using GET for state-changing operations.\n\n---\n\n# Request Design\n\nDocument:\n\n- Headers\n- Query Parameters\n- Path Parameters\n- Request Body\n- Validation Rules\n- Required Fields\n\nEnsure all inputs are validated.\n\n---\n\n# Response Design\n\nResponses should include:\n\n- HTTP Status Code\n- Response Body\n- Metadata\n- Pagination\n- Error Details\n\nMaintain a consistent response structure across all APIs.\n\n---\n\n# Error Handling\n\nStandardize:\n\n- Error Codes\n- Error Messages\n- Validation Errors\n- Authentication Errors\n- Authorization Errors\n- Server Errors\n\nError messages should be actionable and never expose sensitive information.\n\n---\n\n# Authentication & Security\n\nSupport:\n\n- OAuth 2.0\n- OpenID Connect\n- JWT Bearer Tokens\n- API Keys\n- Mutual TLS (where required)\n\nApply authorization checks to every protected endpoint.\n\n---\n\n# Versioning\n\nSupport:\n\n- URI Versioning\n- Header Versioning\n- Semantic Versioning\n\nDocument deprecation and migration strategies.\n\n---\n\n# Pagination & Filtering\n\nFor collections support:\n\n- Pagination\n- Sorting\n- Filtering\n- Search\n\nAvoid returning unbounded result sets.\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Resources consistently named\n- HTTP methods correctly applied\n- Request schema defined\n- Response schema defined\n- Error responses standardized\n- Security requirements implemented\n- Versioning strategy documented\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- Resources are undefined\n- API purpose is unclear\n- Security requirements are missing\n- Response format is inconsistent\n- Versioning strategy is absent\n\n---\n\n# Outputs\n\nGenerate:\n\n- API Design Specification\n- Endpoint Catalog\n- Request\u002FResponse Standards\n- Error Catalog\n- Versioning Strategy\n\n---\n\n# Rules\n\n- Prefer consistency over creativity.\n- Design APIs around resources.\n- Keep endpoints predictable.\n- Never expose internal implementation details.\n- Design for backward compatibility whenever possible.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- APIs are easy to understand\n- integrations are reliable\n- security is consistently applied\n- breaking changes are minimized\n- documentation matches implementation\n\n---\n\n# Related Skills\n\n- authentication\n- authorization\n- security\n- database\n- validation\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |",{"name":5,"author":24,"license":15,"version":25,"category":26,"priority":27,"description":7},"AI Business OS","1.0.0","shared","required","main","8ba4c8c0d58db28bdcfccd02e7d75b7a3cf70dc9","skills\u002Fshared\u002Fapi-design","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master","https:\u002F\u002Fai-web-master-cnbiz-web.vercel.app","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot","2026-11-14 20:43:00",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add panksooungman-dot\u002FAI-Web-Master --skill api-design",{"tool":41,"command":42},"bunx","bunx skills add panksooungman-dot\u002FAI-Web-Master --skill api-design",{"tool":44,"command":45},"pnpm","pnpm dlx skills add panksooungman-dot\u002FAI-Web-Master --skill api-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fshared\u002Fapi-design\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"README.md","REFERENCE","参考文档",134,"https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fshared\u002Fapi-design\u002FREADME.md",[56,63,70,77,84,91],{"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},"01M77S2FHFC73NY664GYHNHGE8","rollback","Plan, validate, and execute safe rollback procedures to restore a stable system state when deployments introduce critical issues.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Frollback\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},"01M77S2C5NW59NY9F939ECFVN0","release-note","Create clear, concise, and stakeholder-friendly release notes that communicate new features, improvements, fixes, breaking changes, and operational guidance for each release.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Frelease-note\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},"01M77S28YMHR597AZF39CR0CNG","monitoring","Continuously observe application health, performance, reliability, and business metrics after deployment to detect issues early and support operational excellence.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fmonitoring\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},"01M77S26FGE7P6W5MDSBQ1WTPV","maintenance","Maintain, improve, and support production systems after release through continuous monitoring, issue resolution, updates, and operational excellence.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fmaintenance\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},"01M77S24CZGKFZEXXS3N0B067G","deployment","Plan, validate, and execute application deployments safely and consistently across environments while minimizing downtime and deployment risk.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fdeployment\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M77S21AG798PAEH5HEVYBYF7","changelog","Maintain a structured, accurate, and versioned changelog that records all notable changes made to the project across releases.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fchangelog\u002FSKILL.md",[],[]]