[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2F4D9V2JR7JCD990FQ94R":3,"skill-same:01M7B2F4D9V2JR7JCD990FQ94R":64},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7B2F4D9V2JR7JCD990FQ94R","variant",null,"Builds multiple variants of a component you're working on and helps you iterate and pick one.","jorgesolerrr\u002Fskills","jorgesolerrr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92542744?v=4","01M7B2B710R5NTAHS08MWZJXB0","Jorge Soler","01M7B2B721D4CAZJH7E6ZM4ZQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjakubkrehel\u002Fvariant\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjakubkrehel\u002Fvariant\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: variant\ndescription: Builds multiple variants of a component you're working on and helps you iterate and pick one.\ndisable-model-invocation: true\n---\n\n# Variants\n\nThis skill takes one described piece of UI and builds three versions that differ on purpose. They go behind a picker in the real page, so you can flip between them and choose.\n\nIt produces candidates and never ranks them. Reviewing existing UI is `interface-review` and `better-interface`, stress testing one component is `break` and working through a component's states is `state-machine`.\n\n## Different answers, not different tints\n\nEach variant is a different answer to the same brief, on an axis this collection owns:\n\n| Axis | Owner | What varies |\n| --- | --- | --- |\n| Structure | `better-layout` | Grouping, order, column count, what collapses |\n| Density | `better-layout` | Spacing scale, how much fits |\n| Emphasis | `better-colors` | Where filled color goes, what recedes |\n| Type | `better-typography` | Scale steps, weight contrast, measure |\n| Voice | `better-writing` | Labels, tone, how much copy |\n\nPick **one primary axis** and give each variant a different position on it. The axis names the picker's group heading. Secondary choices follow from it rather than varying on their own. A dense variant may need a smaller type step, and that is coherence, not a second axis.\n\n## The floor every variant clears\n\nBefore a variant enters the picker it clears `better-interface`'s escalation triggers, which are:\n\n- Every control has an accessible name and a visible focus indicator.\n- Keyboard reaches everything a pointer does.\n- Motion and auto-playing content respect `prefers-reduced-motion`.\n- Nothing clips, overlaps or becomes unreachable at 320px width or 200% zoom.\n- Body and control text pass their required contrast ratio.\n- No state or meaning rides on color alone, and no state change on motion alone.\n- A destructive action has a confirmation, an undo or a distinct treatment.\n- Truncated content has a way to reach the full value.\n- Nothing hides past a scroll edge or behind a disclosure with no visible cue.\n- Every error names a way to recover.\n- No semantic color is used against its meaning, such as the danger hue on a non-destructive action.\n\nThat floor is identical across variants. It is not an axis and never trades against one. Where a direction can only work by breaking it, say so and drop the direction.\n\n## 1. Scope one piece\n\nOne piece of UI per run. \"The dashboard\" is not a piece; the metric card is. Where the request spans several, list the candidates and ask which one to explore.\n\nRestate the brief in one sentence: what the thing is, where it renders, what it has to do.\n\n## 2. Learn the ground\n\nVariants have to look like they could ship tomorrow, so read what they stand on:\n\n- The styling system, the component library and any motion library.\n- The tokens: color, spacing, radius, type scale, easing.\n- The product's density and voice. A dense professional tool bounds how far the boldest variant may go.\n- Where the piece renders: against what background, beside which neighbours, at which widths.\n\nWith no project to read, use neutral grays, one accent and the system font stack, and say that is what you did.\n\n## 3. Name the axis before writing code\n\nDefault to three variants. Go to five only when asked.\n\nWrite the set down first, a name and an axis position each. Names say what the direction is, so `Quiet`, `Editorial`, `Dense`, never `Option A`.\n\nThis step is done when no two variants share a position and you can state each one's axis in a phrase.\n\n## 4. Build it into the real page\n\nHost the variants on the page that will actually contain the piece, with the real chrome, the real neighbours and realistic data.\n\nSelect with a URL search param such as `?__variant=quiet`, so every variant is a link you can send someone. A grouped list beside the piece sets it. Where there is no room beside the piece, it moves above it as a select with the same groups. [picker.md](picker.md) holds the spec.\n\nRender one variant at a time, full size. Thumbnails distort spacing and scale, and spacing is usually the thing you are choosing between.\n\nVariant files may import production components. Only the hosting page imports a variant, and nothing else imports from the harness.\n\nWhere no page can host it, build one self-contained HTML file and keep the same picker.\n\nGive every variant real content: product-shaped copy, plausible names and the number of items the page will really carry. Lorem ipsum and three rows make every structure look good.\n\n## 5. Present the tradeoffs and stop\n\nLoad the page once in a browser already at hand and flip through every variant. Each one renders, each interaction responds and the console is clean. With no browser at hand, say so and hand the URL over for the user to check.\n\nThen hand the decision over:\n\n| Variant | Axis position | Right when | Costs |\n| --- | --- | --- | --- |\n| Quiet | Lowest visual weight | The page is used daily | Least memorable |\n| Editorial | Largest type, most space | The moment deserves weight | Eats vertical space |\n\nSay where the picker is running, which key flips it and which width you judged at. The answer can change between 375px and 1440px.\n\nNever mark a favourite in the table. Asked directly, answer from how often the piece is seen and from the product's personality, not from which one you enjoyed building.\n\n## 6. Promote one, delete the rest\n\nOn a choice, build that variant properly where it belongs, following the project's own conventions. Then delete the other variants, the picker and the guarded import. Search for the variant names and the `__variant` param, and check the diff leaves nothing of the harness behind.\n\nAsked for another round instead, keep the harness and run **Name the axis before writing code** again, taking new positions around the direction you leaned toward.\n\n## Before you finish\n\n| Mistake | Fix |\n| --- | --- |\n| Variants differ only in accent color or copy | Move one to a different position on the primary axis, or cut it |\n| Every axis varies at once | Vary one; let the rest follow from it |\n| Judged on a blank route | Host them on the page that will contain the piece |\n| Lorem ipsum, three rows, \"Jane Doe\" | Real copy and the item count the page will really carry |\n| The boldest variant skips keyboard or focus | Clear the floor or drop the direction |\n| A favourite marked in the table | State each variant's cost and let the user choose |\n| Picker restyled with the project's tokens | Keep it visibly outside the design system |\n| One long row of tabs, one per variant | A grouped list beside the piece that scrolls on its own; a select above it where the list does not fit |\n| Harness left behind after promotion | Delete it and search for the names and the param |\n","# Variants\n\nThis skill takes one described piece of UI and builds three versions that differ on purpose. They go behind a picker in the real page, so you can flip between them and choose.\n\nIt produces candidates and never ranks them. Reviewing existing UI is `interface-review` and `better-interface`, stress testing one component is `break` and working through a component's states is `state-machine`.\n\n## Different answers, not different tints\n\nEach variant is a different answer to the same brief, on an axis this collection owns:\n\n| Axis | Owner | What varies |\n| --- | --- | --- |\n| Structure | `better-layout` | Grouping, order, column count, what collapses |\n| Density | `better-layout` | Spacing scale, how much fits |\n| Emphasis | `better-colors` | Where filled color goes, what recedes |\n| Type | `better-typography` | Scale steps, weight contrast, measure |\n| Voice | `better-writing` | Labels, tone, how much copy |\n\nPick **one primary axis** and give each variant a different position on it. The axis names the picker's group heading. Secondary choices follow from it rather than varying on their own. A dense variant may need a smaller type step, and that is coherence, not a second axis.\n\n## The floor every variant clears\n\nBefore a variant enters the picker it clears `better-interface`'s escalation triggers, which are:\n\n- Every control has an accessible name and a visible focus indicator.\n- Keyboard reaches everything a pointer does.\n- Motion and auto-playing content respect `prefers-reduced-motion`.\n- Nothing clips, overlaps or becomes unreachable at 320px width or 200% zoom.\n- Body and control text pass their required contrast ratio.\n- No state or meaning rides on color alone, and no state change on motion alone.\n- A destructive action has a confirmation, an undo or a distinct treatment.\n- Truncated content has a way to reach the full value.\n- Nothing hides past a scroll edge or behind a disclosure with no visible cue.\n- Every error names a way to recover.\n- No semantic color is used against its meaning, such as the danger hue on a non-destructive action.\n\nThat floor is identical across variants. It is not an axis and never trades against one. Where a direction can only work by breaking it, say so and drop the direction.\n\n## 1. Scope one piece\n\nOne piece of UI per run. \"The dashboard\" is not a piece; the metric card is. Where the request spans several, list the candidates and ask which one to explore.\n\nRestate the brief in one sentence: what the thing is, where it renders, what it has to do.\n\n## 2. Learn the ground\n\nVariants have to look like they could ship tomorrow, so read what they stand on:\n\n- The styling system, the component library and any motion library.\n- The tokens: color, spacing, radius, type scale, easing.\n- The product's density and voice. A dense professional tool bounds how far the boldest variant may go.\n- Where the piece renders: against what background, beside which neighbours, at which widths.\n\nWith no project to read, use neutral grays, one accent and the system font stack, and say that is what you did.\n\n## 3. Name the axis before writing code\n\nDefault to three variants. Go to five only when asked.\n\nWrite the set down first, a name and an axis position each. Names say what the direction is, so `Quiet`, `Editorial`, `Dense`, never `Option A`.\n\nThis step is done when no two variants share a position and you can state each one's axis in a phrase.\n\n## 4. Build it into the real page\n\nHost the variants on the page that will actually contain the piece, with the real chrome, the real neighbours and realistic data.\n\nSelect with a URL search param such as `?__variant=quiet`, so every variant is a link you can send someone. A grouped list beside the piece sets it. Where there is no room beside the piece, it moves above it as a select with the same groups. [picker.md](picker.md) holds the spec.\n\nRender one variant at a time, full size. Thumbnails distort spacing and scale, and spacing is usually the thing you are choosing between.\n\nVariant files may import production components. Only the hosting page imports a variant, and nothing else imports from the harness.\n\nWhere no page can host it, build one self-contained HTML file and keep the same picker.\n\nGive every variant real content: product-shaped copy, plausible names and the number of items the page will really carry. Lorem ipsum and three rows make every structure look good.\n\n## 5. Present the tradeoffs and stop\n\nLoad the page once in a browser already at hand and flip through every variant. Each one renders, each interaction responds and the console is clean. With no browser at hand, say so and hand the URL over for the user to check.\n\nThen hand the decision over:\n\n| Variant | Axis position | Right when | Costs |\n| --- | --- | --- | --- |\n| Quiet | Lowest visual weight | The page is used daily | Least memorable |\n| Editorial | Largest type, most space | The moment deserves weight | Eats vertical space |\n\nSay where the picker is running, which key flips it and which width you judged at. The answer can change between 375px and 1440px.\n\nNever mark a favourite in the table. Asked directly, answer from how often the piece is seen and from the product's personality, not from which one you enjoyed building.\n\n## 6. Promote one, delete the rest\n\nOn a choice, build that variant properly where it belongs, following the project's own conventions. Then delete the other variants, the picker and the guarded import. Search for the variant names and the `__variant` param, and check the diff leaves nothing of the harness behind.\n\nAsked for another round instead, keep the harness and run **Name the axis before writing code** again, taking new positions around the direction you leaned toward.\n\n## Before you finish\n\n| Mistake | Fix |\n| --- | --- |\n| Variants differ only in accent color or copy | Move one to a different position on the primary axis, or cut it |\n| Every axis varies at once | Vary one; let the rest follow from it |\n| Judged on a blank route | Host them on the page that will contain the piece |\n| Lorem ipsum, three rows, \"Jane Doe\" | Real copy and the item count the page will really carry |\n| The boldest variant skips keyboard or focus | Clear the floor or drop the direction |\n| A favourite marked in the table | State each variant's cost and let the user choose |\n| Picker restyled with the project's tokens | Keep it visibly outside the design system |\n| One long row of tabs, one per variant | A grouped list beside the piece that scrolls on its own; a select above it where the list does not fit |\n| Harness left behind after promotion | Delete it and search for the names and the param |\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","5affa1dd6283cecc37579e77a6de9288f5a4177f","skills\u002Fjakubkrehel\u002Fvariant","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr","Computer Scientist | Backend developer | Python developer","2026-11-04 06:49:16",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jorgesolerrr\u002Fskills --skill variant",{"tool":39,"command":40},"bunx","bunx skills add jorgesolerrr\u002Fskills --skill variant",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jorgesolerrr\u002Fskills --skill variant","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjakubkrehel\u002Fvariant\u002FSKILL.md",[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",152,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjakubkrehel\u002Fvariant\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"CREDITS.md",322,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjakubkrehel\u002Fvariant\u002FCREDITS.md",{"path":57,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":16},"LICENSE","许可证",1069,{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"picker.md",7042,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjakubkrehel\u002Fvariant\u002Fpicker.md",[65,73,81,89,97,105],{"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":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":20},"01M7B31X3JCSHDXNTNZ0VH2773","explainroo","Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\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":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":20},"01M7B31SZRHNV2M04YW4WR5EJZ","unslop","Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or \"sounds like AI\".","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\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":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":20},"01M7B31PBF1VQ9VHDDSS6WMBJ6","technical-writing","Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\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":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":20},"01M7B31KHS6P377SZT8SD1RTHW","no-comments","Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M7B31FAY1MDAQ6RDXCFJH2P3","ponytail","Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says \"ponytail\", \"be lazy\", \"simplest solution\", \"yagni\", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M7B31AXF7VDH9NFSRXBN6FAM","ponytail-review","Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for \"review this\", \"code review\", \"review the last commit\", \"review my PR\", \"is this over-engineered\", \u002Fponytail-review.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FSKILL.md",[],[]]