[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C2AYE10MA1HJKDEP31FFSY":3,"skill-same:01M6C2AYE10MA1HJKDEP31FFSY":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6C2AYE10MA1HJKDEP31FFSY","pr-green-definition",null,"Canonical \u002Fgreen definition — applicable CI or documented exception + no merge conflicts, verified at current PR HEAD SHA. Quality gates live in pr-lifecycle.","jleechanorg\u002Fjleechan-skills","jleechanorg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221404966?v=4","01M6C1VJ99XG950X1DWPEBCBGX","01M6C1VJDK5YVDNT3362RT5WSB",6,"MIT","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpr-green-definition\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"definition","pr","pr green definition","green","conflicts","verified","at","canonical","head","live","gates","policy","merge conflicts","quality","lifecycle","ci","quality gates","merge","2026-11-10 10:12:30",false,"---\nname: pr-green-definition\ndescription: Canonical \u002Fgreen definition — applicable CI or documented exception + no merge conflicts, verified at current PR HEAD SHA. Quality gates live in pr-lifecycle.\nmetadata:\n  type: policy\n---\n\n# PR \"Green\" Definition (2-Gate, canonical 2026-07-28)\n\n`\u002Fgreen` has exactly two gates, both bound to the PR's current `headRefOid`.\n\n## Mandatory PR state and head check\n\nBefore choosing a Gate 1 validation route or evaluating either gate, read the current PR state, merge status and head together:\n\n```bash\ngh api repos\u002FOWNER\u002FREPO\u002Fpulls\u002FN --jq '{state, merged, head: .head.sha}'\n```\n\n`state` must be `open` and `merged` must be `false`. For a closed or merged PR, stop and report its terminal state without evaluating Gate 1 or Gate 2. Any other state is unproven; do not continue. Pin the returned `head` for both gates. If a later read finds a different head, restart from this check before selecting a route or evaluating a gate.\n\n| # | Gate | Verification |\n|---|---|---|\n| 1 | **Applicable validation** | Documentation-only: `CI NOT REQUIRED` with proportionate local validation. Otherwise every required check passes at HEAD through CI, a documented `CI NOT APPLICABLE` exception, or the local-equivalent exception for backlogged checks. |\n| 2 | **No merge conflicts** | `mergeable == MERGEABLE` (`UNKNOWN` may be re-polled only while the PR remains open and unmerged; `CONFLICTING` is a hard FAIL). |\n\nNothing else gates `\u002Fgreen`: inline-comment, evidence-link and PR-description checks, old \"6-green\" numbering, CodeRabbit and Bugbot are not gates or waits. Stages, reviewer routes\u002Fquorum, evidence applicability\u002Fpublication, SHA reuse, and runtime\u002Fvisual\u002Fbundle requirements belong to [`pr-lifecycle`](..\u002Fpr-lifecycle\u002FSKILL.md); follow its claim\u002Frisk applicability instead of duplicating those manuals here. Pure instruction Markdown is not automatically runtime\u002Fvisual\u002Fbundle-required or exempt solely by line count. Known relevant mechanical failures remain failures; skipped or neutral checks never become passes. Green alone does not establish READY.\n\nMerge authorization is separate: follow `~\u002F.codex\u002FAGENTS.md` § Merge safety and the target repository's explicit merge contract.\n\n## Retained review integrations\n\nFollow [pr-lifecycle's retained review integrations](..\u002Fpr-lifecycle\u002FSKILL.md#retained-review-integrations) for discovery, `UNAVAILABLE` reporting, quorum and disclosure boundaries.\n\n## Documentation-only CI exception\n\nClassify the complete current-head diff by actual effects, not file extension or line count. Instruction\u002Fskill documentation, documentation-only pointer maintenance, and files including `AGENTS.md`, `CLAUDE.md` and `SKILL.md` qualify only when no executable or application-runtime behavior changes; they need no CI trigger\u002Fretry, runner wait or backlog threshold. Embedded code, automation, prompts, workflows, schemas, runtime configuration and mixed diffs do not qualify merely because they are Markdown. This exception selects Gate 1's result only; it never bypasses the mandatory open-state\u002Fhead check or Gate 2. Run proportionate local checks (diff hygiene, link\u002Fpointer resolution or metadata validation) and record `Gate 1: CI NOT REQUIRED — documentation-only` with SHA, scope, commands and results. Never call skipped\u002Funrun CI passed; Gate 2, lifecycle review\u002Fevidence requirements and merge authorization remain separate.\n\n## No-CI exception — a check that cannot run is not a check to wait on\n\nDo not sleep-poll absent CI. `CI NOT APPLICABLE` requires bounded proof of one case: no workflow matches the changed paths; zero eligible runners; repeated observations show every eligible runner busy while the check remains `QUEUED`\u002F`PENDING`; or a no-start rollup is explained by that same capacity evidence. Resolve workflow filters, labels, runner group, repository access and eligible pool as applicable; a directory listing, one busy snapshot or a stuck rollup alone is insufficient. Otherwise Gate 1 stays unproven.\n\nFor a qualifying case, run the actual workflow command (or bounded repository validation when no workflow applies) immediately and record:\n\n```\nGate 1: CI NOT APPLICABLE — \u003Cno matching workflow | zero eligible runners | runners saturated QUEUED or PENDING>\n  evidence: \u003Cbounded command + proving output>\n  local equivalent: \u003Cworkflow command or bounded validation> → \u003Cresult at SHA>\n  validation\u002Fcapacity details: \u003Cresult or timestamped eligibility\u002Fqueue observations>\n```\n\nNever call unrun CI passed, disable\u002Fcancel jobs or touch branch protection, and do not use this exception for merely slow or failed CI. A started check is backlogged CI and follows the local-equivalent rule below.\n\n## Gate 1 — CI verification at the fresh head\n\nAfter the mandatory state\u002Fhead check above, read the complete `statusCheckRollup`; `gh pr checks` is only a summary, never proof. The rollup includes legacy `StatusContext` and Actions `CheckRun` rows:\n\n```bash\ngh pr view N --json headRefOid,statusCheckRollup --jq '[.statusCheckRollup[] | if .__typename == \"StatusContext\" then {name:(.context \u002F\u002F \"\"), kind:\"legacy-context\", state:(.state \u002F\u002F \"\" | ascii_upcase), conclusion:null} elif .__typename == \"CheckRun\" then {name:(.name \u002F\u002F \"\"), kind:\"check-run\", state:(.status \u002F\u002F \"\" | ascii_upcase), conclusion:(.conclusion \u002F\u002F \"\" | ascii_upcase)} else {name:\"\", kind:(.__typename \u002F\u002F \"\"), state:\"\", conclusion:\"\"} end]'\n```\n\nRequire `headRefOid` to equal the pinned `head` from the mandatory state\u002Fhead check; if it differs, restart from that check. `StatusContext` is the legacy context shape; `CheckRun` uses `status` and `conclusion`. Bucket required results as `PASS` only for legacy `SUCCESS` or completed `CheckRun`\u002F`SUCCESS`; `PENDING` while incomplete; `FAIL` for a completed non-success; and `UNPROVEN` for missing\u002Funknown or non-applicable evidence. Skipped or neutral results are never `PASS`, including optional checks; CodeRabbit\u002FBugbot never gate. Fix known required mechanical failures. Re-read the current head for every verdict; raw check-run reads use that SHA, the current run's jobs and pagination, with REST\u002FGraphQL fallback per `..\u002Fgithub-cli-reference\u002FSKILL.md` before claiming unavailable.\n\n## Gate 2 — no merge conflicts at that same head\n\n```bash\ngh pr view N --json headRefOid,mergeable,mergeStateStatus --jq '.'\n```\n\nRequire `headRefOid` to equal the pinned `head` from the mandatory state\u002Fhead check; if it differs, restart from that check. `mergeable` must be `MERGEABLE`; re-poll `UNKNOWN` only after repeating the state\u002Fhead check and confirming the same PR is still `open` and unmerged. Stop and report if it is closed or merged. Resolve `CONFLICTING`. `mergeStateStatus` is informational (`DIRTY` corroborates conflict; other non-`CLEAN` values can reflect CI). Re-check whenever stating a verdict because base-branch changes can recompute mergeability.\n\n## Backlogged CI — local-equivalent Gate 1 evidence\n\nFor a required check queued\u002Fpending more than 10 minutes, run its actual workflow command locally and report `local run — CI still pending\u002Frerunning` with command, output, timestamp and current head SHA. Map each substituted job and matrix entry to its workflow command, runtime, dependencies, services, flags, configuration and artifacts; record base\u002Fhead, dirty-state hashes, timestamps, exit status, source\u002Fartifact hashes and environment differences. Distinguish CI PASS, local-equivalent PASS, pending, failed and unproven per job; a convenient subset, wrong platform, mock boundary or non-reproducible hosted check is not equivalent and stays unproven. This does not waive failures, freshness, Gate 2, lifecycle evidence or merge authorization.\n\n## Related\n\n- `..\u002Fpr-lifecycle\u002FSKILL.md` — canonical lifecycle, stages and review\u002Fevidence applicability\n- `..\u002Fgithub-cli-reference\u002FSKILL.md` — REST ↔ GraphQL dual-bucket procedure\n","# PR \"Green\" Definition (2-Gate, canonical 2026-07-28)\n\n`\u002Fgreen` has exactly two gates, both bound to the PR's current `headRefOid`.\n\n## Mandatory PR state and head check\n\nBefore choosing a Gate 1 validation route or evaluating either gate, read the current PR state, merge status and head together:\n\n```bash\ngh api repos\u002FOWNER\u002FREPO\u002Fpulls\u002FN --jq '{state, merged, head: .head.sha}'\n```\n\n`state` must be `open` and `merged` must be `false`. For a closed or merged PR, stop and report its terminal state without evaluating Gate 1 or Gate 2. Any other state is unproven; do not continue. Pin the returned `head` for both gates. If a later read finds a different head, restart from this check before selecting a route or evaluating a gate.\n\n| # | Gate | Verification |\n|---|---|---|\n| 1 | **Applicable validation** | Documentation-only: `CI NOT REQUIRED` with proportionate local validation. Otherwise every required check passes at HEAD through CI, a documented `CI NOT APPLICABLE` exception, or the local-equivalent exception for backlogged checks. |\n| 2 | **No merge conflicts** | `mergeable == MERGEABLE` (`UNKNOWN` may be re-polled only while the PR remains open and unmerged; `CONFLICTING` is a hard FAIL). |\n\nNothing else gates `\u002Fgreen`: inline-comment, evidence-link and PR-description checks, old \"6-green\" numbering, CodeRabbit and Bugbot are not gates or waits. Stages, reviewer routes\u002Fquorum, evidence applicability\u002Fpublication, SHA reuse, and runtime\u002Fvisual\u002Fbundle requirements belong to [`pr-lifecycle`](..\u002Fpr-lifecycle\u002FSKILL.md); follow its claim\u002Frisk applicability instead of duplicating those manuals here. Pure instruction Markdown is not automatically runtime\u002Fvisual\u002Fbundle-required or exempt solely by line count. Known relevant mechanical failures remain failures; skipped or neutral checks never become passes. Green alone does not establish READY.\n\nMerge authorization is separate: follow `~\u002F.codex\u002FAGENTS.md` § Merge safety and the target repository's explicit merge contract.\n\n## Retained review integrations\n\nFollow [pr-lifecycle's retained review integrations](..\u002Fpr-lifecycle\u002FSKILL.md#retained-review-integrations) for discovery, `UNAVAILABLE` reporting, quorum and disclosure boundaries.\n\n## Documentation-only CI exception\n\nClassify the complete current-head diff by actual effects, not file extension or line count. Instruction\u002Fskill documentation, documentation-only pointer maintenance, and files including `AGENTS.md`, `CLAUDE.md` and `SKILL.md` qualify only when no executable or application-runtime behavior changes; they need no CI trigger\u002Fretry, runner wait or backlog threshold. Embedded code, automation, prompts, workflows, schemas, runtime configuration and mixed diffs do not qualify merely because they are Markdown. This exception selects Gate 1's result only; it never bypasses the mandatory open-state\u002Fhead check or Gate 2. Run proportionate local checks (diff hygiene, link\u002Fpointer resolution or metadata validation) and record `Gate 1: CI NOT REQUIRED — documentation-only` with SHA, scope, commands and results. Never call skipped\u002Funrun CI passed; Gate 2, lifecycle review\u002Fevidence requirements and merge authorization remain separate.\n\n## No-CI exception — a check that cannot run is not a check to wait on\n\nDo not sleep-poll absent CI. `CI NOT APPLICABLE` requires bounded proof of one case: no workflow matches the changed paths; zero eligible runners; repeated observations show every eligible runner busy while the check remains `QUEUED`\u002F`PENDING`; or a no-start rollup is explained by that same capacity evidence. Resolve workflow filters, labels, runner group, repository access and eligible pool as applicable; a directory listing, one busy snapshot or a stuck rollup alone is insufficient. Otherwise Gate 1 stays unproven.\n\nFor a qualifying case, run the actual workflow command (or bounded repository validation when no workflow applies) immediately and record:\n\n```\nGate 1: CI NOT APPLICABLE — \u003Cno matching workflow | zero eligible runners | runners saturated QUEUED or PENDING>\n  evidence: \u003Cbounded command + proving output>\n  local equivalent: \u003Cworkflow command or bounded validation> → \u003Cresult at SHA>\n  validation\u002Fcapacity details: \u003Cresult or timestamped eligibility\u002Fqueue observations>\n```\n\nNever call unrun CI passed, disable\u002Fcancel jobs or touch branch protection, and do not use this exception for merely slow or failed CI. A started check is backlogged CI and follows the local-equivalent rule below.\n\n## Gate 1 — CI verification at the fresh head\n\nAfter the mandatory state\u002Fhead check above, read the complete `statusCheckRollup`; `gh pr checks` is only a summary, never proof. The rollup includes legacy `StatusContext` and Actions `CheckRun` rows:\n\n```bash\ngh pr view N --json headRefOid,statusCheckRollup --jq '[.statusCheckRollup[] | if .__typename == \"StatusContext\" then {name:(.context \u002F\u002F \"\"), kind:\"legacy-context\", state:(.state \u002F\u002F \"\" | ascii_upcase), conclusion:null} elif .__typename == \"CheckRun\" then {name:(.name \u002F\u002F \"\"), kind:\"check-run\", state:(.status \u002F\u002F \"\" | ascii_upcase), conclusion:(.conclusion \u002F\u002F \"\" | ascii_upcase)} else {name:\"\", kind:(.__typename \u002F\u002F \"\"), state:\"\", conclusion:\"\"} end]'\n```\n\nRequire `headRefOid` to equal the pinned `head` from the mandatory state\u002Fhead check; if it differs, restart from that check. `StatusContext` is the legacy context shape; `CheckRun` uses `status` and `conclusion`. Bucket required results as `PASS` only for legacy `SUCCESS` or completed `CheckRun`\u002F`SUCCESS`; `PENDING` while incomplete; `FAIL` for a completed non-success; and `UNPROVEN` for missing\u002Funknown or non-applicable evidence. Skipped or neutral results are never `PASS`, including optional checks; CodeRabbit\u002FBugbot never gate. Fix known required mechanical failures. Re-read the current head for every verdict; raw check-run reads use that SHA, the current run's jobs and pagination, with REST\u002FGraphQL fallback per `..\u002Fgithub-cli-reference\u002FSKILL.md` before claiming unavailable.\n\n## Gate 2 — no merge conflicts at that same head\n\n```bash\ngh pr view N --json headRefOid,mergeable,mergeStateStatus --jq '.'\n```\n\nRequire `headRefOid` to equal the pinned `head` from the mandatory state\u002Fhead check; if it differs, restart from that check. `mergeable` must be `MERGEABLE`; re-poll `UNKNOWN` only after repeating the state\u002Fhead check and confirming the same PR is still `open` and unmerged. Stop and report if it is closed or merged. Resolve `CONFLICTING`. `mergeStateStatus` is informational (`DIRTY` corroborates conflict; other non-`CLEAN` values can reflect CI). Re-check whenever stating a verdict because base-branch changes can recompute mergeability.\n\n## Backlogged CI — local-equivalent Gate 1 evidence\n\nFor a required check queued\u002Fpending more than 10 minutes, run its actual workflow command locally and report `local run — CI still pending\u002Frerunning` with command, output, timestamp and current head SHA. Map each substituted job and matrix entry to its workflow command, runtime, dependencies, services, flags, configuration and artifacts; record base\u002Fhead, dirty-state hashes, timestamps, exit status, source\u002Fartifact hashes and environment differences. Distinguish CI PASS, local-equivalent PASS, pending, failed and unproven per job; a convenient subset, wrong platform, mock boundary or non-reproducible hosted check is not equivalent and stays unproven. This does not waive failures, freshness, Gate 2, lifecycle evidence or merge authorization.\n\n## Related\n\n- `..\u002Fpr-lifecycle\u002FSKILL.md` — canonical lifecycle, stages and review\u002Fevidence applicability\n- `..\u002Fgithub-cli-reference\u002FSKILL.md` — REST ↔ GraphQL dual-bucket procedure\n",{"name":5,"metadata":41,"description":7},{"type":29},"main","d57b06df00b496fc5debe2002b49987696f02a8c",".claude\u002Fskills\u002Fpr-green-definition",0,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills","https:\u002F\u002Fgithub.com\u002Fjleechanorg","2026-11-12 14:45:07",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add jleechanorg\u002Fjleechan-skills --skill pr-green-definition",{"tool":55,"command":56},"bunx","bunx skills add jleechanorg\u002Fjleechan-skills --skill pr-green-definition",{"tool":58,"command":59},"pnpm","pnpm dlx skills add jleechanorg\u002Fjleechan-skills --skill pr-green-definition","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpr-green-definition\u002FSKILL.md",true,[],[64,82,104,118,131,147],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":36},"01M716Y5MTJ6GYJZ2ATXCJK8G4","instinct","Use when the user invokes \u002Finstinct or \u002Fin, or asks to \"message Instinct\", \"ask Instinct\", \"tell Instinct\", \"check Instinct\", or read replies from the configured peer assistant. iMessage first, WhatsApp Web as fallback.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Finstinct\u002FSKILL.md",[],[66,71,72,73,74,75,76,77,78,79,80,81],"user","when","replies","check","use","identity","whatsapp","gmail","read","message","ask",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":93,"publishedAt":36},"01M716Y4HF7FVVMJSA2CCVN5VF","hr","Compatibility alias for history-resume; produce the same fresh-state, provenance-aware resume briefing.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhr\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[84,94,95,96,97,98,99,100,101,102,103],"resume","compatibility","provenance","for","history","produce","alias","briefing","state","fresh",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":36},"01M716Y1FFNFKFJYYKF8HQA6T8","history-resume","Resume briefing for the current repository branch or worktree using fresh state and admitted history sources.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhistory-resume\u002FSKILL.md",[110],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[98,94,112,113,71,114,101,115,97,116,117,102,103],"history resume","branch","analysis","repository","worktree","sources",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":36},"01M716XWXJ8EPHK4RH9T14TR85","grok","Alias for the canonical grokbot browser conversation workflow; \u002Fgrok talks to the Grok bot the same way \u002Fdot talks to Dot.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrok\u002FSKILL.md",[],[120,125,126,127,97,25,100,128,129,130],"dot","bot","workflow","conversation","browser","grokbot",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":36},"01M70N9Q07DTE0EW5KFXMMMSJ0","codexa-bench","Compare `codexa` and normal `codex` on a fair split of comparable work by default; use `--strict` for duplicate runs of the exact same task.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcodexa-bench\u002FSKILL.md",[],[138,139,140,75,141,97,142,143,144,145,146],"codexa bench","work","split","default","duplicate","task","compare","normal","codex",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":151,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":166,"publishedAt":36},"01M6C24S2X60SP8BBFGAEKPEGW","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[155,160,163],{"categoryNo":156,"categoryName":157,"taxonomyType":158,"taxonomyTypeDesc":159},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":161,"categoryName":162,"taxonomyType":158,"taxonomyTypeDesc":159},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":164,"categoryName":165,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000032","设计师",[167,168,169,75,170,171,172,71,173,174,175,176,177,178,179,180,181,182,31,183,184,185,186,187,188,189,72,190],"frontend","design","frontend design","generic","ui design","react","html","components","code","artifacts","ui","aesthetics","Production","web components","landing","applications","web","css","create","examples","with","react components","web ui","pages"]