Results for “schemas”
9 skillsapi-and-interface-design
Design stable, well-documented interfaces that are hard to misuse, including REST APIs, GraphQL schemas, module boundaries, and component props.
69.5k
saas-scaffolder
Generates a complete, production-ready SaaS project boilerplate with Next.js 14+, TypeScript, Tailwind CSS, shadcn/ui, Drizzle ORM, and Stripe, including authentication, database schemas, billing integration, API routes, and a working dashboard.
20.4k · bundle
More results
schema
Implement schema.org structured data markup to help search engines understand content and enable rich results in search.
36.3k · bundle
schema-org
Applies Schema.org structured data principles to guide decision-making, structure analysis, and improve search visibility outcomes.
2
schema-markup
Implement, audit, and validate JSON-LD structured data to earn rich results in Google and improve AI search visibility.
20.4k · bundle
schema-markup
Adds, fixes, and optimizes schema.org structured data (JSON-LD) for rich results, including validation and implementation guidance.
1 · bundle
seo-schema
Detects, validates, and generates Schema.org structured data, preferring JSON-LD, with guidance on supported types and common errors.
39
saas-scaffolder
Generates complete, production-ready SaaS project boilerplate including authentication, database schemas, billing integration, API routes, and a working dashboard using Next.js 14+ App Router, TypeScript, Tailwind CSS, shadcn/ui, Drizzle ORM, and Stripe. Use when the user wants to create a new SaaS app, start a subscription-based web project, scaffold a Next.js application, or mentions terms like starter template, boilerplate, new project, or wiring up auth and payments.
0 · bundle
api-design-principles
Designs REST and GraphQL APIs following production best practices for resource naming, error handling, versioning, authentication, and documentation. Use this skill when designing new API endpoints, reviewing API contracts, implementing GraphQL schemas, establishing API conventions for a project, or writing API documentation. Apply when creating any route in Next.js API routes or route handlers, any Supabase Edge Function, or any backend endpoint — even if it starts small, these patterns prevent painful rewrites later.
3