[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CEMK9TEQBHA3EX78EGDRKB":3,"skill-same:01M7CEMK9TEQBHA3EX78EGDRKB":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":5,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7CEMK9TEQBHA3EX78EGDRKB","better-typography",null,"Focuses on type scale, spacing, sizing, variable fonts, OpenType features, wrapping, truncation and other details that make typography feel great across your product.","getedgehq\u002Fskills","getedgehq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F327350993?v=4","01M7CEH5YJQYF1PB3MDG9PA5HX","01M7CEH5ZAPY8TX4H3E04KM875",5,"MIT","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: better-typography\ndescription: Focuses on type scale, spacing, sizing, variable fonts, OpenType features, wrapping, truncation and other details that make typography feel great across your product.\nmetadata:\n  author: \"Jakub Krehel\"\n  source: https:\u002F\u002Fgithub.com\u002Fjakubkrehel\u002Fskills\u002Ftree\u002F267330e1adfc66a718fb65fa6918c1f06d0a689e\u002Fskills\u002Fbetter-typography\n---\n\n# Typography\n\nTypography is mostly restraint: a sensible scale, comfortable spacing, enough contrast. A label, a table cell, a marketing headline and an article paragraph do not share one set of rules.\n\nWhen reviewing, read the rendered page instead of scanning the code. Bad wrapping, widows and truncation only show up at real content lengths.\n\nWrite every fix in the project's styling system, and use the exact values below rather than familiar-looking equivalents. The [cheat sheet](css-cheat-sheet.md) maps each declaration to its Tailwind equivalent.\n\nThe words themselves belong to `better-writing`. Semantic heading structure belongs to `better-accessibility`. Spatial RTL layout and logical properties belong to `better-layout`. Contrast measurement belongs to `better-colors`. This skill owns how text renders, wraps and behaves in mixed-direction content.\n\n## Serve the right format\n\nUse `.woff2` on the web, for Brotli compression and broad support. `.woff` is a fallback for very old browsers. `.ttf` and `.otf` are desktop formats with no web compression. How the files load is the project's concern.\n\n## Properties over raw tags\n\nWhen a CSS property exists, use it. `font-weight: 650` instead of `font-variation-settings: \"wght\" 650`. `font-optical-sizing: auto` instead of `\"opsz\"`. `font-variant-numeric: tabular-nums` instead of `font-feature-settings: \"tnum\" 1`.\n\nProperties keep working when a non-variable fallback renders. Reserve raw tags for custom axes (`\"GRAD\" 80`) and niche features (`\"ss01\" 1`) with no property of their own. Axes and feature tags are listed in [variable-fonts-and-opentype.md](variable-fonts-and-opentype.md).\n\n## Load intended weights and styles\n\nBrowsers synthesize a weight or style the active family doesn't provide, distorting the real face. Load the faces the design uses.\n\n`font-synthesis: none` turns synthesis off, but it erases emphasis rather than reporting it. Set it only after checking every required bold, italic, small-cap, superscript and subscript form stays distinct across the fallback stack.\n\n## Fewer fonts, sizes and weights\n\nRarely use more than three fonts. Weight and size define hierarchy; overusing them hurts readability fast. Pair for contrast, not similarity: a serif headline over a sans body reads as deliberate, two near-identical sans-serifs read as a mistake.\n\nBelow `18px`, stay at weight `400` or heavier. Weights under `300` are display-only at `28px`+; they disappear at text sizes. Pairing guidance is in [choosing-fonts.md](choosing-fonts.md).\n\n## Use a type scale with semantic names\n\nDefine a small set of sizes and deviate from it as little as possible. Hard-coded sizes with no system behind them break down at scale.\n\nSolo, default names like `text-sm` are fine when the usage rules are clear. On a team, name sizes by use (`text-body-sm`) so the rules survive other people. Scale construction is in [spacing-and-sizing.md](spacing-and-sizing.md).\n\n## Heading sizes descend with level\n\nMap heading levels to descending steps of the type scale, so a visually subordinate heading never overpowers its parent. Adjacent levels may share a size toward the small end of the scale, as long as weight or spacing keeps them distinct. The semantic element is `better-accessibility`'s; this skill sets only the visual treatment.\n\n## Line-height by role\n\nHeadings tighter, around `1.1`. Body copy `1.5` to `1.6`. Prefer unitless values, so line-height scales with the font size; a fixed `24px` does not.\n\nTight line-height is for short text. Anything that wraps to three or more lines needs at least `1.4`, even in a height-constrained row.\n\n## Letter-spacing by size\n\nLarge headings often look better with slightly negative letter-spacing. Small uppercase labels need a little positive letter-spacing, or the letters feel crowded. Body copy at reading sizes needs neither.\n\n## Cap the measure\n\nLong lines make it hard for the eye to find the next one. Cap long-form text around 60–75 characters per line. Any unit works, as long as a cap exists and the line length lands in range. See [unit choices and the pixel equivalents](wrapping-and-punctuation.md#measure-line-length).\n\n## Wrap deliberately\n\nFour declarations, four jobs:\n\n- `text-wrap: balance` distributes text evenly across lines. Use it on headings.\n- `text-wrap: pretty` stops a single short word landing on the final line. Use it on descriptions.\n- `overflow-wrap: break-word` where a long word, link, or ID could escape the container.\n- `white-space: nowrap` on labels and badges where a line break looks broken.\n\nSkip `balance` and `pretty` in long-form text.\n\n## Tabular numbers on changing values\n\nDigits have different widths by default, so timers, counters and prices shift the layout as they update. Apply `font-variant-numeric: tabular-nums` to any value that changes.\n\n## Truncate without losing content\n\nFor a single line, `text-overflow: ellipsis` with `overflow: hidden` and `white-space: nowrap`. For several, `line-clamp`. Truncation hides content. When the missing text matters, keep the full value reachable in a tooltip or an expanded view.\n\n## Write copy naturally, style with CSS\n\nStore text in natural case and control presentation with `text-transform`, so a redesign never means rewriting copy.\n\nUse smart punctuation in rendered text:\n\n- Curly quotes in prose, straight quotes in code.\n- An en dash for ranges: `2010–2020`.\n- The single ellipsis character, not three periods.\n- `&nbsp;` to hold `16 px` together across a line break.\n- `&shy;` to say where a long word may break.\n\n## Underlines from the font\n\nDefault underlines sit wherever the browser decides. Pull position and thickness from the font's own metrics with `text-underline-position: from-font` and `text-decoration-thickness: from-font`. Tune by hand with `text-decoration-thickness`, `text-underline-offset` and `text-decoration-skip-ink`.\n\n`text-decoration-style` draws the line dotted, dashed, or wavy. A dotted underline is a common hint that a word carries extra information, such as an abbreviation or a defined term.\n\nColor is the only part of a real underline that animates reliably. So unless the only thing animating is the color, build the underline as a separate element rather than using `text-decoration`.\n\n## Inputs at 16px on mobile\n\niOS Safari zooms the whole page when an input's text is smaller than `16px`. Two fixes hold the size at `16px` and look different, so ask which one the design wants:\n\n- Size the input up on mobile (`text-base sm:text-sm`). Changes how it looks on small screens.\n- Keep `font-size: 16px` and render the intended size with `transform: scale()`, compensating width and `line-height`. Identical at every viewport, more code to maintain.\n\nBoth recipes are in [details-and-accessibility.md](details-and-accessibility.md).\n\n## Size and contrast floors\n\nStart long-form body text at `16px`, the browser default. Move off it only for a reason you can name: the typeface runs small, the measure is narrow, or the product is a dense professional tool.\n\nUI text can go smaller. `14px` is a useful starting point for inputs and menus, `13px` for captions and rarely below `12px`. Inputs still need `16px` on mobile.\n\nWhen text looks low-contrast, use `better-colors` to measure the rendered pair and `better-accessibility` to classify the requirement. Leave the colors alone unless asked.\n\n## Font smoothing on the root\n\nOn macOS, text renders heavier than intended. Apply `-webkit-font-smoothing: antialiased` and `-moz-osx-font-smoothing: grayscale` once on the root layout, never per component. Tailwind's `antialiased` covers both.\n\n## Language and bidi behavior\n\nSet `lang` so browsers and assistive technology pick the right pronunciation, quotes and hyphenation. Set `dir` at the document or at the content boundary where direction changes. Preserve digit order, and use `\u003Cbdi>` to isolate a mixed-direction value. Spatial mirroring and logical CSS properties belong to `better-layout`.\n\n## Keep useful text selectable\n\nKeep text selectable by default. `::selection` can carry brand into the reading experience, as long as the selected combination stays legible.\n\n`user-select: none` belongs on a draggable or gesture-driven surface where accidental selection interferes. Never across the interface and never because a button label can be highlighted.\n\n## Before you finish\n\n| Mistake | Fix |\n| --- | --- |\n| Synthesized face differs from the design | Load the real face; disable only the verified synthesis mode |\n| Child heading visually overpowers its parent | Map that section's hierarchy to descending scale steps |\n| Heading element picked for its default size | Choose semantics first, then set the size in CSS |\n| Orphan on the last line of a paragraph | `text-wrap: pretty` |\n| Lopsided two-line heading | `text-wrap: balance` |\n| Justified text in an interface | `text-align: start`; reserve justify for specific editorial layouts |\n| Underline cuts through descenders | `text-decoration-skip-ink: auto`, `from-font` metrics |\n| Mixed-direction value renders in the wrong order | Correct `lang`\u002F`dir`; isolate the value with `\u003Cbdi>` |\n| Selection disabled across application chrome | Restore it; suppress only where it conflicts with a drag or gesture |\n| Extra-info hint with no visual cue | Dotted underline via `text-decoration-style: dotted` |\n| Thin\u002FLight weight on `14px` UI text | Weight `400`+ below `18px`; thin weights are display-only |\n| `leading-none` on a three-line card description | At least `1.4` on any text that wraps to 3+ lines |\n\n## Reporting\n\n**Severity.** `HIGH` makes text unreadable or truncates content with no way to recover it. `MEDIUM` breaks the type system or the heading hierarchy. `LOW` is isolated polish.\n\n**Verification.** Without a browser: computed size and weight for each heading level, checked descending; declared line-height and measure; truncation rules against realistic string lengths. With one: resize the viewport to catch wrapping, widows and truncation at real content lengths. Report every check you could not run as `Not verified`.\n\n**Format.** Group findings under the principle each violates, ordered by severity, one row per root cause listing every location it appears in:\n\n| Severity | Location | Before | After | Why |\n| --- | --- | --- | --- | --- |\n\n`Location` is `path\u002Fto\u002Ffile:line`. `Why` names the principle and the user impact.\n\nEnd with `Block` when any `HIGH` remains, `Approve` otherwise, leaving the rest in the table as work to do. Never `Approve` coverage you did not inspect. With nothing to report, state \"No actionable typography findings\" and report verification.\n","# Typography\n\nTypography is mostly restraint: a sensible scale, comfortable spacing, enough contrast. A label, a table cell, a marketing headline and an article paragraph do not share one set of rules.\n\nWhen reviewing, read the rendered page instead of scanning the code. Bad wrapping, widows and truncation only show up at real content lengths.\n\nWrite every fix in the project's styling system, and use the exact values below rather than familiar-looking equivalents. The [cheat sheet](css-cheat-sheet.md) maps each declaration to its Tailwind equivalent.\n\nThe words themselves belong to `better-writing`. Semantic heading structure belongs to `better-accessibility`. Spatial RTL layout and logical properties belong to `better-layout`. Contrast measurement belongs to `better-colors`. This skill owns how text renders, wraps and behaves in mixed-direction content.\n\n## Serve the right format\n\nUse `.woff2` on the web, for Brotli compression and broad support. `.woff` is a fallback for very old browsers. `.ttf` and `.otf` are desktop formats with no web compression. How the files load is the project's concern.\n\n## Properties over raw tags\n\nWhen a CSS property exists, use it. `font-weight: 650` instead of `font-variation-settings: \"wght\" 650`. `font-optical-sizing: auto` instead of `\"opsz\"`. `font-variant-numeric: tabular-nums` instead of `font-feature-settings: \"tnum\" 1`.\n\nProperties keep working when a non-variable fallback renders. Reserve raw tags for custom axes (`\"GRAD\" 80`) and niche features (`\"ss01\" 1`) with no property of their own. Axes and feature tags are listed in [variable-fonts-and-opentype.md](variable-fonts-and-opentype.md).\n\n## Load intended weights and styles\n\nBrowsers synthesize a weight or style the active family doesn't provide, distorting the real face. Load the faces the design uses.\n\n`font-synthesis: none` turns synthesis off, but it erases emphasis rather than reporting it. Set it only after checking every required bold, italic, small-cap, superscript and subscript form stays distinct across the fallback stack.\n\n## Fewer fonts, sizes and weights\n\nRarely use more than three fonts. Weight and size define hierarchy; overusing them hurts readability fast. Pair for contrast, not similarity: a serif headline over a sans body reads as deliberate, two near-identical sans-serifs read as a mistake.\n\nBelow `18px`, stay at weight `400` or heavier. Weights under `300` are display-only at `28px`+; they disappear at text sizes. Pairing guidance is in [choosing-fonts.md](choosing-fonts.md).\n\n## Use a type scale with semantic names\n\nDefine a small set of sizes and deviate from it as little as possible. Hard-coded sizes with no system behind them break down at scale.\n\nSolo, default names like `text-sm` are fine when the usage rules are clear. On a team, name sizes by use (`text-body-sm`) so the rules survive other people. Scale construction is in [spacing-and-sizing.md](spacing-and-sizing.md).\n\n## Heading sizes descend with level\n\nMap heading levels to descending steps of the type scale, so a visually subordinate heading never overpowers its parent. Adjacent levels may share a size toward the small end of the scale, as long as weight or spacing keeps them distinct. The semantic element is `better-accessibility`'s; this skill sets only the visual treatment.\n\n## Line-height by role\n\nHeadings tighter, around `1.1`. Body copy `1.5` to `1.6`. Prefer unitless values, so line-height scales with the font size; a fixed `24px` does not.\n\nTight line-height is for short text. Anything that wraps to three or more lines needs at least `1.4`, even in a height-constrained row.\n\n## Letter-spacing by size\n\nLarge headings often look better with slightly negative letter-spacing. Small uppercase labels need a little positive letter-spacing, or the letters feel crowded. Body copy at reading sizes needs neither.\n\n## Cap the measure\n\nLong lines make it hard for the eye to find the next one. Cap long-form text around 60–75 characters per line. Any unit works, as long as a cap exists and the line length lands in range. See [unit choices and the pixel equivalents](wrapping-and-punctuation.md#measure-line-length).\n\n## Wrap deliberately\n\nFour declarations, four jobs:\n\n- `text-wrap: balance` distributes text evenly across lines. Use it on headings.\n- `text-wrap: pretty` stops a single short word landing on the final line. Use it on descriptions.\n- `overflow-wrap: break-word` where a long word, link, or ID could escape the container.\n- `white-space: nowrap` on labels and badges where a line break looks broken.\n\nSkip `balance` and `pretty` in long-form text.\n\n## Tabular numbers on changing values\n\nDigits have different widths by default, so timers, counters and prices shift the layout as they update. Apply `font-variant-numeric: tabular-nums` to any value that changes.\n\n## Truncate without losing content\n\nFor a single line, `text-overflow: ellipsis` with `overflow: hidden` and `white-space: nowrap`. For several, `line-clamp`. Truncation hides content. When the missing text matters, keep the full value reachable in a tooltip or an expanded view.\n\n## Write copy naturally, style with CSS\n\nStore text in natural case and control presentation with `text-transform`, so a redesign never means rewriting copy.\n\nUse smart punctuation in rendered text:\n\n- Curly quotes in prose, straight quotes in code.\n- An en dash for ranges: `2010–2020`.\n- The single ellipsis character, not three periods.\n- `&nbsp;` to hold `16 px` together across a line break.\n- `&shy;` to say where a long word may break.\n\n## Underlines from the font\n\nDefault underlines sit wherever the browser decides. Pull position and thickness from the font's own metrics with `text-underline-position: from-font` and `text-decoration-thickness: from-font`. Tune by hand with `text-decoration-thickness`, `text-underline-offset` and `text-decoration-skip-ink`.\n\n`text-decoration-style` draws the line dotted, dashed, or wavy. A dotted underline is a common hint that a word carries extra information, such as an abbreviation or a defined term.\n\nColor is the only part of a real underline that animates reliably. So unless the only thing animating is the color, build the underline as a separate element rather than using `text-decoration`.\n\n## Inputs at 16px on mobile\n\niOS Safari zooms the whole page when an input's text is smaller than `16px`. Two fixes hold the size at `16px` and look different, so ask which one the design wants:\n\n- Size the input up on mobile (`text-base sm:text-sm`). Changes how it looks on small screens.\n- Keep `font-size: 16px` and render the intended size with `transform: scale()`, compensating width and `line-height`. Identical at every viewport, more code to maintain.\n\nBoth recipes are in [details-and-accessibility.md](details-and-accessibility.md).\n\n## Size and contrast floors\n\nStart long-form body text at `16px`, the browser default. Move off it only for a reason you can name: the typeface runs small, the measure is narrow, or the product is a dense professional tool.\n\nUI text can go smaller. `14px` is a useful starting point for inputs and menus, `13px` for captions and rarely below `12px`. Inputs still need `16px` on mobile.\n\nWhen text looks low-contrast, use `better-colors` to measure the rendered pair and `better-accessibility` to classify the requirement. Leave the colors alone unless asked.\n\n## Font smoothing on the root\n\nOn macOS, text renders heavier than intended. Apply `-webkit-font-smoothing: antialiased` and `-moz-osx-font-smoothing: grayscale` once on the root layout, never per component. Tailwind's `antialiased` covers both.\n\n## Language and bidi behavior\n\nSet `lang` so browsers and assistive technology pick the right pronunciation, quotes and hyphenation. Set `dir` at the document or at the content boundary where direction changes. Preserve digit order, and use `\u003Cbdi>` to isolate a mixed-direction value. Spatial mirroring and logical CSS properties belong to `better-layout`.\n\n## Keep useful text selectable\n\nKeep text selectable by default. `::selection` can carry brand into the reading experience, as long as the selected combination stays legible.\n\n`user-select: none` belongs on a draggable or gesture-driven surface where accidental selection interferes. Never across the interface and never because a button label can be highlighted.\n\n## Before you finish\n\n| Mistake | Fix |\n| --- | --- |\n| Synthesized face differs from the design | Load the real face; disable only the verified synthesis mode |\n| Child heading visually overpowers its parent | Map that section's hierarchy to descending scale steps |\n| Heading element picked for its default size | Choose semantics first, then set the size in CSS |\n| Orphan on the last line of a paragraph | `text-wrap: pretty` |\n| Lopsided two-line heading | `text-wrap: balance` |\n| Justified text in an interface | `text-align: start`; reserve justify for specific editorial layouts |\n| Underline cuts through descenders | `text-decoration-skip-ink: auto`, `from-font` metrics |\n| Mixed-direction value renders in the wrong order | Correct `lang`\u002F`dir`; isolate the value with `\u003Cbdi>` |\n| Selection disabled across application chrome | Restore it; suppress only where it conflicts with a drag or gesture |\n| Extra-info hint with no visual cue | Dotted underline via `text-decoration-style: dotted` |\n| Thin\u002FLight weight on `14px` UI text | Weight `400`+ below `18px`; thin weights are display-only |\n| `leading-none` on a three-line card description | At least `1.4` on any text that wraps to 3+ lines |\n\n## Reporting\n\n**Severity.** `HIGH` makes text unreadable or truncates content with no way to recover it. `MEDIUM` breaks the type system or the heading hierarchy. `LOW` is isolated polish.\n\n**Verification.** Without a browser: computed size and weight for each heading level, checked descending; declared line-height and measure; truncation rules against realistic string lengths. With one: resize the viewport to catch wrapping, widows and truncation at real content lengths. Report every check you could not run as `Not verified`.\n\n**Format.** Group findings under the principle each violates, ordered by severity, one row per root cause listing every location it appears in:\n\n| Severity | Location | Before | After | Why |\n| --- | --- | --- | --- | --- |\n\n`Location` is `path\u002Fto\u002Ffile:line`. `Why` names the principle and the user impact.\n\nEnd with `Block` when any `HIGH` remains, `Approve` otherwise, leaving the rest in the table as work to do. Never `Approve` coverage you did not inspect. With nothing to report, state \"No actionable typography findings\" and report verification.\n",{"name":5,"metadata":24,"description":7},{"author":25,"source":26},"Jakub Krehel","https:\u002F\u002Fgithub.com\u002Fjakubkrehel\u002Fskills\u002Ftree\u002F267330e1adfc66a718fb65fa6918c1f06d0a689e\u002Fskills\u002Fbetter-typography","main","01960aeb08909dbd0c1a2d4f219cdb300099b8b9",0,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills","https:\u002F\u002Fgetedge.cc","https:\u002F\u002Fgithub.com\u002Fgetedgehq","2026-11-12 10:05:02",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add getedgehq\u002Fskills --skill better-typography",{"tool":40,"command":41},"bunx","bunx skills add getedgehq\u002Fskills --skill better-typography",{"tool":43,"command":44},"pnpm","pnpm dlx skills add getedgehq\u002Fskills --skill better-typography","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",111,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"choosing-fonts.md",3179,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002Fchoosing-fonts.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"css-cheat-sheet.md",3952,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002Fcss-cheat-sheet.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"DERIVATION.json",5754,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002FDERIVATION.json",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"details-and-accessibility.md",4211,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002Fdetails-and-accessibility.md",{"path":71,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":15},"LICENSE","许可证",1069,{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"spacing-and-sizing.md",4294,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002Fspacing-and-sizing.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"variable-fonts-and-opentype.md",4308,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002Fvariable-fonts-and-opentype.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"wrapping-and-punctuation.md",3277,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbetter-typography\u002Fwrapping-and-punctuation.md",[87,96,104,111,118,126],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CFVPC1P7JN60J5AN9AZZ5G","zero-downtime-cloud-move","Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7CFVH8VN6G2KE8PBFD1CRMN","zayats-ceo-branding","Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7CFV9BB7G8K8CX9RKZ3GECX","yc-app-roast","YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks \"what would a YC partner think\", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-roast\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7CFV11Z1HB9EEWFQ6PCJ98X","yc-app-review","YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press \"Send my notes\" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-review\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M7CFTSVJV7XCSW62W39MX8CZ","x-growth-playbook","X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says \"analyse my X posts\", \"what works on my Twitter\", \"how do I grow on X\", \"what should I post next on X\", \"audit my X account\", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7CFTK101S3P00MQ129G5YNH","workplan","Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: \"workplan\", \"work plan\", \"create a plan\", \"what's the plan\", \"where was I\", or when Claude detects a multi-step task that needs tracking.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FSKILL.md",[],[]]