Loading...
Loading...
Found 27 Skills
Advanced TypeScript patterns and best practices for 2025
Expert guidance for Angular and TypeScript development focused on scalable, high-performance web applications
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
React Native development best practices for TypeScript, functional components, performance optimization, and styling guidelines.
Expert frontend development guidance covering React, Vue, Angular, TypeScript, state management, component architecture, performance optimization, accessibility, testing, and modern web APIs. Produces production-ready, maintainable, and performant frontend code with best practices. Use when building web applications, implementing UI components, managing application state, optimizing performance, or when users mention React, Vue, Angular, TypeScript, hooks, state management, components, or frontend development.
Modern web development best practices for TypeScript, Next.js 14, React Server Components, Supabase, GraphQL, and Tailwind CSS.
Node.js development guidelines covering Payload CMS, Vue.js with TypeScript, and general TypeScript best practices
Use when any is unavoidable. Use when working with untyped libraries. Use when silencing specific type errors.
TypeScript best practices for React development. Use when writing typed React components, hooks, events, refs, or generic components. Triggers on tasks involving TypeScript errors, type definitions, props typing, or type-safe React patterns.
Use when forced to use any. Use when any is too broad. Use when function types need any.
Apply Spatie's JavaScript coding standards for any task that creates, edits, reviews, refactors, or formats JavaScript or TypeScript code; use for variable declarations, comparisons, functions, destructuring, and Prettier configuration to align with Spatie's JS conventions.
MUST be used whenever reviewing a Dune app for code quality, maintainability, or clean code issues — before a PR review, after a feature is complete, or when the user asks for a code review. Do NOT skip linting steps. Triggers: code quality, code review, clean code, refactor, maintainability, technical debt, any type, naming, dead code, duplication, DRY, single responsibility, component size, lint, linting, TypeScript strict, dependency injection, file structure.