[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NF4KHY7797M1MZ97F5N00":3,"skill-same:01M71NF4KHY7797M1MZ97F5N00":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":25,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":13,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M71NF4KHY7797M1MZ97F5N00","code-craft",null,"Contract-first coding standard for writing code. Use before you implement a feature or fix, refactor code, or write tests, and when trimming code you just wrote that accumulated defensive guards, silent fallbacks, speculative abstractions, or unrelated changes. Write against the checked contract and the current requirement instead of coding around uncertainty. Not an independent review or merge decision; to review a diff, use code-craft-review.","SikongJueluo\u002Fskills","SikongJueluo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F53223107?v=4","01M71NEWK46KJB0R64SBCD990Z","01M71NEWKPCXWFQFMNTXW5ZYQN",0,"MIT","https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcode-craft\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000037","律师与法务",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"code craft","code","craft","contract","guards","when","for","uncertainty","you","refactor code","feature","tests","writing","diff","use","fix","just","decision","file","write tests","2026-11-10 10:56:23",false,"---\nname: code-craft\ndescription: Contract-first coding standard for writing code. Use before you implement a feature or fix, refactor code, or write tests, and when trimming code you just wrote that accumulated defensive guards, silent fallbacks, speculative abstractions, or unrelated changes. Write against the checked contract and the current requirement instead of coding around uncertainty. Not an independent review or merge decision; to review a diff, use code-craft-review.\nargument-hint: \"[optional task, file, or decision to focus]\"\n---\n\n# code-craft\n\nWrite code that satisfies the current requirement directly, on evidence. **Do not convert your own uncertainty into runtime complexity.**\n\nThe quality bar is [references\u002Fstandards.md](references\u002Fstandards.md). Read it before the first edit; this page is the working procedure.\n\n## 1. Establish the local contract\n\nRead the project's rules (AGENTS.md, CLAUDE.md, docs, lint, tests) and the code you are about to change. For every interface whose behavior changes the implementation, find the guarantee: declaration, implementation, boundary validation, tests, docs. Callers show usage, not the guarantee.\n\nInvestigate until the decision is determined, not until the repository is understood. When a question stays open, report the unknown instead of choosing a contract and defending against it.\n\nCompletion: for each guarantee you rely on or guard, you can name its source; open questions that would change behavior are stated, not coded around.\n\n## 2. Implement the current need\n\nWrite the simplest direct implementation that satisfies the task under the standards. A new guard, default, retry, wrapper, config, or layer needs a fact it serves. Let errors propagate through the project's existing mechanism unless this code owns a recovery.\n\nPut the judgment in the code shape, not in a justification report or design notes.\n\nCompletion: every added branch and abstraction has a current reason, and the diff contains nothing the requirement does not need.\n\n## 3. Trim and verify\n\nReread your own diff for code added to satisfy uncertainty rather than a requirement. Prefer the clearer shape over the shorter one. Run the project's required checks (format, lint, typecheck, tests) and know their result.\n\nCompletion: the diff is what you would defend in review, and verification results are known or their absence is reported.\n","# code-craft\n\nWrite code that satisfies the current requirement directly, on evidence. **Do not convert your own uncertainty into runtime complexity.**\n\nThe quality bar is [references\u002Fstandards.md](references\u002Fstandards.md). Read it before the first edit; this page is the working procedure.\n\n## 1. Establish the local contract\n\nRead the project's rules (AGENTS.md, CLAUDE.md, docs, lint, tests) and the code you are about to change. For every interface whose behavior changes the implementation, find the guarantee: declaration, implementation, boundary validation, tests, docs. Callers show usage, not the guarantee.\n\nInvestigate until the decision is determined, not until the repository is understood. When a question stays open, report the unknown instead of choosing a contract and defending against it.\n\nCompletion: for each guarantee you rely on or guard, you can name its source; open questions that would change behavior are stated, not coded around.\n\n## 2. Implement the current need\n\nWrite the simplest direct implementation that satisfies the task under the standards. A new guard, default, retry, wrapper, config, or layer needs a fact it serves. Let errors propagate through the project's existing mechanism unless this code owns a recovery.\n\nPut the judgment in the code shape, not in a justification report or design notes.\n\nCompletion: every added branch and abstraction has a current reason, and the diff contains nothing the requirement does not need.\n\n## 3. Trim and verify\n\nReread your own diff for code added to satisfy uncertainty rather than a requirement. Prefer the clearer shape over the shorter one. Run the project's required checks (format, lint, typecheck, tests) and know their result.\n\nCompletion: the diff is what you would defend in review, and verification results are known or their absence is reported.\n",{"name":5,"description":7,"argument-hint":51},"[optional task, file, or decision to focus]","main","f48fc8bda161a30c80be9ca1189279414dde1f3a","skills\u002Fcode-craft","https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills","https:\u002F\u002Fgithub.com\u002FSikongJueluo","https:\u002F\u002Fwww.swordlost.top","安得广厦千万间，大庇天下寒士俱欢颜！","2026-10-28 22:03:31",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add SikongJueluo\u002Fskills --skill code-craft",{"tool":66,"command":67},"bunx","bunx skills add SikongJueluo\u002Fskills --skill code-craft",{"tool":69,"command":70},"pnpm","pnpm dlx skills add SikongJueluo\u002Fskills --skill code-craft","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcode-craft\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fstandards.md","REFERENCE","参考文档",8734,"https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcode-craft\u002Freferences\u002Fstandards.md",[81,104,120,140,171,192],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":46},"01M71NFQMX5RNAXMZCXTCA0FFW","teaching","Teach toward a maintainable implementation when the user asks to learn before building, or says they are unfamiliar with technology required by a development task. Use for conversational co-design tied to real project work; not for general explanations, standalone tutorials, or persistent courses.","https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fteaching\u002FSKILL.md",[],[83,88,89,40,31,90,91,92,93,94,95,32,96,97,98,99,100,101,102,103],"implementation","task","learn","user","before building","project work","project","co","development","courses","standalone","work","with","technology","general","design",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":46},"01M71NFP48KR5WA41MWB59MBSZ","teach-me","Learn enough to co-design and maintain a real development change.","https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fteach-me\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000039","教师与教育",[114,115,116,95,90,96,117,118,103,119],"teach me","me","teach","maintain","change","true",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":46},"01M71NFM3K25R1843319SZ9JJ7","review-with-me","Curate the code worth a human's attention and present it in reviewable slices.","https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Freview-with-me\u002FSKILL.md",[],[115,100,127,128,129,130,131,132,133,134,27,119,135,136,137,138,139],"review","review with me","it","language","present","bookmark","curate","human","commits","scope","branch","attention","natural language",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":154,"publishedAt":46},"01M71NFHBZQR70H9PATVKWDN68","refactor-ui","Improve an existing UI, screen, slide deck, or visual artifact that the user mostly accepts but finds too busy, unclear, inconsistent, ugly, plain, or over-decorated. Use when the user gives feedback on a rendered artifact and wants a bounded revision that preserves what works. Not for building from scratch, exploring an undecided visual direction, deck production or conversion, or implementing a specified design.","https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frefactor-ui\u002FSKILL.md",[146,151],{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000032","设计师",[155,156,157,158,159,160,161,162,163,31,164,40,103,165,166,167,168,32,169,170],"refactor","ui","refactor ui","implementing","artifact","From Scratch","conversion","visual","URL","Existing","improve","screen","scratch","deck","direction","feedback",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":46},"01M71NFDMN0VZ3JYMZBK6BJF5P","jj-describe","Write and apply concise, self-contained Conventional Commits descriptions for Jujutsu commits. Use when the user asks to describe a jj commit, and after completing a cohesive code or documentation change in a jj repository when the current non-empty commit is undescribed. Explain what changed and why without context-only planning labels such as P0 or P1.","https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjj-describe\u002FSKILL.md",[],[178,179,180,181,40,182,183,184,32,135,185,39,186,187,31,27,188,189,190,191],"jj describe","jj","describe","as","only","labels","jujutsu","planning","cohesive","show","git log","apply","Bash","conventional commits",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":46},"01M71NFBQXB3GDS2V272956BWN","jj-desc","Write a concise, self-contained Jujutsu commit description that explains what changed and why.","https:\u002F\u002Fgithub.com\u002FSikongJueluo\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjj-desc\u002FSKILL.md",[],[199,179,200,201,202,203,184,204,118,119,205,206],"jj desc","write","self-contained","commit","why","concise","self","id"]