メニュー
Generate a diverse, inclusive persona set for a product. Chains: disability-inclusive-personas, situational-impairment-mapping, assistive-technology-scenarios, ability-spectrum-mapping. Use when creating a new persona set or expanding an existing one to be more inclusive.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate an accessibility decision handoff for engineering. Chains: decision-documentation, compliance-mapping, accessibility-testing-strategy. Use when a design is ready for implementation and the engineering team needs clear accessibility specifications.
Review and surface undocumented accessibility assumptions in an existing feature or product. Chains: decision-documentation, tradeoff-analysis, compliance-mapping, accessibility-debt-tracking. Use when inheriting a product, joining a team, or auditing a feature where accessibility decisions were never formally captured.
Document accessibility decisions and tradeoffs for a feature. Chains: decision-documentation, tradeoff-analysis, compliance-mapping. Use when a feature is being designed or shipped and accessibility decisions need to be captured.
Plan what to test, how to test, and who should test for accessibility. Use when defining a testing approach, planning QA, setting up automated and manual testing, or deciding what level of accessibility testing a project needs. Triggers on: accessibility testing, how to test, test plan, automated testing, manual testing, screen reader testing, user testing, accessibility QA, what to test, testing strategy.
Track and manage accessibility debt — known accessibility issues that have been deferred. Use when managing a backlog of accessibility issues, planning remediation, or when accessibility problems are accumulating faster than they're being fixed. Triggers on: accessibility debt, tech debt, known issues, backlog, deferred, we'll fix it later, remediation, accessibility backlog, accumulating issues, regression.
Communicate accessibility decisions, requirements, and value to stakeholders who aren't accessibility specialists. Use when presenting accessibility work to leadership, product managers, engineers, or anyone who needs to understand why accessibility decisions matter. Triggers on: stakeholder, business case, justify accessibility, explain accessibility, leadership, executive, ROI, why accessibility, cost of accessibility, persuade, convince, accessibility presentation.
| name | generate |
| description | Generate a diverse, inclusive persona set for a product. Chains: disability-inclusive-personas, situational-impairment-mapping, assistive-technology-scenarios, ability-spectrum-mapping. Use when creating a new persona set or expanding an existing one to be more inclusive. |
Create a complete persona set that represents the full range of human diversity — including disability, situational impairment, age, language, and technical confidence.
Before creating personas, establish:
Using ability-spectrum-mapping, identify which ability dimensions are most relevant to this product's core tasks (vision, hearing, motor, cognitive, speech).
Using situational-impairment-mapping, identify the common situational impairments for this product's typical use contexts.
Using disability-inclusive-personas, create 4–6 personas that together cover:
Each persona includes: bio, goals, frustrations, context of use, devices and assistive technology, and a realistic scenario.
Using assistive-technology-scenarios, write a detailed usage scenario for each persona that uses assistive technology, showing step-by-step interaction with the product.
Deliver a persona set document containing:
