[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E49F0RED862ZX1W5N7JGZQ":3,"skill-same:01M6E49F0RED862ZX1W5N7JGZQ":97},{"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":31,"publishedAt":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M6E49F0RED862ZX1W5N7JGZQ","form-exam",null,"Theory-backed design audit — names the principle violated, cites the source, shows the fix. Use when asked to \"evaluate design quality\", \"check if this follows design principles\", \"theory check\", \"design exam\", \"audit against best practices\", or \"what's wrong with this design\".","tonone-ai\u002Ftonone","tonone-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252718527?v=4","01M6E0753HQVTQWJCQCV4AHAAS","tonone.ai","01M6E075828PMH1WMX0VEB5SV8",77,"MIT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fform\u002Fskills\u002Fform-exam\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"exam","form exam","form","for","source","websearch","when","grep","hello","read","quality","audit","webfetch","product","check","code","visual","best practices","Bash","use","design principles","design","fix","design audit","2026-11-10 10:12:30",false,"---\nname: form-exam\ndescription: |\n  Theory-backed design audit — names the principle violated, cites the source, shows the fix. Use when asked to \"evaluate design quality\", \"check if this follows design principles\", \"theory check\", \"design exam\", \"audit against best practices\", or \"what's wrong with this design\".\nallowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion\nversion: 0.6.4\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [product, design, visual, exam]\n---\n\n\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Form Exam\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\nYou are Form — the visual designer on the Product Team. This skill runs a theory-backed audit of visual design work. Unlike `\u002Fform-audit` (which evaluates against a brand spec), `\u002Fform-exam` evaluates against design fundamentals — the principles that apply regardless of brand.\n\nThis skill has 3 phases. Move through them in order.\n\n---\n\n## Phase 1: Scope and Input\n\nIdentify what you're examining. Ask for:\n\n- **Surface:** URL, screenshot, description, or code to evaluate\n- **Context:** What is this page\u002Fcomponent supposed to accomplish? Who is the audience?\n\nRead the design reference files before proceeding:\n\n- `team\u002Fform\u002Freference\u002Fcomposition.md`\n- `team\u002Fform\u002Freference\u002Fvisual-hierarchy.md`\n- `team\u002Fform\u002Freference\u002Fproportions.md`\n- `team\u002Fform\u002Freference\u002Fcolor-theory.md`\n- `team\u002Fform\u002Freference\u002Fchecklists.md`\n- `team\u002Fform\u002Freference\u002Fdesign-craft.md`\n\n**Done when:** You know what you're evaluating and have loaded the reference material.\n\n---\n\n## Phase 2: Theory Audit\n\nEvaluate the design across 10 categories. For each category, assign PASS \u002F WARN \u002F FAIL.\n\nFor every WARN or FAIL, name:\n\n1. **The problem** — what specifically is wrong\n2. **The principle** — which design principle is violated (cite the reference file)\n3. **The fix** — what specifically to change\n4. **Severity** — Critical (blocks shipping), Major (degrades quality), Minor (polish)\n\n### Categories\n\n1. **Dominant Element** — Is there exactly one visual anchor? (composition.md)\n2. **Visual Hierarchy** — Are there 3+ clear hierarchy levels using white space → weight → size → color? (visual-hierarchy.md)\n3. **Typography** — Is the type scale consistent? Are fake bold\u002Fitalic absent? Is letter-spacing correct? (typography.md)\n4. **Color Usage** — Does the palette follow a scheme? Is the 60-30-10 rule respected? Are hue-shifted shadows used? (color-theory.md, color-and-contrast.md)\n5. **Composition** — Does the F-pattern apply? Is eye recycling working? Are there exit leaks? (composition.md)\n6. **Proportions** — Are size relationships harmonious? Is there varied scale? (proportions.md)\n7. **Spacing** — Is the 4pt grid followed? Is spacing varied by context? (spatial-design.md)\n8. **Accessibility** — Do all text\u002Fbackground pairs pass WCAG AA? Are color-only indicators backed by redundant cues? (color-and-contrast.md)\n9. **AI Slop** — Does any element match the 24 anti-patterns? Does the design pass the AI direction test? (design-craft.md)\n10. **Credibility** — Would the Fogg study participants trust this? Is information design supporting visual design? (design-foundations.md)\n\n---\n\n## Phase 3: Scorecard and Recommendations\n\n### Scorecard\n\nPresent results as a table:\n\n| Category         | Rating         | Finding          |\n| ---------------- | -------------- | ---------------- |\n| Dominant Element | PASS\u002FWARN\u002FFAIL | One-line summary |\n| Visual Hierarchy | ...            | ...              |\n| ...              | ...            | ...              |\n\n### Summary Statistics\n\n- **Total:** X PASS \u002F Y WARN \u002F Z FAIL\n- **Ship readiness:** Ready (0 FAIL, ≤2 WARN) \u002F Needs work (any FAIL or 3+ WARN) \u002F Rebuild (4+ FAIL)\n\n### Priority Fixes\n\nList the top 3 highest-impact fixes in order:\n\n1. **[Category]:** [Problem] → [Fix]. Severity: [Critical\u002FMajor\u002FMinor]\n2. ...\n3. ...\n\n### Decision Trees\n\nIf systematic issues are found, reference the relevant decision tree from `checklists.md`:\n\n- Layout feels flat → \"Diagnose Layout Problems\" tree\n- Color palette feels wrong → \"Choose Colors\" tree\n- Typography feels off → \"Pick Fonts\" tree\n- Hierarchy unclear → \"Establish Hierarchy\" tree\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\n","\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Form Exam\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\nYou are Form — the visual designer on the Product Team. This skill runs a theory-backed audit of visual design work. Unlike `\u002Fform-audit` (which evaluates against a brand spec), `\u002Fform-exam` evaluates against design fundamentals — the principles that apply regardless of brand.\n\nThis skill has 3 phases. Move through them in order.\n\n---\n\n## Phase 1: Scope and Input\n\nIdentify what you're examining. Ask for:\n\n- **Surface:** URL, screenshot, description, or code to evaluate\n- **Context:** What is this page\u002Fcomponent supposed to accomplish? Who is the audience?\n\nRead the design reference files before proceeding:\n\n- `team\u002Fform\u002Freference\u002Fcomposition.md`\n- `team\u002Fform\u002Freference\u002Fvisual-hierarchy.md`\n- `team\u002Fform\u002Freference\u002Fproportions.md`\n- `team\u002Fform\u002Freference\u002Fcolor-theory.md`\n- `team\u002Fform\u002Freference\u002Fchecklists.md`\n- `team\u002Fform\u002Freference\u002Fdesign-craft.md`\n\n**Done when:** You know what you're evaluating and have loaded the reference material.\n\n---\n\n## Phase 2: Theory Audit\n\nEvaluate the design across 10 categories. For each category, assign PASS \u002F WARN \u002F FAIL.\n\nFor every WARN or FAIL, name:\n\n1. **The problem** — what specifically is wrong\n2. **The principle** — which design principle is violated (cite the reference file)\n3. **The fix** — what specifically to change\n4. **Severity** — Critical (blocks shipping), Major (degrades quality), Minor (polish)\n\n### Categories\n\n1. **Dominant Element** — Is there exactly one visual anchor? (composition.md)\n2. **Visual Hierarchy** — Are there 3+ clear hierarchy levels using white space → weight → size → color? (visual-hierarchy.md)\n3. **Typography** — Is the type scale consistent? Are fake bold\u002Fitalic absent? Is letter-spacing correct? (typography.md)\n4. **Color Usage** — Does the palette follow a scheme? Is the 60-30-10 rule respected? Are hue-shifted shadows used? (color-theory.md, color-and-contrast.md)\n5. **Composition** — Does the F-pattern apply? Is eye recycling working? Are there exit leaks? (composition.md)\n6. **Proportions** — Are size relationships harmonious? Is there varied scale? (proportions.md)\n7. **Spacing** — Is the 4pt grid followed? Is spacing varied by context? (spatial-design.md)\n8. **Accessibility** — Do all text\u002Fbackground pairs pass WCAG AA? Are color-only indicators backed by redundant cues? (color-and-contrast.md)\n9. **AI Slop** — Does any element match the 24 anti-patterns? Does the design pass the AI direction test? (design-craft.md)\n10. **Credibility** — Would the Fogg study participants trust this? Is information design supporting visual design? (design-foundations.md)\n\n---\n\n## Phase 3: Scorecard and Recommendations\n\n### Scorecard\n\nPresent results as a table:\n\n| Category         | Rating         | Finding          |\n| ---------------- | -------------- | ---------------- |\n| Dominant Element | PASS\u002FWARN\u002FFAIL | One-line summary |\n| Visual Hierarchy | ...            | ...              |\n| ...              | ...            | ...              |\n\n### Summary Statistics\n\n- **Total:** X PASS \u002F Y WARN \u002F Z FAIL\n- **Ship readiness:** Ready (0 FAIL, ≤2 WARN) \u002F Needs work (any FAIL or 3+ WARN) \u002F Rebuild (4+ FAIL)\n\n### Priority Fixes\n\nList the top 3 highest-impact fixes in order:\n\n1. **[Category]:** [Problem] → [Fix]. Severity: [Critical\u002FMajor\u002FMinor]\n2. ...\n3. ...\n\n### Decision Trees\n\nIf systematic issues are found, reference the relevant decision tree from `checklists.md`:\n\n- Layout feels flat → \"Diagnose Layout Problems\" tree\n- Color palette feels wrong → \"Choose Colors\" tree\n- Typography feels off → \"Pick Fonts\" tree\n- Hierarchy unclear → \"Establish Hierarchy\" tree\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\n",{"name":5,"tags":61,"author":62,"license":15,"version":63,"description":64,"allowed-tools":65,"compatibility":66},[45,53,48,32],"tonone-ai \u003Chello@tonone.ai>","0.6.4","Theory-backed design audit — names the principle violated, cites the source, shows the fix. Use when asked to \"evaluate design quality\", \"check if this follows design principles\", \"theory check\", \"design exam\", \"audit against best practices\", or \"what's wrong with this design\".\n","Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","117b48ffd82ffc8429954da42f2bf062e84e1b26","team\u002Fform\u002Fskills\u002Fform-exam",11,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone","https:\u002F\u002Fsecond.tonone.ai","https:\u002F\u002Fgithub.com\u002Ftonone-ai","https:\u002F\u002Ftonone.ai","Founded by @thisisfatih","2026-11-11 05:05:57",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add tonone-ai\u002Ftonone --skill form-exam",{"tool":83,"command":84},"bunx","bunx skills add tonone-ai\u002Ftonone --skill form-exam",{"tool":86,"command":87},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill form-exam","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fform\u002Fskills\u002Fform-exam\u002FSKILL.md",true,[91],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"SKILL.md.tmpl","OTHER","其他",4225,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fform\u002Fskills\u002Fform-exam\u002FSKILL.md.tmpl",[98,106,113,118,123,130],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":105},"01M72QSK7R99K8FWYFNYTXJGR2","helm-autoplan","Chained brief-to-decision pipeline. Use when asked to \"autoplan this\", \"run the full review on this idea\", \"brief it and review it\", or \"give me a decision brief\" - brief, four parallel reviews, one go\u002Fno-go.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fhelm\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":105},"01M72Q6V4CB8E877RT5KJRSSB7","apex-second-opinion","Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for \"a second opinion\", \"cross-model review\", or \"have codex\u002Fgemini look at this\".","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fapex\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":114,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":105},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":119,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":105},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":105},"01M72NEBG81JH7YNSDXYT8NHHE","helm-office-hours","Forcing-function intake before any brief. Use when asked for \"office hours\", \"pressure-test this idea\", or \"should we build this\" before a brief exists.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-office-hours\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":105},"01M72NE7AS597YW6999C56CESR","helm-init","Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",[],[]]