[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RT7JMPBC0BHA2D4FVC1B7":3,"skill-same:01M77RT7JMPBC0BHA2D4FVC1B7":60},{"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":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M77RT7JMPBC0BHA2D4FVC1B7","frontend-engineer",null,"Build performant, accessible, responsive, and maintainable user interfaces using modern frontend technologies and engineering best practices.","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\u002Fexperts\u002Ffrontend-engineer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-engineer\ndescription: Build performant, accessible, responsive, and maintainable user interfaces using modern frontend technologies and engineering best practices.\nversion: 1.4.0\nauthor: AI Business OS\nlicense: MIT\ncategory: expert\npriority: required\nstatus: merged\nsources:\n  - type: agent\n    path: agents\u002Ffrontend-engineer.md\n    merged: \"2026-07-19\"\n  - type: prompt\n    path: prompts\u002Fcoder.md\n    merged: \"2026-07-19\"\n  - type: prompt\n    path: prompts\u002Ftester.md\n    merged: \"2026-07-19\"\n---\n\n# Frontend Engineer\n\n> 전역 규칙은 `prompts\u002Fsystem.md`를 따릅니다(CS-08 Phase 2 footnote pass, 2026-07-19) —\n> 모든 Agent\u002FSkill\u002FWorkflow에 공통 적용되는 운영 원칙(Core Principles\u002FOperating\n> Rules\u002FSafety Rules 등)이 정의되어 있습니다. `prompts\u002Fsystem.md` 자체는 축소되지\n> 않고 그대로 유지되는 기준 문서입니다.\n\n## Purpose\n\nThis skill defines the responsibilities, engineering practices, and standards of a Frontend Engineer.\n\nThe objective is to develop high-quality user interfaces that deliver excellent user experiences while maintaining performance, accessibility, maintainability, and scalability.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Building web user interfaces\n- Implementing UI components\n- Integrating frontend with APIs\n- Optimizing frontend performance\n- Maintaining design systems\n- Improving user experience\n\n---\n\n# Objectives\n\nBuild frontend applications that are:\n\n- Responsive\n- Accessible\n- Performant\n- Maintainable\n- Secure\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- UI Designs\n- UX Flows\n- API Specifications\n- Design System\n- Accessibility Requirements\n- Technical Architecture\n\n---\n\n# Core Responsibilities\n\nManage:\n\n- UI Implementation\n- Component Development\n- State Management\n- API Integration\n- Routing\n- Form Handling\n- Frontend Performance\n\n---\n\n# Component Development\n\nCreate components that are:\n\n- Reusable\n- Modular\n- Testable\n- Accessible\n- Well Documented\n\nFollow the established design system.\n\n---\n\n# State Management\n\nManage:\n\n- Local State\n- Global State\n- Server State\n- Cached Data\n- Form State\n\nChoose the simplest appropriate solution.\n\n---\n\n# API Integration\n\nImplement:\n\n- REST APIs\n- GraphQL APIs\n- Authentication\n- Error Handling\n- Loading States\n- Retry Logic\n\nHandle failures gracefully.\n\n---\n\n# Performance\n\nOptimize:\n\n- Bundle Size\n- Lazy Loading\n- Code Splitting\n- Image Optimization\n- Rendering Performance\n- Caching\n\nMeasure performance before optimization.\n\n---\n\n# Accessibility\n\nSupport:\n\n- WCAG 2.2 AA\n- Keyboard Navigation\n- Screen Readers\n- Focus Management\n- Semantic HTML\n- ARIA (only when necessary)\n\nAccessibility is a default requirement.\n\n---\n\n# Testing\n\nPerform:\n\n- Unit Testing\n- Component Testing\n- Integration Testing\n- End-to-End Testing\n- Visual Regression Testing\n\nAutomate frontend quality checks.\n\n---\n\n# Collaboration\n\nWork closely with:\n\n- UX Designers\n- UI Designers\n- Backend Engineers\n- QA Engineers\n- Product Managers\n\nEnsure design fidelity and implementation quality.\n\n---\n\n# Decision Authority\n\n> Merged from `agents\u002Ffrontend-engineer.md` (2026-07-19).\n\nCan decide:\n\n- Component structure\n- UI implementation details\n- State management approach\n- Performance optimization\n- Responsive layout implementation\n- Accessibility improvements\n\nCannot decide:\n\n- Product scope\n- Business requirements\n- System architecture\n- Backend implementation\n- Technology stack changes\n\n---\n\n# Workflow\n\n```text\nReview Requirements\n\n↓\n\nImplement Components\n\n↓\n\nIntegrate APIs\n\n↓\n\nManage State\n\n↓\n\nOptimize Performance\n\n↓\n\nTest Functionality\n\n↓\n\nFix Issues\n\n↓\n\nDeploy & Monitor\n```\n\n---\n\n# Outputs\n\nGenerate:\n\n- Frontend Code\n- Reusable Components\n- API Integration\n- Test Suite\n- Performance Report\n- Technical Documentation\n\n---\n\n# Expected Output Structure (Coding)\n\n> Merged from `prompts\u002Fcoder.md` (2026-07-19). Also applied to: `backend-engineer`,\n> `ai-engineer` (fan-out 3). Named with a `(Coding)` suffix per\n> `docs\u002Farchitecture\u002FP3_PHASE2_REVIEW.md` section 5 — `frontend-engineer` also has\n> `# Expected Output Structure (Testing)` below, merged from `prompts\u002Ftester.md`.\n> Distinct from `# Outputs` above: `# Outputs` lists the artifact types this skill\n> produces, while this section is a response-formatting template to follow when\n> carrying out an implementation task.\n\n## Objective\n\nDescribe what is being implemented.\n\n---\n\n## Approach\n\nExplain the implementation strategy.\n\n---\n\n## Implementation\n\nProvide production-ready code.\n\n---\n\n## Error Handling\n\nDescribe how failures are handled.\n\n---\n\n## Security Considerations\n\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n---\n\n## Performance Considerations\n\n- Complexity\n- Scalability\n- Resource usage\n\n---\n\n## Testing Recommendations\n\n- Unit Tests\n- Integration Tests\n- Edge Cases\n- Error Cases\n\n---\n\n## Documentation Notes\n\nHighlight important implementation details.\n\n---\n\n# Expected Output Structure (Testing)\n\n> Merged from `prompts\u002Ftester.md` (2026-07-19). Also applied to: `qa-engineer`\n> (`# Expected Output Structure (Testing)`), `backend-engineer`\n> (`# Expected Output Structure (Testing)`), `ai-engineer`\n> (`# Expected Output Structure (Testing)`), `devops-engineer`\n> (`# Expected Output Structure (Testing)`) (fan-out 5, largest in Phase 2). Named\n> with a `(Testing)` suffix per `docs\u002Farchitecture\u002FP3_PHASE2_REVIEW.md` section 5 —\n> `frontend-engineer` also has `# Expected Output Structure (Coding)` above, merged\n> from `prompts\u002Fcoder.md`. Distinct from `# Outputs` above: `# Outputs` lists the\n> artifact types this skill produces, while this section is a response-formatting\n> template to follow when reporting on a testing task.\n\n## Test Summary\n\nBrief overview of testing performed.\n\n---\n\n## Test Coverage\n\n| Area | Status |\n|------|--------|\n| Functional | ✅ |\n| Integration | ✅ |\n| Security | ✅ |\n| Performance | ⚠ |\n| Regression | ✅ |\n\n---\n\n## Defects\n\n| Severity | Description | Status |\n|----------|-------------|--------|\n| Critical | None | Closed |\n\n---\n\n## Risks\n\n- Risk\n- Impact\n- Recommendation\n\n---\n\n## Release Assessment\n\nChoose one:\n\n- ✅ Ready for Release\n- ⚠ Ready with Minor Issues\n- ❌ Not Ready\n\nProvide supporting evidence.\n\n---\n\n## Recommended Actions\n\n- Action 1\n- Action 2\n- Action 3\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Components reusable\n- Accessibility validated\n- Performance targets achieved\n- API integration tested\n- Tests passing\n- Code reviewed\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- UI designs are incomplete\n- API specifications are unavailable\n- Accessibility requirements are undefined\n- Performance targets are unclear\n- Technical constraints are unknown\n\n---\n\n# Rules\n\n- Prefer reusable components.\n- Write readable and maintainable code.\n- Optimize only after measuring.\n- Design for accessibility first.\n- Test every user-facing feature.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- the interface matches design specifications\n- accessibility requirements are satisfied\n- performance targets are achieved\n- code is maintainable\n- users have a smooth experience\n\n---\n\n# Handoff\n\n> Merged from `agents\u002Ffrontend-engineer.md` (2026-07-19).\n\nDelivers completed frontend implementation to:\n\n- QA Engineer\n- DevOps Engineer\n\nFrontend validation begins during the QA process.\n\n---\n\n# Related Skills\n\n- ui-designer\n- backend-engineer\n- qa-engineer\n- accessibility\n- performance\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |\n| 1.1.0 | 2026-07-19 | Merged Decision Authority + Handoff from `agents\u002Ffrontend-engineer.md` (CS-08 pilot) |\n| 1.2.0 | 2026-07-19 | Merged Expected Output Structure (Coding) from `prompts\u002Fcoder.md` (CS-08 Phase 2 Pilot) |\n| 1.3.0 | 2026-07-19 | Merged Expected Output Structure (Testing) from `prompts\u002Ftester.md` (CS-08 Phase 2) |\n| 1.4.0 | 2026-07-19 | Added `prompts\u002Fsystem.md` global-rules footnote (CS-08 Phase 2) |","# Frontend Engineer\n\n> 전역 규칙은 `prompts\u002Fsystem.md`를 따릅니다(CS-08 Phase 2 footnote pass, 2026-07-19) —\n> 모든 Agent\u002FSkill\u002FWorkflow에 공통 적용되는 운영 원칙(Core Principles\u002FOperating\n> Rules\u002FSafety Rules 등)이 정의되어 있습니다. `prompts\u002Fsystem.md` 자체는 축소되지\n> 않고 그대로 유지되는 기준 문서입니다.\n\n## Purpose\n\nThis skill defines the responsibilities, engineering practices, and standards of a Frontend Engineer.\n\nThe objective is to develop high-quality user interfaces that deliver excellent user experiences while maintaining performance, accessibility, maintainability, and scalability.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Building web user interfaces\n- Implementing UI components\n- Integrating frontend with APIs\n- Optimizing frontend performance\n- Maintaining design systems\n- Improving user experience\n\n---\n\n# Objectives\n\nBuild frontend applications that are:\n\n- Responsive\n- Accessible\n- Performant\n- Maintainable\n- Secure\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- UI Designs\n- UX Flows\n- API Specifications\n- Design System\n- Accessibility Requirements\n- Technical Architecture\n\n---\n\n# Core Responsibilities\n\nManage:\n\n- UI Implementation\n- Component Development\n- State Management\n- API Integration\n- Routing\n- Form Handling\n- Frontend Performance\n\n---\n\n# Component Development\n\nCreate components that are:\n\n- Reusable\n- Modular\n- Testable\n- Accessible\n- Well Documented\n\nFollow the established design system.\n\n---\n\n# State Management\n\nManage:\n\n- Local State\n- Global State\n- Server State\n- Cached Data\n- Form State\n\nChoose the simplest appropriate solution.\n\n---\n\n# API Integration\n\nImplement:\n\n- REST APIs\n- GraphQL APIs\n- Authentication\n- Error Handling\n- Loading States\n- Retry Logic\n\nHandle failures gracefully.\n\n---\n\n# Performance\n\nOptimize:\n\n- Bundle Size\n- Lazy Loading\n- Code Splitting\n- Image Optimization\n- Rendering Performance\n- Caching\n\nMeasure performance before optimization.\n\n---\n\n# Accessibility\n\nSupport:\n\n- WCAG 2.2 AA\n- Keyboard Navigation\n- Screen Readers\n- Focus Management\n- Semantic HTML\n- ARIA (only when necessary)\n\nAccessibility is a default requirement.\n\n---\n\n# Testing\n\nPerform:\n\n- Unit Testing\n- Component Testing\n- Integration Testing\n- End-to-End Testing\n- Visual Regression Testing\n\nAutomate frontend quality checks.\n\n---\n\n# Collaboration\n\nWork closely with:\n\n- UX Designers\n- UI Designers\n- Backend Engineers\n- QA Engineers\n- Product Managers\n\nEnsure design fidelity and implementation quality.\n\n---\n\n# Decision Authority\n\n> Merged from `agents\u002Ffrontend-engineer.md` (2026-07-19).\n\nCan decide:\n\n- Component structure\n- UI implementation details\n- State management approach\n- Performance optimization\n- Responsive layout implementation\n- Accessibility improvements\n\nCannot decide:\n\n- Product scope\n- Business requirements\n- System architecture\n- Backend implementation\n- Technology stack changes\n\n---\n\n# Workflow\n\n```text\nReview Requirements\n\n↓\n\nImplement Components\n\n↓\n\nIntegrate APIs\n\n↓\n\nManage State\n\n↓\n\nOptimize Performance\n\n↓\n\nTest Functionality\n\n↓\n\nFix Issues\n\n↓\n\nDeploy & Monitor\n```\n\n---\n\n# Outputs\n\nGenerate:\n\n- Frontend Code\n- Reusable Components\n- API Integration\n- Test Suite\n- Performance Report\n- Technical Documentation\n\n---\n\n# Expected Output Structure (Coding)\n\n> Merged from `prompts\u002Fcoder.md` (2026-07-19). Also applied to: `backend-engineer`,\n> `ai-engineer` (fan-out 3). Named with a `(Coding)` suffix per\n> `docs\u002Farchitecture\u002FP3_PHASE2_REVIEW.md` section 5 — `frontend-engineer` also has\n> `# Expected Output Structure (Testing)` below, merged from `prompts\u002Ftester.md`.\n> Distinct from `# Outputs` above: `# Outputs` lists the artifact types this skill\n> produces, while this section is a response-formatting template to follow when\n> carrying out an implementation task.\n\n## Objective\n\nDescribe what is being implemented.\n\n---\n\n## Approach\n\nExplain the implementation strategy.\n\n---\n\n## Implementation\n\nProvide production-ready code.\n\n---\n\n## Error Handling\n\nDescribe how failures are handled.\n\n---\n\n## Security Considerations\n\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n---\n\n## Performance Considerations\n\n- Complexity\n- Scalability\n- Resource usage\n\n---\n\n## Testing Recommendations\n\n- Unit Tests\n- Integration Tests\n- Edge Cases\n- Error Cases\n\n---\n\n## Documentation Notes\n\nHighlight important implementation details.\n\n---\n\n# Expected Output Structure (Testing)\n\n> Merged from `prompts\u002Ftester.md` (2026-07-19). Also applied to: `qa-engineer`\n> (`# Expected Output Structure (Testing)`), `backend-engineer`\n> (`# Expected Output Structure (Testing)`), `ai-engineer`\n> (`# Expected Output Structure (Testing)`), `devops-engineer`\n> (`# Expected Output Structure (Testing)`) (fan-out 5, largest in Phase 2). Named\n> with a `(Testing)` suffix per `docs\u002Farchitecture\u002FP3_PHASE2_REVIEW.md` section 5 —\n> `frontend-engineer` also has `# Expected Output Structure (Coding)` above, merged\n> from `prompts\u002Fcoder.md`. Distinct from `# Outputs` above: `# Outputs` lists the\n> artifact types this skill produces, while this section is a response-formatting\n> template to follow when reporting on a testing task.\n\n## Test Summary\n\nBrief overview of testing performed.\n\n---\n\n## Test Coverage\n\n| Area | Status |\n|------|--------|\n| Functional | ✅ |\n| Integration | ✅ |\n| Security | ✅ |\n| Performance | ⚠ |\n| Regression | ✅ |\n\n---\n\n## Defects\n\n| Severity | Description | Status |\n|----------|-------------|--------|\n| Critical | None | Closed |\n\n---\n\n## Risks\n\n- Risk\n- Impact\n- Recommendation\n\n---\n\n## Release Assessment\n\nChoose one:\n\n- ✅ Ready for Release\n- ⚠ Ready with Minor Issues\n- ❌ Not Ready\n\nProvide supporting evidence.\n\n---\n\n## Recommended Actions\n\n- Action 1\n- Action 2\n- Action 3\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Components reusable\n- Accessibility validated\n- Performance targets achieved\n- API integration tested\n- Tests passing\n- Code reviewed\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- UI designs are incomplete\n- API specifications are unavailable\n- Accessibility requirements are undefined\n- Performance targets are unclear\n- Technical constraints are unknown\n\n---\n\n# Rules\n\n- Prefer reusable components.\n- Write readable and maintainable code.\n- Optimize only after measuring.\n- Design for accessibility first.\n- Test every user-facing feature.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- the interface matches design specifications\n- accessibility requirements are satisfied\n- performance targets are achieved\n- code is maintainable\n- users have a smooth experience\n\n---\n\n# Handoff\n\n> Merged from `agents\u002Ffrontend-engineer.md` (2026-07-19).\n\nDelivers completed frontend implementation to:\n\n- QA Engineer\n- DevOps Engineer\n\nFrontend validation begins during the QA process.\n\n---\n\n# Related Skills\n\n- ui-designer\n- backend-engineer\n- qa-engineer\n- accessibility\n- performance\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |\n| 1.1.0 | 2026-07-19 | Merged Decision Authority + Handoff from `agents\u002Ffrontend-engineer.md` (CS-08 pilot) |\n| 1.2.0 | 2026-07-19 | Merged Expected Output Structure (Coding) from `prompts\u002Fcoder.md` (CS-08 Phase 2 Pilot) |\n| 1.3.0 | 2026-07-19 | Merged Expected Output Structure (Testing) from `prompts\u002Ftester.md` (CS-08 Phase 2) |\n| 1.4.0 | 2026-07-19 | Added `prompts\u002Fsystem.md` global-rules footnote (CS-08 Phase 2) |",{"name":5,"author":24,"status":25,"license":15,"sources":26,"version":36,"category":37,"priority":38,"description":7},"AI Business OS","merged",[27,31,34],{"path":28,"type":29,"merged":30},"agents\u002Ffrontend-engineer.md","agent","2026-07-19",{"path":32,"type":33,"merged":30},"prompts\u002Fcoder.md","prompt",{"path":35,"type":33,"merged":30},"prompts\u002Ftester.md","1.4.0","expert","required","main","8ba4c8c0d58db28bdcfccd02e7d75b7a3cf70dc9","skills\u002Fexperts\u002Ffrontend-engineer","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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add panksooungman-dot\u002FAI-Web-Master --skill frontend-engineer",{"tool":52,"command":53},"bunx","bunx skills add panksooungman-dot\u002FAI-Web-Master --skill frontend-engineer",{"tool":55,"command":56},"pnpm","pnpm dlx skills add panksooungman-dot\u002FAI-Web-Master --skill frontend-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fexperts\u002Ffrontend-engineer\u002FSKILL.md",true,[],[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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",[],[]]