[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPDFZD4DE68Y3Z90HPK71P":3,"skill-same:01M7CPDFZD4DE68Y3Z90HPK71P":53},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M7CPDFZD4DE68Y3Z90HPK71P","to-tickets",null,"Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","ThienHN0910\u002FTemplate-P","ThienHN0910","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F84314573?v=4","01M7CPATNRT0K5DSRBBHEQJJT3","HO NGOC THIEN","01M7CPATPDW689M0YJMGGJGFYZ",2,"MIT","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fpocock\u002Fto-tickets\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: to-tickets\ndescription: Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).\ndisable-model-invocation: true\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.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fsetup-matt-pocock-skills`.\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 spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.\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. A ticket with no blockers can start immediately.\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 the tickets to the configured tracker\n\nPublish the approved tickets. **How** depends on the tracker `\u002Fsetup-matt-pocock-skills` configured; the tickets are the same either way, only the shape of the blocking edges changes:\n\n- **Local files** → write one file per ticket under `.scratch\u002F\u003Cfeature-slug>\u002Fissues\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first). Each file's \"Blocked by\" lists the numbers\u002Ftitles it depends on. Use the per-ticket file template below: one ticket per file, never a single combined file.\n- **A real issue tracker (GitHub, Linear, …)** → publish one issue per ticket in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Use the platform's native blocking \u002F sub-issue relationship where it has one; otherwise set each ticket's \"Blocked by\" to the blocking issues. Apply the `ready-for-agent` triage label unless instructed otherwise; the tickets are agent-grabbable by construction.\n\nWork the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.\n\nDo NOT close or modify any parent issue.\n\n\u003Clocal-ticket-template>\n\n# \u003CNN>: \u003CTicket title>\n\n**What to build:** the end-to-end behaviour this ticket makes work, from the user's perspective, not a layer-by-layer implementation list.\n\n**Blocked by:** the numbers\u002Ftitles of the tickets that gate this one, or \"None (can start immediately)\".\n\n**Status:** ready-for-agent\n\n- [ ] Acceptance criterion 1\n- [ ] Acceptance criterion 2\n\n\u003C\u002Flocal-ticket-template>\n\n\u003Cissue-template>\n\n## Parent\n\nA reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to build\n\nThe end-to-end behaviour this ticket makes work, from the user's perspective, not layer-by-layer implementation.\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Blocked by\n\n- A reference to each blocking ticket, or \"None (can start immediately)\".\n\n\u003C\u002Fissue-template>\n\nIn either form, avoid specific file paths or code snippets: 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. Trim to the decision-rich parts, not a working demo, just the important bits.\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.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fsetup-matt-pocock-skills`.\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 spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.\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. A ticket with no blockers can start immediately.\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 the tickets to the configured tracker\n\nPublish the approved tickets. **How** depends on the tracker `\u002Fsetup-matt-pocock-skills` configured; the tickets are the same either way, only the shape of the blocking edges changes:\n\n- **Local files** → write one file per ticket under `.scratch\u002F\u003Cfeature-slug>\u002Fissues\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first). Each file's \"Blocked by\" lists the numbers\u002Ftitles it depends on. Use the per-ticket file template below: one ticket per file, never a single combined file.\n- **A real issue tracker (GitHub, Linear, …)** → publish one issue per ticket in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Use the platform's native blocking \u002F sub-issue relationship where it has one; otherwise set each ticket's \"Blocked by\" to the blocking issues. Apply the `ready-for-agent` triage label unless instructed otherwise; the tickets are agent-grabbable by construction.\n\nWork the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.\n\nDo NOT close or modify any parent issue.\n\n\u003Clocal-ticket-template>\n\n# \u003CNN>: \u003CTicket title>\n\n**What to build:** the end-to-end behaviour this ticket makes work, from the user's perspective, not a layer-by-layer implementation list.\n\n**Blocked by:** the numbers\u002Ftitles of the tickets that gate this one, or \"None (can start immediately)\".\n\n**Status:** ready-for-agent\n\n- [ ] Acceptance criterion 1\n- [ ] Acceptance criterion 2\n\n\u003C\u002Flocal-ticket-template>\n\n\u003Cissue-template>\n\n## Parent\n\nA reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to build\n\nThe end-to-end behaviour this ticket makes work, from the user's perspective, not layer-by-layer implementation.\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Blocked by\n\n- A reference to each blocking ticket, or \"None (can start immediately)\".\n\n\u003C\u002Fissue-template>\n\nIn either form, avoid specific file paths or code snippets: 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. Trim to the decision-rich parts, not a working demo, just the important bits.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","a1dd0de00a0db2613339b710e20f458f78439cbe","templates\u002Fskills\u002Fpocock\u002Fto-tickets",0,"https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@thienhn\u002Fcreate-template","https:\u002F\u002Fgithub.com\u002FThienHN0910","https:\u002F\u002Fthienhn.io.vn\u002Fabout","2026-11-09 15:21:02",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add ThienHN0910\u002FTemplate-P --skill to-tickets",{"tool":40,"command":41},"bunx","bunx skills add ThienHN0910\u002FTemplate-P --skill to-tickets",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ThienHN0910\u002FTemplate-P --skill to-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fpocock\u002Fto-tickets\u002FSKILL.md",[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",146,"https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fpocock\u002Fto-tickets\u002Fagents\u002Fopenai.yaml",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7CPGT91CB71D2H3Q8WB36P3","stitch-design-taste","Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fstitch-design-taste\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7CPGP56DA29RQS9Z61T05MW","minimalist-ui","Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fminimalist-ui\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7CPGGFY7H5BY59NRZMSH3AG","industrial-brutalist-ui","Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Findustrial-brutalist-ui\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"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},"01M7CPG61M01PSE6Y07ZA7Y1VG","imagegen-frontend-web","Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text \u002F right-image), background-image freedom, varied CTAs, varied hero scales (giant \u002F mid \u002F mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fimagegen-frontend-web\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},"01M7CPFVXKVQX1QZADQ84QENHJ","imagegen-frontend-mobile","Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fimagegen-frontend-mobile\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CPFHSD6HJ5MKGCWQZZZ439","image-to-code","Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fimage-to-code\u002FSKILL.md",[],[]]