visual-design
Visual Design
Overview
Use this skill to create visual systems that are consistent, accessible, and implementation-ready.
Scope Boundaries
- Product surfaces need a coherent visual language or redesign.
- Teams must align brand expression with usability and accessibility constraints.
- Implementation teams need explicit visual rules rather than isolated mockups.
Templates And Assets
- Visual spec template:
assets/visual-spec-template.md
Inputs To Gather
- Brand and product positioning goals.
- Existing UI inconsistencies and readability issues.
- Accessibility requirements (contrast, legibility, scaling).
- Platform constraints (web/mobile/native, theming model).
Deliverables
- Visual specification covering color roles, typography, spacing, and hierarchy.
- Component-level visual usage guidelines and anti-pattern notes.
- Accessibility validation notes for key visual decisions.
Workflow
- Define hierarchy goals by task criticality and information density.
- Build typography and spacing scales with explicit rationale.
- Define semantic color roles and permitted usage boundaries.
- Apply rules to representative screens and states.
- Validate readability/contrast and adjust conflicting decisions.
- Deliver implementation-ready specs and examples.
Quality Standard
- Visual system supports content hierarchy and task focus.
- Rules are reusable across pages and components.
- Accessibility checks are integrated into visual decisions.
- Spec quality is high enough to reduce interpretation drift in implementation.
Failure Conditions
- Stop when specs rely on one-off exceptions as default behavior.
- Stop when contrast or legibility fails baseline requirements.
- Escalate when brand constraints 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