Discover Databases skills, compare source repositories and read the instructions for each workflow.
Captures Dmitrii's distinctive writing voice and preferences for all written outputs. Use when creating case studies, blog posts, articles, documents, emails, proposals, PRDs, specifications, messages, or any w...
List all open intents with progress tracking. Use when the user wants to see what intents are in progress, check completion status, or get an overview of their work.
Generate a Marp presentation from an intent's spec. Use when the user wants to create slides for an intent or asks to make a presentation.
Mark an intent as complete and move to done folder. Use when the user has finished working on an intent and wants to document completion, add PR links, and archive it.
Start a new intent with spec-driven development. Use when the user wants to begin working on a new feature, bug fix, or task and needs to document the problem, solution, and requirements.
When you need to run code before a request completes: auth checks, redirects, headers, A/B testing. **Version Context**: Next.js 16.0+ uses `proxy.ts` (replaces `middleware.ts` from v15 and earlier).
Apply when designing RESTful APIs, defining endpoints, HTTP methods, status codes, and response formats.
Apply when styling components with Tailwind CSS: responsive design, component patterns, and class organization.
When checking if skill content matches current library/framework version.
When building UI components, forms, or any user-facing interface. Check before every frontend PR.
When designing layouts, navigation, forms, or feedback components. Reference for consistent UI decisions.
Apply when improving code structure without changing behavior: reducing duplication, simplifying complexity, or improving readability.
Apply when writing code documentation: JSDoc comments, README files, API documentation, and inline comments.
Apply when writing Supabase client queries for CRUD operations, filtering, joins, and real-time subscriptions.
When writing, reviewing, or validating user stories. Used by ARCHITECT-AGENT and PRODUCT-OWNER.
When implementing backend APIs, database queries, authentication, or handling user input.
Apply when writing reusable functions, components, or utilities that work with multiple types while maintaining type safety.
Apply when building forms with validation, handling form state, or integrating with validation libraries like Zod.
Apply when deciding state management approach: local state, context, Zustand for client state, or TanStack Query for server state.
Apply when validating API request inputs: body, query params, path params, and headers. This skill covers Zod v4 patterns.
Apply when designing error responses, implementing error handlers, and ensuring consistent error format across APIs.
Apply when testing React components: rendering, user interactions, and accessibility-focused testing.
When reporting bugs found during manual testing or QA validation.
When building Next.js App Router pages and deciding between Server and Client Components.
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.