interaction-design
Interaction Design
Overview
Use this skill to define clear, accessible interaction behavior for primary and edge-case user journeys.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Interaction feedback principles:
references/interaction-feedback-principles.md
Templates And Assets
- Flow spec template:
assets/flow-spec-template.md
- State transition template:
assets/state-transition-template.csv
- Edge-case checklist:
assets/interaction-edge-case-checklist.md
Inputs To Gather
- User tasks and business-critical journeys.
- Existing flow issues and support signals.
- Platform interaction constraints.
- Error/retry expectations and accessibility constraints.
Deliverables
- Flow specifications with start/end/alternate/failure paths.
- State transition and feedback behavior map.
- Explicit edge-case behavior definitions.
- Accessibility-ready interaction checkpoints.
Workflow
- Define flow boundaries in
assets/flow-spec-template.md. - Map state transitions in
assets/state-transition-template.csv. - Apply feedback principles from
references/interaction-feedback-principles.md. - Cover failure and edge behavior via
assets/interaction-edge-case-checklist.md. - Validate consistency and accessibility across similar patterns.
Quality Standard
- Critical flows have explicit state and transition models.
- Failure states are actionable and recovery paths are clear.
- Interaction behavior is consistent for similar intents.
- Keyboard/focus behavior supports accessibility requirements.
Failure Conditions
- Stop when flow goals or state boundaries are ambiguous.
- Stop when edge-case behavior is undefined for critical tasks.
- Escalate when interaction rules conflict with accessibility requirements.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9