[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CANRGR3MNF2QYYYFZT3556":3,"skill-same:01M6CANRGR3MNF2QYYYFZT3556":67},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6CANRGR3MNF2QYYYFZT3556","session-learn-distill",null,"After a complex \u002F multi-turn session (>5 tool calls, multiple spawns, multiple commits, or user corrections), use this skill to extract \u002Flearn artifacts (memory + skills) BEFORE ending the session. Triggers on \"\u002Flearn\", \"\u002Flearn from this session\", \"anything to learn\", \"what did we learn\", \"skillify from this\", \"save this for next time\", or any post-session reflection ask.","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\u002Fhermes\u002Fskills\u002Fsession-learn-distill\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"learn","distill","session","session learn distill","tool calls","memory","for","calls","multi","post","triggers","time","next","reflection","use","extract","user","ask","tool","commits","save","artifacts","skillify","2026-11-10 10:12:30",false,"---\nname: session-learn-distill\ndescription: After a complex \u002F multi-turn session (>5 tool calls, multiple spawns, multiple commits, or user corrections), use this skill to extract \u002Flearn artifacts (memory + skills) BEFORE ending the session. Triggers on \"\u002Flearn\", \"\u002Flearn from this session\", \"anything to learn\", \"what did we learn\", \"skillify from this\", \"save this for next time\", or any post-session reflection ask.\n---\n\n# Session Learn Distill — \u002Flearn workflow\n\n## When to use\n\nAfter any session that meets ANY of these:\n- Spawned >=3 AO workers (multi-PR coordination)\n- Made >=3 commits\n- User corrected you at least once\n- Discovered a new file path \u002F config value \u002F pitfall that future sessions will hit\n- Used a workaround or recovery pattern that wasn't documented\n- Hit a three-home artifact drift (staging vs prod vs origin\u002Fmain)\n- Ran the cmux codex advisor pattern OR needed to fall back because cmux was wedged\n\nThe cost of skipping this is high — every \"wtf is this?\" Slack thread becomes a 30-min investigation instead of a 30-second skill load.\n\n## Pipeline (in order, every \u002Flearn)\n\n### 1. Extract the raw material\n\nBefore \u002Flearn artifacts, gather:\n- The user's original asks (in this conversation)\n- The corrections \u002F pushbacks the user gave (those are the highest-value signals)\n- The commands that failed and how you recovered\n- The files you wrote that contain reusable knowledge\n- The mem0 entries you saved (if any)\n\nA quick self-scan: re-read the last 5-10 user messages. For each correction, ask: \"would future-me hit this same trap?\" If yes, \u002Flearn it.\n\n### 2. Decide the destination\n\nFor each piece of knowledge, pick the right bucket:\n\n| Type of knowledge | Destination | Why |\n|-------------------|-------------|-----|\n| User preferences, personal facts | `mem0_conclude` (persistent across all sessions) | Survives even when skills aren't loaded |\n| Stable environment facts (paths, configs, ports) | `memory` action='add' (in-session memory) | Available immediately in current session |\n| Durable workflows (5+ steps, multiple commands) | `skill_manage` action='create' (new SKILL.md) | Loaded on-demand by future sessions |\n| Specific pitfalls \u002F gotchas | Patch an EXISTING skill with `skill_manage` action='patch' | Lives where future lookups will find it |\n| Three-home artifact contract | Patch `~\u002F.hermes_prod\u002FSOUL.md` `## COMMIT:` sections | Enforced by session-init scan |\n| User explicitly asked for a report in `~\u002Froadmap` (verified 2026-07-20, Slack `C09GRLXF9GR\u002Fp1784573431`) | Also write a dedicated `~\u002Froadmap\u002F\u003Ctopic>-YYYY-MM-DD.md` | Short-form audit trail lives in the monthly log; the dedicated report is the referenceable artifact |\n\n**Anti-pattern:** Don't put environment facts in skills (they go in memory). Don't put preferences in memory if they're session-specific.\n\n### 3. Apply the 5-rail closure contract (per three-home artifact rule)\n\nFor any new skill or SOUL.md patch:\n1. Write to `~\u002F.hermes_prod\u002F` (runtime, prod)\n2. Copy to `~\u002F.hermes\u002F` (staging)\n3. `git add` + `git commit` + `git push origin main` (origin)\n4. Verify: `git ls-files`, `git show origin\u002Fmain:\u003Cpath>`, count lines\n5. Log SHA in report \u002F Slack reply\n\nIf any of the 5 rails is missing, the skill is not durable.\n\n### 4. Test the trigger\n\nAfter writing the skill, write 2-3 realistic trigger queries (\"show me the iteration budget skill when I ask...\") and verify it triggers. The `skill-creator` skill has the full eval pattern.\n\n### 5. Tell the user what was learned\n\nEnd with a 1-line per artifact summary:\n- `mem0: \u003Centry name>` (saves to long-term memory)\n- `~\u002F.hermes\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (new skill, 5-rail closed)\n- `~\u002F.hermes\u002Fskills\u002F\u003Cexisting>\u002FSKILL.md` patched (pitfall added)\n- `~\u002F.hermes_prod\u002FSOUL.md` patched (COMMIT: added)\n\nThis lets the user audit what's in their harness.\n\n## Common mistakes\n\n- **Stopping at the report push.** The \u002Froadmap skill has a documented bug-ref where the agent stopped at \"report pushed, here are the issues\" — same pattern. \u002Flearn must include the COMMIT-PUSH step.\n- **Putting static config in skills.** If a value is a single number (e.g. \"Hermes is at 1000 turns\"), it goes in memory, not a 200-line skill. Skills are for workflows.\n- **Not testing the trigger.** A skill that exists but never loads is worse than no skill (false confidence). Use the eval pattern.\n- **Three-home drift.** A skill only in `~\u002F.hermes_prod\u002F` is gone on next `~\u002F.hermes` reset. Always commit.\n\n## This-session worked example (2026-06-27)\n\nIn the \u002Froadmap session that triggered this skill:\n- **L1 (new skill):** `hermes-budget-fields` — documents the 3 distinct iteration fields. Created this turn.\n- **L2 (patch existing skill):** `agento` SKILL.md — added `--claim-pr auto` pitfall. Pushed to origin\u002Fmain commit `0efe263bdd`.\n- **L3 (patch existing skill):** `roadmap` SKILL.md — added Step 8.5 \u002Fa fullrun drive phase. Pushed to origin\u002Fmain commit `8d6e888a4a`.\n- **L4 (mem0):** `hermes-budget-fields-three`, `ao-no-iteration-concept`, `auto-cron-clarification`.\n- **L5 (commit + push):** 4 commits on `jleechanorg\u002Fjleechanclaw`, 4 commits on `jleechanorg\u002Froadmap`, all on origin\u002Fmain.\n\nTotal artifacts produced in 1 turn: 1 new skill + 2 skill patches + 3 mem0 entries + 8 commits.\n\n## Related\n\n- `skillify` — class-level skill with the full skill creation pattern\n- `skill-creator` — eval-driven skill improvement loop\n- `hermes-deploy-pipeline` — staging\u002Fprod\u002Forigin sync contract\n- `mem0_search` \u002F `mem0_conclude` — memory tool reference\n- `~\u002F.hermes_prod\u002FSOUL.md` `## COMMIT: three-home-artifact-closure-contract`\n\n## Hermes-side `wiki-ingest` resolver gap (added 2026-07-20)\n\nThe Claude-side `\u002Fwiki-ingest` skill lives at `~\u002F.claude\u002Fskills\u002Fwiki-ingest\u002FSKILL.md` and is **not** in the Hermes resolver (`skill_view(name='wiki-ingest')` returns \"Skill not found\" from Hermes sessions). When running \u002Flearn closure from a Hermes session, this skill's \"Always wiki-ingest (call the skill, do not write files manually)\" rule cannot be honored.\n\n**Fallback when wiki-ingest is unreachable from the runtime:**\n1. Write `~\u002Fllm_wiki\u002Fwiki\u002Fsources\u002F\u003Cslug>.md` directly via `write_file` with full YAML frontmatter (title, type, tags, sources, created, updated) — match the format used by existing source pages in the wiki\n2. Write\u002Fupdate `~\u002Fllm_wiki\u002Fwiki\u002Fentities\u002F\u003Cname>.md` for every named entity (orgs, hosts, tools) — same frontmatter shape\n3. Prepend a Sources entry at the top of `~\u002Fllm_wiki\u002Fwiki\u002Findex.md` `## Sources` section (after the `## Sources` heading, before the first existing entry) via `patch` mode=replace targeting the heading + first-row anchor\n4. Append `## [YYYY-MM-DD] ingest | \u003Ctitle>` to `~\u002Fllm_wiki\u002Fwiki\u002Flog.md` listing every file created\u002Fupdated\n5. Use `[[wikilinks]]` in source pages linking to entity pages (e.g. `[[Prime Radiant]]`, `[[Cloud-Superpowers-Build]]`)\n\nThis deviation from the Claude-side `\u002Flearn` skill's \"do not write files into `~\u002Fllm_wiki\u002Fwiki\u002F` directly\" rule is acceptable because the rule's purpose (forcing the skill to do entity\u002Fconcept extraction) cannot be honored when the skill is unreachable. **Long-term fix**: ship a Hermes-side overlay at `~\u002F.hermes\u002Fskills\u002Fwiki-ingest\u002FSKILL.md` so `skill_view(name='wiki-ingest')` resolves from any runtime — separate bead.\n","# Session Learn Distill — \u002Flearn workflow\n\n## When to use\n\nAfter any session that meets ANY of these:\n- Spawned >=3 AO workers (multi-PR coordination)\n- Made >=3 commits\n- User corrected you at least once\n- Discovered a new file path \u002F config value \u002F pitfall that future sessions will hit\n- Used a workaround or recovery pattern that wasn't documented\n- Hit a three-home artifact drift (staging vs prod vs origin\u002Fmain)\n- Ran the cmux codex advisor pattern OR needed to fall back because cmux was wedged\n\nThe cost of skipping this is high — every \"wtf is this?\" Slack thread becomes a 30-min investigation instead of a 30-second skill load.\n\n## Pipeline (in order, every \u002Flearn)\n\n### 1. Extract the raw material\n\nBefore \u002Flearn artifacts, gather:\n- The user's original asks (in this conversation)\n- The corrections \u002F pushbacks the user gave (those are the highest-value signals)\n- The commands that failed and how you recovered\n- The files you wrote that contain reusable knowledge\n- The mem0 entries you saved (if any)\n\nA quick self-scan: re-read the last 5-10 user messages. For each correction, ask: \"would future-me hit this same trap?\" If yes, \u002Flearn it.\n\n### 2. Decide the destination\n\nFor each piece of knowledge, pick the right bucket:\n\n| Type of knowledge | Destination | Why |\n|-------------------|-------------|-----|\n| User preferences, personal facts | `mem0_conclude` (persistent across all sessions) | Survives even when skills aren't loaded |\n| Stable environment facts (paths, configs, ports) | `memory` action='add' (in-session memory) | Available immediately in current session |\n| Durable workflows (5+ steps, multiple commands) | `skill_manage` action='create' (new SKILL.md) | Loaded on-demand by future sessions |\n| Specific pitfalls \u002F gotchas | Patch an EXISTING skill with `skill_manage` action='patch' | Lives where future lookups will find it |\n| Three-home artifact contract | Patch `~\u002F.hermes_prod\u002FSOUL.md` `## COMMIT:` sections | Enforced by session-init scan |\n| User explicitly asked for a report in `~\u002Froadmap` (verified 2026-07-20, Slack `C09GRLXF9GR\u002Fp1784573431`) | Also write a dedicated `~\u002Froadmap\u002F\u003Ctopic>-YYYY-MM-DD.md` | Short-form audit trail lives in the monthly log; the dedicated report is the referenceable artifact |\n\n**Anti-pattern:** Don't put environment facts in skills (they go in memory). Don't put preferences in memory if they're session-specific.\n\n### 3. Apply the 5-rail closure contract (per three-home artifact rule)\n\nFor any new skill or SOUL.md patch:\n1. Write to `~\u002F.hermes_prod\u002F` (runtime, prod)\n2. Copy to `~\u002F.hermes\u002F` (staging)\n3. `git add` + `git commit` + `git push origin main` (origin)\n4. Verify: `git ls-files`, `git show origin\u002Fmain:\u003Cpath>`, count lines\n5. Log SHA in report \u002F Slack reply\n\nIf any of the 5 rails is missing, the skill is not durable.\n\n### 4. Test the trigger\n\nAfter writing the skill, write 2-3 realistic trigger queries (\"show me the iteration budget skill when I ask...\") and verify it triggers. The `skill-creator` skill has the full eval pattern.\n\n### 5. Tell the user what was learned\n\nEnd with a 1-line per artifact summary:\n- `mem0: \u003Centry name>` (saves to long-term memory)\n- `~\u002F.hermes\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (new skill, 5-rail closed)\n- `~\u002F.hermes\u002Fskills\u002F\u003Cexisting>\u002FSKILL.md` patched (pitfall added)\n- `~\u002F.hermes_prod\u002FSOUL.md` patched (COMMIT: added)\n\nThis lets the user audit what's in their harness.\n\n## Common mistakes\n\n- **Stopping at the report push.** The \u002Froadmap skill has a documented bug-ref where the agent stopped at \"report pushed, here are the issues\" — same pattern. \u002Flearn must include the COMMIT-PUSH step.\n- **Putting static config in skills.** If a value is a single number (e.g. \"Hermes is at 1000 turns\"), it goes in memory, not a 200-line skill. Skills are for workflows.\n- **Not testing the trigger.** A skill that exists but never loads is worse than no skill (false confidence). Use the eval pattern.\n- **Three-home drift.** A skill only in `~\u002F.hermes_prod\u002F` is gone on next `~\u002F.hermes` reset. Always commit.\n\n## This-session worked example (2026-06-27)\n\nIn the \u002Froadmap session that triggered this skill:\n- **L1 (new skill):** `hermes-budget-fields` — documents the 3 distinct iteration fields. Created this turn.\n- **L2 (patch existing skill):** `agento` SKILL.md — added `--claim-pr auto` pitfall. Pushed to origin\u002Fmain commit `0efe263bdd`.\n- **L3 (patch existing skill):** `roadmap` SKILL.md — added Step 8.5 \u002Fa fullrun drive phase. Pushed to origin\u002Fmain commit `8d6e888a4a`.\n- **L4 (mem0):** `hermes-budget-fields-three`, `ao-no-iteration-concept`, `auto-cron-clarification`.\n- **L5 (commit + push):** 4 commits on `jleechanorg\u002Fjleechanclaw`, 4 commits on `jleechanorg\u002Froadmap`, all on origin\u002Fmain.\n\nTotal artifacts produced in 1 turn: 1 new skill + 2 skill patches + 3 mem0 entries + 8 commits.\n\n## Related\n\n- `skillify` — class-level skill with the full skill creation pattern\n- `skill-creator` — eval-driven skill improvement loop\n- `hermes-deploy-pipeline` — staging\u002Fprod\u002Forigin sync contract\n- `mem0_search` \u002F `mem0_conclude` — memory tool reference\n- `~\u002F.hermes_prod\u002FSOUL.md` `## COMMIT: three-home-artifact-closure-contract`\n\n## Hermes-side `wiki-ingest` resolver gap (added 2026-07-20)\n\nThe Claude-side `\u002Fwiki-ingest` skill lives at `~\u002F.claude\u002Fskills\u002Fwiki-ingest\u002FSKILL.md` and is **not** in the Hermes resolver (`skill_view(name='wiki-ingest')` returns \"Skill not found\" from Hermes sessions). When running \u002Flearn closure from a Hermes session, this skill's \"Always wiki-ingest (call the skill, do not write files manually)\" rule cannot be honored.\n\n**Fallback when wiki-ingest is unreachable from the runtime:**\n1. Write `~\u002Fllm_wiki\u002Fwiki\u002Fsources\u002F\u003Cslug>.md` directly via `write_file` with full YAML frontmatter (title, type, tags, sources, created, updated) — match the format used by existing source pages in the wiki\n2. Write\u002Fupdate `~\u002Fllm_wiki\u002Fwiki\u002Fentities\u002F\u003Cname>.md` for every named entity (orgs, hosts, tools) — same frontmatter shape\n3. Prepend a Sources entry at the top of `~\u002Fllm_wiki\u002Fwiki\u002Findex.md` `## Sources` section (after the `## Sources` heading, before the first existing entry) via `patch` mode=replace targeting the heading + first-row anchor\n4. Append `## [YYYY-MM-DD] ingest | \u003Ctitle>` to `~\u002Fllm_wiki\u002Fwiki\u002Flog.md` listing every file created\u002Fupdated\n5. Use `[[wikilinks]]` in source pages linking to entity pages (e.g. `[[Prime Radiant]]`, `[[Cloud-Superpowers-Build]]`)\n\nThis deviation from the Claude-side `\u002Flearn` skill's \"do not write files into `~\u002Fllm_wiki\u002Fwiki\u002F` directly\" rule is acceptable because the rule's purpose (forcing the skill to do entity\u002Fconcept extraction) cannot be honored when the skill is unreachable. **Long-term fix**: ship a Hermes-side overlay at `~\u002F.hermes\u002Fskills\u002Fwiki-ingest\u002FSKILL.md` so `skill_view(name='wiki-ingest')` resolves from any runtime — separate bead.\n",{"name":5,"description":7},"main","05df7380981a2c4af868ce0fa57962ae0eea62a9","hermes\u002Fskills\u002Fsession-learn-distill",0,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills","https:\u002F\u002Fgithub.com\u002Fjleechanorg","2026-11-11 22:19:36",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add jleechanorg\u002Fjleechan-skills --skill session-learn-distill",{"tool":59,"command":60},"bunx","bunx skills add jleechanorg\u002Fjleechan-skills --skill session-learn-distill",{"tool":62,"command":63},"pnpm","pnpm dlx skills add jleechanorg\u002Fjleechan-skills --skill session-learn-distill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fsession-learn-distill\u002FSKILL.md",true,[],[68,83,104,118,132,148],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":41},"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",[],[70,34,75,76,77,32,78,79,80,81,82,35],"when","replies","check","identity","whatsapp","gmail","read","message",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":94,"publishedAt":41},"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",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[85,95,96,97,24,98,99,100,101,102,103],"resume","compatibility","provenance","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":41},"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":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[98,95,112,113,34,114,101,115,24,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":41},"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,24,128,100,129,130,131],"dot","bot","workflow","canonical","conversation","browser","grokbot",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":41},"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",[],[139,140,141,32,142,24,143,144,145,146,147],"codexa bench","work","split","default","duplicate","task","compare","normal","codex",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":152,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":167,"publishedAt":41},"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",[156,161,164],{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":162,"categoryName":163,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":165,"categoryName":166,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000032","设计师",[168,169,170,32,171,172,173,34,174,175,176,39,177,178,179,180,181,182,183,184,185,186,187,188,189,190,75,191],"frontend","design","frontend design","generic","ui design","react","html","components","code","ui","aesthetics","Production","web components","landing","applications","quality","web","css","create","examples","with","react components","web ui","pages"]