[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CGQPKJ3FS8TM4B0P7ETFX4":3,"skill-same:01M7CGQPKJ3FS8TM4B0P7ETFX4":44},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7CGQPKJ3FS8TM4B0P7ETFX4","impeccable-preflight",null,"Run Impeccable's deterministic frontend detector before subjective UI review. Use for implemented frontend\u002FUI changes to catch machine-detectable anti-patterns, accessibility, responsive, typography, layout, and design-system issues without treating detector output as design truth.","harunonsystem\u002Fharunon-harness-slim","harunonsystem","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34958457?v=4","01M7CGJNZEEY4GZ845775PPBV1","harunon","01M7CGJP01K9B4N0F5HMNGYC8Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharunonsystem\u002Fharunon-harness-slim\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fimpeccable-preflight\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: impeccable-preflight\ndescription: Run Impeccable's deterministic frontend detector before subjective UI review. Use for implemented frontend\u002FUI changes to catch machine-detectable anti-patterns, accessibility, responsive, typography, layout, and design-system issues without treating detector output as design truth.\n---\n\n# Impeccable preflight\n\nRun a deterministic UI-quality pass before subjective design review. This skill is a guardrail, not a replacement for `better-interface`, `frontend-verify`, repository design conventions, or product judgment.\n\n## Scope\n\nUse this after frontend code has been implemented or changed and before `better-interface` \u002F `frontend-verify`.\n\nPrefer the narrowest useful target:\n\n- changed UI files when the detector can analyze them directly;\n- the affected frontend package\u002Fapp directory when imports or linked styles matter;\n- a URL only when a rendered-page detector pass is explicitly useful. `frontend-verify` remains the primary live-browser evidence path.\n\nDo not scan an entire monorepo by default when the UI change is localized.\n\n## Run\n\nThe harness intentionally invokes the deterministic CLI directly instead of installing Impeccable's full opinionated workflow. Use the pinned CLI version so review behavior does not silently drift:\n\n```bash\nnpx --yes impeccable@4.1.0 detect --json \u003Ctarget...>\n```\n\nExamples:\n\n```bash\nnpx --yes impeccable@4.1.0 detect --json src\u002Fcomponents\u002FProfileCard.tsx\nnpx --yes impeccable@4.1.0 detect --json apps\u002Fweb\u002Fsrc\u002F\nnpx --yes impeccable@4.1.0 detect --json https:\u002F\u002Flocalhost:3000\u002Fsettings\n```\n\nInterpret exit status correctly:\n\n- `0`: scan completed with no primary findings; advisory findings may still exist;\n- `1`: at least one requested target could not be scanned — this is an operational failure;\n- `2`: scan completed and found one or more primary findings — this is expected detector output, not a CLI failure.\n\nIf `npx` cannot fetch\u002Frun the pinned CLI because of network, runtime, or policy restrictions, report that the deterministic preflight did not run and continue with the available review path. Never claim detector coverage when it did not execute.\n\n## Triage findings\n\nTreat findings as candidate defects, not automatic requirements.\n\n1. Separate primary findings from advisory findings.\n2. Verify each material finding against the actual code, repository conventions, design system, and user brief.\n3. Fix clear implementation defects when the task includes implementation\u002Ffixes.\n4. For review-only requests, report findings without changing code.\n5. If a rule conflicts with an intentional product\u002Fdesign decision, keep the decision and document the exception rather than redesigning to satisfy the detector.\n\nImpeccable supports project-level detector ignores and inline `impeccable-disable*` comments. Add an ignore only for a stable, intentional exception with a short reason. Do not blanket-disable rules merely to obtain a clean scan.\n\n## Boundaries\n\n- Do not automatically run Impeccable's subjective transformation commands (`bolder`, `delight`, `colorize`, `overdrive`, etc.).\n- Do not let an Impeccable preference override an explicit design brief, established brand rule, or repository component\u002Ftoken convention.\n- Do not duplicate `better-interface`: detector findings should cover deterministic signals; holistic hierarchy, clarity, visual coherence, writing, and design judgment stay with `better-interface`.\n- Do not duplicate `frontend-verify`: rendered state, screenshots, responsive behavior in the running app, and interactions stay with the browser verification step.\n\n## Handoff\n\nReturn a compact preflight record containing:\n\n- targets scanned;\n- CLI exit status;\n- primary findings retained after verification;\n- advisory findings worth carrying forward;\n- intentional exceptions \u002F ignores;\n- whether the scan was incomplete or unavailable.\n","# Impeccable preflight\n\nRun a deterministic UI-quality pass before subjective design review. This skill is a guardrail, not a replacement for `better-interface`, `frontend-verify`, repository design conventions, or product judgment.\n\n## Scope\n\nUse this after frontend code has been implemented or changed and before `better-interface` \u002F `frontend-verify`.\n\nPrefer the narrowest useful target:\n\n- changed UI files when the detector can analyze them directly;\n- the affected frontend package\u002Fapp directory when imports or linked styles matter;\n- a URL only when a rendered-page detector pass is explicitly useful. `frontend-verify` remains the primary live-browser evidence path.\n\nDo not scan an entire monorepo by default when the UI change is localized.\n\n## Run\n\nThe harness intentionally invokes the deterministic CLI directly instead of installing Impeccable's full opinionated workflow. Use the pinned CLI version so review behavior does not silently drift:\n\n```bash\nnpx --yes impeccable@4.1.0 detect --json \u003Ctarget...>\n```\n\nExamples:\n\n```bash\nnpx --yes impeccable@4.1.0 detect --json src\u002Fcomponents\u002FProfileCard.tsx\nnpx --yes impeccable@4.1.0 detect --json apps\u002Fweb\u002Fsrc\u002F\nnpx --yes impeccable@4.1.0 detect --json https:\u002F\u002Flocalhost:3000\u002Fsettings\n```\n\nInterpret exit status correctly:\n\n- `0`: scan completed with no primary findings; advisory findings may still exist;\n- `1`: at least one requested target could not be scanned — this is an operational failure;\n- `2`: scan completed and found one or more primary findings — this is expected detector output, not a CLI failure.\n\nIf `npx` cannot fetch\u002Frun the pinned CLI because of network, runtime, or policy restrictions, report that the deterministic preflight did not run and continue with the available review path. Never claim detector coverage when it did not execute.\n\n## Triage findings\n\nTreat findings as candidate defects, not automatic requirements.\n\n1. Separate primary findings from advisory findings.\n2. Verify each material finding against the actual code, repository conventions, design system, and user brief.\n3. Fix clear implementation defects when the task includes implementation\u002Ffixes.\n4. For review-only requests, report findings without changing code.\n5. If a rule conflicts with an intentional product\u002Fdesign decision, keep the decision and document the exception rather than redesigning to satisfy the detector.\n\nImpeccable supports project-level detector ignores and inline `impeccable-disable*` comments. Add an ignore only for a stable, intentional exception with a short reason. Do not blanket-disable rules merely to obtain a clean scan.\n\n## Boundaries\n\n- Do not automatically run Impeccable's subjective transformation commands (`bolder`, `delight`, `colorize`, `overdrive`, etc.).\n- Do not let an Impeccable preference override an explicit design brief, established brand rule, or repository component\u002Ftoken convention.\n- Do not duplicate `better-interface`: detector findings should cover deterministic signals; holistic hierarchy, clarity, visual coherence, writing, and design judgment stay with `better-interface`.\n- Do not duplicate `frontend-verify`: rendered state, screenshots, responsive behavior in the running app, and interactions stay with the browser verification step.\n\n## Handoff\n\nReturn a compact preflight record containing:\n\n- targets scanned;\n- CLI exit status;\n- primary findings retained after verification;\n- advisory findings worth carrying forward;\n- intentional exceptions \u002F ignores;\n- whether the scan was incomplete or unavailable.\n",{"name":5,"description":7},"main","d7d37ad7e79d10fc5b881a8a401979484b6ee1ac","claude\u002Fskills\u002Fimpeccable-preflight","https:\u002F\u002Fgithub.com\u002Fharunonsystem\u002Fharunon-harness-slim","https:\u002F\u002Fgithub.com\u002Fharunonsystem","2026-11-14 07:03:55",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add harunonsystem\u002Fharunon-harness-slim --skill impeccable-preflight",{"tool":36,"command":37},"bunx","bunx skills add harunonsystem\u002Fharunon-harness-slim --skill impeccable-preflight",{"tool":39,"command":40},"pnpm","pnpm dlx skills add harunonsystem\u002Fharunon-harness-slim --skill impeccable-preflight","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharunonsystem\u002Fharunon-harness-slim\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fimpeccable-preflight\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7CH39JSS2D4J52SCASDTJ9Q","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fharunonsystem\u002Fharunon-harness-slim\u002Fblob\u002Fmain\u002Fshared-agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"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},"01M7CH36HM1KX4VEFNKNQZ37WP","wrangler","Run or troubleshoot Wrangler CLI commands in projects that have a wrangler.jsonc, wrangler.json, or wrangler.toml file, including local development, Previews, deployment, and resource management. For new projects and projects without a Wrangler configuration file, use the cf CLI instead.","https:\u002F\u002Fgithub.com\u002Fharunonsystem\u002Fharunon-harness-slim\u002Fblob\u002Fmain\u002Fshared-agents\u002Fskills\u002Fwrangler\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},"01M7CH335A6PP55E1VE1R7EXB1","workflow-modernize","パッケージ\u002FCLI更新時や定期見直し時に、自作スキル・ワークフロー・設定を監査し、不要なworkaroundの撤廃・新機能の適用・プロンプトの簡素化をGrill（壁打ち）と多角比較で提案・修正する。「workflow-modernize」「スキル監査」「ワークフロー改善」「パッケージ更新後の見直し」「モダナイズ」で起動。","https:\u002F\u002Fgithub.com\u002Fharunonsystem\u002Fharunon-harness-slim\u002Fblob\u002Fmain\u002Fshared-agents\u002Fskills\u002Fworkflow-modernize\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},"01M7CH303YN7MP9VCSFAB7KSG7","workers-best-practices","Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.","https:\u002F\u002Fgithub.com\u002Fharunonsystem\u002Fharunon-harness-slim\u002Fblob\u002Fmain\u002Fshared-agents\u002Fskills\u002Fworkers-best-practices\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},"01M7CH2XJPDFMHNRBKZXQD16S0","web-perf","Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.","https:\u002F\u002Fgithub.com\u002Fharunonsystem\u002Fharunon-harness-slim\u002Fblob\u002Fmain\u002Fshared-agents\u002Fskills\u002Fweb-perf\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},"01M7CH2V3AFZB7F055Y9KAFXZ3","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fharunonsystem\u002Fharunon-harness-slim\u002Fblob\u002Fmain\u002Fshared-agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]