Claude Skills by maxritter

Build a central library to manage .claude folders across projects. One repo for skills, agents, commands, hooks, and configs.

Build reusable Claude Code skills from any topic — /create-skill explores the codebase, drafts the SKILL.md interactively, and ships a slash command.

Build accessible UIs with semantic HTML, ARIA attributes, keyboard navigation, color contrast, and screen reader support. Apply when creating or modifying frontend components, forms, interactive elements, or any UI that needs WCAG compliance.

Design RESTful API endpoints with proper HTTP methods, status codes, resource-based URLs, and consistent error formats. Apply when creating or modifying route handlers, controllers, or API endpoints.

Design reusable, composable UI components with single responsibility, clear prop interfaces, and encapsulation. Apply when creating or modifying React, Vue, Svelte, or web components.

Write consistent CSS following the project's methodology (Tailwind, BEM, CSS modules) with design tokens and performance optimization. Apply when writing or modifying styles, utility classes, CSS-in-JS, or any styling code.

Create visually distinctive frontend interfaces that avoid generic AI-generated aesthetics. Apply when building landing pages, dashboards, product UIs, selecting fonts, choosing color palettes, designing layouts, adding animations or micro-interactions, or when the output risks looking like typical AI-generated UI.

Apply Go standards including modules, go test, gofmt/go vet/golangci-lint, idiomatic error handling, and self-documenting code. Apply when working with Go code, managing dependencies, or ensuring code quality.

Create reversible database migrations with proper naming, zero-downtime strategies, and backwards compatibility. Apply when creating migration files, modifying schema, or managing database versioning.

Define database models with clear naming, appropriate types, constraints, relationships, and multi-layer validation. Apply when creating or modifying ORM classes, schema definitions, or model relationships.

Apply Python standards including uv package management, pytest, ruff/basedpyright, type hints, and one-line docstrings. Apply when working with Python code, managing dependencies, or ensuring code quality.

Write secure, optimized database queries with parameterized inputs, eager loading, and strategic indexing. Apply when writing SQL, ORM queries, or optimizing data access patterns.

Build responsive, mobile-first layouts with fluid containers, media queries, and touch-friendly design. Apply when creating adaptive UI layouts, responsive grids, or multi-device interfaces.

Prevent testing anti-patterns by ensuring tests verify real behavior, keeping production code free from test-only pollution, and enforcing thoughtful mocking strategies. Apply when writing test files, adding mocks or test doubles, or reviewing test implementation patterns.

Write focused tests for core user flows with clear names, behavior-focused assertions, and mocked external dependencies. Apply when creating unit tests, integration tests, or implementing TDD.

Apply TypeScript standards including package manager detection (npm/yarn/pnpm/bun), strict types, no `any`, and explicit return types on exports. Apply when working with TypeScript/JavaScript code, managing dependencies, or ensuring type safety.

Apply these standards when creating or modifying API endpoints, route handlers, and controllers.

**Core Rule:** Use uv for all package operations, pytest for testing, ruff for formatting/linting. Write self-documenting code with minimal comments.

**Core Rule:** Write secure, performant queries using parameterized statements, eager loading, and strategic indexing.

**Core Rule:** Build accessible interfaces that work for all users, including those using assistive technologies.

**Core Rule:** Build small, focused components with single responsibility. Compose complex UIs from simple pieces.

**Rule:** Follow project CSS methodology consistently, leverage framework patterns, maintain design system tokens.

**Rule:** Mobile-first development with consistent breakpoints, fluid layouts, relative units, and touch-friendly targets.

**Rule:** Test real behavior, not mock behavior. Never pollute production code with test-only methods.

**Core Philosophy**: Write minimal, focused tests for critical paths. Defer comprehensive testing until explicitly requested.

Apply product-grounded visual quality constraints during user-visible UI changes. Use for layout, styling, content hierarchy, theming, responsive behavior, or interaction affordances. Stay inactive for logic-only changes that preserve the rendered interface.

Extract, document, or normalize a product UI design system from code, screenshots, or brand sources. Use for visual tokens, theme variables, typography, spacing, colors, radii, shadows, component inventories, variants, states, or building a reusable UI library. Do not use for software architecture, database schemas, or generic system design.

Access the Anthropic product named Claude Design when the request contains that exact name, a claude.ai/design URL, or a .dc.html file. Use for its projects, files, design systems, previews, conversations, comments, sharing, and code-to-design or design-to-code synchronization; otherwise stay inactive.

Create or redesign product UI in an existing codebase, including a wireframe, substantive visual variations, and an interactive prototype. Use for requests about UI layout, visual direction, screens, flows, components, a landing page, dashboard, or making an interface feel polished. Do not use for backend work, system architecture, decks, or logic-only UI fixes.

Review or polish a product UI for accessibility, brand fidelity, hierarchy, rhythm, responsive behavior, themes, interaction states, and generic AI-template patterns. Use for visual audits, accessibility checks, UX polish, UI critique, or pre-ship design review. Do not use for generic code review, backend review, or API design.