[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75YZT29RFCAPZ652C4CFHGN":3,"skill-same:01M75YZT29RFCAPZ652C4CFHGN":45},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75YZT29RFCAPZ652C4CFHGN","plain-tickets",null,"Name and write tickets, issues, ADRs and board tasks so they land cold — a plain verb phrase for the name, never a codename, and reader-facing prose in short active sentences using only words the codebase already uses. Use when naming or renaming a ticket, issue, board task, ADR or branch; when writing a ticket's description or summary; when a name gets the reaction \"what does that even mean\"; or when asked to make a task read better.","JoseArron\u002Fskills","JoseArron","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87633971?v=4","01M75YX3KAHAS3QG3VWTE99Q82","okjose","01M75YX3KY032CBX4FDYZVX0AN",2,"MIT","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frequirements-and-planning\u002Fplain-tickets\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: plain-tickets\ndescription: Name and write tickets, issues, ADRs and board tasks so they land cold — a plain verb phrase for the name, never a codename, and reader-facing prose in short active sentences using only words the codebase already uses. Use when naming or renaming a ticket, issue, board task, ADR or branch; when writing a ticket's description or summary; when a name gets the reaction \"what does that even mean\"; or when asked to make a task read better.\n---\n\n# Plain tickets\n\nA ticket name is read in a list, cold, months later, with nothing else open. That is the whole\nbudget. Everything here follows from it.\n\n## The three names, and their different jobs\n\nOne ticket carries three names. They are not the same length and not the same job.\n\n| Name | Length | Job |\n| --- | --- | --- |\n| **File slug** | 2–4 words after the number | Sort and find it on disk. `new-07-fix-missing-column.md` |\n| **Board name** | 3–7 words, one clause | Point at the thing, in a list of thirty. `Split Missing into loss and lacking` |\n| **H1** | one line, may add a clause after an em dash | Name the thing, then say what the change is. Body carries mechanics like endpoint moves and regen order — the H1 does not need to. |\n\nMechanics — how it ships, what it breaks, who rebases — go in the body. Never in the name.\n\n## Naming: five tests, in order\n\n**1. Is it a codename?** Delete it. \"THE CUT\", \"Project Lighthouse\", \"the big one\". A codename feels\nlike shared shorthand and is shorthand for exactly one person: whoever coined it. Everyone else\nreads it and asks what it means. It also spreads — one codename reached 23 files and 53 mentions\nbefore anyone said \"what is the cut supposed to mean\".\n\n**2. Can you say it out loud as one sentence?** If the name has three clauses bolted together, it is\nnotes, not a name. `Stop the Missing column hiding loss, in one regen` fails. Two ideas and a build\nstep jammed into a title.\n\n**3. Does it start with a verb and name a thing that exists?** The default shape is `Fix \u003Cthe thing>`.\nReach for `Rename`, `Delete`, `Seed`, `Bring`, `Consolidate` when they are more exact. The thing\nshould be something the reader can point at — a column header, a field name, a screen, a table.\n\n**4. Does every word appear in the codebase or on screen?** If a word only exists in a design doc,\nan ADR, or your head, it does not go in the name. No build-step vocabulary either: `regen`, `seam`,\n`cutover`, `fold`, `ledger`, `slice`. Those are how the work happens, not what is wrong.\n\n**5. Would it still make sense to someone who has not read the ticket?** If not, it is not shorter,\nit is just missing.\n\n**6. Does the name accidentally claim the wrong kind of fix?** A name built around *where the bug\nshows* can misdirect about *what changes*. `Fix the Missing column` names a real thing on screen, but\nreads as a frontend display bug when the actual work is a three-way API contract break with a client\nrename riding along. Naming the mechanism instead — what actually happens to the data — avoids this\nwithout losing concreteness. `Split Missing into loss and lacking` says two things happen to one\nvalue; nothing here can be mistaken for a CSS fix.\n\n### Ambiguity beats brevity every time\n\nA shorter name that can be read two ways is worse than a longer one that cannot.\n\n`Fix missing counts` is shorter than `Fix the Missing column`. It is also worse: \"missing counts\"\nreads as *counts that are missing* — which is a real, different defect. Capital-M **Missing** is the\ncolumn header on screen; lowercase *missing* is an adjective. One character of casing is doing work\nthe reader will not notice.\n\nBefore shortening, read the short version as if you had never seen the ticket. If a second meaning\nappears, keep the longer name.\n\n## Writing the reader-facing zones\n\nTicket descriptions, issue summaries, board copy, chat replies. Not the spec body, not code\ncomments.\n\nWrite them in `plain-english`: short active sentences, present tense, the project's own glossary\nwords, the key point first. Three rules sit on top of it, specific to tickets:\n\n- **Lead with the defect in one sentence**, then the evidence, then the fix. Not the other way round.\n- **Every claim names its symbol and path.** `loadTypeHasCustomer returns true for refill —\n  client\u002Fapps\u002Fmobile\u002Flib\u002Fload-plan.ts:16`. A claim with no path is a rumour.\n- **Verify before filing.** Open the file. If the defect moved or was fixed, the ticket is wrong on\n  arrival and everything downstream inherits the error.\n\n## Worked example\n\nThe real path a ticket took, including the wrong middle step.\n\n**Before.** `THE CUT — honest loss reporting: response shape, endpoint paths and names, in one regen`\n\nCodename (test 1). Three clauses (test 2). `regen` is a build step (test 4). \"the cut\" meant *one\ncutover*, which the name never says.\n\n**First attempt.** `Stop the Missing column hiding loss, in one regen`\n\nStill fails. `Stop X hiding Y` inverts the sentence to force the defect into the title, and `regen`\nsurvived. The reaction was \"it still sounds like words just placed together\".\n\n**Second attempt.** `Fix the Missing column`\n\nPasses tests 1–5. Verb, three words, points at a real header on screen. But it fails test 6: it reads\nas a frontend display bug, when most of the ticket is a backend contract break — a response-shape\nrename, endpoint paths moving, a field rename — with a small client cleanup riding along. The\nreaction was \"if we're going with column it reads more like a display bug on the frontend, right?\".\nIt was.\n\n**Shipped.** `Split Missing into loss and lacking`\n\nNames the mechanism, not the location. One merged value becomes two named ones —\n`countVariance` (loss) and `emptiesLacking`. Nothing here can be misread as a calculation fix (nothing\nis recalculated) or a display fix (the split happens in the API response, not the render). The three\ncontract breaks and the regen order still live in the body.\n\n## Rewriting a description\n\n**Before:** *\"Taking the larger of the two hides theft whenever customers hold more empties than the\nBranch has lost. The engine underneath is correct; the API named its results wrong.\"*\n\n**After:** *\"The page shows the larger of the two. So when customers hold more empties than the Depot\nlost, the loss disappears from the screen. The calculation is correct. The API gave its results the\nwrong names.\"*\n\nWhat changed: one idea per sentence, \"engine underneath\" replaced with the plain \"calculation\",\nBranch\u002FDepot matched to the glossary, and the semicolon split into two sentences.\n\n## Renaming something that already shipped\n\nA name that spread costs a sweep. Do the whole sweep in one pass.\n\n1. Change the board name and H1 first. Zero link cost.\n2. Rename the file, then update every link to it.\n3. Sweep the old nickname out of prose. Grep it. Ordinary-looking phrases are usually the nickname\n   too.\n4. Check nothing is left: the grep must return zero, not \"a few harmless ones\".\n5. Back up first if the docs are not under version control.\n","# Plain tickets\n\nA ticket name is read in a list, cold, months later, with nothing else open. That is the whole\nbudget. Everything here follows from it.\n\n## The three names, and their different jobs\n\nOne ticket carries three names. They are not the same length and not the same job.\n\n| Name | Length | Job |\n| --- | --- | --- |\n| **File slug** | 2–4 words after the number | Sort and find it on disk. `new-07-fix-missing-column.md` |\n| **Board name** | 3–7 words, one clause | Point at the thing, in a list of thirty. `Split Missing into loss and lacking` |\n| **H1** | one line, may add a clause after an em dash | Name the thing, then say what the change is. Body carries mechanics like endpoint moves and regen order — the H1 does not need to. |\n\nMechanics — how it ships, what it breaks, who rebases — go in the body. Never in the name.\n\n## Naming: five tests, in order\n\n**1. Is it a codename?** Delete it. \"THE CUT\", \"Project Lighthouse\", \"the big one\". A codename feels\nlike shared shorthand and is shorthand for exactly one person: whoever coined it. Everyone else\nreads it and asks what it means. It also spreads — one codename reached 23 files and 53 mentions\nbefore anyone said \"what is the cut supposed to mean\".\n\n**2. Can you say it out loud as one sentence?** If the name has three clauses bolted together, it is\nnotes, not a name. `Stop the Missing column hiding loss, in one regen` fails. Two ideas and a build\nstep jammed into a title.\n\n**3. Does it start with a verb and name a thing that exists?** The default shape is `Fix \u003Cthe thing>`.\nReach for `Rename`, `Delete`, `Seed`, `Bring`, `Consolidate` when they are more exact. The thing\nshould be something the reader can point at — a column header, a field name, a screen, a table.\n\n**4. Does every word appear in the codebase or on screen?** If a word only exists in a design doc,\nan ADR, or your head, it does not go in the name. No build-step vocabulary either: `regen`, `seam`,\n`cutover`, `fold`, `ledger`, `slice`. Those are how the work happens, not what is wrong.\n\n**5. Would it still make sense to someone who has not read the ticket?** If not, it is not shorter,\nit is just missing.\n\n**6. Does the name accidentally claim the wrong kind of fix?** A name built around *where the bug\nshows* can misdirect about *what changes*. `Fix the Missing column` names a real thing on screen, but\nreads as a frontend display bug when the actual work is a three-way API contract break with a client\nrename riding along. Naming the mechanism instead — what actually happens to the data — avoids this\nwithout losing concreteness. `Split Missing into loss and lacking` says two things happen to one\nvalue; nothing here can be mistaken for a CSS fix.\n\n### Ambiguity beats brevity every time\n\nA shorter name that can be read two ways is worse than a longer one that cannot.\n\n`Fix missing counts` is shorter than `Fix the Missing column`. It is also worse: \"missing counts\"\nreads as *counts that are missing* — which is a real, different defect. Capital-M **Missing** is the\ncolumn header on screen; lowercase *missing* is an adjective. One character of casing is doing work\nthe reader will not notice.\n\nBefore shortening, read the short version as if you had never seen the ticket. If a second meaning\nappears, keep the longer name.\n\n## Writing the reader-facing zones\n\nTicket descriptions, issue summaries, board copy, chat replies. Not the spec body, not code\ncomments.\n\nWrite them in `plain-english`: short active sentences, present tense, the project's own glossary\nwords, the key point first. Three rules sit on top of it, specific to tickets:\n\n- **Lead with the defect in one sentence**, then the evidence, then the fix. Not the other way round.\n- **Every claim names its symbol and path.** `loadTypeHasCustomer returns true for refill —\n  client\u002Fapps\u002Fmobile\u002Flib\u002Fload-plan.ts:16`. A claim with no path is a rumour.\n- **Verify before filing.** Open the file. If the defect moved or was fixed, the ticket is wrong on\n  arrival and everything downstream inherits the error.\n\n## Worked example\n\nThe real path a ticket took, including the wrong middle step.\n\n**Before.** `THE CUT — honest loss reporting: response shape, endpoint paths and names, in one regen`\n\nCodename (test 1). Three clauses (test 2). `regen` is a build step (test 4). \"the cut\" meant *one\ncutover*, which the name never says.\n\n**First attempt.** `Stop the Missing column hiding loss, in one regen`\n\nStill fails. `Stop X hiding Y` inverts the sentence to force the defect into the title, and `regen`\nsurvived. The reaction was \"it still sounds like words just placed together\".\n\n**Second attempt.** `Fix the Missing column`\n\nPasses tests 1–5. Verb, three words, points at a real header on screen. But it fails test 6: it reads\nas a frontend display bug, when most of the ticket is a backend contract break — a response-shape\nrename, endpoint paths moving, a field rename — with a small client cleanup riding along. The\nreaction was \"if we're going with column it reads more like a display bug on the frontend, right?\".\nIt was.\n\n**Shipped.** `Split Missing into loss and lacking`\n\nNames the mechanism, not the location. One merged value becomes two named ones —\n`countVariance` (loss) and `emptiesLacking`. Nothing here can be misread as a calculation fix (nothing\nis recalculated) or a display fix (the split happens in the API response, not the render). The three\ncontract breaks and the regen order still live in the body.\n\n## Rewriting a description\n\n**Before:** *\"Taking the larger of the two hides theft whenever customers hold more empties than the\nBranch has lost. The engine underneath is correct; the API named its results wrong.\"*\n\n**After:** *\"The page shows the larger of the two. So when customers hold more empties than the Depot\nlost, the loss disappears from the screen. The calculation is correct. The API gave its results the\nwrong names.\"*\n\nWhat changed: one idea per sentence, \"engine underneath\" replaced with the plain \"calculation\",\nBranch\u002FDepot matched to the glossary, and the semicolon split into two sentences.\n\n## Renaming something that already shipped\n\nA name that spread costs a sweep. Do the whole sweep in one pass.\n\n1. Change the board name and H1 first. Zero link cost.\n2. Rename the file, then update every link to it.\n3. Sweep the old nickname out of prose. Grep it. Ordinary-looking phrases are usually the nickname\n   too.\n4. Check nothing is left: the grep must return zero, not \"a few harmless ones\".\n5. Back up first if the docs are not under version control.\n",{"name":5,"description":7},"main","cb49d66200006e1d66bc1a8c416862b3b935c491","skills\u002Frequirements-and-planning\u002Fplain-tickets",0,"https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills","https:\u002F\u002Fgithub.com\u002FJoseArron","2026-10-11 15:51:18",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add JoseArron\u002Fskills --skill plain-tickets",{"tool":37,"command":38},"bunx","bunx skills add JoseArron\u002Fskills --skill plain-tickets",{"tool":40,"command":41},"pnpm","pnpm dlx skills add JoseArron\u002Fskills --skill plain-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frequirements-and-planning\u002Fplain-tickets\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M75Z1R3CAY688TG5NMBNZK28","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworking-with-skills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75Z1P4SQQ2CSAGE9XD57GHZ","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworking-with-skills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75Z1K7X70CQ3DY038Q2Y37P","resync-upstream-skills","Resync a selectively derived skills repository with its recorded upstream sources. Use when the user wants to pull upstream skill releases, reconcile renamed or changed skills, refresh third-party attribution, or audit whether local adaptations have drifted.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworking-with-skills\u002Fresync-upstream-skills\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M75Z1G8CEVXMY8QENAKCT9AC","find-skills","Helps users discover and install agent skills when they ask questions like \"how do I do X\", \"find a skill for X\", \"is there a skill that can...\", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworking-with-skills\u002Ffind-skills\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M75Z1E0RSRDZJ2F15YQ2Q6G2","ux-review","Evaluate a built screen or flow against UX heuristics and report what to fix — each finding with a severity and a concrete fix. Use to review or audit a UI's usability, before shipping a flow, or to turn \"this feels off\" into specific, rankable problems. The UX counterpart to \u002Fcode-review.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fux\u002Fux-review\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M75Z1A7E4X45K9MEERGCY7D4","ux-flows","Design and implement app screens and user flows with calm, user-first UX — obvious CTAs, feedback at the point of action, thumb-zone layout, and domain-modularized components. Use when the user asks to build or polish UI\u002FUX, design a user flow, make a screen \"feel\" right, or mentions effortless\u002Fcalm design, confirmations, error states, or empty states.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fux\u002Fux-flows\u002FSKILL.md",[],[]]