GitHub
docker-next-config-mounts
Use when asked to fix Docker Compose bind mounts for Next.js config so they mount next.config.mjs (not next.config.js) and avoid the next.config.js/ directory bug.
☆ 1View skill
tools full stack AI Skills
Discover tools full stack skills, compare source repositories and read the instructions for each workflow.
Categories: tools full stack
tools full stack Clear filters
Browse skills
GitHub
frontend-testing-patterns
Provides comprehensive testing strategies and patterns for React applications. This skill should be used when writing tests, setting up testing infrastructure, or deciding what to test.
☆ 1View skill
GitHub
backend-controller-pattern-backdoor
Provides NestJS Controller patterns for Backdoor (Service-to-Service) endpoints. This skill should be used when building endpoints that require API Key authentication for internal communication.
☆ 1View skill
GitHub
frontend-code-quality
Provides code quality standards for frontend applications. This skill should be used when configuring linting rules, organizing file structures, or ensuring consistency across React applications.
☆ 1View skill
GitHub
eridu-authentication-authorization-frontend
Provides frontend-specific authentication and authorization implementation patterns for React applications. This skill should be used when implementing login flows, protecting routes, storing tokens securely, m...
☆ 1View skill
GitHub
backend-controller-pattern-integration
Provides NestJS Controller patterns for Integration endpoints. This skill should be used when building endpoints for external integrations like Google Sheets or Webhooks.
☆ 1View skill
GitHub
frontend-performance
Provides performance optimization patterns for React applications. This skill should be used when optimizing bundle size, implementing code splitting, reducing re-renders, or improving web vitals.
☆ 1View skill
GitHub
frontend-tech-stack
Provides standards for the frontend application technology stack. This skill should be used when setting up new frontend projects or upgrading existing ones with React 19, Vite, and Tailwind v4.
☆ 1View skill
GitHub
repository-pattern
Provides general guidance for implementing data access layers in backend applications. This skill should be used when designing repositories, implementing query methods, or managing database access patterns.
☆ 1View skill
GitHub
frontend-code-quality
Provides code quality standards for frontend applications. This skill should be used when configuring linting rules, organizing file structures, or ensuring consistency across React applications.
☆ 1View skill
GitHub
frontend-api-layer
Provides patterns for structuring the API layer in React applications. This skill should be used when setting up API clients, defining API request declarations, or integrating with TanStack Query for data fetch...
☆ 1View skill
GitHub
frontend-tech-stack
Provides standards for the frontend application technology stack. This skill should be used when setting up new frontend projects or upgrading existing ones with React 19, Vite, and Tailwind v4.
☆ 1View skill
GitHub
service-pattern
Provides general guidance for implementing service layers in backend applications. This skill should be used when designing service architectures, implementing CRUD operations, or organizing orchestration servi...
☆ 1View skill
GitHub
eridu-authentication-authorization-backend
Provides backend-specific authentication and authorization implementation patterns for NestJS/TypeScript servers. This skill should be used when implementing JWT validation, role-based access control, API key g...
☆ 1View skill
GitHub
backend-controller-pattern
This skill provides general guidelines for designing backend controller layers across any framework. It should be used when implementing REST endpoints, handling HTTP status codes, managing pagination, or struc...
☆ 1View skill
GitHub
middleware-patterns
Next.js middleware patterns for protected routes, auth redirects, and URL handling. Use when working with middleware.ts, protected routes, or auth redirects. Keywords: middleware, protected routes, redirect, au...
☆ 1View skill
GitHub
error-handling
Centralized error handling system for StepLeague using AppError class, error codes, and reporting. Use when implementing error handling, catching exceptions, or displaying error messages to users. Keywords: err...
☆ 1View skill
GitHub
typescript-debugging
Debugging TypeScript build errors in Next.js and Supabase projects. Use when encountering tsc --noEmit failures, type mismatches, 'never' type errors, or Supabase generic issues. Keywords: TypeScript, tsc, buil...
☆ 1View skill
GitHub
form-components
StepLeague reusable form components with accessibility features. Use when creating any form, input field, select dropdown, checkbox, or file upload in the application. Keywords: form, input, select, checkbox, t...
☆ 1View skill
GitHub
testing-patterns
Testing patterns for Next.js App Router with Supabase. Use when adding tests, verifying fixes, or preventing regressions. Keywords: test, testing, jest, vitest, unit test, integration test, mock, Supabase mock,...
☆ 1View skill
GitHub
embassy
Embassy async embedded framework for Rust. Use when working with async/await in no_std embedded contexts, task executors, or Embassy crates like embassy-executor, embassy-time, embassy-sync.
☆ 1View skill
GitHub
adynato-vercel
Vercel deployment and configuration for Adynato projects. Covers environment variables, vercel.json, project linking, common errors like VERCEL_ORG_ID/VERCEL_PROJECT_ID, and CI/CD setup. Use when deploying to V...
☆ 1View skill
GitHub
adynato-cloudflare
Cloudflare Workers and Pages deployment for Adynato projects. Covers wrangler CLI, reading logs for debugging, KV/D1/R2 storage, environment variables, and common errors. Use when deploying to Cloudflare, debug...
☆ 1View skill
GitHub
adynato-mobile
Mobile app development conventions for Adynato projects using React Native and Expo. Covers navigation patterns, native APIs, performance optimization, and platform-specific considerations. Use when building or...
☆ 1View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.