New skills

Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 62 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

Client-side tracking with Analytics.js. Include track, identify, page, and group calls. Anonymous ID persists until identify merges with user.

Comprehensive web testing: unit, integration, E2E, load, security, visual regression, accessibility.

Review files for compliance with Web Interface Guidelines.

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

This skill demonstrates the structure and format for Claude Code plugin skills.

Use this skills whenever you are dealing with Remotion code to obtain the domain-specific knowledge.

The CLI uses Chrome/Chromium via CDP directly. Install via npm i -g agent-browser , brew install agent-browser , or cargo install agent-browser . Run agent-browser install to download Chrome.

A skill for creating new skills and iteratively improving them.

Comprehensive design guide for web and mobile applications. Contains 50+ styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, and 25 chart types across 10 technology stacks. Searchable database with priority-based recommendations.

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

Source provenance, compatibility, automated checks, and current evidence depth are available on the full page.

Source provenance, compatibility, automated checks, and current evidence depth are available on the full page.

AI Elements is a component library and custom registry built on top of shadcn/ui to help you build AI-native applications faster. It provides pre-built components like conversations, messages and more.

A .docx file is a ZIP archive containing XML files.

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI....

Unless otherwise stated by the user or existing template

Source provenance, compatibility, automated checks, and current evidence depth are available on the full page.

Write the test first. Watch it fail. Write minimal code to pass.

Load plan, review critically, execute all tasks, report when complete.

To test local web applications, write native Python Playwright scripts.

Always consult better-auth.com/docs for code examples and latest API.

Source provenance, compatibility, automated checks, and current evidence depth are available on the full page.