[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EX7XMMWHZR1S6B6HRC7X7S":3,"skill-same:01M7EX7XMMWHZR1S6B6HRC7X7S":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},"01M7EX7XMMWHZR1S6B6HRC7X7S","backend-module-standards",null,"Enforce this repository's TypeScript backend module architecture standards. Use whenever creating, modifying, refactoring, or reviewing backend code under `server\u002F`, including routes, services, modules, repositories, shared backend code, and backend tests. Do not apply these rules to frontend code or non-backend scaffolding.","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\u002F05-技能与代理开发\u002Fbackend-module-standards\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: backend-module-standards\ndescription: Enforce this repository's TypeScript backend module architecture standards. Use whenever creating, modifying, refactoring, or reviewing backend code under `server\u002F`, including routes, services, modules, repositories, shared backend code, and backend tests. Do not apply these rules to frontend code or non-backend scaffolding.\n---\n\n# Backend Module Standards\n\nApply these rules after the repository's basic scaffolding is in place. Limit them to backend code under `server\u002F`. Preserve the requested task scope: make touched and newly generated backend code compliant without performing an unrelated repository-wide migration.\n\n## Inspect before editing\n\n1. Identify the owning feature module and its existing barrel, services, routes, and tests.\n2. Search for existing shared types, interfaces, and utilities before adding any definition.\n3. Search for every consumer before changing a module's public exports.\n\n## Organize backend modules\n\n- Place each feature in `server\u002Fmodules\u002F\u003Cfeature>\u002F`.\n- Use TypeScript for every file inside `server\u002Fmodules\u002F`. Do not add JavaScript backend module files.\n- When touched JavaScript utilities belong to the work, migrate them to TypeScript. Place a one-use utility in its sole component; place a utility used in at least two locations in `server\u002Fshared\u002Futils.ts`.\n- Give every feature module an `index.ts` barrel that exposes only its required public API.\n- Import another feature module only through that module's `index.ts`. Never deep-import another module's routes, services, repositories, adapters, or internal files.\n- Treat `server\u002Fshared\u002F` as the shared module. Keep shared definitions in `server\u002Fshared\u002Ftypes.ts`, `server\u002Fshared\u002Finterfaces.ts`, and `server\u002Fshared\u002Futils.ts`, and expose only required cross-module members through its barrel.\n- Do not create module-local `types.ts`, `interfaces.ts`, or `utils.ts` files.\n- Keep module-private implementation details unexported.\n\n## Place types, interfaces, and utilities\n\n- Use `type` by default. Use `interface` only for a contract that a class is intended to implement.\n- Use `export type` for type exports and `import type` for type-only imports.\n- Define a type, interface, or utility directly in its component file when it is used in only that location.\n- Move a type or interface used in two or more locations to `server\u002Fshared\u002Ftypes.ts` or `server\u002Fshared\u002Finterfaces.ts` as appropriate.\n- Move a utility used in two or more locations to `server\u002Fshared\u002Futils.ts`.\n- Do not duplicate an existing shared definition to avoid importing it.\n- Give every shared type, interface, and utility a detailed doc comment explaining its behavior, valid usage, and important constraints.\n- Keep related shared definitions adjacent. Introduce each group with `\u002F\u002F----------------- DESCRIPTION OF GROUP ------------` and separate unrelated groups with `\u002F\u002F ---------------------------`.\n\n## Design exports deliberately\n\n- Export a function or variable at its declaration, such as `export function loadSession()`. Do not collect ordinary exports at the end of an implementation file.\n- The preceding rule does not apply to `index.ts` barrel exports.\n- For every exported component, add a brief comment at its definition naming the consuming module or modules and explaining why they use it. Update the comment when consumers change.\n- Do not export speculative helpers, implementation details, or symbols that have no cross-file consumer.\n- Use clear, specific names for functions and variables. Add a concise comment anywhere intent, ordering, invariants, or edge cases could be confusing.\n\n## Keep routes thin\n\n- Parse and validate transport input in the route, convert it to the service's expected typed input, call one or more services, and translate the result to the response.\n- Keep business logic, persistence, filesystem work, subprocess execution, and orchestration out of routes.\n- Allow a service to call other services. Access another module's services through that module's public barrel contract.\n\n## Test within the module\n\n- Put feature tests in `server\u002Fmodules\u002F\u003Cfeature>\u002Ftests\u002F`.\n- Add or update unit tests for changed service behavior and route parsing.\n\n## Verify the result\n\nBefore finishing:\n\n1. Confirm all cross-module imports use `index.ts` barrels and all public exports are necessary and documented.\n2. Confirm shared definitions follow the one-use versus multiple-use placement rule and grouping-comment format.\n3. Confirm routes only parse, call services, and format responses.\n4. Run the narrow relevant tests, then `npm run build`, `npm run typecheck`, and `npm run lint` when the task scope and environment permit.\n","# Backend Module Standards\n\nApply these rules after the repository's basic scaffolding is in place. Limit them to backend code under `server\u002F`. Preserve the requested task scope: make touched and newly generated backend code compliant without performing an unrelated repository-wide migration.\n\n## Inspect before editing\n\n1. Identify the owning feature module and its existing barrel, services, routes, and tests.\n2. Search for existing shared types, interfaces, and utilities before adding any definition.\n3. Search for every consumer before changing a module's public exports.\n\n## Organize backend modules\n\n- Place each feature in `server\u002Fmodules\u002F\u003Cfeature>\u002F`.\n- Use TypeScript for every file inside `server\u002Fmodules\u002F`. Do not add JavaScript backend module files.\n- When touched JavaScript utilities belong to the work, migrate them to TypeScript. Place a one-use utility in its sole component; place a utility used in at least two locations in `server\u002Fshared\u002Futils.ts`.\n- Give every feature module an `index.ts` barrel that exposes only its required public API.\n- Import another feature module only through that module's `index.ts`. Never deep-import another module's routes, services, repositories, adapters, or internal files.\n- Treat `server\u002Fshared\u002F` as the shared module. Keep shared definitions in `server\u002Fshared\u002Ftypes.ts`, `server\u002Fshared\u002Finterfaces.ts`, and `server\u002Fshared\u002Futils.ts`, and expose only required cross-module members through its barrel.\n- Do not create module-local `types.ts`, `interfaces.ts`, or `utils.ts` files.\n- Keep module-private implementation details unexported.\n\n## Place types, interfaces, and utilities\n\n- Use `type` by default. Use `interface` only for a contract that a class is intended to implement.\n- Use `export type` for type exports and `import type` for type-only imports.\n- Define a type, interface, or utility directly in its component file when it is used in only that location.\n- Move a type or interface used in two or more locations to `server\u002Fshared\u002Ftypes.ts` or `server\u002Fshared\u002Finterfaces.ts` as appropriate.\n- Move a utility used in two or more locations to `server\u002Fshared\u002Futils.ts`.\n- Do not duplicate an existing shared definition to avoid importing it.\n- Give every shared type, interface, and utility a detailed doc comment explaining its behavior, valid usage, and important constraints.\n- Keep related shared definitions adjacent. Introduce each group with `\u002F\u002F----------------- DESCRIPTION OF GROUP ------------` and separate unrelated groups with `\u002F\u002F ---------------------------`.\n\n## Design exports deliberately\n\n- Export a function or variable at its declaration, such as `export function loadSession()`. Do not collect ordinary exports at the end of an implementation file.\n- The preceding rule does not apply to `index.ts` barrel exports.\n- For every exported component, add a brief comment at its definition naming the consuming module or modules and explaining why they use it. Update the comment when consumers change.\n- Do not export speculative helpers, implementation details, or symbols that have no cross-file consumer.\n- Use clear, specific names for functions and variables. Add a concise comment anywhere intent, ordering, invariants, or edge cases could be confusing.\n\n## Keep routes thin\n\n- Parse and validate transport input in the route, convert it to the service's expected typed input, call one or more services, and translate the result to the response.\n- Keep business logic, persistence, filesystem work, subprocess execution, and orchestration out of routes.\n- Allow a service to call other services. Access another module's services through that module's public barrel contract.\n\n## Test within the module\n\n- Put feature tests in `server\u002Fmodules\u002F\u003Cfeature>\u002Ftests\u002F`.\n- Add or update unit tests for changed service behavior and route parsing.\n\n## Verify the result\n\nBefore finishing:\n\n1. Confirm all cross-module imports use `index.ts` barrels and all public exports are necessary and documented.\n2. Confirm shared definitions follow the one-use versus multiple-use placement rule and grouping-comment format.\n3. Confirm routes only parse, call services, and format responses.\n4. Run the narrow relevant tests, then `npm run build`, `npm run typecheck`, and `npm run lint` when the task scope and environment permit.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fbackend-module-standards",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 backend-module-standards",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill backend-module-standards",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill backend-module-standards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbackend-module-standards\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",233,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbackend-module-standards\u002Fagents\u002Fopenai.yaml",[53,61,66,73,80,87],{"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":60},"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",[],[],"2026-11-16 10:05:34",{"skillNo":62,"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":63,"categories":64,"keywords":65,"publishedAt":60},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\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":60},"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":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":60},"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":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":60},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":60},"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",[],[]]