Conform the prisma-8 skill to the skill-authoring guidelines (pre-conditions, trigger-only description, dead links) - #30264

…ditions, trigger-only description, dead links) (prisma#30264)

## Linked issue

n/a — follow-up to prisma#30250 (the rc.9 fact refresh); no Linear ticket.

## Skill update

This PR is a skill update: structural conformance of `skills/prisma-8/`
with the internal skill-authoring guidelines. No public surface changes.

## At a glance

The routing file now opens with pre-conditions an agent must check
before acting:

```markdown
## Pre-conditions

1. **The project is on Prisma 8.** `prisma.config.ts` exports `definePrismaConfig({ orm: ... })`,
   and `package.json` depends on `@prisma/orm-postgres`, `@prisma/orm-sqlite`, or `@prisma/orm-mongo`.
   A project with `schema.prisma` and `@prisma/client` is Prisma 7 or earlier; this skill does not apply.
2. **The skill matches the installed version.** Compare `metadata.library_version` with the installed
   `@prisma/orm-*` version. If they differ, run `prisma skills sync` and re-read this file.
3. **The contract artefacts exist.** `contract.json` and `contract.d.ts` sit next to the contract source;
   if missing or stale, run `prisma contract emit` first.
```

Before, the frontmatter description was a capability summary and the
file had no pre-conditions.

## Summary

The guidelines ask for trigger-only descriptions, a dated
`metadata.version`, a pre-conditions section, no tool names, and
relative links that resolve. The skill failed five of those checks; this
PR fixes them without touching the verified facts landed in prisma#30250.

## Decision

Ship the structural fixes only:

1. `description` rewritten as "Use when …" trigger phrases (870 chars,
under the 1024 lint cap).
2. `metadata.version: '2026-09-11'` added; the prepack stamper rewrites
only `library` / `library_version` and leaves it intact.
3. `## Pre-conditions` added to `SKILL.md`.
4. Nine `../../docs/…` links in `migrations.md` / `migration-review.md`
repointed at GitHub — inside the published tarball there is no `docs/`
directory, so they resolved nowhere.
5. The one tool-name reference ("ripgrep") removed.
6. `queries-postgres.md` states that `.some()` / `.none()` / `.every()`
take an optional predicate, a gap the behavioral validation surfaced.

## Reviewer notes

- **Imperative voice is not done.** The references open most workflows
with "The concept: …" prose. Converting ~3,900 lines of freshly verified
content is a separate per-file pass with re-verification; it is called
out in the commit body rather than attempted here.
- **Behavioral validation** (the guidelines' step 8) was run: a fresh
agent, ten realistic Prisma 8 tasks, forbidden from reading anything but
the skill. Without the skill 8/10 answers were wrong (invented APIs such
as `db.sql.insert("user").values(...)`, `--allow-destructive`,
`@prisma/orm-postgres/lints`); with the skill 10/10 matched the verified
facts. The two loopholes it flagged are closed (the import-path mapping
in prisma#30250, the optional predicate here).
- Ephemeral-marker rules do not apply: the skill produces code, not
review artifacts.

## Testing performed

- `pnpm lint:skills` passes.
- `stampSkillMetadata` from `scripts/set-version-utils.ts` exercised
against the new frontmatter to confirm the extra key survives stamping.
- Behavioral validation as described above (scratch answer files, not
committed).

## Alternatives considered

- **Rewrite the reference bodies into imperatives in the same PR.**
Rejected: it would churn every line of content that was just verified
and reviewed, and mistakes in that rewrite would be hard to spot under
the structural diff.
- **Keep repo-relative doc links and rely on readers having the
monorepo.** Rejected: the skill ships in the npm tarball, where those
paths are dead.

## Checklist

- [x] All commits are signed off (`git commit -s`) per the
[DCO](../CONTRIBUTING.md#developer-certificate-of-origin-dco).
- [x] I read [CONTRIBUTING.md](../CONTRIBUTING.md) and the change is
scoped to one logical concern.
- [x] Tests are updated (n/a — doc-only skill content).
- [ ] The PR title is in `TML-NNNN: <sentence-case title>` form — no
Linear ticket exists; retitle once one is filed.
- [x] The **Skill update** section above is filled in.

## Notes for the reviewer

See *Reviewer notes* above.

🤖 Generated with [Claude Code](https://claude.com/claude-code)


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Documentation**
- Clarified Prisma 8 guidance, including supported signals, required
configuration, dependency versions, and artifact prerequisites.
  - Updated documentation links for more reliable navigation.
- Clarified relation predicate requirements: `.some()` and `.none()` may
omit predicates, while `.every()` requires one.
- Refined runtime guidance to avoid assumptions about unsupported
configuration keys.
  - Added a publication version to the Prisma 8 skill metadata.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: willbot <[email protected]>
Signed-off-by: Will Madden <[email protected]>
Co-authored-by: Claude Fable 5.1 <[email protected]>