[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P04PRTY8F1F2J1F9NTRY75":3,"skill-same:01M6P04PRTY8F1F2J1F9NTRY75":72},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":71},"01M6P04PRTY8F1F2J1F9NTRY75","audit",null,"Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.","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\u002F.claude\u002Fskills\u002Faudit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"responsive design","performance audit","ratings","accessibility check","actionable","feature","responsive","across","quality review","patterns","design","anti-patterns","page","plan","severity","run","component","performance","review","2026-11-10 10:12:30",false,"---\nname: audit\ndescription: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.\nuser-invocable: true\nargument-hint: \"[area (feature, page, component...)]\"\n---\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\nRun systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.\n\nThis is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation.\n\n## Diagnostic Scan\n\nRun comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below.\n\n### 1. Accessibility (A11y)\n\n**Check for**:\n- **Contrast issues**: Text contrast ratios \u003C 4.5:1 (or 7:1 for AAA)\n- **Missing ARIA**: Interactive elements without proper roles, labels, or states\n- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps\n- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons\n- **Alt text**: Missing or poor image descriptions\n- **Form issues**: Inputs without labels, poor error messaging, missing required indicators\n\n**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA)\n\n### 2. Performance\n\n**Check for**:\n- **Layout thrashing**: Reading\u002Fwriting layout properties in loops\n- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform\u002Fopacity\n- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change\n- **Bundle size**: Unnecessary imports, unused dependencies\n- **Render performance**: Unnecessary re-renders, missing memoization\n\n**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized)\n\n### 3. Theming\n\n**Check for**:\n- **Hard-coded colors**: Colors not using design tokens\n- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme\n- **Inconsistent tokens**: Using wrong tokens, mixing token types\n- **Theme switching issues**: Values that don't update on theme change\n\n**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly)\n\n### 4. Responsive Design\n\n**Check for**:\n- **Fixed widths**: Hard-coded widths that break on mobile\n- **Touch targets**: Interactive elements \u003C 44x44px\n- **Horizontal scroll**: Content overflow on narrow viewports\n- **Text scaling**: Layouts that break when text size increases\n- **Missing breakpoints**: No mobile\u002Ftablet variants\n\n**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets)\n\n### 5. Anti-Patterns (CRITICAL)\n\nCheck against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).\n\n**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design)\n\n## Generate Report\n\n### Audit Health Score\n\n| # | Dimension | Score | Key Finding |\n|---|-----------|-------|-------------|\n| 1 | Accessibility | ? | [most critical a11y issue or \"--\"] |\n| 2 | Performance | ? | |\n| 3 | Responsive Design | ? | |\n| 4 | Theming | ? | |\n| 5 | Anti-Patterns | ? | |\n| **Total** | | **??\u002F20** | **[Rating band]** |\n\n**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues)\n\n### Anti-Patterns Verdict\n**Start here.** Pass\u002Ffail: Does this look AI-generated? List specific tells. Be brutally honest.\n\n### Executive Summary\n- Audit Health Score: **??\u002F20** ([rating band])\n- Total issues found (count by severity: P0\u002FP1\u002FP2\u002FP3)\n- Top 3-5 critical issues\n- Recommended next steps\n\n### Detailed Findings by Severity\n\nTag every issue with **P0-P3 severity**:\n- **P0 Blocking**: Prevents task completion — fix immediately\n- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release\n- **P2 Minor**: Annoyance, workaround exists — fix in next pass\n- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits\n\nFor each issue, document:\n- **[P?] Issue name**\n- **Location**: Component, file, line\n- **Category**: Accessibility \u002F Performance \u002F Theming \u002F Responsive \u002F Anti-Pattern\n- **Impact**: How it affects users\n- **WCAG\u002FStandard**: Which standard it violates (if applicable)\n- **Recommendation**: How to fix it\n- **Suggested command**: Which command to use (prefer: \u002Fanimate, \u002Fquieter, \u002Foptimize, \u002Fadapt, \u002Fclarify, \u002Fdistill, \u002Fdelight, \u002Fonboard, \u002Fnormalize, \u002Faudit, \u002Fharden, \u002Fpolish, \u002Fextract, \u002Fbolder, \u002Farrange, \u002Ftypeset, \u002Fcritique, \u002Fcolorize, \u002Foverdrive)\n\n### Patterns & Systemic Issues\n\nIdentify recurring problems that indicate systemic gaps rather than one-off mistakes:\n- \"Hard-coded colors appear in 15+ components, should use design tokens\"\n- \"Touch targets consistently too small (\u003C44px) throughout mobile experience\"\n\n### Positive Findings\n\nNote what's working well — good practices to maintain and replicate.\n\n## Recommended Actions\n\nList recommended commands in priority order (P0 first, then P1, then P2):\n\n1. **[P?] `\u002Fcommand-name`** — Brief description (specific context from audit findings)\n2. **[P?] `\u002Fcommand-name`** — Brief description (specific context)\n\n**Rules**: Only recommend commands from: \u002Fanimate, \u002Fquieter, \u002Foptimize, \u002Fadapt, \u002Fclarify, \u002Fdistill, \u002Fdelight, \u002Fonboard, \u002Fnormalize, \u002Faudit, \u002Fharden, \u002Fpolish, \u002Fextract, \u002Fbolder, \u002Farrange, \u002Ftypeset, \u002Fcritique, \u002Fcolorize, \u002Foverdrive. Map findings to the most appropriate command. End with `\u002Fpolish` as the final step if any fixes were recommended.\n\nAfter presenting the summary, tell the user:\n\n> You can ask me to run these one at a time, all at once, or in any order you prefer.\n>\n> Re-run `\u002Faudit` after fixes to see your score improve.\n\n**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters.\n\n**NEVER**:\n- Report issues without explaining impact (why does this matter?)\n- Provide generic recommendations (be specific and actionable)\n- Skip positive findings (celebrate what works)\n- Forget to prioritize (everything can't be P0)\n- Report false positives without verification\n\nRemember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement.","## 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\nRun systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.\n\nThis is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation.\n\n## Diagnostic Scan\n\nRun comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below.\n\n### 1. Accessibility (A11y)\n\n**Check for**:\n- **Contrast issues**: Text contrast ratios \u003C 4.5:1 (or 7:1 for AAA)\n- **Missing ARIA**: Interactive elements without proper roles, labels, or states\n- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps\n- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons\n- **Alt text**: Missing or poor image descriptions\n- **Form issues**: Inputs without labels, poor error messaging, missing required indicators\n\n**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA)\n\n### 2. Performance\n\n**Check for**:\n- **Layout thrashing**: Reading\u002Fwriting layout properties in loops\n- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform\u002Fopacity\n- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change\n- **Bundle size**: Unnecessary imports, unused dependencies\n- **Render performance**: Unnecessary re-renders, missing memoization\n\n**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized)\n\n### 3. Theming\n\n**Check for**:\n- **Hard-coded colors**: Colors not using design tokens\n- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme\n- **Inconsistent tokens**: Using wrong tokens, mixing token types\n- **Theme switching issues**: Values that don't update on theme change\n\n**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly)\n\n### 4. Responsive Design\n\n**Check for**:\n- **Fixed widths**: Hard-coded widths that break on mobile\n- **Touch targets**: Interactive elements \u003C 44x44px\n- **Horizontal scroll**: Content overflow on narrow viewports\n- **Text scaling**: Layouts that break when text size increases\n- **Missing breakpoints**: No mobile\u002Ftablet variants\n\n**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets)\n\n### 5. Anti-Patterns (CRITICAL)\n\nCheck against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).\n\n**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design)\n\n## Generate Report\n\n### Audit Health Score\n\n| # | Dimension | Score | Key Finding |\n|---|-----------|-------|-------------|\n| 1 | Accessibility | ? | [most critical a11y issue or \"--\"] |\n| 2 | Performance | ? | |\n| 3 | Responsive Design | ? | |\n| 4 | Theming | ? | |\n| 5 | Anti-Patterns | ? | |\n| **Total** | | **??\u002F20** | **[Rating band]** |\n\n**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues)\n\n### Anti-Patterns Verdict\n**Start here.** Pass\u002Ffail: Does this look AI-generated? List specific tells. Be brutally honest.\n\n### Executive Summary\n- Audit Health Score: **??\u002F20** ([rating band])\n- Total issues found (count by severity: P0\u002FP1\u002FP2\u002FP3)\n- Top 3-5 critical issues\n- Recommended next steps\n\n### Detailed Findings by Severity\n\nTag every issue with **P0-P3 severity**:\n- **P0 Blocking**: Prevents task completion — fix immediately\n- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release\n- **P2 Minor**: Annoyance, workaround exists — fix in next pass\n- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits\n\nFor each issue, document:\n- **[P?] Issue name**\n- **Location**: Component, file, line\n- **Category**: Accessibility \u002F Performance \u002F Theming \u002F Responsive \u002F Anti-Pattern\n- **Impact**: How it affects users\n- **WCAG\u002FStandard**: Which standard it violates (if applicable)\n- **Recommendation**: How to fix it\n- **Suggested command**: Which command to use (prefer: \u002Fanimate, \u002Fquieter, \u002Foptimize, \u002Fadapt, \u002Fclarify, \u002Fdistill, \u002Fdelight, \u002Fonboard, \u002Fnormalize, \u002Faudit, \u002Fharden, \u002Fpolish, \u002Fextract, \u002Fbolder, \u002Farrange, \u002Ftypeset, \u002Fcritique, \u002Fcolorize, \u002Foverdrive)\n\n### Patterns & Systemic Issues\n\nIdentify recurring problems that indicate systemic gaps rather than one-off mistakes:\n- \"Hard-coded colors appear in 15+ components, should use design tokens\"\n- \"Touch targets consistently too small (\u003C44px) throughout mobile experience\"\n\n### Positive Findings\n\nNote what's working well — good practices to maintain and replicate.\n\n## Recommended Actions\n\nList recommended commands in priority order (P0 first, then P1, then P2):\n\n1. **[P?] `\u002Fcommand-name`** — Brief description (specific context from audit findings)\n2. **[P?] `\u002Fcommand-name`** — Brief description (specific context)\n\n**Rules**: Only recommend commands from: \u002Fanimate, \u002Fquieter, \u002Foptimize, \u002Fadapt, \u002Fclarify, \u002Fdistill, \u002Fdelight, \u002Fonboard, \u002Fnormalize, \u002Faudit, \u002Fharden, \u002Fpolish, \u002Fextract, \u002Fbolder, \u002Farrange, \u002Ftypeset, \u002Fcritique, \u002Fcolorize, \u002Foverdrive. Map findings to the most appropriate command. End with `\u002Fpolish` as the final step if any fixes were recommended.\n\nAfter presenting the summary, tell the user:\n\n> You can ask me to run these one at a time, all at once, or in any order you prefer.\n>\n> Re-run `\u002Faudit` after fixes to see your score improve.\n\n**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters.\n\n**NEVER**:\n- Report issues without explaining impact (why does this matter?)\n- Provide generic recommendations (be specific and actionable)\n- Skip positive findings (celebrate what works)\n- Forget to prioritize (everything can't be P0)\n- Report false positives without verification\n\nRemember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement.",{"name":5,"description":7,"argument-hint":48,"user-invocable":49},"[area (feature, page, component...)]",true,"main","afc7b6d68a4179af3aed48adbb19456133f8ae06",".claude\u002Fskills\u002Faudit",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":60,"prompt":70,"zipAvailable":49},[61,64,67],{"tool":62,"command":63},"npx","npx skills add arnabdeypolimi\u002Fclaude_code_setup --skill audit",{"tool":65,"command":66},"bunx","bunx skills add arnabdeypolimi\u002Fclaude_code_setup --skill audit",{"tool":68,"command":69},"pnpm","pnpm dlx skills add arnabdeypolimi\u002Fclaude_code_setup --skill audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faudit\u002FSKILL.md",[],[73,82,91,122,140,169],{"skillNo":74,"name":75,"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":76,"categories":77,"keywords":78,"publishedAt":43},"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",[],[79,80,81],"git operations","operations","git",{"skillNo":83,"name":84,"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":85,"categories":86,"keywords":87,"publishedAt":43},"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",[],[88,89,90],"python best practices","best practices","python",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":103,"publishedAt":43},"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",[97,100],{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[104,105,106,107,108,42,109,110,111,112,113,114,115,116,117,118,50,119,120,121],"paper","typst","typst paper","title","writing","cleanup","Bash","improve","projects","only","pseudocode","uv","files","translation","chinese","english","expression","error",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":43},"01M6P0V8N502GK89FSX4PB3DFB","typeset","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.","https:\u002F\u002Fgithub.com\u002Farnabdeypolimi\u002Fclaude_code_setup\u002Fblob\u002Fmain\u002Fcreate-claude-setup\u002Fassets\u002Fskills\u002Ftypeset\u002FSKILL.md",[],[124,129,130,131,132,133,134,135,136,137,138,139],"fonts","more","user","true","font","hierarchy","type","readability","text","use","typography",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":155,"publishedAt":43},"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",[146,147,152],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":153,"categoryName":154,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000039","教师与教育",[156,157,158,34,159,160,161,39,162,163,164,165,166,167,132,168],"teach impeccable","impeccable","teach","config","setup","guidelines","file","context","ai config","time","project","it","for",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":180,"publishedAt":43},"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",[175,176,177],{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":178,"categoryName":179,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000036","内容创作者",[108,104,181,182,183,42,184,185,186,111,187,188,189,190,191,192,193,194,195,196],"research paper writing","research","Paper Writing","support","experiments","flow","reviewer","work","alignment","claim","structure","self","presentation","figures","papers","tables"]