ux-accessibility
Accessibility principles for inclusive design - keyboard navigation, screen readers, ARIA, color contrast, and focus management. WCAG compliance for interfaces usable by all. Use when implementing interactive UI components requiring accessibility: - Forms, buttons, links, interactive elements needing keyboard access - Keyboard navigation, focus management, tab order - Screen reader support with semantic HTML and ARIA attributes - Color contrast validation for text/buttons (WCAG AA/AAA standards) - Modals, dialogs, dropdowns needing focus trapping - User mentions "accessible", "WCAG", "disabilities", "keyboard", "screen reader" Keywords: accessible, accessibility, WCAG, keyboard, screen reader, ARIA, contrast, a11y Do NOT load for: - Visual design/styling only (use frontend-design-fundamentals) - Theme/color selection (use frontend-design-theme-factory) - Responsive layout (use frontend-design-responsive) - Figma extraction (use frontend-design-figma-extraction) - Code quality checks (use quality-code-check
responsive-ui-auditor
Skill for ensuring components follow mobile-first and responsive best practices.
golden-circle
Golden Circle framework implementation based on Simon Sinek's concept of Why, How, and What for creating meaningful projects and products. Use when Claude needs to develop projects with clear purpose, methodology, and implementation: (1) Starting with 'Why' to establish purpose and motivation, (2) Defining 'How' to outline methodology and approach, (3) Specifying 'What' to detail the tangible outcomes, (4) Ensuring alignment between all three circles for authentic value creation, or any other purpose-driven development operations.
upgrade-integration
Integrate Carnegie Learning's UpGrade A/B testing platform into LMS and EdTech applications. Guides setup of decision points, experiment conditions, LTI/xAPI integration, and outcome logging. Use when asked to add A/B testing, experiments, or feature flags to educational software.
brainstorming
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
product-requirements
Turns a single product idea (within this repo) into an evolving requirements collection. Use when the user wants to capture product design, add or refine requirements, or review the current product design state. Stores process memory in SQLite and keeps Markdown views up to date.
frontend-design-alt-2
Appliquer une approche "intentional minimalism" pour concevoir des interfaces frontend avantโgardistes, รฉpurรฉes et hautement intentionnelles. Utiliser quand l'utilisateur demande une interface sobre mais trรจs pensรฉe (pages, dashboards, composants) avec de fortes exigences UX et longรฉvitรฉ. Supporte un mode "ULTRATHINK" pour une analyse de design exhaustive avant de produire le code.
plan-feature
ๆฉ่ฝใฎๅฎ่ฃ ่จ็ปใ็ซๆกใใใใฎ่จญ่จใ่ใใฆใใใใฎๅฎ่ฃ ๆน้ใใใใใฉใๅฎ่ฃ ใใ๏ผใใจ่จใใใๆใซไฝฟ็จ
prd-reviewing
Reviews and validates Product Requirements Documents for completeness, clarity, and feasibility. Identifies gaps, ambiguities, and risks using systematic checklist. Use when reviewing PRDs before approval, during stakeholder reviews, or validating requirements quality.
brainstorm
Brainstorming partner for specification and design discussions
member-experience
Load when working on member onboarding, retention strategies, feedback collection, NPS surveys, or improving the overall member journey. Contains frameworks for creating exceptional member experiences at every touchpoint.
features-plan
Analyze user input and generate detailed feature specification files.
growth-hacker
Growth Hacker Agent. ์ฑ์ฅ ์ ๋ต ์๋ฆฝ, ๋น ๋ฅธ ์คํ ์ค๊ณ, ๊ทธ๋ก์ค ํดํน์ ๋ด๋นํฉ๋๋ค.
requirements-clarification
Force requirements clarification BEFORE implementation to prevent misunderstandings. Auto-activates on "้ๆฑ", "requirement", "ๅฎขๆถ่ฆ", "ๆฐๅ่ฝ", "ๆกไธป่ชช", "็จๆถๆณ่ฆ" keywords. Uses structured CARIO format to clarify ambiguous requirements and validate understanding.
ux-ui-animation
์ ๋๋ฉ์ด์ ์์ด์ ํธ. UI ์ ๋๋ฉ์ด์ ๊ณผ ํธ๋์ง์ ์ ์ค๊ณํฉ๋๋ค.
client-arch-explain
็ๆๅฎขๆทๅๅฅฝ็ๆถๆ่ฏดๆ๏ผ้ไฟ่ฏญ่จ่งฃ้ๆถๆๅฑๆฌกใๆฐๆฎๆตใๆๆฏ้ๅ๏ผ๏ผ้ๅๆผ็คบๅ่ฏๅฎกไผ่ฎฎใๅฝๅๅคๅฎขๆทๆผ็คบๆ็จๆท้ชๆถๅไฝฟ็จใ
backend-engineer
็่งฃไบงๅ้ๆฑ๏ผๅฎ็ฐๅ็ซฏๆๅกๅ่ฝ๏ผๆๅปบไธๅก้ขๅๅๆฐๆฎๅค็้ป่พใ
design-aesthetics
Ensure the user interface meets premium design standards, maintains consistency with existing design tokens, and provides a polished user experience.
plan-confirm
ๆนๆก็กฎ่ฎคๅฏผ่ชใ่งฆๅ๏ผ็จๆทๆฅ็็กฎๅฎๆนๆกๅ้็ฅ"็กฎ่ฎคๆนๆก"ๆ"ๅผๅงๆง่ก"ๆถไฝฟ็จ๏ผๅๅงๅopenspecใๅๅปบๆๆกใ่พๅบๅญไปฃ็ไปปๅกๆธ ๅไธๅๅทฅใ
