[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SBYGPHM83V67NTCDGPZYS":3,"skill-same:01M77SBYGPHM83V67NTCDGPZYS":54},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M77SBYGPHM83V67NTCDGPZYS","judgment-day",null,"Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.","janpereira-dev\u002FskillsCurate","janpereira-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6440548?v=4","01M6KKKXBFFK7QF5Y2JFXN35FF","Jan Pereira","01M77ND31QCT5KM25E1SW71M8F",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fjudgment-day\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: judgment-day\ndescription: \"Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.\"\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.4\"\n---\n\n## Activation Contract\n\nLoad this skill only when the user explicitly asks for Judgment Day, dual\u002Fadversarial review, or equivalent Spanish trigger (`juzgar`, `que lo juzguen`). Review a specific target: files, feature, PR, or architecture slice.\n\n## Hard Rules\n\n- Resolve project skills before launching agents: read skill registry, match compact rules by target files\u002Ftask, and inject the same `Project Standards` block into both judge prompts and fix prompts.\n- Launch **two blind judges in parallel** with identical target and criteria; never review the code yourself.\n- Wait for both judges before synthesis; never accept a partial verdict.\n- Classify warnings as `WARNING (real)` only if normal intended use can trigger them; otherwise downgrade to INFO as `WARNING (theoretical)`.\n- Ask before fixing Round 1 confirmed issues.\n- After any fix agent runs, immediately re-launch both judges in parallel before commit\u002Fpush\u002Fdone\u002Fsession summary.\n- Terminal states are only `JUDGMENT: APPROVED` or `JUDGMENT: ESCALATED`.\n- After 2 fix iterations with remaining issues, ask the user whether to continue.\n\n## Decision Gates\n\n| Condition | Action |\n|---|---|\n| Target unclear | Ask for scope; do not launch judges. |\n| No skill registry | Warn, proceed with generic criteria, and record `Skill Resolution: none`. |\n| Both judges find same CRITICAL\u002Freal WARNING | Confirmed; ask\u002Ffix according to round rules. |\n| One judge finds issue | Suspect; report and triage, do not auto-fix. |\n| Judges contradict | Escalate for manual decision. |\n| Round 2+ has only theoretical warnings\u002Fsuggestions | Report as INFO; do not re-judge. |\n\n## Execution Steps\n\n1. Confirm target and optional custom criteria.\n2. Resolve compact project standards from registry or warn if missing.\n3. Start Judge A and Judge B concurrently via delegation.\n4. Synthesize findings into confirmed, suspect, contradiction, and INFO buckets.\n5. Ask before Round 1 fixes; delegate a separate fix agent for confirmed approved fixes only.\n6. Re-judge in parallel after fixes; repeat until approved, escalated, or user asks to stop.\n7. Before any terminal action, verify every active Judgment Day has a terminal state.\n\n## Output Contract\n\nReturn `## Judgment Day — {target}` with round number, verdict table, confirmed\u002Fsuspect\u002Fcontradiction counts, fixes applied, re-judgment result, `Skill Resolution`, and final `JUDGMENT: APPROVED ✅` or `JUDGMENT: ESCALATED ⚠️`.\n\n## References\n\n- [references\u002Fprompts-and-formats.md](references\u002Fprompts-and-formats.md) — judge\u002Ffix prompts, warning rubric, verdict tables, and language snippets.\n","## Activation Contract\n\nLoad this skill only when the user explicitly asks for Judgment Day, dual\u002Fadversarial review, or equivalent Spanish trigger (`juzgar`, `que lo juzguen`). Review a specific target: files, feature, PR, or architecture slice.\n\n## Hard Rules\n\n- Resolve project skills before launching agents: read skill registry, match compact rules by target files\u002Ftask, and inject the same `Project Standards` block into both judge prompts and fix prompts.\n- Launch **two blind judges in parallel** with identical target and criteria; never review the code yourself.\n- Wait for both judges before synthesis; never accept a partial verdict.\n- Classify warnings as `WARNING (real)` only if normal intended use can trigger them; otherwise downgrade to INFO as `WARNING (theoretical)`.\n- Ask before fixing Round 1 confirmed issues.\n- After any fix agent runs, immediately re-launch both judges in parallel before commit\u002Fpush\u002Fdone\u002Fsession summary.\n- Terminal states are only `JUDGMENT: APPROVED` or `JUDGMENT: ESCALATED`.\n- After 2 fix iterations with remaining issues, ask the user whether to continue.\n\n## Decision Gates\n\n| Condition | Action |\n|---|---|\n| Target unclear | Ask for scope; do not launch judges. |\n| No skill registry | Warn, proceed with generic criteria, and record `Skill Resolution: none`. |\n| Both judges find same CRITICAL\u002Freal WARNING | Confirmed; ask\u002Ffix according to round rules. |\n| One judge finds issue | Suspect; report and triage, do not auto-fix. |\n| Judges contradict | Escalate for manual decision. |\n| Round 2+ has only theoretical warnings\u002Fsuggestions | Report as INFO; do not re-judge. |\n\n## Execution Steps\n\n1. Confirm target and optional custom criteria.\n2. Resolve compact project standards from registry or warn if missing.\n3. Start Judge A and Judge B concurrently via delegation.\n4. Synthesize findings into confirmed, suspect, contradiction, and INFO buckets.\n5. Ask before Round 1 fixes; delegate a separate fix agent for confirmed approved fixes only.\n6. Re-judge in parallel after fixes; repeat until approved, escalated, or user asks to stop.\n7. Before any terminal action, verify every active Judgment Day has a terminal state.\n\n## Output Contract\n\nReturn `## Judgment Day — {target}` with round number, verdict table, confirmed\u002Fsuspect\u002Fcontradiction counts, fixes applied, re-judgment result, `Skill Resolution`, and final `JUDGMENT: APPROVED ✅` or `JUDGMENT: ESCALATED ⚠️`.\n\n## References\n\n- [references\u002Fprompts-and-formats.md](references\u002Fprompts-and-formats.md) — judge\u002Ffix prompts, warning rubric, verdict tables, and language snippets.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"gentleman-programming","1.4","main","ba43a4e7e8b0fd6b150b14bcb48978ec40879a28",".agents\u002Fskills\u002Fjudgment-day","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev","IT Leader, Scrum Master, FullStack Developer, SEO\u002FSEM Master #Angular #React\r\n","2026-07-13 03:04:32",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add janpereira-dev\u002FskillsCurate --skill judgment-day",{"tool":40,"command":41},"bunx","bunx skills add janpereira-dev\u002FskillsCurate --skill judgment-day",{"tool":43,"command":44},"pnpm","pnpm dlx skills add janpereira-dev\u002FskillsCurate --skill judgment-day","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fjudgment-day\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fprompts-and-formats.md","REFERENCE","参考文档",2679,"https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fjudgment-day\u002Freferences\u002Fprompts-and-formats.md",[55,62,69,76,84,92],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M77T9KN6TEJMPPTQZDEB4K61","zustand-5","Zustand 5 state management patterns. Trigger: When managing React state with Zustand.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzustand-5\u002FSKILL.md",[],[],{"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},"01M77T9GN2GABPPWDGDCXJ6QWK","zod-4","Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzod-4\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M77T98A9R6PK155P71VX9MND","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77T9505TGQGWHGAYVXGE2KS","web-quality-audit","Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to \"audit my site\", \"review web quality\", \"run lighthouse audit\", \"check page quality\", or \"optimize my website\".","MIT","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-quality-audit\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M77T8YRVRNK8W4MG63XM80NK","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M77T8CEPQFZRRNGBYZX46P4Y","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvercel-react-view-transitions\u002FSKILL.md",[],[]]