[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79S4W6DSTMNXM3409X5FZRQ":3,"skill-same:01M79S4W6DSTMNXM3409X5FZRQ":44},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79S4W6DSTMNXM3409X5FZRQ","to-ticket",null,"Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published via taskr.","ro-56\u002Frepo-dashboard","ro-56","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31988896?v=4","01M79S3TVE085R308S56XHHEZR","Rodrigo","01M79S3TW2BPEPVX31R3RCZJ96",0,"MIT","https:\u002F\u002Fgithub.com\u002Fro-56\u002Frepo-dashboard\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fto-ticket\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: to-ticket\ndescription: Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published via taskr.\n---\n\n# To Tickets\n\nBreak a plan, spec, or conversation into a set of **tickets** — tracer-bullet vertical slices, each declaring the tickets that **block** it. Tickets are published via `taskr`.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a reference (a ticket ID or path) as an argument, fetch it with `taskr show \u003Cid>` and read its full body.\n\n### 2. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\nLook for opportunities to prefactor the code to make the implementation easier. \"Make the change easy, then make the easy change.\"\n\n### 3. Draft vertical slices\n\nBreak the work into **tracer bullet** tickets.\n\n\u003Cvertical-slice-rules>\n\n- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer\n- A completed slice is demoable or verifiable on its own\n- Each slice is sized to fit in a single fresh context window\n- Any prefactoring should be done first\n\n\u003C\u002Fvertical-slice-rules>\n\nGive each ticket its **blocking edges** — the other tickets that must complete before it can start.\n\n**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change — rename a column, retype a shared symbol — whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket — green is promised only there.\n\n### 4. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each ticket, show:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets (if any) must complete first\n- **What it delivers**: the end-to-end behaviour this ticket makes work\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the blocking edges correct — does each ticket only depend on tickets that genuinely gate it?\n- Should any tickets be merged or split further?\n\nIterate until the user approves the breakdown.\n\n### 5. Publish via taskr\n\nEnsure taskr is initialized (`taskr init` — safe to re-run).\n\nCreate tickets in dependency order (blockers first) so each ticket's ID is available for linking:\n\n```bash\n# Create each ticket\ntaskr add \"\u003Ctitle>\" --type task --mode afk --body \"\u003Cdescription with acceptance criteria>\"\n\n# Link dependencies (dependent blocks until depends-on is closed)\ntaskr link \u003Cdependent-id> \u003Cdepends-on-id>\n\n# Link to the task epic (if any)\ntaskr relate \u003Coriginal-reference-id> \u003Cnew-ticket-id>\n```\n\nTask relations are directed: `taskr relate \u003Cfrom> \u003Cto>` means \"from\" is a subtask of \"to\". The epic is the original reference ticket, and each new ticket is a subtask of it.\n\nFor each ticket's `--body`, include:\n\n- **What to build** — the end-to-end behaviour from the user's perspective\n- **Acceptance criteria** — as a markdown checklist\n\nAvoid specific file paths or code snippets in the body — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype.\n\n### 6. Verify\n\nRun `taskr ready` to confirm the unblocked tickets are correct, and `taskr dep-tree \u003Cid>` on the final ticket to confirm the full dependency graph looks right.\n","# To Tickets\n\nBreak a plan, spec, or conversation into a set of **tickets** — tracer-bullet vertical slices, each declaring the tickets that **block** it. Tickets are published via `taskr`.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a reference (a ticket ID or path) as an argument, fetch it with `taskr show \u003Cid>` and read its full body.\n\n### 2. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\nLook for opportunities to prefactor the code to make the implementation easier. \"Make the change easy, then make the easy change.\"\n\n### 3. Draft vertical slices\n\nBreak the work into **tracer bullet** tickets.\n\n\u003Cvertical-slice-rules>\n\n- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer\n- A completed slice is demoable or verifiable on its own\n- Each slice is sized to fit in a single fresh context window\n- Any prefactoring should be done first\n\n\u003C\u002Fvertical-slice-rules>\n\nGive each ticket its **blocking edges** — the other tickets that must complete before it can start.\n\n**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change — rename a column, retype a shared symbol — whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket — green is promised only there.\n\n### 4. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each ticket, show:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets (if any) must complete first\n- **What it delivers**: the end-to-end behaviour this ticket makes work\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the blocking edges correct — does each ticket only depend on tickets that genuinely gate it?\n- Should any tickets be merged or split further?\n\nIterate until the user approves the breakdown.\n\n### 5. Publish via taskr\n\nEnsure taskr is initialized (`taskr init` — safe to re-run).\n\nCreate tickets in dependency order (blockers first) so each ticket's ID is available for linking:\n\n```bash\n# Create each ticket\ntaskr add \"\u003Ctitle>\" --type task --mode afk --body \"\u003Cdescription with acceptance criteria>\"\n\n# Link dependencies (dependent blocks until depends-on is closed)\ntaskr link \u003Cdependent-id> \u003Cdepends-on-id>\n\n# Link to the task epic (if any)\ntaskr relate \u003Coriginal-reference-id> \u003Cnew-ticket-id>\n```\n\nTask relations are directed: `taskr relate \u003Cfrom> \u003Cto>` means \"from\" is a subtask of \"to\". The epic is the original reference ticket, and each new ticket is a subtask of it.\n\nFor each ticket's `--body`, include:\n\n- **What to build** — the end-to-end behaviour from the user's perspective\n- **Acceptance criteria** — as a markdown checklist\n\nAvoid specific file paths or code snippets in the body — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype.\n\n### 6. Verify\n\nRun `taskr ready` to confirm the unblocked tickets are correct, and `taskr dep-tree \u003Cid>` on the final ticket to confirm the full dependency graph looks right.\n",{"name":5,"description":7},"main","eefc243af407341b8f16e77cc9900c45fb6f0ee0",".claude\u002Fskills\u002Fto-ticket","https:\u002F\u002Fgithub.com\u002Fro-56\u002Frepo-dashboard","https:\u002F\u002Fgithub.com\u002Fro-56","2026-08-04 20:24:30",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add ro-56\u002Frepo-dashboard --skill to-ticket",{"tool":36,"command":37},"bunx","bunx skills add ro-56\u002Frepo-dashboard --skill to-ticket",{"tool":39,"command":40},"pnpm","pnpm dlx skills add ro-56\u002Frepo-dashboard --skill to-ticket","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fro-56\u002Frepo-dashboard\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fto-ticket\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M79S5ZXJP8335YHKWK5CDJ3G","sveltekit-structure","SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.","https:\u002F\u002Fgithub.com\u002Fro-56\u002Frepo-dashboard\u002Fblob\u002Fmain\u002Fsrc\u002F.claude\u002Fskills\u002Fsveltekit-structure\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79S5W324WD1G026FNQ67AD8","sveltekit-data-flow","SvelteKit data flow guidance. Use when working with load functions, form actions, server\u002Fclient boundaries, serialization, or invalidation.","https:\u002F\u002Fgithub.com\u002Fro-56\u002Frepo-dashboard\u002Fblob\u002Fmain\u002Fsrc\u002F.claude\u002Fskills\u002Fsveltekit-data-flow\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79S5RE6GTCEH06PV4P1RB42","svelte-template-directives","Svelte template directive guidance. Use when working with snippets, attachments, dynamic HTML, declaration tags, debugging tags, or global DOM events.","https:\u002F\u002Fgithub.com\u002Fro-56\u002Frepo-dashboard\u002Fblob\u002Fmain\u002Fsrc\u002F.claude\u002Fskills\u002Fsvelte-template-directives\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79S5MSBD8R46CFB0YEYSZ1P","svelte-styling","Svelte CSS styling patterns. Use for scoped styles, CSS custom properties, style: directive, :global, or styling child components.","https:\u002F\u002Fgithub.com\u002Fro-56\u002Frepo-dashboard\u002Fblob\u002Fmain\u002Fsrc\u002F.claude\u002Fskills\u002Fsvelte-styling\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79S5H8XB5DA46FFM02PTBJD","svelte-runes","Implement Svelte 5 runes correctly. Use for reactive state, props, effects, $state.raw, $derived.by, $props, and $bindable.","https:\u002F\u002Fgithub.com\u002Fro-56\u002Frepo-dashboard\u002Fblob\u002Fmain\u002Fsrc\u002F.claude\u002Fskills\u002Fsvelte-runes\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79S5DHAT20HYC8HAFRT09V8","svelte-layerchart","Build Svelte LayerChart components. Use for tooltip snippets, Chart context access, gradients, highlights, axes, and Svelte 5 snippet patterns.","https:\u002F\u002Fgithub.com\u002Fro-56\u002Frepo-dashboard\u002Fblob\u002Fmain\u002Fsrc\u002F.claude\u002Fskills\u002Fsvelte-layerchart\u002FSKILL.md",[],[]]