hugin-cowork

Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions for skill evaluation.

Automatically resolve TypeScript compilation and build errors systematically. Use when fixing build errors, TypeScript errors, compilation failures, tsc errors, or when the build is broken and needs to be fixed.

Semantic code review using project-specific rules

Review recently written code for best practices, architectural consistency, and system integration. Use when reviewing code, checking implementations, after completing significant code changes, or when asking for a code review.

Refactor code for better organization, cleaner architecture, and improved maintainability. Use when reorganizing code, cleaning up messy files, extracting components, splitting large files, or improving code structure.

This skill should be used when the user asks about accessibility concerns, including WCAG compliance (any success criterion including SC 1.3.5 autocomplete, SC 2.4.11 focus obscured), ARIA roles and attributes, screen reader behavior, axe-core or WAVE audit failures, color and non-text contrast, keyboard navigation, focus trapping and management, skip links, touch targets, VPAT reports, or accessible form patterns. Also triggers when the user asks whether a UI library such as shadcn or Radix handles keyboard interactions — but only if the question is specifically about accessibility behavior, not general usage.

This skill should be used when the user asks to write an ADR, create an ADR, document this decision, ADR for X, architecture decision record for X, record this decision, or document the decision to use X. It writes, validates, and commits Architecture Decision Records in MADR 4.0.0 format. Do NOT trigger on lookup or audit tasks such as what ADR covers X or check ADR compliance.

This skill provides automatic semantic code review triggered after file modifications. It is hook-driven — logging file changes via PostToolUse and running the automatic-code-reviewer agent on Stop. It should not be invoked directly by the user; it is triggered automatically by lifecycle hooks.

This skill should be used when the user asks to code connect, connect this component to code, connect Figma to code, map this component, link component to code, create code connect mapping, or add code connect. It connects Figma design components to code components using Code Connect.

This skill should be used when the user asks to visualize components, show component dependencies, dependency graph, component map, or what depends on what. It generates interactive HTML dependency graphs for React components.

10 hooks across 5 events