[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RZ24MTSGDVMJ8GGNWVY30":3,"skill-same:01M77RZ24MTSGDVMJ8GGNWVY30":49},{"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},"01M77RZ24MTSGDVMJ8GGNWVY30","architecture",null,"Design the software architecture for the project by defining system structure, modules, technologies, data flow, and architectural decisions before implementation begins.","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\u002Fworkflows\u002Fdevelopment\u002Farchitecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: architecture\ndescription: Design the software architecture for the project by defining system structure, modules, technologies, data flow, and architectural decisions before implementation begins.\nversion: 1.0.0\nauthor: AI Business OS\nlicense: MIT\ncategory: workflow\npriority: required\n---\n\n# Architecture\n\n## Purpose\n\nThis skill defines the overall software architecture for the project.\n\nIts objective is to create a scalable, maintainable, secure, and performant foundation before implementation begins.\n\nArchitecture decisions should support both current requirements and future growth.\n\n---\n\n# When to Use\n\nExecute after:\n\n- planning\u002Fprd\n- planning\u002Ffeature-planning\n- design\u002Fprototype\n\nExecute before:\n\n- frontend\n- backend\n- api\n- database\n\n---\n\n# Objectives\n\nDesign an architecture that defines:\n\n- System structure\n- Technology stack\n- Module boundaries\n- Data flow\n- Communication patterns\n- Security model\n- Deployment strategy\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Product Requirements Document\n- Feature Planning\n- User Flow\n- Technical Constraints\n- Business Goals\n- Prototype\n\n---\n\n# Architecture Principles\n\nFollow these principles:\n\n- Simplicity\n- Scalability\n- Maintainability\n- Reusability\n- Security\n- Performance\n- Observability\n\nAvoid unnecessary complexity.\n\n---\n\n# Technology Stack\n\nDefine:\n\n- Frontend Framework\n- Backend Framework\n- Database\n- Authentication\n- API Style\n- Hosting Platform\n- Storage\n- Monitoring\n\nExample:\n\n- Frontend: Next.js\n- Backend: Supabase\n- Database: PostgreSQL\n- Authentication: Supabase Auth\n- Deployment: Vercel\n\n---\n\n# System Structure\n\nDefine major layers.\n\nExample:\n\n```\nPresentation Layer\n\n↓\n\nApplication Layer\n\n↓\n\nDomain Layer\n\n↓\n\nInfrastructure Layer\n\n↓\n\nDatabase\n```\n\nKeep responsibilities separated.\n\n---\n\n# Module Design\n\nIdentify modules such as:\n\n- Authentication\n- User Management\n- Dashboard\n- Products\n- Orders\n- Payments\n- Notifications\n- Administration\n\nEach module should have a clear responsibility.\n\n---\n\n# Data Flow\n\nDocument:\n\n- Client Requests\n- Server Processing\n- Database Operations\n- API Communication\n- External Services\n\nVisualize end-to-end request flow.\n\n---\n\n# API Strategy\n\nSpecify:\n\n- REST\n- GraphQL\n- RPC\n\nDocument:\n\n- Versioning\n- Error Handling\n- Authentication\n- Rate Limiting\n\n---\n\n# Database Strategy\n\nDefine:\n\n- Entities\n- Relationships\n- Indexing\n- Constraints\n- Migration Strategy\n\nNormalize where appropriate.\n\n---\n\n# Security Architecture\n\nInclude:\n\n- Authentication\n- Authorization\n- Input Validation\n- Encryption\n- Secrets Management\n- CSRF Protection\n- XSS Prevention\n\nSecurity is mandatory.\n\n---\n\n# Performance Strategy\n\nPlan for:\n\n- Caching\n- Lazy Loading\n- Pagination\n- Image Optimization\n- Code Splitting\n- Query Optimization\n\nMeasure performance continuously.\n\n---\n\n# Scalability\n\nConsider:\n\n- Horizontal Scaling\n- Background Jobs\n- CDN\n- Queue Systems\n- Storage Growth\n\nDesign for future expansion.\n\n---\n\n# Error Handling\n\nDefine:\n\n- Error Categories\n- Logging Strategy\n- Retry Policy\n- User Feedback\n- Monitoring\n\nNever expose sensitive information.\n\n---\n\n# Workflow\n\n```\nReview Requirements\n\n↓\n\nChoose Technology Stack\n\n↓\n\nDesign System Structure\n\n↓\n\nDefine Modules\n\n↓\n\nDesign Data Flow\n\n↓\n\nPlan APIs\n\n↓\n\nPlan Database\n\n↓\n\nReview Security\n\n↓\n\nValidate Architecture\n\n↓\n\nApprove\n```\n\n---\n\n# Outputs\n\nGenerate:\n\n- Architecture Document\n- System Diagram\n- Module Diagram\n- Data Flow Diagram\n- Technology Stack\n- API Strategy\n- Security Plan\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Architecture supports requirements\n- Modules are well defined\n- Security is addressed\n- Scalability is considered\n- Performance strategy exists\n- Documentation is complete\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- Requirements are incomplete\n- Technology stack is undecided\n- Security requirements are unknown\n- External integrations are undefined\n- Critical business rules are missing\n\n---\n\n# Rules\n\n- Keep architecture simple.\n- Prefer existing proven patterns.\n- Minimize coupling.\n- Maximize cohesion.\n- Design for maintainability.\n- Document every major decision.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- architecture is clearly documented\n- module boundaries are defined\n- technology stack is approved\n- security strategy exists\n- implementation can begin confidently\n\n---\n\n# Next Skills\n\nInvoke:\n\n```\nfrontend\n\n↓\n\nbackend\n\n↓\n\napi\n\n↓\n\ndatabase\n```\n\n---\n\n# Related Skills\n\n- prd\n- feature-planning\n- prototype\n- frontend\n- backend\n- api\n- database\n- documentation\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |","# Architecture\n\n## Purpose\n\nThis skill defines the overall software architecture for the project.\n\nIts objective is to create a scalable, maintainable, secure, and performant foundation before implementation begins.\n\nArchitecture decisions should support both current requirements and future growth.\n\n---\n\n# When to Use\n\nExecute after:\n\n- planning\u002Fprd\n- planning\u002Ffeature-planning\n- design\u002Fprototype\n\nExecute before:\n\n- frontend\n- backend\n- api\n- database\n\n---\n\n# Objectives\n\nDesign an architecture that defines:\n\n- System structure\n- Technology stack\n- Module boundaries\n- Data flow\n- Communication patterns\n- Security model\n- Deployment strategy\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Product Requirements Document\n- Feature Planning\n- User Flow\n- Technical Constraints\n- Business Goals\n- Prototype\n\n---\n\n# Architecture Principles\n\nFollow these principles:\n\n- Simplicity\n- Scalability\n- Maintainability\n- Reusability\n- Security\n- Performance\n- Observability\n\nAvoid unnecessary complexity.\n\n---\n\n# Technology Stack\n\nDefine:\n\n- Frontend Framework\n- Backend Framework\n- Database\n- Authentication\n- API Style\n- Hosting Platform\n- Storage\n- Monitoring\n\nExample:\n\n- Frontend: Next.js\n- Backend: Supabase\n- Database: PostgreSQL\n- Authentication: Supabase Auth\n- Deployment: Vercel\n\n---\n\n# System Structure\n\nDefine major layers.\n\nExample:\n\n```\nPresentation Layer\n\n↓\n\nApplication Layer\n\n↓\n\nDomain Layer\n\n↓\n\nInfrastructure Layer\n\n↓\n\nDatabase\n```\n\nKeep responsibilities separated.\n\n---\n\n# Module Design\n\nIdentify modules such as:\n\n- Authentication\n- User Management\n- Dashboard\n- Products\n- Orders\n- Payments\n- Notifications\n- Administration\n\nEach module should have a clear responsibility.\n\n---\n\n# Data Flow\n\nDocument:\n\n- Client Requests\n- Server Processing\n- Database Operations\n- API Communication\n- External Services\n\nVisualize end-to-end request flow.\n\n---\n\n# API Strategy\n\nSpecify:\n\n- REST\n- GraphQL\n- RPC\n\nDocument:\n\n- Versioning\n- Error Handling\n- Authentication\n- Rate Limiting\n\n---\n\n# Database Strategy\n\nDefine:\n\n- Entities\n- Relationships\n- Indexing\n- Constraints\n- Migration Strategy\n\nNormalize where appropriate.\n\n---\n\n# Security Architecture\n\nInclude:\n\n- Authentication\n- Authorization\n- Input Validation\n- Encryption\n- Secrets Management\n- CSRF Protection\n- XSS Prevention\n\nSecurity is mandatory.\n\n---\n\n# Performance Strategy\n\nPlan for:\n\n- Caching\n- Lazy Loading\n- Pagination\n- Image Optimization\n- Code Splitting\n- Query Optimization\n\nMeasure performance continuously.\n\n---\n\n# Scalability\n\nConsider:\n\n- Horizontal Scaling\n- Background Jobs\n- CDN\n- Queue Systems\n- Storage Growth\n\nDesign for future expansion.\n\n---\n\n# Error Handling\n\nDefine:\n\n- Error Categories\n- Logging Strategy\n- Retry Policy\n- User Feedback\n- Monitoring\n\nNever expose sensitive information.\n\n---\n\n# Workflow\n\n```\nReview Requirements\n\n↓\n\nChoose Technology Stack\n\n↓\n\nDesign System Structure\n\n↓\n\nDefine Modules\n\n↓\n\nDesign Data Flow\n\n↓\n\nPlan APIs\n\n↓\n\nPlan Database\n\n↓\n\nReview Security\n\n↓\n\nValidate Architecture\n\n↓\n\nApprove\n```\n\n---\n\n# Outputs\n\nGenerate:\n\n- Architecture Document\n- System Diagram\n- Module Diagram\n- Data Flow Diagram\n- Technology Stack\n- API Strategy\n- Security Plan\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Architecture supports requirements\n- Modules are well defined\n- Security is addressed\n- Scalability is considered\n- Performance strategy exists\n- Documentation is complete\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- Requirements are incomplete\n- Technology stack is undecided\n- Security requirements are unknown\n- External integrations are undefined\n- Critical business rules are missing\n\n---\n\n# Rules\n\n- Keep architecture simple.\n- Prefer existing proven patterns.\n- Minimize coupling.\n- Maximize cohesion.\n- Design for maintainability.\n- Document every major decision.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- architecture is clearly documented\n- module boundaries are defined\n- technology stack is approved\n- security strategy exists\n- implementation can begin confidently\n\n---\n\n# Next Skills\n\nInvoke:\n\n```\nfrontend\n\n↓\n\nbackend\n\n↓\n\napi\n\n↓\n\ndatabase\n```\n\n---\n\n# Related Skills\n\n- prd\n- feature-planning\n- prototype\n- frontend\n- backend\n- api\n- database\n- documentation\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","workflow","required","main","8ba4c8c0d58db28bdcfccd02e7d75b7a3cf70dc9","skills\u002Fworkflows\u002Fdevelopment\u002Farchitecture","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 architecture",{"tool":41,"command":42},"bunx","bunx skills add panksooungman-dot\u002FAI-Web-Master --skill architecture",{"tool":44,"command":45},"pnpm","pnpm dlx skills add panksooungman-dot\u002FAI-Web-Master --skill architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fdevelopment\u002Farchitecture\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]