[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F9BRJT8AH2SYBVT8BGW2TY":3,"skill-same:01M7F9BRJT8AH2SYBVT8BGW2TY":61},{"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":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M7F9BRJT8AH2SYBVT8BGW2TY","full-output-enforcement",null,"Use when a task requires exhaustive unabridged output, complete files, or strict prevention of placeholders and skipped code.","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\u002F06-前端与设计\u002Ffull-output-enforcement\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: full-output-enforcement\ndescription: \"Use when a task requires exhaustive unabridged output, complete files, or strict prevention of placeholders and skipped code.\"\ncategory: frontend\nrisk: safe\nsource: community\nsource_repo: Leonxlnx\u002Ftaste-skill\nsource_type: community\ndate_added: \"2026-04-17\"\nauthor: Leonxlnx\ntags: [output, code-generation, quality]\ntools: [claude, cursor, codex, antigravity]\n---\n# Full-Output Enforcement\n\n## When to Use\n\n- Use when the user explicitly asks for full files, complete implementations, exhaustive lists, or unabridged deliverables.\n- Use when placeholder code, skipped sections, TODO stubs, or descriptions in place of implementation would break the request.\n- Use when a long answer may need clean continuation chunks without losing completeness or structural integrity.\n\n## Limitations\n\n- This skill enforces completeness, but it does not override token limits, safety constraints, missing source context, or user-provided scope boundaries.\n- Split long outputs into clearly labeled continuation chunks when necessary, and verify that each chunk connects cleanly to the previous one.\n- Do not invent unavailable code, credentials, private APIs, or project files to satisfy a request for complete output.\n\n\n## Baseline\n\nTreat every task as production-critical. A partial output is a broken output. Do not optimize for brevity — optimize for completeness. If the user asks for a full file, deliver the full file. If the user asks for 5 components, deliver 5 components. No exceptions.\n\n## Banned Output Patterns\n\nThe following patterns are hard failures. Never produce them:\n\n**In code blocks:** `\u002F\u002F ...`, `\u002F\u002F rest of code`, `\u002F\u002F implement here`, `\u002F\u002F TODO`, `\u002F* ... *\u002F`, `\u002F\u002F similar to above`, `\u002F\u002F continue pattern`, `\u002F\u002F add more as needed`, bare `...` standing in for omitted code\n\n**In prose:** \"Let me know if you want me to continue\", \"I can provide more details if needed\", \"for brevity\", \"the rest follows the same pattern\", \"similarly for the remaining\", \"and so on\" (when replacing actual content), \"I'll leave that as an exercise\"\n\n**Structural shortcuts:** Outputting a skeleton when the request was for a full implementation. Showing the first and last section while skipping the middle. Replacing repeated logic with one example and a description. Describing what code should do instead of writing it.\n\n## Execution Process\n\n1. **Scope** — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.\n2. **Build** — Generate every deliverable completely. No partial drafts, no \"you can extend this later.\"\n3. **Cross-check** — Before output, re-read the original request. Compare your deliverable count against the scope count. If anything is missing, add it before responding.\n\n## Handling Long Outputs\n\nWhen a response approaches the token limit:\n\n- Do not compress remaining sections to squeeze them in.\n- Do not skip ahead to a conclusion.\n- Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).\n- End with:\n\n```\n[PAUSED — X of Y complete. Send \"continue\" to resume from: next section name]\n```\n\nOn \"continue\", pick up exactly where you stopped. No recap, no repetition.\n\n## Quick Check\n\nBefore finalizing any response, verify:\n- No banned patterns from the list above appear anywhere in the output\n- Every item the user requested is present and finished\n- Code blocks contain actual runnable code, not descriptions of what code would do\n- Nothing was shortened to save space\n","# Full-Output Enforcement\n\n## When to Use\n\n- Use when the user explicitly asks for full files, complete implementations, exhaustive lists, or unabridged deliverables.\n- Use when placeholder code, skipped sections, TODO stubs, or descriptions in place of implementation would break the request.\n- Use when a long answer may need clean continuation chunks without losing completeness or structural integrity.\n\n## Limitations\n\n- This skill enforces completeness, but it does not override token limits, safety constraints, missing source context, or user-provided scope boundaries.\n- Split long outputs into clearly labeled continuation chunks when necessary, and verify that each chunk connects cleanly to the previous one.\n- Do not invent unavailable code, credentials, private APIs, or project files to satisfy a request for complete output.\n\n\n## Baseline\n\nTreat every task as production-critical. A partial output is a broken output. Do not optimize for brevity — optimize for completeness. If the user asks for a full file, deliver the full file. If the user asks for 5 components, deliver 5 components. No exceptions.\n\n## Banned Output Patterns\n\nThe following patterns are hard failures. Never produce them:\n\n**In code blocks:** `\u002F\u002F ...`, `\u002F\u002F rest of code`, `\u002F\u002F implement here`, `\u002F\u002F TODO`, `\u002F* ... *\u002F`, `\u002F\u002F similar to above`, `\u002F\u002F continue pattern`, `\u002F\u002F add more as needed`, bare `...` standing in for omitted code\n\n**In prose:** \"Let me know if you want me to continue\", \"I can provide more details if needed\", \"for brevity\", \"the rest follows the same pattern\", \"similarly for the remaining\", \"and so on\" (when replacing actual content), \"I'll leave that as an exercise\"\n\n**Structural shortcuts:** Outputting a skeleton when the request was for a full implementation. Showing the first and last section while skipping the middle. Replacing repeated logic with one example and a description. Describing what code should do instead of writing it.\n\n## Execution Process\n\n1. **Scope** — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.\n2. **Build** — Generate every deliverable completely. No partial drafts, no \"you can extend this later.\"\n3. **Cross-check** — Before output, re-read the original request. Compare your deliverable count against the scope count. If anything is missing, add it before responding.\n\n## Handling Long Outputs\n\nWhen a response approaches the token limit:\n\n- Do not compress remaining sections to squeeze them in.\n- Do not skip ahead to a conclusion.\n- Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).\n- End with:\n\n```\n[PAUSED — X of Y complete. Send \"continue\" to resume from: next section name]\n```\n\nOn \"continue\", pick up exactly where you stopped. No recap, no repetition.\n\n## Quick Check\n\nBefore finalizing any response, verify:\n- No banned patterns from the list above appear anywhere in the output\n- Every item the user requested is present and finished\n- Code blocks contain actual runnable code, not descriptions of what code would do\n- Nothing was shortened to save space\n",{"name":5,"risk":24,"tags":25,"tools":29,"author":34,"source":35,"category":36,"date_added":37,"description":7,"source_repo":38,"source_type":35},"safe",[26,27,28],"output","code-generation","quality",[30,31,32,33],"claude","cursor","codex","antigravity","Leonxlnx","community","frontend","2026-04-17","Leonxlnx\u002Ftaste-skill","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Ffull-output-enforcement",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":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill full-output-enforcement",{"tool":53,"command":54},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill full-output-enforcement",{"tool":56,"command":57},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill full-output-enforcement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Ffull-output-enforcement\u002FSKILL.md",true,[],[62,69,74,81,88,95],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":64,"nameZh":6,"description":65,"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},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\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},"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":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},"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":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},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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",[],[]]