[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77TJ2KD6FJDAPAQG5VAF3EF":3,"skill-same:01M77TJ2KD6FJDAPAQG5VAF3EF":55},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M77TJ2KD6FJDAPAQG5VAF3EF","critique-theater",null,"Five-dimension design quality review — score the artifact against craft, brand, accessibility, and copy, then fix what falls short before handing it over.","hiktan44\u002Fopen-design-app","hiktan44","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140920746?v=4","01M77SNV7J2RH7G3TQVS2FXMW9","hikmet tanriverdi","01M77SNV87GR8D3BJ9WJHFMZ9Y",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fatoms\u002Fcritique-theater\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: critique-theater\ndescription: Five-dimension design quality review — score the artifact against craft, brand, accessibility, and copy, then fix what falls short before handing it over.\nod:\n  scenario: general\n  mode: critique\n---\n\n# Design review\n\nBefore you hand an artifact over, review it against five dimensions and fix\nwhat falls short. This is a quality bar, not a performance: do the review,\napply the fixes, and describe the outcome in ordinary prose.\n\n## The five dimensions\n\nJudge the artifact you just produced from five angles. Each one owns its own\nscope; do not let a strength in one excuse a failure in another.\n\n- **Craft** — layout, hierarchy, spacing, alignment, and visual rhythm. Does it\n  read as deliberate work rather than a template with the words swapped out?\n- **Critique** — does it actually solve the user's stated problem? Look for\n  the weakest claim, the thinnest section, the thing a sceptical reviewer would\n  attack first.\n- **Brand** — does it follow the active design system's tokens, typography, and\n  voice? A brand violation is a defect even when the result looks pleasant.\n- **Accessibility** — contrast ratios, touch-target sizes, focus rings, labels\n  on interactive controls and dialogs, keyboard reachability, sensible\n  heading order.\n- **Copy** — is the text specific, readable, and free of filler? Placeholder\n  phrasing and marketing padding both count as defects.\n\n## What to do with the findings\n\nRecord each concrete defect and fix it in the same turn. A finding you cannot\nfix is worth stating plainly, with the reason, so the user can decide.\n\nKeep iterating while defects remain and you still have room to work. Stop when\nthe artifact clears all five dimensions, or when further rounds stop producing\nreal improvements — whichever comes first. Three passes is a sensible ceiling.\n\n`OD_MAX_DEVLOOP_ITERATIONS` caps the outer plugin pipeline stage; it is not\nthis review's round limit. A pipeline's `critique.score` signal is a\nscheduler-facing projection, not something you should write into your answer.\n\n## How to report it\n\nWrite the outcome the way you would write any other part of your answer: plain\nprose, in the user's language, saying what you checked, what you fixed, and\nanything you deliberately left alone.\n\nDo not invent a structured review transcript, a scored panel, a cast of named\nreviewer personas, or any tag-based envelope around your answer. Do not write a\n`critique.json` file into the project. None of those are inputs to anything —\nthey only add noise to the user's chat.\n","# Design review\n\nBefore you hand an artifact over, review it against five dimensions and fix\nwhat falls short. This is a quality bar, not a performance: do the review,\napply the fixes, and describe the outcome in ordinary prose.\n\n## The five dimensions\n\nJudge the artifact you just produced from five angles. Each one owns its own\nscope; do not let a strength in one excuse a failure in another.\n\n- **Craft** — layout, hierarchy, spacing, alignment, and visual rhythm. Does it\n  read as deliberate work rather than a template with the words swapped out?\n- **Critique** — does it actually solve the user's stated problem? Look for\n  the weakest claim, the thinnest section, the thing a sceptical reviewer would\n  attack first.\n- **Brand** — does it follow the active design system's tokens, typography, and\n  voice? A brand violation is a defect even when the result looks pleasant.\n- **Accessibility** — contrast ratios, touch-target sizes, focus rings, labels\n  on interactive controls and dialogs, keyboard reachability, sensible\n  heading order.\n- **Copy** — is the text specific, readable, and free of filler? Placeholder\n  phrasing and marketing padding both count as defects.\n\n## What to do with the findings\n\nRecord each concrete defect and fix it in the same turn. A finding you cannot\nfix is worth stating plainly, with the reason, so the user can decide.\n\nKeep iterating while defects remain and you still have room to work. Stop when\nthe artifact clears all five dimensions, or when further rounds stop producing\nreal improvements — whichever comes first. Three passes is a sensible ceiling.\n\n`OD_MAX_DEVLOOP_ITERATIONS` caps the outer plugin pipeline stage; it is not\nthis review's round limit. A pipeline's `critique.score` signal is a\nscheduler-facing projection, not something you should write into your answer.\n\n## How to report it\n\nWrite the outcome the way you would write any other part of your answer: plain\nprose, in the user's language, saying what you checked, what you fixed, and\nanything you deliberately left alone.\n\nDo not invent a structured review transcript, a scored panel, a cast of named\nreviewer personas, or any tag-based envelope around your answer. Do not write a\n`critique.json` file into the project. None of those are inputs to anything —\nthey only add noise to the user's chat.\n",{"od":24,"name":5,"description":7},{"mode":25,"scenario":26},"critique","general","main","f403d5b733fab92eab16d13e9baf3ac951afed55","plugins\u002F_official\u002Fatoms\u002Fcritique-theater","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app","https:\u002F\u002Fgithub.com\u002Fhiktan44","fasheone.com","Hikmet Tanrıverdi\r\nSTRATEJI DANIŞMANLIK, 2008-2018 İHKİB İSTANBUL HAZIR GİYİM BŞK, İTO MECLİS ÜYESİ, TEXMART DIŞ TİCARET YK STRATEGY CONSULTING, 2008-2018 PRESI","2026-10-11 23:59:08",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add hiktan44\u002Fopen-design-app --skill critique-theater",{"tool":41,"command":42},"bunx","bunx skills add hiktan44\u002Fopen-design-app --skill critique-theater",{"tool":44,"command":45},"pnpm","pnpm dlx skills add hiktan44\u002Fopen-design-app --skill critique-theater","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fatoms\u002Fcritique-theater\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"open-design.json","REFERENCE","参考文档",830,"https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fatoms\u002Fcritique-theater\u002Fopen-design.json",[56,63,70,77,84,93],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M77WGV99HNV3Q6JN3H8Z70JE","Beta Skill","Instruction-only fixture skill.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77WGRXNRGHT9J1K929BPV5H","Alpha Skill","First fixture skill with a runnable demo.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M77WGQK7F7R1W6RBFZFEZ53M","Deck One","A small deck template fixture.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fdesign-templates\u002Fdeck-one\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77WGNPEGTDWMKDX659FS5DT","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77WGJ9KKT6Q4P10GAV3KC48","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","MIT","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M77WGF9P0WT4XBXMM0B9WRGR","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwpds\u002FSKILL.md",[],[]]