unicode-color-accessibility
This skill should be used when the user asks about Unicode rendering, wcwidth, grapheme clusters, emoji, combining marks, East Asian width, BiDi text, box drawing, Nerd Fonts, color themes, truecolor, 256-color fallback, NO_COLOR, contrast, accessibility, screen-reader behavior, keyboard access, reduced motion, or non-TUI fallbacks. PROACTIVELY activate for: Unicode width bugs, misaligned tables, emoji layout, ANSI-aware string measurement, color accessibility, screen-reader friendly CLI design, plain output mode, ASCII fallback, and terminal theme support. Provides: text measurement rules, color/fallback policy, accessibility checklist, and failure-mode fixes.
What this skill does
# Unicode, Color, Accessibility, and Non-TUI Fallbacks Use this skill when terminal output must be visually correct, readable, inclusive, and robust across fonts, locales, themes, and assistive technologies. ## Text correctness rules - Display width is not byte length, code point count, or user-perceived character count. - Cursor movement and deletion should operate on grapheme clusters. - Layout should measure printable text after stripping ANSI control sequences. - Double-width characters, combining marks, emoji sequences, variation selectors, and zero-width joiners must be tested. - Treat ambiguous East Asian width as narrow by default unless the target environment explicitly differs. ## Visual design rules - Use semantic roles: error, warning, success, info, muted, selected, focused, disabled. - Do not encode meaning by color alone; pair color with text, shape, icon, or position. - Provide ASCII fallback for box drawing, braille charts, block elements, emoji, and private-use icons. - Avoid assuming Nerd Fonts or patched fonts. - Support light and dark backgrounds, 16-color, 256-color, truecolor, and no-color modes. ## Color preferences Respect user and environment preferences: - `NO_COLOR` disables non-essential color. - `CLICOLOR`, `CLICOLOR_FORCE`, and `FORCE_COLOR` may force color depending on ecosystem conventions. - `TERM=dumb`, non-TTY output, and CI usually imply plain output unless overridden. - Provide explicit flags such as `--color=auto|always|never`, `--plain`, and `--ascii`. ## Accessibility requirements - All functionality must be keyboard-operable. - Focus indicators must be visible without relying on color alone. - Avoid flashing more than three times per second. - Allow spinner, animation, and live-region suppression for reduced motion, logs, and CI. - Provide screen-reader friendly alternatives: plain prompts, line-oriented commands, `--json`, `--plain`, or documented stdin/stdout workflows. - Use meaningful labels, stable ordering, and visible status messages. ## Failure modes | Symptom | Likely cause | Fix | |--|--|--| | Misaligned tables | byte length or ANSI counted as visible width | use ANSI-aware wcwidth/grapheme measurement | | Cursor splits emoji | movement by code point | move by grapheme cluster | | Borders look broken | font or width mismatch | provide ASCII mode and test common fonts | | Error only shown in red | color-only meaning | add text/icon/label and contrast check | | Screen reader unusable | full-screen repaint grid | provide non-TUI mode and line-oriented flows | ## Reference files - `references/text-measurement.md` - Unicode width, graphemes, emoji, BiDi, and ANSI measurement. - `references/accessibility-fallbacks.md` - Color policy, screen-reader alternatives, and inclusive UX checklist.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.