Claude Skills by nota-america

Write or review UX copy — microcopy, error messages, empty states,

Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.

Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.

Generate developer handoff specs from a design. Use when a design is ready for engineering and needs a spec sheet covering layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details.

Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.

Synthesize user research into themes, insights, and recommendations. Use when you have interview transcripts, survey results, usability test notes, support tickets, or NPS responses that need to be distilled into patterns, user segments, and prioritized next steps.

Plan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research.

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

Create or evaluate an architecture decision record (ADR). Use when

Review code changes for security, performance, and correctness.

Structured debugging session — reproduce, isolate, diagnose, and

Pre-deployment verification checklist. Use when about to ship a

Write and maintain technical documentation. Trigger with "write

Run an incident response workflow — triage, communicate, and write

Generate a standup update from recent activity. Use when preparing

Design systems, services, and architectures. Trigger with "design a

Identify, categorize, and prioritize technical debt. Trigger with

Design test strategies and test plans. Trigger with "how should we

Create or evaluate an architecture decision record (ADR). Use when

Review code changes for security, performance, and correctness.

Structured debugging session — reproduce, isolate, diagnose, and

Pre-deployment verification checklist. Use when about to ship a

Write and maintain technical documentation. Trigger with "write

Run an incident response workflow — triage, communicate, and write

Generate a standup update from recent activity. Use when preparing

Design systems, services, and architectures. Trigger with "design a

Identify, categorize, and prioritize technical debt. Trigger with

Design test strategies and test plans. Trigger with "how should we

Create or evaluate an architecture decision record (ADR). Use when

Review code changes for security, performance, and correctness.

Structured debugging session — reproduce, isolate, diagnose, and

Pre-deployment verification checklist. Use when about to ship a

Write and maintain technical documentation. Trigger with "write

Run an incident response workflow — triage, communicate, and write

Generate a standup update from recent activity. Use when preparing

Design systems, services, and architectures. Trigger with "design a

Identify, categorize, and prioritize technical debt. Trigger with

Design test strategies and test plans. Trigger with "how should we

Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.

Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

Pre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production, or documenting rollback triggers ahead of time.

Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

Generate a standup update from recent activity. Use when preparing for daily standup, summarizing yesterday's commits and PRs and ticket moves, formatting work into yesterday/today/blockers, or structuring a few rough notes into a shareable update.

Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.

Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.

Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.

Generate a daily or weekly digest of activity across all connected

Combines search results from multiple sources into coherent,