Results for “schemas”

Safe patterns for evolving database schemas in production with decision trees and troubleshooting guidance.

Database management and queries. Connect to SQL and NoSQL databases, run queries, and manage schemas.

Manage schemas, subjects, compatibility levels, modes, and contexts in the Redpanda Schema Registry via the rpk registry CLI. Register or fetch Avro, Protobuf, and JSON schemas, set compatibility levels, change registry mode, and work with schema contexts.

Generate realistic mock data from descriptions, types, or schemas. Use when you need test data fast.

OpenAPI/Swagger documentation agent for creating and maintaining comprehensive API specifications with schemas, examples, and security definitions

Use when the user asks to create ERD diagrams, normalize database schemas, design table relationships, or plan schema migrations.

Regex/parser/DSL design specialist for grammar authoring and ReDoS-safe regex. Not for REST APIs (Gateway) or DB schemas (Schema).

INVOKE THIS SKILL when writing ANY LangGraph code. Covers StateGraph, state schemas, nodes, edges, Command, Send, invoke, streaming, and error handling.

Defines structural schemas, data ontologies, and interaction boundaries for autonomous entities and synthetic data architectures.

You are an expert in tRPC, the framework for building type-safe APIs without schemas or code generation. You help developers create full-stack TypeScript applications where the server defines procedures and the client calls them with full type inference — no REST routes, no GraphQL schemas, no OpenAPI specs, just TypeScript functions that are type-safe from database to UI.

Ecto patterns for Phoenix/Elixir apps. Covers schemas, changesets, migrations, queries, Ecto.Multi, transactions, constraints, associations, pagination, tenant partitioning, performance, and testing.

Implement schema.org structured data markup to help search engines understand content and enable rich results in search.

Generate typed SDK bindings (Pydantic v2 models, TypeScript types) from the Bloodbank JSON Schema tree at `bloodbank/schemas/bloodbank/v1/**` (Draft 2020-12). Uses `datamodel-code-generator` and `json-schema-to-typescript` — NOT the deprecated hand-rolled Holyfields generators. Use when generating event-contract bindings for a Bloodbank consumer, importing typed CloudEvents envelopes into another project, or scaffolding a `bloodbank-contracts` SDK package. Trigger keywords — "bloodbank SDK", "bloodbank contracts", "Pydantic from bloodbank schemas", "TypeScript types for bloodbank events", "bloodbank.v1.* types", "event contract bindings", "datamodel-code-generator", "json-schema-to-typescript", "regenerate SDK", "CloudEvents bindings". Do NOT use for schema authoring (edit `bloodbank/schemas/` directly per `docs/event-naming.md` §12), runtime envelope validation (use `BLOODBANK_HOOK_VALIDATE=1`), schema-tree consistency (`mise run smoketest:schemas`), or generic JSON Schema codegen unrelated to Bloodbank.

Generate knowledge schemas and ontologies from any input format. Extract semantic structures, relationships, and hierarchies. Output as Obsidian markdown with YAML frontmatter, wikilinks, tags, and mermaid diagrams, or export to semantic formats (JSON-LD, RDF, Neo4j Cypher, GraphQL). Supports fractal mode (strict hierarchical constraints) and free mode (flexible generation). Auto-activates for queries containing "schema", "ontology", "knowledge graph", "extract structure", or "generate outline".

Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact.

Applies Schema.org structured data principles to guide decision-making, structure analysis, and improve search visibility outcomes.

Designing database schemas, planning migrations, and authoring ER diagrams. Handles normalization, index strategies, and relation definitions. Use when DB schema design is needed.

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.

Designs normalized database schemas, creates indexes, writes efficient queries, and manages transactions and data integrity.

Use when designing PostgreSQL tables, enums, relationships, migrations, storage metadata, or tenant-aware schema structures for a Supabase-backed app. Trigger on requests about Supabase schema planning or SQL-first data design.

Implement, audit, and validate JSON-LD structured data to earn rich results in Google and improve AI search visibility.

Design an application database schema from product flows and backend responsibilities. Use when the team needs core entities, relationships, lifecycle fields, indexes, audit needs, tenancy boundaries, and migration-minded schema planning for an MVP or production system.

Design PostgreSQL schemas with best practices for data types, indexing, constraints, and performance patterns.

Database Schema Management Skill

Implementa e valida dados estruturados schema.org em JSON-LD — Organization, Article, FAQPage, Product, BreadcrumbList. Use quando o usuário disser "schema", "dados estruturados", "JSON-LD", "rich snippet", "FAQ schema", "schema.org".

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features

Provides production patterns and non-obvious traps for Prisma ORM in TypeScript backends, covering schema design, query optimization, transactions, pagination, and common pitfalls.

Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.