CURATIONSX
Checking GitHub identity...
← Find Skills

Illustrative Skill record · no external Skill imported, installed, matched, or executed

35

PLAN + DESIGN

Schema-first planning

Turns important records and relationships into a clearer implementation plan.

REVIEWED✓ COMMUNITY SUBMITTEDv1.1fixture review - 2026-07-17

Authenticated action preview · no request or persistence

Why it may fit

Explain the match before asking the builder to act

The approved PRD names several records and relationships but leaves ownership and lifecycle decisions open.

Supported hosts
  • GitHub Copilot CLI
  • Claude Code
Permissions
  • Approved PRD text
  • No shell
  • No network
Constraints
  • Uses only the approved PRD revision.
  • Does not inspect repository files.
  • Returns a schema discussion prompt, not generated code.
Risk

Low fixture risk; no executable Artifact exists.

Stack context

Explicit compatibility context

SupabaseSQLite

Community SkillUseOutcome

Explicit member reports

SKILL OUTCOMEWorked after adaptation

A builder kept the record map but replaced the suggested status names before revising the PRD.

Illustrative member-reported outcome

Public Examples

Cited examples remain separate from community outcomes

PUBLICLY SOURCEDPublic plan structure example

The fixture plan demonstrates separate Project type, stage, Stack, and outcome objects.

PUBLICLY SOURCED - fixture contract

Discussion

Anchored human question

@CurationsLA

Which constraint should a builder confirm before saving this exact Skill revision?