Conciseness

The 380-line body includes decorative ASCII box diagrams, full boilerplate schema definitions for Drizzle/Prisma/SQLAlchemy that Claude already knows, and a verification checklist repeated three times (Pre-Code Checklist, Session Start state, final Checklist). This is noticeably verbose with several padded sections — anchor 2 — though not anchor 1 since there is no conceptual tutoring prose.

Actionability

Concrete executable commands ('npx prisma generate', 'supabase gen types typescript --local > src/types/database.ts', 'npx drizzle-kit generate') and real type-safe query examples cover common cases, with minor gaps: the SQLAlchemy example uses 'relationship' without importing it, and the TypeORM row gets no example at all. Anchor 4 (mostly executable, minor gaps) rather than 5.

Workflow Clarity

The migration workflow is a clear six-step sequence with explicit validation ('Run type check - find all broken code', 'Fix type errors, update tests, run full validation'), and the Schema Verification Checklist acts as a pre-code checkpoint — satisfying the database-operations feedback-loop requirement. Minor gaps ('If schema file doesn't exist → CREATE IT' with no how) keep it at anchor 4 rather than 5.

Progressive Disclosure

No bundle files exist and everything is inline in one 380-line file; per-stack type-generation guides and the schema-reference template clearly belong in separate reference files. Section headers are clear and navigation within the file is fine, which lifts it above anchor 2 ('minimal structure') to anchor 3 ('some structure, content that should be separate is inline').

Specificity

The description names the domain ('Schema awareness') and 2-3 concrete actions ('read before coding', 'type generation', 'prevent column errors'), but they are telegraphic fragments rather than fully specified actions, and 'prevent column errors' is an outcome rather than a capability. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); anchor 4 requires several specific, well-articulated actions.

Completeness

The 'what' is only weakly stated ('Schema awareness' is a concept, not an action description), and the description field itself contains no 'Use when...' clause — trigger guidance exists only in the separate frontmatter 'when-to-use' field, so per the judging guideline completeness is capped at 3. Not score 2 because the what, while terse, is still discernible.

Trigger Term Quality

Terms like 'schema', 'type generation', and 'column errors' are relevant to the domain, but common natural phrases users would say — 'SQL', 'ORM', 'migrations', 'tables', 'Postgres' — are absent. This matches anchor 3 (some relevant keywords, missing common variations and synonyms) rather than anchor 4's good coverage.

Distinctiveness Conflict Risk

The database-schema niche ('type generation', 'prevent column errors', database queries) is mostly distinct with clear triggers, though it could minorly overlap with migration or general TDD/coding skills. Matches anchor 4 (mostly distinct, minor overlap risk) rather than anchor 5, whose triggers are more comprehensively differentiated.