[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RVG6ADSZX0FCRV1Y8CN7K":3,"skill-same:01M77RVG6ADSZX0FCRV1Y8CN7K":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},"01M77RVG6ADSZX0FCRV1Y8CN7K","coding-standards",null,"Define coding standards, naming conventions, formatting rules, code quality expectations, and maintainability principles across all software projects.","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\u002Fcoding-standards\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: coding-standards\ndescription: Define coding standards, naming conventions, formatting rules, code quality expectations, and maintainability principles across all software projects.\nversion: 1.0.0\nauthor: AI Business OS\nlicense: MIT\ncategory: shared\npriority: required\n---\n\n# Coding Standards\n\n## Purpose\n\nThis skill establishes consistent coding standards that improve readability, maintainability, quality, and collaboration across all software projects.\n\nThese standards are language-agnostic and should be adapted to each project's ecosystem.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Starting a new project\n- Writing production code\n- Reviewing pull requests\n- Refactoring existing code\n- Defining engineering guidelines\n- Onboarding new developers\n\n---\n\n# Objectives\n\nEnsure code is:\n\n- Readable\n- Consistent\n- Maintainable\n- Testable\n- Secure\n- Easy to review\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Project Requirements\n- Architecture Guidelines\n- Programming Language\n- Framework Conventions\n- Team Standards\n\n---\n\n# Naming Conventions\n\nUse meaningful names for:\n\n- Variables\n- Constants\n- Functions\n- Methods\n- Classes\n- Interfaces\n- Files\n- Directories\n\nAvoid abbreviations unless they are industry standard.\n\n---\n\n# Code Organization\n\nOrganize code into:\n\n- Modules\n- Packages\n- Components\n- Services\n- Utilities\n- Configuration\n- Tests\n\nFollow the Single Responsibility Principle.\n\n---\n\n# Formatting Standards\n\nMaintain consistent:\n\n- Indentation\n- Line Length\n- Blank Lines\n- Import Order\n- File Structure\n- Comment Style\n\nAutomate formatting with project-approved tools.\n\n---\n\n# Documentation\n\nDocument:\n\n- Public APIs\n- Complex Business Logic\n- Configuration\n- Architectural Decisions\n- Usage Examples\n\nPrefer self-documenting code over excessive comments.\n\n---\n\n# Error Handling\n\nEnsure:\n\n- Exceptions are meaningful\n- Errors are logged appropriately\n- Sensitive information is never exposed\n- Failures are handled gracefully\n\n---\n\n# Code Quality\n\nRequire:\n\n- Small Functions\n- Low Cyclomatic Complexity\n- High Cohesion\n- Loose Coupling\n- Minimal Duplication\n\nRefactor continuously to improve maintainability.\n\n---\n\n# Testing\n\nCode should include:\n\n- Unit Tests\n- Integration Tests\n- Meaningful Test Names\n- Deterministic Test Data\n\nDesign code to be testable from the beginning.\n\n---\n\n# Code Review Checklist\n\nVerify:\n\n- Naming conventions followed\n- Formatting consistent\n- Business logic correct\n- Tests included\n- Documentation updated\n- Security considerations addressed\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Linter passes\n- Formatter applied\n- Tests pass\n- No duplicated code\n- Documentation updated\n- Static analysis completed\n\n---\n\n# Failure Conditions\n\nStop if:\n\n- Standards conflict\n- Code is inconsistent\n- Tests are missing\n- Documentation is incomplete\n- Security concerns are unresolved\n\n---\n\n# Outputs\n\nGenerate:\n\n- Coding Standards Guide\n- Review Checklist\n- Naming Convention Guide\n- Quality Checklist\n\n---\n\n# Rules\n\n- Prefer readability over cleverness.\n- Keep functions focused.\n- Eliminate duplicated logic.\n- Use automated formatting.\n- Treat code reviews as mandatory.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- code is easy to understand\n- style is consistent across the project\n- maintenance costs are reduced\n- reviews are efficient\n- software quality continuously improves\n\n---\n\n# Related Skills\n\n- documentation\n- testing\n- validation\n- api-design\n- error-handling\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |","# Coding Standards\n\n## Purpose\n\nThis skill establishes consistent coding standards that improve readability, maintainability, quality, and collaboration across all software projects.\n\nThese standards are language-agnostic and should be adapted to each project's ecosystem.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Starting a new project\n- Writing production code\n- Reviewing pull requests\n- Refactoring existing code\n- Defining engineering guidelines\n- Onboarding new developers\n\n---\n\n# Objectives\n\nEnsure code is:\n\n- Readable\n- Consistent\n- Maintainable\n- Testable\n- Secure\n- Easy to review\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Project Requirements\n- Architecture Guidelines\n- Programming Language\n- Framework Conventions\n- Team Standards\n\n---\n\n# Naming Conventions\n\nUse meaningful names for:\n\n- Variables\n- Constants\n- Functions\n- Methods\n- Classes\n- Interfaces\n- Files\n- Directories\n\nAvoid abbreviations unless they are industry standard.\n\n---\n\n# Code Organization\n\nOrganize code into:\n\n- Modules\n- Packages\n- Components\n- Services\n- Utilities\n- Configuration\n- Tests\n\nFollow the Single Responsibility Principle.\n\n---\n\n# Formatting Standards\n\nMaintain consistent:\n\n- Indentation\n- Line Length\n- Blank Lines\n- Import Order\n- File Structure\n- Comment Style\n\nAutomate formatting with project-approved tools.\n\n---\n\n# Documentation\n\nDocument:\n\n- Public APIs\n- Complex Business Logic\n- Configuration\n- Architectural Decisions\n- Usage Examples\n\nPrefer self-documenting code over excessive comments.\n\n---\n\n# Error Handling\n\nEnsure:\n\n- Exceptions are meaningful\n- Errors are logged appropriately\n- Sensitive information is never exposed\n- Failures are handled gracefully\n\n---\n\n# Code Quality\n\nRequire:\n\n- Small Functions\n- Low Cyclomatic Complexity\n- High Cohesion\n- Loose Coupling\n- Minimal Duplication\n\nRefactor continuously to improve maintainability.\n\n---\n\n# Testing\n\nCode should include:\n\n- Unit Tests\n- Integration Tests\n- Meaningful Test Names\n- Deterministic Test Data\n\nDesign code to be testable from the beginning.\n\n---\n\n# Code Review Checklist\n\nVerify:\n\n- Naming conventions followed\n- Formatting consistent\n- Business logic correct\n- Tests included\n- Documentation updated\n- Security considerations addressed\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Linter passes\n- Formatter applied\n- Tests pass\n- No duplicated code\n- Documentation updated\n- Static analysis completed\n\n---\n\n# Failure Conditions\n\nStop if:\n\n- Standards conflict\n- Code is inconsistent\n- Tests are missing\n- Documentation is incomplete\n- Security concerns are unresolved\n\n---\n\n# Outputs\n\nGenerate:\n\n- Coding Standards Guide\n- Review Checklist\n- Naming Convention Guide\n- Quality Checklist\n\n---\n\n# Rules\n\n- Prefer readability over cleverness.\n- Keep functions focused.\n- Eliminate duplicated logic.\n- Use automated formatting.\n- Treat code reviews as mandatory.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- code is easy to understand\n- style is consistent across the project\n- maintenance costs are reduced\n- reviews are efficient\n- software quality continuously improves\n\n---\n\n# Related Skills\n\n- documentation\n- testing\n- validation\n- api-design\n- error-handling\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\u002Fcoding-standards","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 coding-standards",{"tool":41,"command":42},"bunx","bunx skills add panksooungman-dot\u002FAI-Web-Master --skill coding-standards",{"tool":44,"command":45},"pnpm","pnpm dlx skills add panksooungman-dot\u002FAI-Web-Master --skill coding-standards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fshared\u002Fcoding-standards\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"README.md","REFERENCE","参考文档",155,"https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fshared\u002Fcoding-standards\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",[],[]]