[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DKZX07CDDMSSXHAV6H39PZ":3,"skill-same:01M6DKZX07CDDMSSXHAV6H39PZ":134},{"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":28,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":65},"01M6DKZX07CDDMSSXHAV6H39PZ","design-upgrade",null,"팀 구성 강화 분석 (모델·역할 축)","Nharu\u002Fcc-cmds","Nharu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14357133?v=4","01M6DKV0D72FEBQABDAGSZ021P","nano","01M6DKV0TVG5GV22WQZBNRZ3ZT",3,"MIT","https:\u002F\u002Fgithub.com\u002FNharu\u002Fcc-cmds\u002Fblob\u002Fmaster\u002Fplugins\u002Fcc-cmds\u002Fskills\u002Fdesign-upgrade\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35],"design","upgrade","design upgrade","cc","opus","true","second","2026-11-10 10:12:30",false,"---\nname: design-upgrade\ndescription: 팀 구성 강화 분석 (모델·역할 축)\nwhen_to_use: 직전 `\u002Fdesign` 팀 구성 제안에서 opus 승격이 유의미한 역할이 있는지, 또는 누락 도메인을 메울 신규 역할·과부하 역할 분할이 필요한지 second-opinion으로 검토할 때\ndisable-model-invocation: true\nusage: \"\u002Fcc-cmds:design-upgrade\"\noptions: []\nnotes: |\n    이 커맨드는 별도 인자를 받지 않으며, 직전 `\u002Fdesign` 팀 구성 제안이 현재 대화 컨텍스트에 있어야 동작한다. 모델 승격과 역할 추가·분할은 강화가 유의미할 때만 제안하며, 그 외에는 유지 사유를 제시한다. 독립 실행 시 결과가 불정확할 수 있다.\n---\n\nAnalyze the team composition proposed in the preceding `\u002Fdesign` Step 2 output and produce a second opinion along **two axes** — model and role — recommending only *reinforcing* changes.\n\n**Read `${CLAUDE_SKILL_DIR}\u002F..\u002F_common\u002Fteam-upgrade-analysis.md`** for the axis-agnostic engine: the two-axis Scope, restraint principle, role-gap detection + HARD LIMIT, the per-OPERATION gates (restraint \u002F split \u002F remove \u002F merge), OPERATION output format and integrity rules, the per-existing-role invariant, the degraded-axis handling, and the Cross-axis synthesis. Resolve every `{PLACEHOLDER}` in that core against the `## Bindings` below. The Precondition, design-lite conflict guard, schema-drift sync-note, and 3-path Fallback that follow are this skill's injected prose.\n\n## Bindings\n\n| Placeholder | Value |\n| --- | --- |\n| `{SCOPE_LABEL}` | `탐색 범위` |\n| `{FIELD_ORDER}` | `역할 \u002F 탐색 범위 \u002F 모델` |\n| `{SOURCE_STEP}` | `\u002Fdesign` Step 2 |\n| `{ROSTER_SOT}` | `design\u002FSKILL.md` Step 2 (English prose: role \u002F exploration scope \u002F model, plus the model-alias set) |\n| `{LABEL_RELATION}` | conceptual translation (the Korean OPERATION labels conceptually correspond to Step 2's English-prose fields) |\n| `{ROLE_GAP_ANCHOR}` | *(empty — no skill-specific gap anchor)* |\n| `{RE_EXPLORATION_ANCHOR}` | the interview \u002F task narrative |\n| `{LITE_GUARD_TARGET}` | design-lite |\n| `{PRECONDITION}` | the preceding `\u002Fdesign` Step 2 team composition is in context |\n| `{MODEL_AXIS_DEGRADES_UNDER}` | Fallback Path 2 |\n| `{SAVED_DOC_LOCATION}` | `docs\u002F\u003Cslug>.md` |\n| `{REFEED_TARGET}` | `\u002Fdesign` Step 2 re-proposal (same target on every path) |\n\nThis skill declares no `## Operations Layer` — it uses the core's OPERATION set and forbidden-set unchanged, whatever that set currently contains. The set is deliberately **not** re-enumerated here: a copy of it would go stale the next time the core gains or loses an operation.\n\n## Precondition\n\nThis skill requires the preceding `\u002Fdesign` Step 2 team composition to be in context. It is a `disable-model-invocation: true` second-opinion skill and does NOT auto-chain `\u002Fdesign`.\n\n**design-lite conflict guard**: if the most recent proposal in context was made by `\u002Fdesign-lite` — judged by the command that produced it, not by its model mix, because `\u002Fdesign` now proposes `sonnet` by default and its smallest roster (one domain seat plus the verification seat) has the same two-`sonnet` shape — both axes conflict with the lite contract — UPGRADE→opus violates the sonnet pin, and every role-axis OPERATION mutates a roster the lite skill fixes by design (in either direction: the fixed size is the contract, so shrinking it breaks the contract exactly as growing it does). Emit the caveat and proceed only on explicit user confirmation. (Consistent with the cross-reference in `design-lite\u002FSKILL.md`.)\n\n**Schema-drift sync note**: the source of truth is `design\u002FSKILL.md` Step 2's team-composition field set (role \u002F exploration scope \u002F model, plus the model-alias set — English prose). If Step 2 changes that field set, manually sync this skill's OPERATION Korean labels and model aliases (the Korean labels are this skill's emit surface, conceptually corresponding to Step 2's English fields). Do NOT touch `design\u002FSKILL.md`. The residual risk of a missed sync is accepted without a lint.\n\n## Fallback\n\nWhen the precondition is not met, follow a 3-path fallback:\n\n- **Path 1 — session roster paste**: the user pastes the Step 2 composition → full two-axis analysis.\n- **Path 2 — reverse-engineer from a saved design doc (degraded — role axis only)**: `docs\u002F\u003Cslug>.md` captures architecture\u002Fscope but does NOT save the Step 2 roster (Step 4 saves only architecture \u002F decisions \u002F issues \u002F order). Role-gap detection is possible from the doc's scope, but the model axis is not (no current model assignments). State this limitation when taking this path. Because the model axis is impossible at the source, the core's degraded-axis handling fires here (`{MODEL_AXIS_DEGRADES_UNDER}` = Fallback Path 2): the split gate's cross-axis reconciliation and the Cross-axis synthesis treat the UPGRADE comparison term as N\u002FA and proceed on the role axis alone (skip the SPLIT-vs-UPGRADE tradeoff weighing). Also, since no interview is in session, the lightweight re-exploration anchor is the saved doc's architecture\u002Fscope narrative instead of the interview — limit to surfaces the doc cites\u002Fnames and their adjacent siblings under the same HARD LIMIT. **`REMOVE` and `MERGE` are suppressed on this path** for the same reason the model axis is: both take an existing roster role as their lookup key, and the saved doc holds no roster at all, so there is nothing to name. A gap-driven `ADD` needs no such key and survives; when an `ADD` on this path would exceed the team-size ceiling, the pairing it owes cannot be constructed here — say so and route the user back to a live Step 2 rather than emitting an unpaired over-budget `ADD`.\n- **Path 3 — start a new `\u002Fdesign`**: when neither is available, two-axis analysis is impossible — emit a Korean notice (e.g., *\"분석할 팀 구성이 없습니다. 먼저 `\u002Fcc-cmds:design`을 실행해 팀 구성을 받은 뒤 다시 호출하세요.\"*) and stop.\n","Analyze the team composition proposed in the preceding `\u002Fdesign` Step 2 output and produce a second opinion along **two axes** — model and role — recommending only *reinforcing* changes.\n\n**Read `${CLAUDE_SKILL_DIR}\u002F..\u002F_common\u002Fteam-upgrade-analysis.md`** for the axis-agnostic engine: the two-axis Scope, restraint principle, role-gap detection + HARD LIMIT, the per-OPERATION gates (restraint \u002F split \u002F remove \u002F merge), OPERATION output format and integrity rules, the per-existing-role invariant, the degraded-axis handling, and the Cross-axis synthesis. Resolve every `{PLACEHOLDER}` in that core against the `## Bindings` below. The Precondition, design-lite conflict guard, schema-drift sync-note, and 3-path Fallback that follow are this skill's injected prose.\n\n## Bindings\n\n| Placeholder | Value |\n| --- | --- |\n| `{SCOPE_LABEL}` | `탐색 범위` |\n| `{FIELD_ORDER}` | `역할 \u002F 탐색 범위 \u002F 모델` |\n| `{SOURCE_STEP}` | `\u002Fdesign` Step 2 |\n| `{ROSTER_SOT}` | `design\u002FSKILL.md` Step 2 (English prose: role \u002F exploration scope \u002F model, plus the model-alias set) |\n| `{LABEL_RELATION}` | conceptual translation (the Korean OPERATION labels conceptually correspond to Step 2's English-prose fields) |\n| `{ROLE_GAP_ANCHOR}` | *(empty — no skill-specific gap anchor)* |\n| `{RE_EXPLORATION_ANCHOR}` | the interview \u002F task narrative |\n| `{LITE_GUARD_TARGET}` | design-lite |\n| `{PRECONDITION}` | the preceding `\u002Fdesign` Step 2 team composition is in context |\n| `{MODEL_AXIS_DEGRADES_UNDER}` | Fallback Path 2 |\n| `{SAVED_DOC_LOCATION}` | `docs\u002F\u003Cslug>.md` |\n| `{REFEED_TARGET}` | `\u002Fdesign` Step 2 re-proposal (same target on every path) |\n\nThis skill declares no `## Operations Layer` — it uses the core's OPERATION set and forbidden-set unchanged, whatever that set currently contains. The set is deliberately **not** re-enumerated here: a copy of it would go stale the next time the core gains or loses an operation.\n\n## Precondition\n\nThis skill requires the preceding `\u002Fdesign` Step 2 team composition to be in context. It is a `disable-model-invocation: true` second-opinion skill and does NOT auto-chain `\u002Fdesign`.\n\n**design-lite conflict guard**: if the most recent proposal in context was made by `\u002Fdesign-lite` — judged by the command that produced it, not by its model mix, because `\u002Fdesign` now proposes `sonnet` by default and its smallest roster (one domain seat plus the verification seat) has the same two-`sonnet` shape — both axes conflict with the lite contract — UPGRADE→opus violates the sonnet pin, and every role-axis OPERATION mutates a roster the lite skill fixes by design (in either direction: the fixed size is the contract, so shrinking it breaks the contract exactly as growing it does). Emit the caveat and proceed only on explicit user confirmation. (Consistent with the cross-reference in `design-lite\u002FSKILL.md`.)\n\n**Schema-drift sync note**: the source of truth is `design\u002FSKILL.md` Step 2's team-composition field set (role \u002F exploration scope \u002F model, plus the model-alias set — English prose). If Step 2 changes that field set, manually sync this skill's OPERATION Korean labels and model aliases (the Korean labels are this skill's emit surface, conceptually corresponding to Step 2's English fields). Do NOT touch `design\u002FSKILL.md`. The residual risk of a missed sync is accepted without a lint.\n\n## Fallback\n\nWhen the precondition is not met, follow a 3-path fallback:\n\n- **Path 1 — session roster paste**: the user pastes the Step 2 composition → full two-axis analysis.\n- **Path 2 — reverse-engineer from a saved design doc (degraded — role axis only)**: `docs\u002F\u003Cslug>.md` captures architecture\u002Fscope but does NOT save the Step 2 roster (Step 4 saves only architecture \u002F decisions \u002F issues \u002F order). Role-gap detection is possible from the doc's scope, but the model axis is not (no current model assignments). State this limitation when taking this path. Because the model axis is impossible at the source, the core's degraded-axis handling fires here (`{MODEL_AXIS_DEGRADES_UNDER}` = Fallback Path 2): the split gate's cross-axis reconciliation and the Cross-axis synthesis treat the UPGRADE comparison term as N\u002FA and proceed on the role axis alone (skip the SPLIT-vs-UPGRADE tradeoff weighing). Also, since no interview is in session, the lightweight re-exploration anchor is the saved doc's architecture\u002Fscope narrative instead of the interview — limit to surfaces the doc cites\u002Fnames and their adjacent siblings under the same HARD LIMIT. **`REMOVE` and `MERGE` are suppressed on this path** for the same reason the model axis is: both take an existing roster role as their lookup key, and the saved doc holds no roster at all, so there is nothing to name. A gap-driven `ADD` needs no such key and survives; when an `ADD` on this path would exceed the team-size ceiling, the pairing it owes cannot be constructed here — say so and route the user back to a live Step 2 rather than emitting an unpaired over-budget `ADD`.\n- **Path 3 — start a new `\u002Fdesign`**: when neither is available, two-axis analysis is impossible — emit a Korean notice (e.g., *\"분석할 팀 구성이 없습니다. 먼저 `\u002Fcc-cmds:design`을 실행해 팀 구성을 받은 뒤 다시 호출하세요.\"*) and stop.\n",{"name":5,"notes":41,"usage":42,"options":43,"description":7,"when_to_use":44,"disable-model-invocation":45},"이 커맨드는 별도 인자를 받지 않으며, 직전 `\u002Fdesign` 팀 구성 제안이 현재 대화 컨텍스트에 있어야 동작한다. 모델 승격과 역할 추가·분할은 강화가 유의미할 때만 제안하며, 그 외에는 유지 사유를 제시한다. 독립 실행 시 결과가 불정확할 수 있다.","\u002Fcc-cmds:design-upgrade",[],"직전 `\u002Fdesign` 팀 구성 제안에서 opus 승격이 유의미한 역할이 있는지, 또는 누락 도메인을 메울 신규 역할·과부하 역할 분할이 필요한지 second-opinion으로 검토할 때",true,"master","f5e7f5e77d5e8603b1ec0e9247198315c7910461","plugins\u002Fcc-cmds\u002Fskills\u002Fdesign-upgrade",1,"https:\u002F\u002Fgithub.com\u002FNharu\u002Fcc-cmds","https:\u002F\u002Fgithub.com\u002FNharu","2026-11-11 07:18:55",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":45},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Nharu\u002Fcc-cmds --skill design-upgrade",{"tool":59,"command":60},"bunx","bunx skills add Nharu\u002Fcc-cmds --skill design-upgrade",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Nharu\u002Fcc-cmds --skill design-upgrade","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNharu\u002Fcc-cmds\u002Fblob\u002Fmaster\u002Fplugins\u002Fcc-cmds\u002Fskills\u002Fdesign-upgrade\u002FSKILL.md",[66,72,76,80,84,88,92,96,100,106,110,114,118,122,126,130],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"docs\u002Fawk-reference.md","REFERENCE","参考文档",9048,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fdocs\u002Fawk-reference.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"docs\u002Fbash-reference.md",8399,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fdocs\u002Fbash-reference.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"docs\u002Fcommon-mistakes.md",9210,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fdocs\u002Fcommon-mistakes.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"docs\u002Fgrep-reference.md",8691,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fdocs\u002Fgrep-reference.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"docs\u002Fregex-reference.md",8588,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fdocs\u002Fregex-reference.md",{"path":89,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":90,"sourceHtmlUrl":91},"docs\u002Fsed-reference.md",9415,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fdocs\u002Fsed-reference.md",{"path":93,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":94,"sourceHtmlUrl":95},"docs\u002Fshell-reference.md",8943,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fdocs\u002Fshell-reference.md",{"path":97,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":98,"sourceHtmlUrl":99},"docs\u002Fshellcheck-reference.md",7366,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fdocs\u002Fshellcheck-reference.md",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"examples\u002Fbad-bash.sh","SCRIPT","脚本",984,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fexamples\u002Fbad-bash.sh",{"path":107,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":108,"sourceHtmlUrl":109},"examples\u002Fbad-shell.sh",1032,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fexamples\u002Fbad-shell.sh",{"path":111,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":112,"sourceHtmlUrl":113},"examples\u002Fgood-bash.sh",1319,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fexamples\u002Fgood-bash.sh",{"path":115,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":116,"sourceHtmlUrl":117},"examples\u002Fgood-shell.sh",1219,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fexamples\u002Fgood-shell.sh",{"path":119,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Frun_ci_checks.sh",681,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fscripts\u002Frun_ci_checks.sh",{"path":123,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fshellcheck_wrapper.sh",4740,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fscripts\u002Fshellcheck_wrapper.sh",{"path":127,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":128,"sourceHtmlUrl":129},"scripts\u002Ftest_validate.sh",12096,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fscripts\u002Ftest_validate.sh",{"path":131,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":132,"sourceHtmlUrl":133},"scripts\u002Fvalidate.sh",15615,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Flatest-release-devops\u002Fbash-script-validator\u002Fscripts\u002Fvalidate.sh",[135,146,158,165,173,182],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":36},"01M6DNB8T41Y37D3M9JKHFT7HV","zeroargs","zero-argument command","https:\u002F\u002Fgithub.com\u002FNharu\u002Fcc-cmds\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Freadme-gen\u002Fsimple\u002Fzeroargs\u002FSKILL.md",[],[137,142,143,32,144,145],"when","argument","command","ZeRO",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":36},"01M6DNB5TG3T9QMEF3HPKJPER0","review","에이전트 팀을 활용한 다관점 코드 리뷰","https:\u002F\u002Fgithub.com\u002FNharu\u002Fcc-cmds\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Freadme-gen\u002Fpre-yq-skills\u002Freview\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[148,156,34,157],"pr","diff",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":36},"01M6DNAYNZFJR1TATEM9PVHGH2","implement","설계 문서 기반 구현","https:\u002F\u002Fgithub.com\u002FNharu\u002Fcc-cmds\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Freadme-gen\u002Fpre-yq-skills\u002Fimplement\u002FSKILL.md",[],[160,34],{"skillNo":166,"name":29,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":172,"publishedAt":36},"01M6DNAVQF4KERY94V79NVWAZA","에이전트 팀을 활용한 기능 설계 토론 진행","https:\u002F\u002Fgithub.com\u002FNharu\u002Fcc-cmds\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Freadme-gen\u002Fpre-yq-skills\u002Fdesign\u002FSKILL.md",[170,171],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[29,34],{"skillNo":174,"name":5,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":180,"publishedAt":36},"01M6DNASB3J3JQMZD57YBDHZ1A","팀원 모델 업그레이드 분석","https:\u002F\u002Fgithub.com\u002FNharu\u002Fcc-cmds\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Freadme-gen\u002Fpre-yq-skills\u002Fdesign-upgrade\u002FSKILL.md",[178,179],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[31,29,30,34,181],"haiku",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":190,"publishedAt":36},"01M6DNAA53K13C0REE8FDT3QHR","design-review","설계 문서 최종 리뷰","https:\u002F\u002Fgithub.com\u002FNharu\u002Fcc-cmds\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Freadme-gen\u002Fpre-yq-skills\u002Fdesign-review\u002FSKILL.md",[188,189],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[148,29,191,34],"design review"]