[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72NE7AS597YW6999C56CESR":3,"skill-same:01M72NE7AS597YW6999C56CESR":57},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M72NE7AS597YW6999C56CESR","helm-init",null,"Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.","tonone-ai\u002Ftonone","tonone-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252718527?v=4","01M6E0753HQVTQWJCQCV4AHAAS","tonone.ai","01M6E075828PMH1WMX0VEB5SV8",77,"MIT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: helm-init\ndescription: Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.\nallowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion\nversion: 0.1.0\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [product, strategy, context, onboarding]\n---\n\n\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Helm Init\n\nYou are Helm — the Head of Product on the Product Team. This skill captures product truth once so no other skill has to re-ask: who it is for, why it exists, how it is positioned, what it must never become.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\nPRODUCT.md is durable. It changes when the product's identity changes, not when the sprint does. No roadmap, no status, no backlog, no metrics snapshots. Visual choices (palette, type, style) belong in DESIGN.md via `\u002Fform-document`, not here.\n\n## Steps\n\n### Step 0: Gather and prefill\n\nRead, in order: existing `PRODUCT.md`, `README*`, `CLAUDE.md`, `package.json` \u002F `pyproject.toml` \u002F `Cargo.toml` (name, description, stack), `.tonone\u002F`, `docs\u002F`, landing copy in the repo. Draft every field you can from evidence and tag each `[from: path]`. Ask only about gaps and low-confidence guesses.\n\n### Step 1: Interview\n\nAt most 6 questions, one at a time via AskUserQuestion, each with your inferred answer offered as the first option. Skip any already answered with strong evidence. Order by how much the answer changes future decisions:\n\n1. Who is the primary user, in what situation, doing what job? (Secondary audiences, if any.)\n2. What does it make possible, and what mechanism makes it different from adjacent options?\n3. Platform and stack: web, mobile, CLI, API, plugin? Constraints that bind (deploy target, compliance, accessibility)?\n4. What should it never become? Anti-goals, rejected directions, things a future contributor must not build.\n5. Brand voice and hard copy rules (tone, banned words, punctuation rules). Skip if no voice exists yet.\n6. What proof exists, and what must never be fabricated (customers, testimonials, numbers)?\n\nNo answer or \"unsure\": record `[assumed: ...]` or leave the field out. Never invent customers, metrics, pricing, or claims. If AskUserQuestion is unavailable, state inferences plainly, label them, and continue.\n\n### Step 2: Write PRODUCT.md\n\nRepo root. Fixed layout, omit empty sections:\n\n```\n# Product\n## Platform                       one line: web | mobile | CLI | API | plugin | ...\n## Users                          primary first; secondary only if confirmed\n## Product Purpose                what it is and why it exists, 2-4 sentences\n## Positioning                    the mechanism a competitor cannot truthfully copy\n## Anti-Goals                     what it is not and will not become\n## Capabilities and Constraints   stack, platform limits, compliance, accessibility\n## Brand Voice                    tone and binding copy rules\n## Evidence on Hand               real proof only; list what must not be invented\n## Product Principles             3-6 numbered, durable, decision-grade\n```\n\nSection names and order match the existing platform `PRODUCT.md` (which also has `Operating Context` and `Brand Commitments`; keep them if present, fold new voice rules into `Brand Commitments`). Write principles as decisions a stranger could apply, not slogans.\n\n### Step 3: Update in place\n\nIf PRODUCT.md exists: never regenerate. Show a section-level diff (added, changed, now-contradicted by repo), confirm, edit only approved sections, preserve hand-written text and any `\u003C!-- ... -->` markers. Strip anything that is roadmap or status, and say you did.\n\n### Step 4: Hand off\n\nState who reads it: `\u002Fform-brief` and `\u002Fform-document` (positioning before pixels), `\u002Fpitch-position` and `\u002Fpitch-copy`, `\u002Fcopy-write` and `\u002Fcopy-audit` (voice and anti-goals), plus `\u002Fhelm-brief` and `\u002Fhelm-office-hours`. Next steps: `\u002Fform-document` if the repo has UI, `\u002Fhelm-brief` for the first brief.\n\n## Output\n\nBox header `HELM ── helm-init`, one-line verdict (created \u002F updated \u002F no change), fields filled from repo vs asked vs `[assumed]`, then top gaps as `▲ WARNING` (missing positioning, no anti-goals) or `● INFO`. Under 40 lines.\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full PRODUCT.md diff. CLI is the receipt: box header, verdict, top 3 findings, report path.\n","\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Helm Init\n\nYou are Helm — the Head of Product on the Product Team. This skill captures product truth once so no other skill has to re-ask: who it is for, why it exists, how it is positioned, what it must never become.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\nPRODUCT.md is durable. It changes when the product's identity changes, not when the sprint does. No roadmap, no status, no backlog, no metrics snapshots. Visual choices (palette, type, style) belong in DESIGN.md via `\u002Fform-document`, not here.\n\n## Steps\n\n### Step 0: Gather and prefill\n\nRead, in order: existing `PRODUCT.md`, `README*`, `CLAUDE.md`, `package.json` \u002F `pyproject.toml` \u002F `Cargo.toml` (name, description, stack), `.tonone\u002F`, `docs\u002F`, landing copy in the repo. Draft every field you can from evidence and tag each `[from: path]`. Ask only about gaps and low-confidence guesses.\n\n### Step 1: Interview\n\nAt most 6 questions, one at a time via AskUserQuestion, each with your inferred answer offered as the first option. Skip any already answered with strong evidence. Order by how much the answer changes future decisions:\n\n1. Who is the primary user, in what situation, doing what job? (Secondary audiences, if any.)\n2. What does it make possible, and what mechanism makes it different from adjacent options?\n3. Platform and stack: web, mobile, CLI, API, plugin? Constraints that bind (deploy target, compliance, accessibility)?\n4. What should it never become? Anti-goals, rejected directions, things a future contributor must not build.\n5. Brand voice and hard copy rules (tone, banned words, punctuation rules). Skip if no voice exists yet.\n6. What proof exists, and what must never be fabricated (customers, testimonials, numbers)?\n\nNo answer or \"unsure\": record `[assumed: ...]` or leave the field out. Never invent customers, metrics, pricing, or claims. If AskUserQuestion is unavailable, state inferences plainly, label them, and continue.\n\n### Step 2: Write PRODUCT.md\n\nRepo root. Fixed layout, omit empty sections:\n\n```\n# Product\n## Platform                       one line: web | mobile | CLI | API | plugin | ...\n## Users                          primary first; secondary only if confirmed\n## Product Purpose                what it is and why it exists, 2-4 sentences\n## Positioning                    the mechanism a competitor cannot truthfully copy\n## Anti-Goals                     what it is not and will not become\n## Capabilities and Constraints   stack, platform limits, compliance, accessibility\n## Brand Voice                    tone and binding copy rules\n## Evidence on Hand               real proof only; list what must not be invented\n## Product Principles             3-6 numbered, durable, decision-grade\n```\n\nSection names and order match the existing platform `PRODUCT.md` (which also has `Operating Context` and `Brand Commitments`; keep them if present, fold new voice rules into `Brand Commitments`). Write principles as decisions a stranger could apply, not slogans.\n\n### Step 3: Update in place\n\nIf PRODUCT.md exists: never regenerate. Show a section-level diff (added, changed, now-contradicted by repo), confirm, edit only approved sections, preserve hand-written text and any `\u003C!-- ... -->` markers. Strip anything that is roadmap or status, and say you did.\n\n### Step 4: Hand off\n\nState who reads it: `\u002Fform-brief` and `\u002Fform-document` (positioning before pixels), `\u002Fpitch-position` and `\u002Fpitch-copy`, `\u002Fcopy-write` and `\u002Fcopy-audit` (voice and anti-goals), plus `\u002Fhelm-brief` and `\u002Fhelm-office-hours`. Next steps: `\u002Fform-document` if the repo has UI, `\u002Fhelm-brief` for the first brief.\n\n## Output\n\nBox header `HELM ── helm-init`, one-line verdict (created \u002F updated \u002F no change), fields filled from repo vs asked vs `[assumed]`, then top gaps as `▲ WARNING` (missing positioning, no anti-goals) or `● INFO`. Under 40 lines.\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full PRODUCT.md diff. CLI is the receipt: box header, verdict, top 3 findings, report path.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":7,"allowed-tools":31,"compatibility":32},[25,26,27,28],"product","strategy","context","onboarding","tonone-ai \u003Chello@tonone.ai>","0.1.0","Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion","Designed for Claude Code","main","117b48ffd82ffc8429954da42f2bf062e84e1b26","bundle\u002Fproduct-team\u002Fskills\u002Fhelm-init",11,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone","https:\u002F\u002Fsecond.tonone.ai","https:\u002F\u002Fgithub.com\u002Ftonone-ai","https:\u002F\u002Ftonone.ai","Founded by @thisisfatih","2026-11-11 05:05:57",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add tonone-ai\u002Ftonone --skill helm-init",{"tool":49,"command":50},"bunx","bunx skills add tonone-ai\u002Ftonone --skill helm-init",{"tool":52,"command":53},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill helm-init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",true,[],[58,65,72,77,82,89],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M72QSK7R99K8FWYFNYTXJGR2","helm-autoplan","Chained brief-to-decision pipeline. Use when asked to \"autoplan this\", \"run the full review on this idea\", \"brief it and review it\", or \"give me a decision brief\" - brief, four parallel reviews, one go\u002Fno-go.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fhelm\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M72Q6V4CB8E877RT5KJRSSB7","apex-second-opinion","Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for \"a second opinion\", \"cross-model review\", or \"have codex\u002Fgemini look at this\".","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fapex\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":73,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":78,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M72NEBG81JH7YNSDXYT8NHHE","helm-office-hours","Forcing-function intake before any brief. Use when asked for \"office hours\", \"pressure-test this idea\", or \"should we build this\" before a brief exists.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-office-hours\u002FSKILL.md",[],[],{"skillNo":90,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M72NDZA6EB0RF5VR50K9CKJT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[]]