Principles

• Use semantic HTML first — ARIA is a last resort, not a first tool
• Proper heading hierarchy — one h1 per page, never skip levels
• Alt text on all meaningful images
• Maintain 4.5:1 minimum color contrast ratio
• Use

  <button>

  for actions,

  <a>

  for navigation — never a styled

  <div>

Rules

Examples

Positive Trigger

design-accessibility

Non-Trigger

design-accessibility

Troubleshooting

Skill Does Not Trigger

• Error: The skill is not selected when expected.
• Cause: Request wording does not clearly match the description trigger conditions.
• Solution: Rephrase with explicit domain/task keywords from the description and retry.

Guidance Conflicts With Another Skill

• Error: Instructions from multiple skills conflict in one task.
• Cause: Overlapping scope across loaded skills.
• Solution: State which skill is authoritative for the current step and apply that workflow first.

Output Is Too Generic

• Error: Result lacks concrete, actionable detail.
• Cause: Task input omitted context, constraints, or target format.
• Solution: Add specific constraints (environment, scope, format, success criteria) and rerun.

Workflow

1. Identify whether the request clearly matches

   design-accessibility

   scope and triggers.
2. Apply the skill rules and referenced guidance to produce a concrete result.
3. Validate output quality against constraints; if gaps remain, refine once with explicit assumptions.