Stack Patterns

Plugin stack-patterns from marketplace casper-studios in Casper-Studios/casper-marketplace. Commands read from the repo's manifest — 13 days ago.

Skills (10)

• better-all-best-practices

  `better-all` conventions for dependency-aware async task graphs. Use when defining `all` or `allSettled` graphs or converting staged async work with task dependencies.

• drizzle-orm-best-practices

  Dialect-aware Drizzle ORM conventions for safe query, mutation, and transaction boundaries. Use when writing or reviewing Drizzle schemas, queries, transactions, or raw SQL.

• open-telemetry-best-practices

  Language-agnostic OpenTelemetry conventions for queryable signals and explicit operational outcomes. Use when adding or reviewing spans, structured logs, attributes, or exception recording.

• python-best-practices

  Python 3.13+ conventions for typed application and library boundaries. Use when writing or reviewing Python contracts, packages, validation, or async resource ownership.

• react-best-practices

  React component conventions for explicit state ownership and data flow. Use when creating or reviewing React components, hooks, effects, or forms.

• tanstack-react-query-best-practices

  TanStack Query conventions for cache-backed React server state. Use when creating or reviewing React queries, mutations, query keys, or cache updates.

• tanstack-react-table-best-practices

  TanStack Table v9 conventions for stable React table schemas and instance behavior. Use when creating or reviewing React tables, columns, metadata, or rendering.

• typescript-best-practices

  TypeScript conventions for precise contracts and valid program states. Use when writing or reviewing TypeScript types, state models, optional values, or untrusted boundaries.

• valibot-best-practices

  Valibot conventions for owned wire contracts and explicit validation outcomes. Use when defining or reviewing Valibot schemas or parsing untrusted data with Valibot.

• zod-best-practices

  Zod v4 conventions for owned wire contracts and explicit validation outcomes. Use when defining or reviewing Zod schemas or parsing untrusted data with Zod.