[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79CY02W1ECX8V12WMZ95VYP":3,"skill-same:01M79CY02W1ECX8V12WMZ95VYP":52},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79CY02W1ECX8V12WMZ95VYP","construction-implementation",null,"Guidelines for code implementation, building features, and development work","JanMichaelSE\u002Fagentic-marketplace","JanMichaelSE","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55473580?v=4","01M79CW862FGHY91NG8DDRRFJC","Jan M Montalvo","01M79CW86M2NJQNRZ41VP9AJ51",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Fconstruction-implementation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: construction-implementation\ndescription: Guidelines for code implementation, building features, and development work\n---\n\n\n# Construction & Implementation Guidelines\n\nUse these guidelines when writing code, implementing features, or making changes.\n\n## Before Coding\n\n1. **Confirm understanding**: Verify requirements are clear\n2. **Review existing code**: Understand current patterns\n3. **Plan the approach**: Outline the implementation steps\n4. **Identify risks**: Note potential issues early\n\n## Implementation Approach\n\n### Start Small\n- Begin with the core functionality\n- Add complexity incrementally\n- Validate each step before proceeding\n\n### Follow Patterns\n- Match existing code style and conventions\n- Use established patterns from the codebase\n- Introduce new patterns only when justified\n\n### Keep Changes Focused\n- One logical change per commit\n- Avoid mixing refactoring with features\n- Separate formatting changes from logic changes\n\n## Code Generation Best Practices\n\n### Structure\n- Create files in appropriate locations\n- Follow project naming conventions\n- Organize code logically within files\n\n### Dependencies\n- Prefer existing dependencies over new ones\n- Check for compatible versions\n- Document why new dependencies are needed\n\n### Configuration\n- Use environment variables for environment-specific values\n- Provide sensible defaults\n- Document configuration options\n\n## Build and Test\n\n### Before Submitting\n1. Run the build to catch compilation errors\n2. Execute relevant tests\n3. Verify the feature works as expected\n4. Check for regressions in related areas\n\n### Test Coverage\n- Add tests for new functionality\n- Update tests for changed behavior\n- Maintain or improve coverage\n\n### Common Issues\n- Missing imports or dependencies\n- Type mismatches\n- Unhandled error cases\n- Race conditions in async code\n\n## Code Review Readiness\n\nEnsure your changes:\n- Have clear commit messages\n- Include necessary tests\n- Update relevant documentation\n- Don't include debug code or comments\n\n## Build Configuration Consistency\n\n### Match Existing Patterns\n- Match build configurations used by other services in the same codebase\n- Don't add unique build configurations unless there's a specific need\n- Remove build plugins that make a service inconsistent with others\n\n### Configuration Changes\n- Document why build configuration changes are needed\n- Test build changes across all affected modules\n","# Construction & Implementation Guidelines\n\nUse these guidelines when writing code, implementing features, or making changes.\n\n## Before Coding\n\n1. **Confirm understanding**: Verify requirements are clear\n2. **Review existing code**: Understand current patterns\n3. **Plan the approach**: Outline the implementation steps\n4. **Identify risks**: Note potential issues early\n\n## Implementation Approach\n\n### Start Small\n- Begin with the core functionality\n- Add complexity incrementally\n- Validate each step before proceeding\n\n### Follow Patterns\n- Match existing code style and conventions\n- Use established patterns from the codebase\n- Introduce new patterns only when justified\n\n### Keep Changes Focused\n- One logical change per commit\n- Avoid mixing refactoring with features\n- Separate formatting changes from logic changes\n\n## Code Generation Best Practices\n\n### Structure\n- Create files in appropriate locations\n- Follow project naming conventions\n- Organize code logically within files\n\n### Dependencies\n- Prefer existing dependencies over new ones\n- Check for compatible versions\n- Document why new dependencies are needed\n\n### Configuration\n- Use environment variables for environment-specific values\n- Provide sensible defaults\n- Document configuration options\n\n## Build and Test\n\n### Before Submitting\n1. Run the build to catch compilation errors\n2. Execute relevant tests\n3. Verify the feature works as expected\n4. Check for regressions in related areas\n\n### Test Coverage\n- Add tests for new functionality\n- Update tests for changed behavior\n- Maintain or improve coverage\n\n### Common Issues\n- Missing imports or dependencies\n- Type mismatches\n- Unhandled error cases\n- Race conditions in async code\n\n## Code Review Readiness\n\nEnsure your changes:\n- Have clear commit messages\n- Include necessary tests\n- Update relevant documentation\n- Don't include debug code or comments\n\n## Build Configuration Consistency\n\n### Match Existing Patterns\n- Match build configurations used by other services in the same codebase\n- Don't add unique build configurations unless there's a specific need\n- Remove build plugins that make a service inconsistent with others\n\n### Configuration Changes\n- Document why build configuration changes are needed\n- Test build changes across all affected modules\n",{"name":5,"description":7},"main","d9e185f133b5cbcd785341095a241d0c64d8310d","plugins\u002Fengineering\u002Fskills\u002Fconstruction-implementation",0,"https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace","https:\u002F\u002Fgithub.com\u002FJanMichaelSE","Software Developer | B.S. Computer Science ","2026-11-14 06:36:51",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add JanMichaelSE\u002Fagentic-marketplace --skill construction-implementation",{"tool":38,"command":39},"bunx","bunx skills add JanMichaelSE\u002Fagentic-marketplace --skill construction-implementation",{"tool":41,"command":42},"pnpm","pnpm dlx skills add JanMichaelSE\u002Fagentic-marketplace --skill construction-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Fconstruction-implementation\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",122,"https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Fconstruction-implementation\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79D1SP72BJKFZDHH2W0VT9G","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Local database with 79 searchable styles (88 catalog entries), 192 color palettes, 74 font pairings, 192 product types, 119 UX guidelines, 105 curated icon entries, 17 GSAP motion presets, and 25 chart types across 22 stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP, Three.js, and HTML\u002FCSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fui-ux\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79D1NPRNKYC0GNSPQBG02AD","figma-mcp","Implement or compare UI against Figma designs using an available Figma MCP integration. Use for Figma-backed implementation, design-token extraction, or visual-parity gap analysis; Figma MCP access is optional and must already be configured by the user.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fui-ux\u002Fskills\u002Ffigma-mcp\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79D1HW8E8EBKHYD0VRPAGDB","improve-codebase-architecture","Find evidence-based, active-change architecture improvements using shared design and domain-modeling guidance. Use when a user wants to reduce architectural friction, deepen a module, or make a current change safer, more testable, and easier to navigate.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsoftware-architecture\u002Fskills\u002Fimprove-codebase-architecture\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79D1E9DJ22BZN68FGNEY6H9","domain-modeling","Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing GLOSSARY.md or CONTEXT.md, or recording or editing an ADR.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsoftware-architecture\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79D1BWY6DT3SDNRVRJV73PH","codebase-design","Provide the shared vocabulary and discipline for designing deep modules with clear interfaces and seams. Use when a user wants to design or improve a module, find deepening opportunities, choose a seam, or make code more testable and AI-navigable.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsoftware-architecture\u002Fskills\u002Fcodebase-design\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79D176DSM0779MS5PCW022A","test-coverage-review","MUST invoke to review whether added or updated tests cover code changes in a diff. Checks new logic, branches, error paths, and regression risk, producing a change-to-test matrix. Use requirements-to-tests-traceability for acceptance-criteria mapping and orchestrated-review for bundled reviews.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Freview-toolkit\u002Fskills\u002Ftest-coverage-review\u002FSKILL.md",[],[]]