[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-design-qa":3,"mdc--z4j5u6-key":36,"related-repo-openai-design-qa":887,"related-org-openai-design-qa":999},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"design-qa","perform design QA on prototypes","Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to audit.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"openai","OpenAI","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fopenai.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Code Review","code-review","tag",{"name":17,"slug":18,"type":15},"QA","qa",{"name":20,"slug":21,"type":15},"Testing","testing",{"name":23,"slug":24,"type":15},"Design","design",427,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Frole-specific-plugins","2026-07-01T07:54:38.209073",null,65,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"Role-specific Codex plugin templates","https:\u002F\u002Fgithub.com\u002Fopenai\u002Frole-specific-plugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fproduct-design\u002Fskills\u002Fdesign-qa","---\nname: design-qa\ndescription: \"Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to audit.\"\n---\n\n# Design QA\n\nUse this internal helper to compare a prototype's source design against the rendered implementation before handoff.\n\nDo not use this skill for broad UX critique, design critique, product audits, or flow reviews. Use [audit](..\u002Faudit\u002FSKILL.md) for those user-facing requests.\n\nUse this skill before every Product Design build handoff.\n\nA passing QA run requires both:\n\n- a source visual target: Figma node, image, screenshot, mockup, or source capture\n- a rendered implementation: local URL, deployed URL, app screen, component, or screenshot\n\nIf either artifact cannot be opened, captured, or compared, write `design-qa.md` with `final result: blocked` and name the blocker. Do not let the build skill hand off as done.\n\n## Critical Overrides\n\nFollow [critical-overrides](..\u002F..\u002Freferences\u002Fcritical-overrides.md).\n\n## Workflow\n\nCompare the intended design to the implementation as a product-quality reviewer, not as a generic aesthetic critic. The output must be a prioritized fix list grounded in evidence from both artifacts.\n\nDo not write the QA review from memory, code, or file paths alone. Open or capture both the source design and the implementation first, then compare what is actually visible.\n\nDo not pretend separate image views are side-by-side comparison. Put the source image and the implementation screenshot together in the same comparison input, then judge the visible differences from that combined input.\n\nDesign QA is an iteration loop. The first comparison may pass only when it finds no actionable P0\u002FP1\u002FP2 differences and no visual fixes are made in response.\n\nWhen a comparison finds any P0\u002FP1\u002FP2 issue:\n\n- Record the finding and keep the current result blocked.\n- Apply the fix.\n- Capture the revised implementation at the same viewport and state.\n- Compare the revised capture against the source again.\n\nA later pass must identify the earlier findings, the fixes made, and the post-fix visual evidence. Build, dependency, lint, deployment, and preview troubleshooting do not count as design-QA iterations.\n\n1. Identify the comparison target.\n   - Determine the source design: Figma node, image, design board, screenshot, spec, or mockup.\n   - Determine the implementation: local URL, deployed URL, app screen, component, screenshot, or code-rendered view.\n   - Match the same viewport, state, theme, device density, route, content, auth state, and interaction state before judging.\n   - If artifacts do not represent the same state, call that out first and avoid false precision.\n\n2. Capture evidence.\n   - For Figma, use design context and screenshot tools when available.\n   - For web\u002Fapp implementations, follow the Browser Choice rule in [index](..\u002Findex\u002FSKILL.md#browser-choice). In ChatGPT Work Mode, follow the active build skill's \"Previewing prototypes in ChatGPT Work Mode\" section before opening a local implementation. Then capture screenshots at the intended viewport.\n   - Capture additional states when relevant: mobile\u002Fdesktop, hover\u002Ffocus\u002Factive, empty\u002Floading\u002Ferror, dark\u002Flight, and key responsive breakpoints.\n   - Save paths or URLs for screenshots when available so findings can cite evidence.\n   - Capturing screenshots is not enough. Put the source image and the implementation screenshot together in the same comparison input before judging.\n\n3. Normalize before comparing.\n   - Align crop, viewport size, scale, and device frame. Do not compare a framed mockup to an unframed page without noting the mismatch.\n   - Prefer comparing content regions over full browser chrome or surrounding canvas.\n\n4. Compare at the right level of detail.\n   - Use a full-view comparison to judge overall composition, hierarchy, layout, density, and responsive structure.\n   - Use focused region comparisons when important details are too small to judge in the full-view comparison.\n   - Choose focused regions from the actual source and implementation. Use them where fidelity depends on precise typography, alignment, imagery, assets, icons, logos, controls, forms, navigation, tables, dense UI, or visible interaction states.\n   - If no focused region is needed, say why in `design-qa.md`.\n   - Do not pass QA from a full-view comparison alone when important details are not clearly readable.\n\n5. Review systematically.\n   - Read [qa-rubric](.\u002Freferences\u002Fqa-rubric.md) when the QA pass spans more than a quick visual check.\n   - Check information architecture, layout, spacing, typography\u002Ffonts, color, imagery\u002Fimage quality, icons, copy, affordances, interaction states, responsiveness, accessibility, and polish.\n   - Always make a specific pass over the five required fidelity surfaces: fonts\u002Ftypography, spacing\u002Flayout rhythm, colors\u002Ftokens, image quality, and copy\u002Fcontent. Do this even if the user did not name those areas explicitly.\n   - If the mock does not address some issue you're seeing (e.g. a null state), call that out as a separate finding as a shortcoming of the mock to be addressed.\n   - Your other goal is to decide whether the implementation \"looks as good\" as the mock. If there are stylistic problems, call them out. If the user's prompt is leaking into the implementation (vs letting the app stand on its own), call that out as well.\n   - Distinguish design drift from intentional product\u002Fcode constraints. If a deviation may be intentional, phrase it as a question or assumption.\n\n6. Produce a fix-oriented QA report.\n   - Lead with findings, ordered by severity and user impact.\n   - For each finding include: severity, location, what differs, evidence, why it matters, and the concrete fix.\n   - Include exact CSS\u002Fcomponent\u002Ftoken suggestions when the implementation context is available.\n   - Separate objective mismatches from subjective polish recommendations.\n   - Do not say a design matches, is done, or is as good as it can get until the required fidelity surfaces have been checked and any remaining differences are explicitly classified as acceptable, expected, or still actionable.\n   - End with a concise implementation checklist.\n\n## Required Fidelity Surfaces\n\nEvery QA report must explicitly evaluate these surfaces:\n\n- Fonts and typography: family, fallback, weight, size, line height, letter spacing, antialiasing, hierarchy, wrapping, truncation, and whether display text and small UI text use appropriate optical weights. It is incredibly important to check fonts carefully for fidelity, including looking up similar typefaces or using image analysis to find the font differences.\n- Spacing and layout rhythm: frame size, crop, alignment, margins, padding, grid tracks, section gaps, component spacing, radii, shadows\u002Felevation, and vertical rhythm.\n- Colors and visual tokens: sampled or inferred palette, gradients, opacity, contrast, semantic state colors, foreground\u002Fbackground balance, and whether CSS tokens map to the source design.\n- Image quality and asset fidelity: subject correctness, crop, scale, sharpness, compression, transparency halos, masking, background treatment, raster-vs-vector appropriateness, and whether generated assets match the source art direction. Fail QA if logos, illustrations, decorative marks, product imagery, non-standard icons, or other visible image assets from the visual target were replaced with custom inline SVG, handcrafted SVG, HTML elements, div\u002Fspan shapes, CSS drawings, gradients, emoji, text glyphs, placeholder shapes, or code-native approximations.\n- Copy and content of app-specific text\n\n## Severity\n\n- `P0`: Blocks core use, severe accessibility failure, broken layout, or impossible task.\n- `P1`: Major design mismatch or usability regression likely to be noticed by users.\n- `P2`: Moderate visual drift, inconsistent state, responsive issue, or fixable polish gap.\n- `P3`: Minor refinement that improves fidelity but does not block acceptance.\n\nTreat viewport overflow that hides persistent app controls, and mismatches that materially change above-the-fold content, major-region proportions, text wrapping, or interface density, as P2 or higher.\n\n## Output Format\n\nUse this structure unless the user asks otherwise:\n\n```markdown\n**Findings**\n- [P1] Short issue title\n  Location: screen\u002Fcomponent\u002Fselector\u002Ffile if known.\n  Evidence: design does X, implementation does Y.\n  Impact: why this matters.\n  Fix: concrete change.\n\n**Open Questions**\n- Any ambiguity about intentional deviations, unavailable states, or missing artifacts.\n\n**Implementation Checklist**\n- Ordered fixes that can be executed directly.\n\n**Follow-up Polish**\n- P3 refinements that can improve fidelity after handoff.\n```\n\nIf there are no substantive mismatches, say that clearly and list any residual test gaps.\n\nWhen this skill is used before handoff, save the latest QA report as project-root `design-qa.md`.\n\n`design-qa.md` must include:\n\n- source visual truth path\n- implementation screenshot path\n- viewport\n- state\n- full-view comparison evidence\n- focused region comparison evidence, or why it was not needed\n- findings\n- comparison history for every P0\u002FP1\u002FP2 iteration: earlier findings, fixes made, and post-fix visual evidence\n- final result\n\nFor ChatGPT Work Mode builds, `design-qa.md` must include the browser-rendered implementation screenshot, viewport, primary interactions tested, console errors checked, and final result. If browser-rendered evidence is missing, `final result` is `blocked`.\n\n`final result` must be exactly `passed` or `blocked`.\n\nUse `passed` when there are no actionable P0\u002FP1\u002FP2 findings. P3 findings may remain as follow-up polish.\nUse `blocked` when actionable P0\u002FP1\u002FP2 findings remain and name the blocker.\n\nReturn the file path with the QA report.\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,49,55,69,74,79,94,116,123,135,141,146,151,156,161,166,189,194,408,414,419,447,453,500,505,511,516,733,738,749,759,807,833,857,876,881],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Design QA",{"type":42,"tag":50,"props":51,"children":52},"p",{},[53],{"type":47,"value":54},"Use this internal helper to compare a prototype's source design against the rendered implementation before handoff.",{"type":42,"tag":50,"props":56,"children":57},{},[58,60,67],{"type":47,"value":59},"Do not use this skill for broad UX critique, design critique, product audits, or flow reviews. Use ",{"type":42,"tag":61,"props":62,"children":64},"a",{"href":63},"..\u002Faudit\u002FSKILL.md",[65],{"type":47,"value":66},"audit",{"type":47,"value":68}," for those user-facing requests.",{"type":42,"tag":50,"props":70,"children":71},{},[72],{"type":47,"value":73},"Use this skill before every Product Design build handoff.",{"type":42,"tag":50,"props":75,"children":76},{},[77],{"type":47,"value":78},"A passing QA run requires both:",{"type":42,"tag":80,"props":81,"children":82},"ul",{},[83,89],{"type":42,"tag":84,"props":85,"children":86},"li",{},[87],{"type":47,"value":88},"a source visual target: Figma node, image, screenshot, mockup, or source capture",{"type":42,"tag":84,"props":90,"children":91},{},[92],{"type":47,"value":93},"a rendered implementation: local URL, deployed URL, app screen, component, or screenshot",{"type":42,"tag":50,"props":95,"children":96},{},[97,99,106,108,114],{"type":47,"value":98},"If either artifact cannot be opened, captured, or compared, write ",{"type":42,"tag":100,"props":101,"children":103},"code",{"className":102},[],[104],{"type":47,"value":105},"design-qa.md",{"type":47,"value":107}," with ",{"type":42,"tag":100,"props":109,"children":111},{"className":110},[],[112],{"type":47,"value":113},"final result: blocked",{"type":47,"value":115}," and name the blocker. Do not let the build skill hand off as done.",{"type":42,"tag":117,"props":118,"children":120},"h2",{"id":119},"critical-overrides",[121],{"type":47,"value":122},"Critical Overrides",{"type":42,"tag":50,"props":124,"children":125},{},[126,128,133],{"type":47,"value":127},"Follow ",{"type":42,"tag":61,"props":129,"children":131},{"href":130},"..\u002F..\u002Freferences\u002Fcritical-overrides.md",[132],{"type":47,"value":119},{"type":47,"value":134},".",{"type":42,"tag":117,"props":136,"children":138},{"id":137},"workflow",[139],{"type":47,"value":140},"Workflow",{"type":42,"tag":50,"props":142,"children":143},{},[144],{"type":47,"value":145},"Compare the intended design to the implementation as a product-quality reviewer, not as a generic aesthetic critic. The output must be a prioritized fix list grounded in evidence from both artifacts.",{"type":42,"tag":50,"props":147,"children":148},{},[149],{"type":47,"value":150},"Do not write the QA review from memory, code, or file paths alone. Open or capture both the source design and the implementation first, then compare what is actually visible.",{"type":42,"tag":50,"props":152,"children":153},{},[154],{"type":47,"value":155},"Do not pretend separate image views are side-by-side comparison. Put the source image and the implementation screenshot together in the same comparison input, then judge the visible differences from that combined input.",{"type":42,"tag":50,"props":157,"children":158},{},[159],{"type":47,"value":160},"Design QA is an iteration loop. The first comparison may pass only when it finds no actionable P0\u002FP1\u002FP2 differences and no visual fixes are made in response.",{"type":42,"tag":50,"props":162,"children":163},{},[164],{"type":47,"value":165},"When a comparison finds any P0\u002FP1\u002FP2 issue:",{"type":42,"tag":80,"props":167,"children":168},{},[169,174,179,184],{"type":42,"tag":84,"props":170,"children":171},{},[172],{"type":47,"value":173},"Record the finding and keep the current result blocked.",{"type":42,"tag":84,"props":175,"children":176},{},[177],{"type":47,"value":178},"Apply the fix.",{"type":42,"tag":84,"props":180,"children":181},{},[182],{"type":47,"value":183},"Capture the revised implementation at the same viewport and state.",{"type":42,"tag":84,"props":185,"children":186},{},[187],{"type":47,"value":188},"Compare the revised capture against the source again.",{"type":42,"tag":50,"props":190,"children":191},{},[192],{"type":47,"value":193},"A later pass must identify the earlier findings, the fixes made, and the post-fix visual evidence. Build, dependency, lint, deployment, and preview troubleshooting do not count as design-QA iterations.",{"type":42,"tag":195,"props":196,"children":197},"ol",{},[198,226,267,285,324,370],{"type":42,"tag":84,"props":199,"children":200},{},[201,203],{"type":47,"value":202},"Identify the comparison target.",{"type":42,"tag":80,"props":204,"children":205},{},[206,211,216,221],{"type":42,"tag":84,"props":207,"children":208},{},[209],{"type":47,"value":210},"Determine the source design: Figma node, image, design board, screenshot, spec, or mockup.",{"type":42,"tag":84,"props":212,"children":213},{},[214],{"type":47,"value":215},"Determine the implementation: local URL, deployed URL, app screen, component, screenshot, or code-rendered view.",{"type":42,"tag":84,"props":217,"children":218},{},[219],{"type":47,"value":220},"Match the same viewport, state, theme, device density, route, content, auth state, and interaction state before judging.",{"type":42,"tag":84,"props":222,"children":223},{},[224],{"type":47,"value":225},"If artifacts do not represent the same state, call that out first and avoid false precision.",{"type":42,"tag":84,"props":227,"children":228},{},[229,231],{"type":47,"value":230},"Capture evidence.",{"type":42,"tag":80,"props":232,"children":233},{},[234,239,252,257,262],{"type":42,"tag":84,"props":235,"children":236},{},[237],{"type":47,"value":238},"For Figma, use design context and screenshot tools when available.",{"type":42,"tag":84,"props":240,"children":241},{},[242,244,250],{"type":47,"value":243},"For web\u002Fapp implementations, follow the Browser Choice rule in ",{"type":42,"tag":61,"props":245,"children":247},{"href":246},"..\u002Findex\u002FSKILL.md#browser-choice",[248],{"type":47,"value":249},"index",{"type":47,"value":251},". In ChatGPT Work Mode, follow the active build skill's \"Previewing prototypes in ChatGPT Work Mode\" section before opening a local implementation. Then capture screenshots at the intended viewport.",{"type":42,"tag":84,"props":253,"children":254},{},[255],{"type":47,"value":256},"Capture additional states when relevant: mobile\u002Fdesktop, hover\u002Ffocus\u002Factive, empty\u002Floading\u002Ferror, dark\u002Flight, and key responsive breakpoints.",{"type":42,"tag":84,"props":258,"children":259},{},[260],{"type":47,"value":261},"Save paths or URLs for screenshots when available so findings can cite evidence.",{"type":42,"tag":84,"props":263,"children":264},{},[265],{"type":47,"value":266},"Capturing screenshots is not enough. Put the source image and the implementation screenshot together in the same comparison input before judging.",{"type":42,"tag":84,"props":268,"children":269},{},[270,272],{"type":47,"value":271},"Normalize before comparing.",{"type":42,"tag":80,"props":273,"children":274},{},[275,280],{"type":42,"tag":84,"props":276,"children":277},{},[278],{"type":47,"value":279},"Align crop, viewport size, scale, and device frame. Do not compare a framed mockup to an unframed page without noting the mismatch.",{"type":42,"tag":84,"props":281,"children":282},{},[283],{"type":47,"value":284},"Prefer comparing content regions over full browser chrome or surrounding canvas.",{"type":42,"tag":84,"props":286,"children":287},{},[288,290],{"type":47,"value":289},"Compare at the right level of detail.",{"type":42,"tag":80,"props":291,"children":292},{},[293,298,303,308,319],{"type":42,"tag":84,"props":294,"children":295},{},[296],{"type":47,"value":297},"Use a full-view comparison to judge overall composition, hierarchy, layout, density, and responsive structure.",{"type":42,"tag":84,"props":299,"children":300},{},[301],{"type":47,"value":302},"Use focused region comparisons when important details are too small to judge in the full-view comparison.",{"type":42,"tag":84,"props":304,"children":305},{},[306],{"type":47,"value":307},"Choose focused regions from the actual source and implementation. Use them where fidelity depends on precise typography, alignment, imagery, assets, icons, logos, controls, forms, navigation, tables, dense UI, or visible interaction states.",{"type":42,"tag":84,"props":309,"children":310},{},[311,313,318],{"type":47,"value":312},"If no focused region is needed, say why in ",{"type":42,"tag":100,"props":314,"children":316},{"className":315},[],[317],{"type":47,"value":105},{"type":47,"value":134},{"type":42,"tag":84,"props":320,"children":321},{},[322],{"type":47,"value":323},"Do not pass QA from a full-view comparison alone when important details are not clearly readable.",{"type":42,"tag":84,"props":325,"children":326},{},[327,329],{"type":47,"value":328},"Review systematically.",{"type":42,"tag":80,"props":330,"children":331},{},[332,345,350,355,360,365],{"type":42,"tag":84,"props":333,"children":334},{},[335,337,343],{"type":47,"value":336},"Read ",{"type":42,"tag":61,"props":338,"children":340},{"href":339},".\u002Freferences\u002Fqa-rubric.md",[341],{"type":47,"value":342},"qa-rubric",{"type":47,"value":344}," when the QA pass spans more than a quick visual check.",{"type":42,"tag":84,"props":346,"children":347},{},[348],{"type":47,"value":349},"Check information architecture, layout, spacing, typography\u002Ffonts, color, imagery\u002Fimage quality, icons, copy, affordances, interaction states, responsiveness, accessibility, and polish.",{"type":42,"tag":84,"props":351,"children":352},{},[353],{"type":47,"value":354},"Always make a specific pass over the five required fidelity surfaces: fonts\u002Ftypography, spacing\u002Flayout rhythm, colors\u002Ftokens, image quality, and copy\u002Fcontent. Do this even if the user did not name those areas explicitly.",{"type":42,"tag":84,"props":356,"children":357},{},[358],{"type":47,"value":359},"If the mock does not address some issue you're seeing (e.g. a null state), call that out as a separate finding as a shortcoming of the mock to be addressed.",{"type":42,"tag":84,"props":361,"children":362},{},[363],{"type":47,"value":364},"Your other goal is to decide whether the implementation \"looks as good\" as the mock. If there are stylistic problems, call them out. If the user's prompt is leaking into the implementation (vs letting the app stand on its own), call that out as well.",{"type":42,"tag":84,"props":366,"children":367},{},[368],{"type":47,"value":369},"Distinguish design drift from intentional product\u002Fcode constraints. If a deviation may be intentional, phrase it as a question or assumption.",{"type":42,"tag":84,"props":371,"children":372},{},[373,375],{"type":47,"value":374},"Produce a fix-oriented QA report.",{"type":42,"tag":80,"props":376,"children":377},{},[378,383,388,393,398,403],{"type":42,"tag":84,"props":379,"children":380},{},[381],{"type":47,"value":382},"Lead with findings, ordered by severity and user impact.",{"type":42,"tag":84,"props":384,"children":385},{},[386],{"type":47,"value":387},"For each finding include: severity, location, what differs, evidence, why it matters, and the concrete fix.",{"type":42,"tag":84,"props":389,"children":390},{},[391],{"type":47,"value":392},"Include exact CSS\u002Fcomponent\u002Ftoken suggestions when the implementation context is available.",{"type":42,"tag":84,"props":394,"children":395},{},[396],{"type":47,"value":397},"Separate objective mismatches from subjective polish recommendations.",{"type":42,"tag":84,"props":399,"children":400},{},[401],{"type":47,"value":402},"Do not say a design matches, is done, or is as good as it can get until the required fidelity surfaces have been checked and any remaining differences are explicitly classified as acceptable, expected, or still actionable.",{"type":42,"tag":84,"props":404,"children":405},{},[406],{"type":47,"value":407},"End with a concise implementation checklist.",{"type":42,"tag":117,"props":409,"children":411},{"id":410},"required-fidelity-surfaces",[412],{"type":47,"value":413},"Required Fidelity Surfaces",{"type":42,"tag":50,"props":415,"children":416},{},[417],{"type":47,"value":418},"Every QA report must explicitly evaluate these surfaces:",{"type":42,"tag":80,"props":420,"children":421},{},[422,427,432,437,442],{"type":42,"tag":84,"props":423,"children":424},{},[425],{"type":47,"value":426},"Fonts and typography: family, fallback, weight, size, line height, letter spacing, antialiasing, hierarchy, wrapping, truncation, and whether display text and small UI text use appropriate optical weights. It is incredibly important to check fonts carefully for fidelity, including looking up similar typefaces or using image analysis to find the font differences.",{"type":42,"tag":84,"props":428,"children":429},{},[430],{"type":47,"value":431},"Spacing and layout rhythm: frame size, crop, alignment, margins, padding, grid tracks, section gaps, component spacing, radii, shadows\u002Felevation, and vertical rhythm.",{"type":42,"tag":84,"props":433,"children":434},{},[435],{"type":47,"value":436},"Colors and visual tokens: sampled or inferred palette, gradients, opacity, contrast, semantic state colors, foreground\u002Fbackground balance, and whether CSS tokens map to the source design.",{"type":42,"tag":84,"props":438,"children":439},{},[440],{"type":47,"value":441},"Image quality and asset fidelity: subject correctness, crop, scale, sharpness, compression, transparency halos, masking, background treatment, raster-vs-vector appropriateness, and whether generated assets match the source art direction. Fail QA if logos, illustrations, decorative marks, product imagery, non-standard icons, or other visible image assets from the visual target were replaced with custom inline SVG, handcrafted SVG, HTML elements, div\u002Fspan shapes, CSS drawings, gradients, emoji, text glyphs, placeholder shapes, or code-native approximations.",{"type":42,"tag":84,"props":443,"children":444},{},[445],{"type":47,"value":446},"Copy and content of app-specific text",{"type":42,"tag":117,"props":448,"children":450},{"id":449},"severity",[451],{"type":47,"value":452},"Severity",{"type":42,"tag":80,"props":454,"children":455},{},[456,467,478,489],{"type":42,"tag":84,"props":457,"children":458},{},[459,465],{"type":42,"tag":100,"props":460,"children":462},{"className":461},[],[463],{"type":47,"value":464},"P0",{"type":47,"value":466},": Blocks core use, severe accessibility failure, broken layout, or impossible task.",{"type":42,"tag":84,"props":468,"children":469},{},[470,476],{"type":42,"tag":100,"props":471,"children":473},{"className":472},[],[474],{"type":47,"value":475},"P1",{"type":47,"value":477},": Major design mismatch or usability regression likely to be noticed by users.",{"type":42,"tag":84,"props":479,"children":480},{},[481,487],{"type":42,"tag":100,"props":482,"children":484},{"className":483},[],[485],{"type":47,"value":486},"P2",{"type":47,"value":488},": Moderate visual drift, inconsistent state, responsive issue, or fixable polish gap.",{"type":42,"tag":84,"props":490,"children":491},{},[492,498],{"type":42,"tag":100,"props":493,"children":495},{"className":494},[],[496],{"type":47,"value":497},"P3",{"type":47,"value":499},": Minor refinement that improves fidelity but does not block acceptance.",{"type":42,"tag":50,"props":501,"children":502},{},[503],{"type":47,"value":504},"Treat viewport overflow that hides persistent app controls, and mismatches that materially change above-the-fold content, major-region proportions, text wrapping, or interface density, as P2 or higher.",{"type":42,"tag":117,"props":506,"children":508},{"id":507},"output-format",[509],{"type":47,"value":510},"Output Format",{"type":42,"tag":50,"props":512,"children":513},{},[514],{"type":47,"value":515},"Use this structure unless the user asks otherwise:",{"type":42,"tag":517,"props":518,"children":523},"pre",{"className":519,"code":520,"language":521,"meta":522,"style":522},"language-markdown shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","**Findings**\n- [P1] Short issue title\n  Location: screen\u002Fcomponent\u002Fselector\u002Ffile if known.\n  Evidence: design does X, implementation does Y.\n  Impact: why this matters.\n  Fix: concrete change.\n\n**Open Questions**\n- Any ambiguity about intentional deviations, unavailable states, or missing artifacts.\n\n**Implementation Checklist**\n- Ordered fixes that can be executed directly.\n\n**Follow-up Polish**\n- P3 refinements that can improve fidelity after handoff.\n","markdown","",[524],{"type":42,"tag":100,"props":525,"children":526},{"__ignoreMap":522},[527,550,581,590,599,608,617,627,644,657,665,682,695,703,720],{"type":42,"tag":528,"props":529,"children":532},"span",{"class":530,"line":531},"line",1,[533,539,545],{"type":42,"tag":528,"props":534,"children":536},{"style":535},"--shiki-light:#39ADB5;--shiki-light-font-weight:bold;--shiki-default:#89DDFF;--shiki-default-font-weight:bold;--shiki-dark:#89DDFF;--shiki-dark-font-weight:bold",[537],{"type":47,"value":538},"**",{"type":42,"tag":528,"props":540,"children":542},{"style":541},"--shiki-light:#E53935;--shiki-light-font-weight:bold;--shiki-default:#F07178;--shiki-default-font-weight:bold;--shiki-dark:#F07178;--shiki-dark-font-weight:bold",[543],{"type":47,"value":544},"Findings",{"type":42,"tag":528,"props":546,"children":547},{"style":535},[548],{"type":47,"value":549},"**\n",{"type":42,"tag":528,"props":551,"children":553},{"class":530,"line":552},2,[554,560,565,570,575],{"type":42,"tag":528,"props":555,"children":557},{"style":556},"--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF",[558],{"type":47,"value":559},"-",{"type":42,"tag":528,"props":561,"children":562},{"style":556},[563],{"type":47,"value":564}," [",{"type":42,"tag":528,"props":566,"children":568},{"style":567},"--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D",[569],{"type":47,"value":475},{"type":42,"tag":528,"props":571,"children":572},{"style":556},[573],{"type":47,"value":574},"]",{"type":42,"tag":528,"props":576,"children":578},{"style":577},"--shiki-light:#90A4AE;--shiki-default:#EEFFFF;--shiki-dark:#BABED8",[579],{"type":47,"value":580}," Short issue title\n",{"type":42,"tag":528,"props":582,"children":584},{"class":530,"line":583},3,[585],{"type":42,"tag":528,"props":586,"children":587},{"style":577},[588],{"type":47,"value":589},"  Location: screen\u002Fcomponent\u002Fselector\u002Ffile if known.\n",{"type":42,"tag":528,"props":591,"children":593},{"class":530,"line":592},4,[594],{"type":42,"tag":528,"props":595,"children":596},{"style":577},[597],{"type":47,"value":598},"  Evidence: design does X, implementation does Y.\n",{"type":42,"tag":528,"props":600,"children":602},{"class":530,"line":601},5,[603],{"type":42,"tag":528,"props":604,"children":605},{"style":577},[606],{"type":47,"value":607},"  Impact: why this matters.\n",{"type":42,"tag":528,"props":609,"children":611},{"class":530,"line":610},6,[612],{"type":42,"tag":528,"props":613,"children":614},{"style":577},[615],{"type":47,"value":616},"  Fix: concrete change.\n",{"type":42,"tag":528,"props":618,"children":620},{"class":530,"line":619},7,[621],{"type":42,"tag":528,"props":622,"children":624},{"emptyLinePlaceholder":623},true,[625],{"type":47,"value":626},"\n",{"type":42,"tag":528,"props":628,"children":630},{"class":530,"line":629},8,[631,635,640],{"type":42,"tag":528,"props":632,"children":633},{"style":535},[634],{"type":47,"value":538},{"type":42,"tag":528,"props":636,"children":637},{"style":541},[638],{"type":47,"value":639},"Open Questions",{"type":42,"tag":528,"props":641,"children":642},{"style":535},[643],{"type":47,"value":549},{"type":42,"tag":528,"props":645,"children":647},{"class":530,"line":646},9,[648,652],{"type":42,"tag":528,"props":649,"children":650},{"style":556},[651],{"type":47,"value":559},{"type":42,"tag":528,"props":653,"children":654},{"style":577},[655],{"type":47,"value":656}," Any ambiguity about intentional deviations, unavailable states, or missing artifacts.\n",{"type":42,"tag":528,"props":658,"children":660},{"class":530,"line":659},10,[661],{"type":42,"tag":528,"props":662,"children":663},{"emptyLinePlaceholder":623},[664],{"type":47,"value":626},{"type":42,"tag":528,"props":666,"children":668},{"class":530,"line":667},11,[669,673,678],{"type":42,"tag":528,"props":670,"children":671},{"style":535},[672],{"type":47,"value":538},{"type":42,"tag":528,"props":674,"children":675},{"style":541},[676],{"type":47,"value":677},"Implementation Checklist",{"type":42,"tag":528,"props":679,"children":680},{"style":535},[681],{"type":47,"value":549},{"type":42,"tag":528,"props":683,"children":685},{"class":530,"line":684},12,[686,690],{"type":42,"tag":528,"props":687,"children":688},{"style":556},[689],{"type":47,"value":559},{"type":42,"tag":528,"props":691,"children":692},{"style":577},[693],{"type":47,"value":694}," Ordered fixes that can be executed directly.\n",{"type":42,"tag":528,"props":696,"children":698},{"class":530,"line":697},13,[699],{"type":42,"tag":528,"props":700,"children":701},{"emptyLinePlaceholder":623},[702],{"type":47,"value":626},{"type":42,"tag":528,"props":704,"children":706},{"class":530,"line":705},14,[707,711,716],{"type":42,"tag":528,"props":708,"children":709},{"style":535},[710],{"type":47,"value":538},{"type":42,"tag":528,"props":712,"children":713},{"style":541},[714],{"type":47,"value":715},"Follow-up Polish",{"type":42,"tag":528,"props":717,"children":718},{"style":535},[719],{"type":47,"value":549},{"type":42,"tag":528,"props":721,"children":723},{"class":530,"line":722},15,[724,728],{"type":42,"tag":528,"props":725,"children":726},{"style":556},[727],{"type":47,"value":559},{"type":42,"tag":528,"props":729,"children":730},{"style":577},[731],{"type":47,"value":732}," P3 refinements that can improve fidelity after handoff.\n",{"type":42,"tag":50,"props":734,"children":735},{},[736],{"type":47,"value":737},"If there are no substantive mismatches, say that clearly and list any residual test gaps.",{"type":42,"tag":50,"props":739,"children":740},{},[741,743,748],{"type":47,"value":742},"When this skill is used before handoff, save the latest QA report as project-root ",{"type":42,"tag":100,"props":744,"children":746},{"className":745},[],[747],{"type":47,"value":105},{"type":47,"value":134},{"type":42,"tag":50,"props":750,"children":751},{},[752,757],{"type":42,"tag":100,"props":753,"children":755},{"className":754},[],[756],{"type":47,"value":105},{"type":47,"value":758}," must include:",{"type":42,"tag":80,"props":760,"children":761},{},[762,767,772,777,782,787,792,797,802],{"type":42,"tag":84,"props":763,"children":764},{},[765],{"type":47,"value":766},"source visual truth path",{"type":42,"tag":84,"props":768,"children":769},{},[770],{"type":47,"value":771},"implementation screenshot path",{"type":42,"tag":84,"props":773,"children":774},{},[775],{"type":47,"value":776},"viewport",{"type":42,"tag":84,"props":778,"children":779},{},[780],{"type":47,"value":781},"state",{"type":42,"tag":84,"props":783,"children":784},{},[785],{"type":47,"value":786},"full-view comparison evidence",{"type":42,"tag":84,"props":788,"children":789},{},[790],{"type":47,"value":791},"focused region comparison evidence, or why it was not needed",{"type":42,"tag":84,"props":793,"children":794},{},[795],{"type":47,"value":796},"findings",{"type":42,"tag":84,"props":798,"children":799},{},[800],{"type":47,"value":801},"comparison history for every P0\u002FP1\u002FP2 iteration: earlier findings, fixes made, and post-fix visual evidence",{"type":42,"tag":84,"props":803,"children":804},{},[805],{"type":47,"value":806},"final result",{"type":42,"tag":50,"props":808,"children":809},{},[810,812,817,819,824,826,832],{"type":47,"value":811},"For ChatGPT Work Mode builds, ",{"type":42,"tag":100,"props":813,"children":815},{"className":814},[],[816],{"type":47,"value":105},{"type":47,"value":818}," must include the browser-rendered implementation screenshot, viewport, primary interactions tested, console errors checked, and final result. If browser-rendered evidence is missing, ",{"type":42,"tag":100,"props":820,"children":822},{"className":821},[],[823],{"type":47,"value":806},{"type":47,"value":825}," is ",{"type":42,"tag":100,"props":827,"children":829},{"className":828},[],[830],{"type":47,"value":831},"blocked",{"type":47,"value":134},{"type":42,"tag":50,"props":834,"children":835},{},[836,841,843,849,851,856],{"type":42,"tag":100,"props":837,"children":839},{"className":838},[],[840],{"type":47,"value":806},{"type":47,"value":842}," must be exactly ",{"type":42,"tag":100,"props":844,"children":846},{"className":845},[],[847],{"type":47,"value":848},"passed",{"type":47,"value":850}," or ",{"type":42,"tag":100,"props":852,"children":854},{"className":853},[],[855],{"type":47,"value":831},{"type":47,"value":134},{"type":42,"tag":50,"props":858,"children":859},{},[860,862,867,869,874],{"type":47,"value":861},"Use ",{"type":42,"tag":100,"props":863,"children":865},{"className":864},[],[866],{"type":47,"value":848},{"type":47,"value":868}," when there are no actionable P0\u002FP1\u002FP2 findings. P3 findings may remain as follow-up polish.\nUse ",{"type":42,"tag":100,"props":870,"children":872},{"className":871},[],[873],{"type":47,"value":831},{"type":47,"value":875}," when actionable P0\u002FP1\u002FP2 findings remain and name the blocker.",{"type":42,"tag":50,"props":877,"children":878},{},[879],{"type":47,"value":880},"Return the file path with the QA report.",{"type":42,"tag":882,"props":883,"children":884},"style",{},[885],{"type":47,"value":886},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"items":888,"total":998},[889,908,923,936,952,966,983],{"slug":890,"name":890,"fn":891,"description":892,"org":893,"tags":894,"stars":25,"repoUrl":26,"updatedAt":907},"analyze-account-signals","analyze account signals for sales intelligence","Use when the user wants to know what changed with one account, monitor an owner portfolio or watchlist, or rank accounts needing attention from recent evidence. Produce an evidence-backed account brief or bounded watchlist summary with recommended actions.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[895,898,901,904],{"name":896,"slug":897,"type":15},"Analytics","analytics",{"name":899,"slug":900,"type":15},"CRM","crm",{"name":902,"slug":903,"type":15},"Research","research",{"name":905,"slug":906,"type":15},"Sales","sales","2026-07-01T07:54:11.79288",{"slug":909,"name":909,"fn":910,"description":911,"org":912,"tags":913,"stars":25,"repoUrl":26,"updatedAt":922},"analyze-data-quality","assess data quality for analysis","Assess whether structured data, query results, dashboards, or analytical evidence are trustworthy enough to use. Use when the task is to check data quality, reconcile conflicting sources or metric definitions, or decide whether evidence is safe to cite.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[914,916,919],{"name":915,"slug":66,"type":15},"Audit",{"name":917,"slug":918,"type":15},"Data Engineering","data-engineering",{"name":920,"slug":921,"type":15},"Data Quality","data-quality","2026-07-01T07:55:01.146961",{"slug":924,"name":924,"fn":925,"description":926,"org":927,"tags":928,"stars":25,"repoUrl":26,"updatedAt":935},"answers-ask-user-input","request missing context from users","Use when a small amount of missing context would materially improve the answer and tappable options plus a free-text answer can gather it efficiently.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[929,932],{"name":930,"slug":931,"type":15},"Communications","communications",{"name":933,"slug":934,"type":15},"Productivity","productivity","2026-07-14T05:43:36.096323",{"slug":937,"name":937,"fn":938,"description":939,"org":940,"tags":941,"stars":25,"repoUrl":26,"updatedAt":951},"apollo","prospect and enrich leads with Apollo","Use only when a focused Sales workflow has selected a present and connected Apollo connector, or the user explicitly asks for Apollo prospecting, enrichment, Company Details, records, sequences, or outbound planning. Apply Apollo v2-specific behavior only after verifying app version 2.0.0 or later.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[942,944,947,950],{"name":943,"slug":937,"type":15},"Apollo",{"name":945,"slug":946,"type":15},"Lead Enrichment","lead-enrichment",{"name":948,"slug":949,"type":15},"Prospecting","prospecting",{"name":905,"slug":906,"type":15},"2026-07-14T05:43:34.800076",{"slug":66,"name":66,"fn":953,"description":954,"org":955,"tags":956,"stars":25,"repoUrl":26,"updatedAt":965},"audit product flows and user journeys","Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[957,958,959,962],{"name":915,"slug":66,"type":15},{"name":23,"slug":24,"type":15},{"name":960,"slug":961,"type":15},"Product Management","product-management",{"name":963,"slug":964,"type":15},"UX Design","ux-design","2026-07-01T07:54:30.613428",{"slug":967,"name":967,"fn":968,"description":969,"org":970,"tags":971,"stars":25,"repoUrl":26,"updatedAt":982},"build-business-case","build customer-led business cases and ROI","Review commercial proposals and build customer-led business cases, ROI or value models, pricing or investment rationales, executive summaries, and customer-ready value stories tied to a customer, workflow, initiative, or decision.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[972,975,978,981],{"name":973,"slug":974,"type":15},"Content Creation","content-creation",{"name":976,"slug":977,"type":15},"Finance","finance",{"name":979,"slug":980,"type":15},"Financial Modeling","financial-modeling",{"name":905,"slug":906,"type":15},"2026-07-01T07:54:02.779003",{"slug":984,"name":984,"fn":985,"description":986,"org":987,"tags":988,"stars":25,"repoUrl":26,"updatedAt":997},"build-competitive-brief","build competitive briefs and battlecards","Use when the user wants a competitor or vendor comparison, market-landscape analysis, battlecard, objection package, positioning brief, or account-specific competitive view. Produce an evidence-backed comparison, guidance, and brief, using supplied materials, connected research, and public evidence when appropriate.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[989,992,995,996],{"name":990,"slug":991,"type":15},"Competitive Intelligence","competitive-intelligence",{"name":993,"slug":994,"type":15},"Marketing","marketing",{"name":902,"slug":903,"type":15},{"name":905,"slug":906,"type":15},"2026-07-01T07:54:13.073252",43,{"items":1000,"total":1201},[1001,1022,1045,1062,1078,1097,1114,1128,1144,1158,1170,1185],{"slug":1002,"name":1002,"fn":1003,"description":1004,"org":1005,"tags":1006,"stars":1019,"repoUrl":1020,"updatedAt":1021},"prior-auth-packet-builder","build healthcare prior authorization packets","Build a concise prior authorization packet from local case files and payer policy docs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1007,1010,1013,1016],{"name":1008,"slug":1009,"type":15},"Documents","documents",{"name":1011,"slug":1012,"type":15},"Healthcare","healthcare",{"name":1014,"slug":1015,"type":15},"Insurance","insurance",{"name":1017,"slug":1018,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":1023,"name":1023,"fn":1024,"description":1025,"org":1026,"tags":1027,"stars":1042,"repoUrl":1043,"updatedAt":1044},"aspnet-core","build ASP.NET Core web applications","Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1028,1031,1033,1036,1039],{"name":1029,"slug":1030,"type":15},".NET","dotnet",{"name":1032,"slug":1023,"type":15},"ASP.NET Core",{"name":1034,"slug":1035,"type":15},"Blazor","blazor",{"name":1037,"slug":1038,"type":15},"C#","csharp",{"name":1040,"slug":1041,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":1046,"name":1046,"fn":1047,"description":1048,"org":1049,"tags":1050,"stars":1042,"repoUrl":1043,"updatedAt":1061},"chatgpt-apps","build ChatGPT Apps SDK applications","Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1051,1054,1057,1060],{"name":1052,"slug":1053,"type":15},"Apps SDK","apps-sdk",{"name":1055,"slug":1056,"type":15},"ChatGPT","chatgpt",{"name":1058,"slug":1059,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":1063,"name":1063,"fn":1064,"description":1065,"org":1066,"tags":1067,"stars":1042,"repoUrl":1043,"updatedAt":1077},"cli-creator","build CLIs from API docs","Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1068,1071,1074],{"name":1069,"slug":1070,"type":15},"API Development","api-development",{"name":1072,"slug":1073,"type":15},"CLI","cli",{"name":1075,"slug":1076,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":1079,"name":1079,"fn":1080,"description":1081,"org":1082,"tags":1083,"stars":1042,"repoUrl":1043,"updatedAt":1096},"cloudflare-deploy","deploy projects to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1084,1087,1090,1093],{"name":1085,"slug":1086,"type":15},"Cloudflare","cloudflare",{"name":1088,"slug":1089,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":1091,"slug":1092,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":1094,"slug":1095,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":1098,"name":1098,"fn":1099,"description":1100,"org":1101,"tags":1102,"stars":1042,"repoUrl":1043,"updatedAt":1113},"define-goal","define and set measurable project goals","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1103,1104,1107,1110],{"name":933,"slug":934,"type":15},{"name":1105,"slug":1106,"type":15},"Project Management","project-management",{"name":1108,"slug":1109,"type":15},"Strategy","strategy",{"name":1111,"slug":1112,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":1115,"name":1115,"fn":1116,"description":1117,"org":1118,"tags":1119,"stars":1042,"repoUrl":1043,"updatedAt":1127},"figma","translate Figma designs into code","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1120,1121,1123,1126],{"name":23,"slug":24,"type":15},{"name":1122,"slug":1115,"type":15},"Figma",{"name":1124,"slug":1125,"type":15},"Frontend","frontend",{"name":1058,"slug":1059,"type":15},"2026-04-12T05:06:47.939943",{"slug":1129,"name":1129,"fn":1130,"description":1131,"org":1132,"tags":1133,"stars":1042,"repoUrl":1043,"updatedAt":1143},"figma-code-connect-components","connect Figma designs to code components","Connects Figma design components to code components using Code Connect mapping tools. Use when user says \"code connect\", \"connect this component to code\", \"map this component\", \"link component to code\", \"create code connect mapping\", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1134,1135,1138,1139,1140],{"name":23,"slug":24,"type":15},{"name":1136,"slug":1137,"type":15},"Design System","design-system",{"name":1122,"slug":1115,"type":15},{"name":1124,"slug":1125,"type":15},{"name":1141,"slug":1142,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":1145,"name":1145,"fn":1146,"description":1147,"org":1148,"tags":1149,"stars":1042,"repoUrl":1043,"updatedAt":1157},"figma-create-design-system-rules","generate design system rules from Figma","Generates custom design system rules for the user's codebase. Use when user says \"create design system rules\", \"generate rules for my project\", \"set up design rules\", \"customize design system guidelines\", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1150,1151,1152,1155,1156],{"name":23,"slug":24,"type":15},{"name":1136,"slug":1137,"type":15},{"name":1153,"slug":1154,"type":15},"Documentation","documentation",{"name":1122,"slug":1115,"type":15},{"name":1124,"slug":1125,"type":15},"2026-05-16T06:07:47.821474",{"slug":1159,"name":1159,"fn":1160,"description":1161,"org":1162,"tags":1163,"stars":1042,"repoUrl":1043,"updatedAt":1169},"figma-implement-design","translate Figma designs into application code","Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions \"implement design\", \"generate code\", \"implement component\", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1164,1165,1166,1167,1168],{"name":23,"slug":24,"type":15},{"name":1122,"slug":1115,"type":15},{"name":1124,"slug":1125,"type":15},{"name":1141,"slug":1142,"type":15},{"name":1040,"slug":1041,"type":15},"2026-05-16T06:07:40.583615",{"slug":1171,"name":1171,"fn":1172,"description":1173,"org":1174,"tags":1175,"stars":1042,"repoUrl":1043,"updatedAt":1184},"hatch-pet","create animated pets for Codex","Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1176,1179,1180,1183],{"name":1177,"slug":1178,"type":15},"Animation","animation",{"name":1075,"slug":1076,"type":15},{"name":1181,"slug":1182,"type":15},"Creative","creative",{"name":23,"slug":24,"type":15},"2026-05-02T05:31:48.48485",{"slug":1186,"name":1186,"fn":1187,"description":1188,"org":1189,"tags":1190,"stars":1042,"repoUrl":1043,"updatedAt":1200},"imagegen","generate and edit raster images","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1191,1192,1193,1196,1199],{"name":1181,"slug":1182,"type":15},{"name":23,"slug":24,"type":15},{"name":1194,"slug":1195,"type":15},"Image Generation","image-generation",{"name":1197,"slug":1198,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]