[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FFD1TE48KXA9CH8VXYCB78":3,"skill-same:01M7FFD1TE48KXA9CH8VXYCB78":46},{"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},"01M7FFD1TE48KXA9CH8VXYCB78","minimal-code-changes",null,"Enforce minimal, narrowly scoped modifications when implementing features, fixing bugs, changing tests, updating configuration, or otherwise editing an existing codebase. Use whenever code must be changed and the requested behavior can be delivered without broad cleanup, especially for requests mentioning minimal diffs, surgical changes, preserving existing structure, avoiding refactors, or not touching unrelated code. Prevent opportunistic renaming, reformatting, abstraction, dependency upgrades, architecture changes, and unrelated fixes. Do not block an explicitly requested refactor, but keep even that refactor strictly within the named scope.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fminimal-code-changes\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: minimal-code-changes\ndescription: >\n  Enforce minimal, narrowly scoped modifications when implementing features, fixing bugs,\n  changing tests, updating configuration, or otherwise editing an existing codebase. Use\n  whenever code must be changed and the requested behavior can be delivered without broad\n  cleanup, especially for requests mentioning minimal diffs, surgical changes, preserving\n  existing structure, avoiding refactors, or not touching unrelated code. Prevent\n  opportunistic renaming, reformatting, abstraction, dependency upgrades, architecture\n  changes, and unrelated fixes. Do not block an explicitly requested refactor, but keep even\n  that refactor strictly within the named scope.\n---\n\n# Minimal Code Changes\n\nImplement the requested behavior with the smallest correct semantic diff.\n\nTreat code outside the necessary change boundary as read-only. Set the default refactor\nbudget to zero. Do not improve code merely because an improvement becomes apparent while\nworking nearby.\n\nMinimal does not mean cryptic or fragile. Keep the patch correct, maintainable, and\nconsistent with the existing local style without expanding its scope.\n\n## Priorities\n\nApply these priorities in order:\n\n1. Satisfy the requested behavior correctly.\n2. Preserve existing behavior outside the request.\n3. Minimize the semantic and textual diff.\n4. Follow the codebase's existing local conventions.\n5. Improve elegance only within the lines that must change.\n\n## Phase 1 — Define the change contract\n\nBefore editing, identify:\n\n- The exact requested outcome.\n- The narrowest relevant file, symbol, function, component, or configuration entry.\n- The existing behavior that must remain unchanged.\n- The focused validation needed to prove the change.\n\nWhen the request is ambiguous, choose the least expansive reasonable interpretation and\nstate the assumption. Do not silently broaden the task.\n\n## Phase 2 — Inspect narrowly\n\nRead enough surrounding code to understand the target and its immediate dependencies.\nSearch for existing patterns that the patch should follow.\n\nDo not turn repository exploration into a cleanup exercise.\n\n## Phase 3 — Establish the change boundary\n\nUse this default boundary:\n\n- **Primary boundary:** the exact function, class, component, module, or configuration\n  entry responsible for the requested behavior.\n- **Secondary boundary:** immediate callers, dependencies, types, or tests only when the\n  primary change cannot work correctly without them.\n- **Outside the boundary:** read-only unless the user explicitly expands the scope.\n\nPrefer changing an existing condition, branch, argument, or local implementation over\nintroducing a new abstraction.\n\n## Phase 4 — Implement surgically\n\n- Edit the fewest files and lines reasonably possible.\n- Preserve existing names, control flow, public APIs, file locations, and architecture.\n- Reuse current dependencies and established local patterns.\n- Match nearby formatting instead of reformatting surrounding code.\n- Add comments or documentation only when required to explain new non-obvious behavior.\n- Preserve pre-existing user changes in the working tree.\n- Avoid destructive Git operations and never revert unrelated work.\n\n## Phase 5 — Validate narrowly\n\nRun the most focused relevant checks available, such as a targeted test, type check, lint\ncommand, or build for the affected package.\n\nAdd or modify only tests that directly verify the requested behavior. Do not rewrite broad\ntest suites, regenerate unrelated snapshots, or fix unrelated failures.\n\nIf an unrelated pre-existing issue blocks validation, report it separately. Do not repair\nit unless the requested change cannot be delivered safely without doing so.\n\n## Phase 6 — Verify the diff\n\nReview the final diff before finishing.\n\nFor every changed line, ask: **Can this line be justified directly by the requested\nbehavior, its focused validation, or a necessary compatibility constraint?**\n\nIf not, revert that line. Remove formatting churn, reordered imports, renamed variables,\ngenerated noise, and incidental cleanup.\n\n## Refactor gate\n\nPermit a refactor only when every condition below is true:\n\n1. It is directly necessary to implement the requested behavior correctly or to prevent a\n   regression introduced by the patch.\n2. No narrower implementation is reasonably available.\n3. It remains inside the smallest enclosing function, component, module, or explicitly\n   requested area.\n4. It preserves external behavior except for the requested change.\n5. It can be validated with focused checks.\n\nCode cleanliness, stylistic preference, duplication reduction, modernization, or future\nflexibility alone are not sufficient reasons.\n\nWhen a broader refactor is truly unavoidable, keep it as small as possible and explicitly\nexplain why it was required. Do not use it to include adjacent improvements.\n\n## Changes forbidden by default\n\nDo not perform any of the following unless explicitly requested or required by the\nrefactor gate:\n\n- Rename variables, functions, types, files, directories, or public symbols.\n- Move code between files or reorganize modules.\n- Extract helpers, introduce generalized abstractions, or redesign interfaces.\n- Replace design patterns, libraries, frameworks, or APIs.\n- Add, remove, or upgrade dependencies.\n- Change public contracts, schemas, data models, or configuration shapes.\n- Reformat untouched code or reorder imports across unrelated sections.\n- Run repository-wide formatters, linters with auto-fix, codemods, or generators that\n  create broad churn.\n- Fix unrelated bugs, warnings, type errors, security findings, spelling, comments, or\n  dead code.\n- Expand error handling beyond the path affected by the request.\n- Rewrite tests simply to make them cleaner.\n- Modify generated files when changing their source is sufficient.\n\nA serious unrelated issue may be reported as a separate follow-up, but must not be folded\ninto the patch without authorization unless leaving it untouched would make the requested\nimplementation immediately unsafe.\n\n## Tool discipline\n\n- Prefer targeted edits over bulk replacements.\n- Scope formatter, lint, build, and test commands to the affected file or package when\n  possible.\n- Inspect `git diff` or the equivalent before completion.\n- Distinguish pre-existing changes from changes made for the current request.\n- Do not alter lockfiles unless dependency resolution actually changed.\n- Do not regenerate artifacts merely because tooling makes it convenient.\n\n## Report\n\nKeep the final report focused:\n\n```\n## \u003Crequested change> — \u003Cfile or area>\n\n1. State what behavior changed and where.\n2. State which focused checks were run and their result.\n3. Mention an intentionally untouched adjacent issue only when it is important for the user to know.\n```\n\n## Examples\n\n### Add a timeout to one request\n\n**Do:** Pass the timeout through the existing client call and update the focused test.\n\n**Do not:** Introduce a new HTTP client factory, rename environment variables, centralize\nall request settings, or upgrade the HTTP library.\n\n### Fix a null-value crash in a parser\n\n**Do:** Add the narrowest guard at the failing path and add a regression test.\n\n**Do not:** Rewrite the parser, redesign its return type, rename neighboring fields, or\nclean up unrelated branches.\n\n### Add one field to an existing response\n\n**Do:** Update the responsible mapping, its type only if required, and focused tests.\n\n**Do not:** Reorganize the response layer, replace the serializer, or normalize every\nrelated endpoint.\n\n### Explicitly requested refactor\n\n**Do:** Refactor only the named service, component, or pattern and preserve behavior with\nfocused validation.\n\n**Do not:** extend the refactor into adjacent modules simply because they use similar\ncode.\n","# Minimal Code Changes\n\nImplement the requested behavior with the smallest correct semantic diff.\n\nTreat code outside the necessary change boundary as read-only. Set the default refactor\nbudget to zero. Do not improve code merely because an improvement becomes apparent while\nworking nearby.\n\nMinimal does not mean cryptic or fragile. Keep the patch correct, maintainable, and\nconsistent with the existing local style without expanding its scope.\n\n## Priorities\n\nApply these priorities in order:\n\n1. Satisfy the requested behavior correctly.\n2. Preserve existing behavior outside the request.\n3. Minimize the semantic and textual diff.\n4. Follow the codebase's existing local conventions.\n5. Improve elegance only within the lines that must change.\n\n## Phase 1 — Define the change contract\n\nBefore editing, identify:\n\n- The exact requested outcome.\n- The narrowest relevant file, symbol, function, component, or configuration entry.\n- The existing behavior that must remain unchanged.\n- The focused validation needed to prove the change.\n\nWhen the request is ambiguous, choose the least expansive reasonable interpretation and\nstate the assumption. Do not silently broaden the task.\n\n## Phase 2 — Inspect narrowly\n\nRead enough surrounding code to understand the target and its immediate dependencies.\nSearch for existing patterns that the patch should follow.\n\nDo not turn repository exploration into a cleanup exercise.\n\n## Phase 3 — Establish the change boundary\n\nUse this default boundary:\n\n- **Primary boundary:** the exact function, class, component, module, or configuration\n  entry responsible for the requested behavior.\n- **Secondary boundary:** immediate callers, dependencies, types, or tests only when the\n  primary change cannot work correctly without them.\n- **Outside the boundary:** read-only unless the user explicitly expands the scope.\n\nPrefer changing an existing condition, branch, argument, or local implementation over\nintroducing a new abstraction.\n\n## Phase 4 — Implement surgically\n\n- Edit the fewest files and lines reasonably possible.\n- Preserve existing names, control flow, public APIs, file locations, and architecture.\n- Reuse current dependencies and established local patterns.\n- Match nearby formatting instead of reformatting surrounding code.\n- Add comments or documentation only when required to explain new non-obvious behavior.\n- Preserve pre-existing user changes in the working tree.\n- Avoid destructive Git operations and never revert unrelated work.\n\n## Phase 5 — Validate narrowly\n\nRun the most focused relevant checks available, such as a targeted test, type check, lint\ncommand, or build for the affected package.\n\nAdd or modify only tests that directly verify the requested behavior. Do not rewrite broad\ntest suites, regenerate unrelated snapshots, or fix unrelated failures.\n\nIf an unrelated pre-existing issue blocks validation, report it separately. Do not repair\nit unless the requested change cannot be delivered safely without doing so.\n\n## Phase 6 — Verify the diff\n\nReview the final diff before finishing.\n\nFor every changed line, ask: **Can this line be justified directly by the requested\nbehavior, its focused validation, or a necessary compatibility constraint?**\n\nIf not, revert that line. Remove formatting churn, reordered imports, renamed variables,\ngenerated noise, and incidental cleanup.\n\n## Refactor gate\n\nPermit a refactor only when every condition below is true:\n\n1. It is directly necessary to implement the requested behavior correctly or to prevent a\n   regression introduced by the patch.\n2. No narrower implementation is reasonably available.\n3. It remains inside the smallest enclosing function, component, module, or explicitly\n   requested area.\n4. It preserves external behavior except for the requested change.\n5. It can be validated with focused checks.\n\nCode cleanliness, stylistic preference, duplication reduction, modernization, or future\nflexibility alone are not sufficient reasons.\n\nWhen a broader refactor is truly unavoidable, keep it as small as possible and explicitly\nexplain why it was required. Do not use it to include adjacent improvements.\n\n## Changes forbidden by default\n\nDo not perform any of the following unless explicitly requested or required by the\nrefactor gate:\n\n- Rename variables, functions, types, files, directories, or public symbols.\n- Move code between files or reorganize modules.\n- Extract helpers, introduce generalized abstractions, or redesign interfaces.\n- Replace design patterns, libraries, frameworks, or APIs.\n- Add, remove, or upgrade dependencies.\n- Change public contracts, schemas, data models, or configuration shapes.\n- Reformat untouched code or reorder imports across unrelated sections.\n- Run repository-wide formatters, linters with auto-fix, codemods, or generators that\n  create broad churn.\n- Fix unrelated bugs, warnings, type errors, security findings, spelling, comments, or\n  dead code.\n- Expand error handling beyond the path affected by the request.\n- Rewrite tests simply to make them cleaner.\n- Modify generated files when changing their source is sufficient.\n\nA serious unrelated issue may be reported as a separate follow-up, but must not be folded\ninto the patch without authorization unless leaving it untouched would make the requested\nimplementation immediately unsafe.\n\n## Tool discipline\n\n- Prefer targeted edits over bulk replacements.\n- Scope formatter, lint, build, and test commands to the affected file or package when\n  possible.\n- Inspect `git diff` or the equivalent before completion.\n- Distinguish pre-existing changes from changes made for the current request.\n- Do not alter lockfiles unless dependency resolution actually changed.\n- Do not regenerate artifacts merely because tooling makes it convenient.\n\n## Report\n\nKeep the final report focused:\n\n```\n## \u003Crequested change> — \u003Cfile or area>\n\n1. State what behavior changed and where.\n2. State which focused checks were run and their result.\n3. Mention an intentionally untouched adjacent issue only when it is important for the user to know.\n```\n\n## Examples\n\n### Add a timeout to one request\n\n**Do:** Pass the timeout through the existing client call and update the focused test.\n\n**Do not:** Introduce a new HTTP client factory, rename environment variables, centralize\nall request settings, or upgrade the HTTP library.\n\n### Fix a null-value crash in a parser\n\n**Do:** Add the narrowest guard at the failing path and add a regression test.\n\n**Do not:** Rewrite the parser, redesign its return type, rename neighboring fields, or\nclean up unrelated branches.\n\n### Add one field to an existing response\n\n**Do:** Update the responsible mapping, its type only if required, and focused tests.\n\n**Do not:** Reorganize the response layer, replace the serializer, or normalize every\nrelated endpoint.\n\n### Explicitly requested refactor\n\n**Do:** Refactor only the named service, component, or pattern and preserve behavior with\nfocused validation.\n\n**Do not:** extend the refactor into adjacent modules simply because they use similar\ncode.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","07-后端与架构\u002Fminimal-code-changes",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill minimal-code-changes",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill minimal-code-changes",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill minimal-code-changes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fminimal-code-changes\u002FSKILL.md",true,[],[47,54,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":55,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]