[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P0V8N502GK89FSX4PB3DFB":3,"skill-same:01M6P0V8N502GK89FSX4PB3DFB":59},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":58},"01M6P0V8N502GK89FSX4PB3DFB","typeset",null,"Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.","arnabdeypolimi\u002Fclaude_code_setup","arnabdeypolimi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F32412133?v=4","01M6P0328AJ1TQ5N763ZSGNRF9","Arnab Dey","01M6P032C9PY7NRT2C9SNRFJ5G",5,"MIT","https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002Fcreate-claude-setup\u002Fassets\u002Fskills\u002Ftypeset\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29],"text","user","use","typography","readability","type","fonts","more","true","font","hierarchy","2026-11-10 10:12:30",false,"---\nname: typeset\ndescription: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.\nuser-invocable: true\nargument-hint: \"[target]\"\n---\n\nAssess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type.\n\n## MANDATORY PREPARATION\n\nInvoke \u002Ffrontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fteach-impeccable first.\n\n---\n\n## Assess Current Typography\n\nAnalyze what's weak or generic about the current type:\n\n1. **Font choices**:\n   - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults)\n   - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface)\n   - Are there too many font families? (More than 2-3 is almost always a mess)\n\n2. **Hierarchy**:\n   - Can you tell headings from body from captions at a glance?\n   - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy)\n   - Are weight contrasts strong enough? (Medium vs Regular is barely visible)\n\n3. **Sizing & scale**:\n   - Is there a consistent type scale, or are sizes arbitrary?\n   - Does body text meet minimum readability? (16px+)\n   - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing\u002Fcontent page headings)\n\n4. **Readability**:\n   - Are line lengths comfortable? (45-75 characters ideal)\n   - Is line-height appropriate for the font and context?\n   - Is there enough contrast between text and background?\n\n5. **Consistency**:\n   - Are the same elements styled the same way throughout?\n   - Are font weights used consistently? (Not bold in one section, semibold in another for the same role)\n   - Is letter-spacing intentional or default everywhere?\n\n**CRITICAL**: The goal isn't to make text \"fancier\" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting.\n\n## Plan Typography Improvements\n\nConsult the [typography reference](reference\u002Ftypography.md) from the frontend-design skill for detailed guidance on scales, pairing, and loading strategies.\n\nCreate a systematic plan:\n\n- **Font selection**: Do fonts need replacing? What fits the brand\u002Fcontext?\n- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy\n- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits)\n- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements\n\n## Improve Typography Systematically\n\n### Font Selection\n\nIf fonts need replacing:\n- Choose fonts that reflect the brand personality\n- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights\n- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks)\n\n### Establish Hierarchy\n\nBuild a clear type scale:\n- **5 sizes cover most needs**: caption, secondary, body, subheading, heading\n- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5)\n- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone\n- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need\n- **Marketing \u002F content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed\n\n### Fix Readability\n\n- Set `max-width` on text containers using `ch` units (`max-width: 65ch`)\n- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7)\n- Increase line-height slightly for light-on-dark text\n- Ensure body text is at least 16px \u002F 1rem\n\n### Refine Details\n\n- Use `tabular-nums` for data tables and numbers that should align\n- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text\n- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`)\n- Set `font-kerning: normal` and consider OpenType features where appropriate\n\n### Weight Consistency\n\n- Define clear roles for each weight and stick to them\n- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty)\n- Load only the weights you actually use (each weight adds to page load)\n\n**NEVER**:\n- Use more than 2-3 font families\n- Pick sizes arbitrarily — commit to a scale\n- Set body text below 16px\n- Use decorative\u002Fdisplay fonts for body text\n- Disable browser zoom (`user-scalable=no`)\n- Use `px` for font sizes — use `rem` to respect user settings\n- Default to Inter\u002FRoboto\u002FOpen Sans when personality matters\n- Pair fonts that are similar but not identical (two geometric sans-serifs)\n\n## Verify Typography Improvements\n\n- **Hierarchy**: Can you identify heading vs body vs caption instantly?\n- **Readability**: Is body text comfortable to read in long passages?\n- **Consistency**: Are same-role elements styled identically throughout?\n- **Personality**: Does the typography reflect the brand?\n- **Performance**: Are web fonts loading efficiently without layout shift?\n- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%?\n\nRemember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make.","Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type.\n\n## MANDATORY PREPARATION\n\nInvoke \u002Ffrontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fteach-impeccable first.\n\n---\n\n## Assess Current Typography\n\nAnalyze what's weak or generic about the current type:\n\n1. **Font choices**:\n   - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults)\n   - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface)\n   - Are there too many font families? (More than 2-3 is almost always a mess)\n\n2. **Hierarchy**:\n   - Can you tell headings from body from captions at a glance?\n   - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy)\n   - Are weight contrasts strong enough? (Medium vs Regular is barely visible)\n\n3. **Sizing & scale**:\n   - Is there a consistent type scale, or are sizes arbitrary?\n   - Does body text meet minimum readability? (16px+)\n   - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing\u002Fcontent page headings)\n\n4. **Readability**:\n   - Are line lengths comfortable? (45-75 characters ideal)\n   - Is line-height appropriate for the font and context?\n   - Is there enough contrast between text and background?\n\n5. **Consistency**:\n   - Are the same elements styled the same way throughout?\n   - Are font weights used consistently? (Not bold in one section, semibold in another for the same role)\n   - Is letter-spacing intentional or default everywhere?\n\n**CRITICAL**: The goal isn't to make text \"fancier\" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting.\n\n## Plan Typography Improvements\n\nConsult the [typography reference](reference\u002Ftypography.md) from the frontend-design skill for detailed guidance on scales, pairing, and loading strategies.\n\nCreate a systematic plan:\n\n- **Font selection**: Do fonts need replacing? What fits the brand\u002Fcontext?\n- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy\n- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits)\n- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements\n\n## Improve Typography Systematically\n\n### Font Selection\n\nIf fonts need replacing:\n- Choose fonts that reflect the brand personality\n- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights\n- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks)\n\n### Establish Hierarchy\n\nBuild a clear type scale:\n- **5 sizes cover most needs**: caption, secondary, body, subheading, heading\n- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5)\n- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone\n- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need\n- **Marketing \u002F content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed\n\n### Fix Readability\n\n- Set `max-width` on text containers using `ch` units (`max-width: 65ch`)\n- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7)\n- Increase line-height slightly for light-on-dark text\n- Ensure body text is at least 16px \u002F 1rem\n\n### Refine Details\n\n- Use `tabular-nums` for data tables and numbers that should align\n- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text\n- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`)\n- Set `font-kerning: normal` and consider OpenType features where appropriate\n\n### Weight Consistency\n\n- Define clear roles for each weight and stick to them\n- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty)\n- Load only the weights you actually use (each weight adds to page load)\n\n**NEVER**:\n- Use more than 2-3 font families\n- Pick sizes arbitrarily — commit to a scale\n- Set body text below 16px\n- Use decorative\u002Fdisplay fonts for body text\n- Disable browser zoom (`user-scalable=no`)\n- Use `px` for font sizes — use `rem` to respect user settings\n- Default to Inter\u002FRoboto\u002FOpen Sans when personality matters\n- Pair fonts that are similar but not identical (two geometric sans-serifs)\n\n## Verify Typography Improvements\n\n- **Hierarchy**: Can you identify heading vs body vs caption instantly?\n- **Readability**: Is body text comfortable to read in long passages?\n- **Consistency**: Are same-role elements styled identically throughout?\n- **Personality**: Does the typography reflect the brand?\n- **Performance**: Are web fonts loading efficiently without layout shift?\n- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%?\n\nRemember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make.",{"name":5,"description":7,"argument-hint":35,"user-invocable":36},"[target]",true,"main","afc7b6d68a4179af3aed48adbb19456133f8ae06","create-claude-setup\u002Fassets\u002Fskills\u002Ftypeset",0,"https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup","https:\u002F\u002Fgithub.com\u002Farnabdeypolimi","arnabdey.co","Senior research engineer with a PhD in Deep Learning and Computer Vision ","2026-09-17 03:30:40",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":36},[48,51,54],{"tool":49,"command":50},"npx","npx skills add arnabdeypolimi\u002Fclaude_code_setup --skill typeset",{"tool":52,"command":53},"bunx","bunx skills add arnabdeypolimi\u002Fclaude_code_setup --skill typeset",{"tool":55,"command":56},"pnpm","pnpm dlx skills add arnabdeypolimi\u002Fclaude_code_setup --skill typeset","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002Fcreate-claude-setup\u002Fassets\u002Fskills\u002Ftypeset\u002FSKILL.md",[],[60,69,78,112,145,173],{"skillNo":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":30},"01M6P0W3RVYQJEJQN9NB4H99T1","git-operations","https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002Fcreate-claude-setup\u002Ftest\u002Ffixtures\u002Fhealthy\u002F.claude\u002Fskills\u002Fgit-operations\u002FSKILL.md",[],[66,67,68],"git operations","operations","git",{"skillNo":70,"name":71,"nameZh":6,"description":6,"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":30},"01M6P0W1AG7EQXZQSCBQJ9RD60","python-best-practices","https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002Fcreate-claude-setup\u002Ftest\u002Ffixtures\u002Fdrifted\u002F.claude\u002Fskills\u002Fpython-best-practices\u002FSKILL.md",[],[75,76,77],"python best practices","best practices","python",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":92,"publishedAt":30},"01M6P0VRDYNE55YYX06G81MJJH","typst-paper","Typst academic paper assistant for existing `.typ` paper projects in English or Chinese. Use this skill whenever the user wants to compile, audit, or improve a Typst paper, including format checks, bibliography validation for BibTeX or Hayagriva, grammar\u002Fsentence\u002Flogic review, expression polishing, translation, title optimization, pseudocode review, algorithm block cleanup, de-AI editing, or experiment-section review. Trigger even when the user only mentions one Typst file, one bibliography issue, one pseudocode block, or one section rewrite. Also trigger when the user mentions \".typ files\", \"typst compile error\", \"typst export\", \"typst bibliography\", `algorithm-figure`, `lovelace`, or `algorithmic` even without saying the word \"Typst\" explicitly.","https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002Fcreate-claude-setup\u002Fassets\u002Fskills\u002Ftypst-paper\u002FSKILL.md",[84,89],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000021","资料检索与研究",[93,94,95,37,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111],"typst paper","typst","paper","writing","review","cleanup","Bash","improve","projects","only","pseudocode","uv","files","translation","chinese","english","expression","error","title",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":129,"publishedAt":30},"01M6P0V3G89JYZ71PA2FVPGM4F","teach-impeccable","One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.","https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002Fcreate-claude-setup\u002Fassets\u002Fskills\u002Fteach-impeccable\u002FSKILL.md",[118,121,126],{"categoryNo":119,"categoryName":120,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":127,"categoryName":128,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000039","教师与教育",[130,131,132,27,133,134,135,136,137,138,139,140,141,142,143,144],"teach impeccable","impeccable","teach","design","for","config","setup","guidelines","run","file","context","ai config","time","project","it",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":156,"publishedAt":30},"01M6P0TEK3SF2V4Y52RVP86JM2","research-paper-writing","Improve academic paper writing quality for ML\u002FCV\u002FNLP-style papers with clear section structure, paragraph flow, and reviewer-facing presentation. Use when drafting or revising Abstract, Introduction, Related Work, Method, Experiments, or Conclusion; polishing figures\u002Ftables; checking claim-support alignment; or performing self-review before submission.","https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002Fcreate-claude-setup\u002Fassets\u002Fskills\u002Fresearch-paper-writing\u002FSKILL.md",[151,152,153],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":154,"categoryName":155,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000036","内容创作者",[95,157,158,96,159,100,160,161,162,163,164,165,166,167,168,169,170,171,97,172],"research paper writing","Paper Writing","research","reviewer","work","alignment","experiments","claim","structure","self","support","presentation","figures","papers","tables","flow",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":185,"publishedAt":30},"01M6P0T85C20EYG8Y36WA6W4M7","remotion-best-practices","Best practices for Remotion - Video creation in React","https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002Fcreate-claude-setup\u002Fassets\u002Fskills\u002Fremotion-best-practices\u002FSKILL.md",[179,182],{"categoryNo":180,"categoryName":181,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":183,"categoryName":184,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000016","图像与多媒体",[76,186,187,134,188,189,190,191,192,193],"remotion best practices","Remotion","creation","remotion, video, react, animation, composition","Composition","Animation","Video","react"]