[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RZDP6VJCPTSQQVFD55ZRW":3,"skill-same:01M77RZDP6VJCPTSQQVFD55ZRW":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},"01M77RZDP6VJCPTSQQVFD55ZRW","frontend",null,"Implement responsive, accessible, and maintainable frontend applications based on the approved architecture, design system, and UI specifications.","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\u002Ffrontend\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend\ndescription: Implement responsive, accessible, and maintainable frontend applications based on the approved architecture, design system, and UI specifications.\nversion: 1.0.0\nauthor: AI Business OS\nlicense: MIT\ncategory: workflow\npriority: required\n---\n\n# Frontend Development\n\n## Purpose\n\nThis skill defines how frontend applications are implemented within AI Business OS.\n\nThe objective is to transform approved designs into production-ready interfaces that are responsive, accessible, performant, and maintainable.\n\nFrontend implementation must strictly follow the Architecture and Design System.\n\n---\n\n# When to Use\n\nExecute after:\n\n- development\u002Farchitecture\n- design\u002Fui-design\n- design\u002Fdesign-system\n- design\u002Fprototype\n\nExecute before:\n\n- backend\n- api\n- integration\n\n---\n\n# Objectives\n\nBuild frontend applications that are:\n\n- Responsive\n- Accessible\n- Maintainable\n- Reusable\n- Performant\n- Scalable\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Architecture Document\n- PRD\n- User Stories\n- UI Design\n- Design System\n- Prototype\n\n---\n\n# Technology Standards\n\nPrefer:\n\n- Next.js\n- React\n- TypeScript\n- Tailwind CSS\n- shadcn\u002Fui\n\nUse project standards whenever defined.\n\n---\n\n# Component Architecture\n\nCreate reusable components.\n\nStructure example:\n\n```\ncomponents\u002F\n├── ui\u002F\n├── layout\u002F\n├── forms\u002F\n├── navigation\u002F\n├── dashboard\u002F\n└── shared\u002F\n```\n\nKeep components focused on a single responsibility.\n\n---\n\n# Page Structure\n\nOrganize pages by feature.\n\nExample:\n\n```\napp\u002F\n\ndashboard\u002F\n\nproducts\u002F\n\norders\u002F\n\nsettings\u002F\n```\n\nAvoid unnecessary nesting.\n\n---\n\n# State Management\n\nUse the simplest appropriate solution.\n\nPriority:\n\n1. Local State\n2. Context\n3. Server State\n4. Global State\n\nAvoid unnecessary global state.\n\n---\n\n# Forms\n\nEvery form should include:\n\n- Validation\n- Error Messages\n- Loading State\n- Success State\n- Accessibility Support\n\nNever trust client validation alone.\n\n---\n\n# Responsive Design\n\nSupport:\n\n- Mobile\n- Tablet\n- Desktop\n\nVerify:\n\n- Layout\n- Typography\n- Navigation\n- Images\n- Tables\n\n---\n\n# Accessibility\n\nEnsure:\n\n- Semantic HTML\n- Keyboard Navigation\n- ARIA Labels\n- Focus States\n- Color Contrast\n\nTarget WCAG AA compliance.\n\n---\n\n# Performance\n\nOptimize:\n\n- Images\n- Fonts\n- Code Splitting\n- Lazy Loading\n- Bundle Size\n- Rendering\n\nMeasure before optimizing.\n\n---\n\n# Error Handling\n\nProvide:\n\n- Error Boundaries\n- Empty States\n- Loading Indicators\n- Retry Options\n- Friendly Messages\n\nNever expose technical errors directly.\n\n---\n\n# Code Quality\n\nRequirements:\n\n- TypeScript Strict Mode\n- ESLint\n- Prettier\n- Reusable Components\n- Clear Naming\n- Small Functions\n\n---\n\n# Testing\n\nVerify:\n\n- Rendering\n- User Interaction\n- Form Validation\n- Navigation\n- Responsive Layout\n- Accessibility\n\n---\n\n# Workflow\n\n```\nReview Architecture\n\n↓\n\nReview Design\n\n↓\n\nCreate Components\n\n↓\n\nBuild Pages\n\n↓\n\nImplement State\n\n↓\n\nImplement Forms\n\n↓\n\nResponsive Review\n\n↓\n\nAccessibility Review\n\n↓\n\nTesting\n\n↓\n\nReady for Backend Integration\n```\n\n---\n\n# Outputs\n\nGenerate:\n\n- Frontend Components\n- Pages\n- Layouts\n- Forms\n- Responsive UI\n- Test Results\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Components reusable\n- Responsive layouts complete\n- Accessibility verified\n- No TypeScript errors\n- Lint passes\n- Tests pass\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- Design is incomplete\n- API contract is missing\n- Architecture conflicts exist\n- Business rules are unclear\n- Required assets are unavailable\n\n---\n\n# Rules\n\n- Follow the Design System.\n- Prefer composition over duplication.\n- Keep components reusable.\n- Write readable code.\n- Optimize only after correctness.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- UI matches approved designs\n- components are reusable\n- responsive behavior is correct\n- accessibility standards are met\n- frontend is ready for backend integration\n\n---\n\n# Next Skills\n\nInvoke:\n\n```\nbackend\n\n↓\n\napi\n\n↓\n\nintegration\n```\n\n---\n\n# Related Skills\n\n- architecture\n- ui-design\n- design-system\n- prototype\n- backend\n- api\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |","# Frontend Development\n\n## Purpose\n\nThis skill defines how frontend applications are implemented within AI Business OS.\n\nThe objective is to transform approved designs into production-ready interfaces that are responsive, accessible, performant, and maintainable.\n\nFrontend implementation must strictly follow the Architecture and Design System.\n\n---\n\n# When to Use\n\nExecute after:\n\n- development\u002Farchitecture\n- design\u002Fui-design\n- design\u002Fdesign-system\n- design\u002Fprototype\n\nExecute before:\n\n- backend\n- api\n- integration\n\n---\n\n# Objectives\n\nBuild frontend applications that are:\n\n- Responsive\n- Accessible\n- Maintainable\n- Reusable\n- Performant\n- Scalable\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Architecture Document\n- PRD\n- User Stories\n- UI Design\n- Design System\n- Prototype\n\n---\n\n# Technology Standards\n\nPrefer:\n\n- Next.js\n- React\n- TypeScript\n- Tailwind CSS\n- shadcn\u002Fui\n\nUse project standards whenever defined.\n\n---\n\n# Component Architecture\n\nCreate reusable components.\n\nStructure example:\n\n```\ncomponents\u002F\n├── ui\u002F\n├── layout\u002F\n├── forms\u002F\n├── navigation\u002F\n├── dashboard\u002F\n└── shared\u002F\n```\n\nKeep components focused on a single responsibility.\n\n---\n\n# Page Structure\n\nOrganize pages by feature.\n\nExample:\n\n```\napp\u002F\n\ndashboard\u002F\n\nproducts\u002F\n\norders\u002F\n\nsettings\u002F\n```\n\nAvoid unnecessary nesting.\n\n---\n\n# State Management\n\nUse the simplest appropriate solution.\n\nPriority:\n\n1. Local State\n2. Context\n3. Server State\n4. Global State\n\nAvoid unnecessary global state.\n\n---\n\n# Forms\n\nEvery form should include:\n\n- Validation\n- Error Messages\n- Loading State\n- Success State\n- Accessibility Support\n\nNever trust client validation alone.\n\n---\n\n# Responsive Design\n\nSupport:\n\n- Mobile\n- Tablet\n- Desktop\n\nVerify:\n\n- Layout\n- Typography\n- Navigation\n- Images\n- Tables\n\n---\n\n# Accessibility\n\nEnsure:\n\n- Semantic HTML\n- Keyboard Navigation\n- ARIA Labels\n- Focus States\n- Color Contrast\n\nTarget WCAG AA compliance.\n\n---\n\n# Performance\n\nOptimize:\n\n- Images\n- Fonts\n- Code Splitting\n- Lazy Loading\n- Bundle Size\n- Rendering\n\nMeasure before optimizing.\n\n---\n\n# Error Handling\n\nProvide:\n\n- Error Boundaries\n- Empty States\n- Loading Indicators\n- Retry Options\n- Friendly Messages\n\nNever expose technical errors directly.\n\n---\n\n# Code Quality\n\nRequirements:\n\n- TypeScript Strict Mode\n- ESLint\n- Prettier\n- Reusable Components\n- Clear Naming\n- Small Functions\n\n---\n\n# Testing\n\nVerify:\n\n- Rendering\n- User Interaction\n- Form Validation\n- Navigation\n- Responsive Layout\n- Accessibility\n\n---\n\n# Workflow\n\n```\nReview Architecture\n\n↓\n\nReview Design\n\n↓\n\nCreate Components\n\n↓\n\nBuild Pages\n\n↓\n\nImplement State\n\n↓\n\nImplement Forms\n\n↓\n\nResponsive Review\n\n↓\n\nAccessibility Review\n\n↓\n\nTesting\n\n↓\n\nReady for Backend Integration\n```\n\n---\n\n# Outputs\n\nGenerate:\n\n- Frontend Components\n- Pages\n- Layouts\n- Forms\n- Responsive UI\n- Test Results\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Components reusable\n- Responsive layouts complete\n- Accessibility verified\n- No TypeScript errors\n- Lint passes\n- Tests pass\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- Design is incomplete\n- API contract is missing\n- Architecture conflicts exist\n- Business rules are unclear\n- Required assets are unavailable\n\n---\n\n# Rules\n\n- Follow the Design System.\n- Prefer composition over duplication.\n- Keep components reusable.\n- Write readable code.\n- Optimize only after correctness.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- UI matches approved designs\n- components are reusable\n- responsive behavior is correct\n- accessibility standards are met\n- frontend is ready for backend integration\n\n---\n\n# Next Skills\n\nInvoke:\n\n```\nbackend\n\n↓\n\napi\n\n↓\n\nintegration\n```\n\n---\n\n# Related Skills\n\n- architecture\n- ui-design\n- design-system\n- prototype\n- backend\n- api\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\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\u002Ffrontend","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 frontend",{"tool":41,"command":42},"bunx","bunx skills add panksooungman-dot\u002FAI-Web-Master --skill frontend",{"tool":44,"command":45},"pnpm","pnpm dlx skills add panksooungman-dot\u002FAI-Web-Master --skill frontend","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fdevelopment\u002Ffrontend\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",[],[]]