_css
CSS patterns, layout, responsive design, and styling conventions. Apply when writing or reviewing styles.
_testing
Test strategy, structure, and patterns for writing effective tests. Apply when writing or reviewing tests.
Proofread
Proofread a message for grammar, clarity, consistency, and factual accuracy while preserving the author's voice. Use when asked to proofread, check, review, or polish a message, email, or piece of writing.
_typescript
TypeScript type safety, naming conventions, and idiomatic patterns. Apply when writing or reviewing TypeScript code.
explain
Explain how something works — code, libraries, APIs, protocols, concepts, or architecture. Use when the user asks to explain, walk through, describe, or teach any software engineering topic (examples include codebase internals, library APIs, domain concepts, protocols, design patterns, or how technologies work).
design
Plan, design, or architect a feature — break down a task into steps, compare approaches, and define scope before coding. Use when the user asks to plan a feature, design a system, architect a solution, scope work, or evaluate approaches (examples include API design, data model planning, refactoring strategies, migration plans, or breaking down complex features into steps).
_code-style
Function design and comment guidelines for code-style consistency. Apply when writing or reviewing code.
refactor
Plan and execute a refactor — assess code against production-readiness, define scope, and improve incrementally. Use when asked to refactor, clean up, improve, harden, or make code production-ready.
Code Review
Review code, PRs, diffs, or changes — check for bugs, impact, and adherence to project patterns. Use when asked to review, audit, or give feedback on code changes.
_react
React component patterns, hooks rules, performance, and state management. Apply when writing or reviewing React code.
_accessibility
Accessible markup, ARIA patterns, keyboard navigation, and inclusive design. Apply when writing or reviewing UI code.
Note Validator
Analyze notes for quality, accuracy, and completeness. Use when asked to validate, review, check, or improve a personal knowledge base note.
implement
Build, implement, create, or add a feature — write production-quality code following project patterns with analysis and validation. Use when the user asks to build, implement, create, code, or develop functionality (examples include adding features, building components, writing API endpoints, creating utilities, or implementing a design plan).