[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78SSFS2YJ7CAJTS6PXA8YYY":3,"skill-same:01M78SSFS2YJ7CAJTS6PXA8YYY":52},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78SSFS2YJ7CAJTS6PXA8YYY","better-interface",null,"User-invoked, cross-discipline interface review that coordinates better-accessibility, better-layout, better-writing, better-typography, better-colors, and better-ui. Use when explicitly invoked for a holistic review of a screen, flow, feature, or product interface. Supports quick and full review modes. Triggers on better-interface, full interface review, holistic UI audit, cross-discipline design review, review the whole interface.","fjooord\u002Fgamecube-decomp-harness","fjooord","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44952366?v=4","01M75A80KS3BN58VMNBG7AXAM1","Ford Lascari","01M75A80MCVXVSXGREY7Y9Z8H5",7,"MIT","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-interface\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: better-interface\ndescription: >-\n  User-invoked, cross-discipline interface review that coordinates better-accessibility, better-layout, better-writing, better-typography, better-colors, and better-ui. Use when explicitly invoked for a holistic review of a screen, flow, feature, or product interface. Supports quick and full review modes. Triggers on better-interface, full interface review, holistic UI audit, cross-discipline design review, review the whole interface.\n---\n\n# Review the interface as one system\n\nA strong interface is not six independent audits stapled together. Review the whole experience, let each `better-*` skill own its domain rules, then consolidate the evidence into one prioritized verdict.\n\nThis skill owns orchestration only. Accessibility rules belong to `better-accessibility`; structure to `better-layout`; copy to `better-writing`; type to `better-typography`; color to `better-colors`; visual polish and motion to `better-ui`. Never duplicate or override their rules here.\n\n## Core Principles\n\n### 1. Resolve Scope and Mode First\n\nInfer the screen, flow, feature, or repository scope from the request and current workspace. State the resolved scope in the output. Use `full` when no mode is supplied.\n\n| Mode | Coverage | Finding cap |\n| --- | --- | --- |\n| `quick` | Primary user path and highest-traffic states; report only `HIGH` and `MEDIUM` issues | 5 |\n| `full` | Entire requested scope across all six domain skills, including empty, loading, error, and narrow-width states when present | 15 |\n\nIf the requested scope is too large to inspect credibly, narrow it to the highest-traffic complete flow and state the boundary. Never imply uninspected surfaces were reviewed.\n\n### 2. Recon Before Judgment\n\nIdentify the framework, styling system, component library, design tokens, supported viewports, and available preview or test commands. Follow the project's established Tailwind, plain CSS, CSS-in-JS, token, and component conventions.\n\n### 3. Use Domain Skills as the Sources of Truth\n\nBefore reviewing, confirm that all six owning skills below are available. Load and apply every available owner. In `quick` mode, inspect all six domains but spend depth only where the primary flow has evidence. In `full` mode, complete each available domain review before consolidation.\n\nReview in this order so foundational failures are not hidden by polish:\n\n1. `better-accessibility`\n2. `better-layout`\n3. `better-writing`\n4. `better-typography`\n5. `better-colors`\n6. `better-ui`\n\nThis skill owns the final response. When a domain skill is loaded through `better-interface`, apply its principles and references but ignore its standalone **Review Output Format**. Use the consolidated format, shared severity, and finding cap in this file instead.\n\nIf an owning skill is unavailable, mark that domain `Not reviewed`, name the missing skill, and continue with the remaining domains. Do not recreate its rules from memory, substitute a neighboring skill, or claim holistic coverage.\n\nWhen two skills appear to cover the same issue, assign it to the skill that owns the underlying rule and mention secondary effects in the **Why** cell. Report it once.\n\n### 4. Require Evidence\n\nEvery finding cites `path\u002Fto\u002Ffile:line` and shows the current implementation. If the review artifact has no source files, cite the exact screen and component. Do not report a code-level finding from visual appearance alone or a visual finding from source code alone when runtime behavior determines the result.\n\n### 5. Rank by User Impact\n\nUse one shared severity scale:\n\n- `HIGH`: blocks a task, misleads the user, hides content or controls, causes data-loss risk, or creates a repeated systemic failure.\n- `MEDIUM`: meaningfully harms comprehension, efficiency, adaptability, or consistency.\n- `LOW`: isolated polish with limited task impact. Include only in `full` mode.\n\nWithin a severity, rank by reach and leverage. A token or shared-component fix outranks the same symptom in one leaf component.\n\n### 6. Consolidate Systemic Findings\n\nOne root cause is one finding. List every confirmed location in the same row rather than producing a row per occurrence. Do not pad the report to reach the finding cap; a short review or no findings is a valid result.\n\n### 7. Make Restraint Visible\n\nRecord candidates considered but deliberately rejected. A candidate is rejected when the owning skill permits the current implementation, evidence is insufficient, the project convention is intentional, or the proposed change would add complexity without user benefit.\n\n### 8. Verify What Can Be Verified\n\nRun safe, relevant checks available in the project. Inspect the rendered interface when runtime behavior or visual judgment matters. Report the exact command or interaction and observed result. If a check cannot be run, label it **Not verified** and state what remains; never convert a verification gap into a finding.\n\n### 9. Review Without Mutating by Default\n\nTreat a review request as read-only. Do not edit source code unless the user also asks to implement the findings. When implementation is requested, preserve the consolidated report as the change scope and re-run the relevant verification afterward.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Six disconnected domain reports | Consolidate into one ranked findings table |\n| Same issue reported by multiple skills | Assign it to the skill that owns the underlying rule |\n| Finding with no exact location | Cite `path\u002Fto\u002Ffile:line` and the current implementation |\n| Visual claim inferred only from source | Inspect the rendered state or mark it not verified |\n| Unlimited low-impact polish | Respect the mode cap; omit `LOW` findings in `quick` |\n| Silent gaps in coverage | Show which domains and states were actually inspected |\n| Missing owning skill silently treated as covered | Mark the domain `Not reviewed` and name the unavailable skill |\n| No rejected candidates | Include the required considered-but-rejected table |\n| Review silently edits code | Stay read-only unless implementation was requested |\n| “Approve” with pending actionable findings | Use `Needs changes` or `Block` |\n\n## Review Output Format\n\nAlways use the following sections.\n\n### Scope and Coverage\n\nState the mode, exact scope, stack and styling conventions, and any review boundary. Then show coverage:\n\n| Domain | Evidence inspected | Result |\n| --- | --- | --- |\n| Accessibility | Files, components, states, or checks | Findings count or `Clear` |\n\nInclude all six domains. `Clear` means inspected with no actionable finding; `Not reviewed` must explain why.\n\n### Findings\n\nUse one table ordered by severity, then reach and leverage:\n\n| # | Severity | Domain | Location | Before | After | Why |\n| --- | --- | --- | --- | --- | --- | --- |\n| 1 | HIGH | Accessibility | `src\u002FDialog.tsx:42` | `\u003Cbutton>\u003CXIcon \u002F>\u003C\u002Fbutton>` | Add `aria-label=\"Close\"` and hide the icon from the accessibility tree | The icon-only control has no accessible name |\n\nEach row is one root cause. The **Domain** value is the owning skill without the `better-` prefix. Respect the mode's finding cap. If there are no findings, omit the table and state \"No actionable interface findings.\"\n\n### Considered but Rejected\n\nInclude 1–3 candidates in `quick` mode and 2–5 in `full` mode:\n\n| Location | Candidate | Rejected because |\n| --- | --- | --- |\n| `src\u002FCard.tsx:28` | Increase the shadow | Existing depth matches the shared surface token; changing one card would reduce consistency |\n\nThese are real candidates inspected during the review, not invented filler. If the scope genuinely contains fewer borderline candidates, include the ones that exist and say so.\n\n### Verification\n\nList each check or interaction, the exact command or steps, and the observed result. Separate checks that passed from checks marked **Not verified**.\n\n### Verdict\n\nEnd with exactly one:\n\n- `Block` — one or more `HIGH` findings remain.\n- `Needs changes` — only `MEDIUM` or `LOW` findings remain.\n- `Approve` — no actionable findings remain and the claimed coverage was verified.\n","# Review the interface as one system\n\nA strong interface is not six independent audits stapled together. Review the whole experience, let each `better-*` skill own its domain rules, then consolidate the evidence into one prioritized verdict.\n\nThis skill owns orchestration only. Accessibility rules belong to `better-accessibility`; structure to `better-layout`; copy to `better-writing`; type to `better-typography`; color to `better-colors`; visual polish and motion to `better-ui`. Never duplicate or override their rules here.\n\n## Core Principles\n\n### 1. Resolve Scope and Mode First\n\nInfer the screen, flow, feature, or repository scope from the request and current workspace. State the resolved scope in the output. Use `full` when no mode is supplied.\n\n| Mode | Coverage | Finding cap |\n| --- | --- | --- |\n| `quick` | Primary user path and highest-traffic states; report only `HIGH` and `MEDIUM` issues | 5 |\n| `full` | Entire requested scope across all six domain skills, including empty, loading, error, and narrow-width states when present | 15 |\n\nIf the requested scope is too large to inspect credibly, narrow it to the highest-traffic complete flow and state the boundary. Never imply uninspected surfaces were reviewed.\n\n### 2. Recon Before Judgment\n\nIdentify the framework, styling system, component library, design tokens, supported viewports, and available preview or test commands. Follow the project's established Tailwind, plain CSS, CSS-in-JS, token, and component conventions.\n\n### 3. Use Domain Skills as the Sources of Truth\n\nBefore reviewing, confirm that all six owning skills below are available. Load and apply every available owner. In `quick` mode, inspect all six domains but spend depth only where the primary flow has evidence. In `full` mode, complete each available domain review before consolidation.\n\nReview in this order so foundational failures are not hidden by polish:\n\n1. `better-accessibility`\n2. `better-layout`\n3. `better-writing`\n4. `better-typography`\n5. `better-colors`\n6. `better-ui`\n\nThis skill owns the final response. When a domain skill is loaded through `better-interface`, apply its principles and references but ignore its standalone **Review Output Format**. Use the consolidated format, shared severity, and finding cap in this file instead.\n\nIf an owning skill is unavailable, mark that domain `Not reviewed`, name the missing skill, and continue with the remaining domains. Do not recreate its rules from memory, substitute a neighboring skill, or claim holistic coverage.\n\nWhen two skills appear to cover the same issue, assign it to the skill that owns the underlying rule and mention secondary effects in the **Why** cell. Report it once.\n\n### 4. Require Evidence\n\nEvery finding cites `path\u002Fto\u002Ffile:line` and shows the current implementation. If the review artifact has no source files, cite the exact screen and component. Do not report a code-level finding from visual appearance alone or a visual finding from source code alone when runtime behavior determines the result.\n\n### 5. Rank by User Impact\n\nUse one shared severity scale:\n\n- `HIGH`: blocks a task, misleads the user, hides content or controls, causes data-loss risk, or creates a repeated systemic failure.\n- `MEDIUM`: meaningfully harms comprehension, efficiency, adaptability, or consistency.\n- `LOW`: isolated polish with limited task impact. Include only in `full` mode.\n\nWithin a severity, rank by reach and leverage. A token or shared-component fix outranks the same symptom in one leaf component.\n\n### 6. Consolidate Systemic Findings\n\nOne root cause is one finding. List every confirmed location in the same row rather than producing a row per occurrence. Do not pad the report to reach the finding cap; a short review or no findings is a valid result.\n\n### 7. Make Restraint Visible\n\nRecord candidates considered but deliberately rejected. A candidate is rejected when the owning skill permits the current implementation, evidence is insufficient, the project convention is intentional, or the proposed change would add complexity without user benefit.\n\n### 8. Verify What Can Be Verified\n\nRun safe, relevant checks available in the project. Inspect the rendered interface when runtime behavior or visual judgment matters. Report the exact command or interaction and observed result. If a check cannot be run, label it **Not verified** and state what remains; never convert a verification gap into a finding.\n\n### 9. Review Without Mutating by Default\n\nTreat a review request as read-only. Do not edit source code unless the user also asks to implement the findings. When implementation is requested, preserve the consolidated report as the change scope and re-run the relevant verification afterward.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Six disconnected domain reports | Consolidate into one ranked findings table |\n| Same issue reported by multiple skills | Assign it to the skill that owns the underlying rule |\n| Finding with no exact location | Cite `path\u002Fto\u002Ffile:line` and the current implementation |\n| Visual claim inferred only from source | Inspect the rendered state or mark it not verified |\n| Unlimited low-impact polish | Respect the mode cap; omit `LOW` findings in `quick` |\n| Silent gaps in coverage | Show which domains and states were actually inspected |\n| Missing owning skill silently treated as covered | Mark the domain `Not reviewed` and name the unavailable skill |\n| No rejected candidates | Include the required considered-but-rejected table |\n| Review silently edits code | Stay read-only unless implementation was requested |\n| “Approve” with pending actionable findings | Use `Needs changes` or `Block` |\n\n## Review Output Format\n\nAlways use the following sections.\n\n### Scope and Coverage\n\nState the mode, exact scope, stack and styling conventions, and any review boundary. Then show coverage:\n\n| Domain | Evidence inspected | Result |\n| --- | --- | --- |\n| Accessibility | Files, components, states, or checks | Findings count or `Clear` |\n\nInclude all six domains. `Clear` means inspected with no actionable finding; `Not reviewed` must explain why.\n\n### Findings\n\nUse one table ordered by severity, then reach and leverage:\n\n| # | Severity | Domain | Location | Before | After | Why |\n| --- | --- | --- | --- | --- | --- | --- |\n| 1 | HIGH | Accessibility | `src\u002FDialog.tsx:42` | `\u003Cbutton>\u003CXIcon \u002F>\u003C\u002Fbutton>` | Add `aria-label=\"Close\"` and hide the icon from the accessibility tree | The icon-only control has no accessible name |\n\nEach row is one root cause. The **Domain** value is the owning skill without the `better-` prefix. Respect the mode's finding cap. If there are no findings, omit the table and state \"No actionable interface findings.\"\n\n### Considered but Rejected\n\nInclude 1–3 candidates in `quick` mode and 2–5 in `full` mode:\n\n| Location | Candidate | Rejected because |\n| --- | --- | --- |\n| `src\u002FCard.tsx:28` | Increase the shadow | Existing depth matches the shared surface token; changing one card would reduce consistency |\n\nThese are real candidates inspected during the review, not invented filler. If the scope genuinely contains fewer borderline candidates, include the ones that exist and say so.\n\n### Verification\n\nList each check or interaction, the exact command or steps, and the observed result. Separate checks that passed from checks marked **Not verified**.\n\n### Verdict\n\nEnd with exactly one:\n\n- `Block` — one or more `HIGH` findings remain.\n- `Needs changes` — only `MEDIUM` or `LOW` findings remain.\n- `Approve` — no actionable findings remain and the claimed coverage was verified.\n",{"name":5,"description":7},"main","e7e6fb660782e780949acacded7546400b54f2ae","ref\u002Fjakubkrehel skills main skills\u002Fbetter-interface",3,"https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness","https:\u002F\u002Fgithub.com\u002Ffjooord","https:\u002F\u002Flascari.ai\u002F","2026-11-06 04:39:50",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add fjooord\u002Fgamecube-decomp-harness --skill better-interface",{"tool":38,"command":39},"bunx","bunx skills add fjooord\u002Fgamecube-decomp-harness --skill better-interface",{"tool":41,"command":42},"pnpm","pnpm dlx skills add fjooord\u002Fgamecube-decomp-harness --skill better-interface","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-interface\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",146,"https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-interface\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M78ST6YK3EBH0GKFER68ZV8V","better-writing","UX writing and interface copy, from voice and button labels to error messages and empty states. Use when writing or reviewing any user-facing text: button and link labels, form errors, placeholders, settings labels, onboarding flows, notifications, or empty states. Triggers on UX writing, microcopy, interface copy, product copy, copywriting, button labels, link text, error messages, empty states, placeholder text, settings labels, capitalization, title case, sentence case, voice and tone.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-writing\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M78ST15FSPN2WB4T98BP4HXE","better-ui","Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, micro-interactions, enter\u002Fexit animations, choosing or reviewing icons, or any visual detail work. Triggers on UI polish, design details, \"make it feel better\", \"feels off\", stagger animations, border radius, optical alignment, image outlines, box shadows, icons, icon stroke weight, icon states, motion restraint.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-ui\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M78SSSVHD4MB3GWJFPHAR6NX","better-typography","Web typography from choosing fonts to spacing, wrapping and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, checking heading hierarchy, styling text in components, truncating text, styling underlines, selection, placeholders or carets, or reviewing frontend code for typography. Triggers on typography, fonts, font formats, woff2, variable fonts, font-weight, opentype, font-feature-settings, letter-spacing, line-height, type scale, heading hierarchy, heading levels, tabular numbers, text-wrap, truncation, line clamp, underlines, text-decoration, text selection, iOS input zoom, font smoothing, text contrast, measure, line length, text-box, smart punctuation, drop cap.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-typography\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78SSM8Z4ESHX0YA5GQSKREK","better-layout","Layout structure for web interfaces, from grouping and alignment to reading order, progressive disclosure, and adaptive breakpoints. Use when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, handling RTL layout direction, or reviewing frontend code for layout. Triggers on layout, spacing, alignment, grouping, negative space, whitespace, visual hierarchy, reading order, progressive disclosure, breakpoints, responsive layout, container queries, safe area, full-bleed, edge-to-edge, layout margins, RTL layout, logical properties.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-layout\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"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":19},"01M78SSB3HCMJVWVZYQ7QN5VPX","better-colors","OKLCH color space and color usage for web projects. Convert hex\u002Frgb\u002Fhsl to oklch, generate palettes, check contrast, handle gamut boundaries, theme with Tailwind v4, and apply color with meaning. Triggers on oklch, color conversion, palette generation, contrast ratio, gamut, display p3, design tokens, semantic color tokens, hue drift, chroma, dark mode colors, accent color, color meaning, light and dark appearance, increased contrast.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-colors\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M78SS50WJGTS3AYGE4SRBNQK","better-accessibility","Accessibility engineering for product interfaces, from focus states and keyboard support to ARIA, forms, and screen readers. Use when building or reviewing UI components, modals, menus, forms, custom widgets, or when the user says \"make this accessible\" or reports keyboard or screen-reader issues. Triggers on accessibility, a11y, WCAG, aria, focus ring, focus-visible, focus trap, keyboard navigation, tab order, tabindex, screen reader, sr-only, aria-live, alt text, hit area, touch target, prefers-reduced-motion, autoplay, toast duration, skip link, semantic HTML, aria-label, form errors, disabled buttons, \"not keyboard accessible\".","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-accessibility\u002FSKILL.md",[],[]]