* docs(skills): rewrite the composer skill around core concepts
Rename the skill to prisma-composer-core-concepts and rebuild the body
around the concepts an agent cannot observe from the code or CLI help:
the declaration model, the two channels, contracts, the converge deploy
model, and the failure modes. CLI reference tables, the tsconfig block,
and the long worked example are dropped; the frontmatter description is
now trigger-only, scoped to deploying or managing an app with Composer.
Two additions: an alchemy section covering the generated stack file,
failure bisection, and the effect pin, and an explicit layering
statement that @prisma/composer is target-agnostic with
@prisma/composer-prisma-cloud as the Prisma Cloud target. The Compute
product is no longer named; "Prisma App" stays, per ADR-0026.
The release scripts discover skills by frontmatter, so the rename only
touches the hardcoded test path and prose references.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Tyler Hogarth <5163494+tylerhogarth@users.noreply.github.com>
* docs(skills): address review feedback on compile vs deploy checks
The compiler-check claim overreached: env-bound input values exist only
at deploy, so secret-binding mismatches and missing platform variables
are deploy-time refusals, not tsc failures. Say so where the claim is
made. Also reword the unclear "names the exits" phrase in the migration
section and label the error-example fence for markdownlint (MD040).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Tyler Hogarth <5163494+tylerhogarth@users.noreply.github.com>
* docs(skills): point at prisma.io/docs and drop CLI-flag references
The intro now states the skill's scope directly: structures,
hierarchies, relationships, and workflows, not a CLI reference. Because
the platform moves fast, it names https://www.prisma.io/docs as the
current documentation and directs agents to `--help` for individual
commands.
Flag references outside workflows are reworded conceptually: stage
selection, destroy targeting, and the dev fresh-start behaviour. The
migration loop, the standalone Next build, and the alchemy bisection
keep their commands; they describe workflows.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Tyler Hogarth <5163494+tylerhogarth@users.noreply.github.com>
* docs(skills): production Branch is removed via Project deletion
The destroy paragraph said the production Branch is never deleted while
also saying the emptied Project is; Project deletion removes every
Branch in it, production included. Say the Branch is never deleted
directly, and that the Project deletion takes it along.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Tyler Hogarth <5163494+tylerhogarth@users.noreply.github.com>
* fix(skills): stage the ORM-rename edits missed by the merge commit
The merge commit ff8bbca1 described porting the Prisma ORM rename and
the 0.16.0 stamp into the renamed skill, but the edits were never
staged: the commit carried the pre-merge file and the working tree held
the changes. This commit adds them: rawPostgres/postgres/dataContract,
the /orm subpath, and library_version 0.16.0. Also reflows the
readFile call in the frontmatter test to Biome's line width.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Tyler Hogarth <5163494+tylerhogarth@users.noreply.github.com>
* docs(skills): scope the package-count claim to Composer packages
An app's package.json also carries its own dependencies and any
prisma-composer-* extensions, so "exactly these two packages appear" was
false. The claim is now: the only two Composer packages a basic Prisma
Cloud app needs, with extensions adding their own package alongside.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Tyler Hogarth <5163494+tylerhogarth@users.noreply.github.com>
* docs(skills): adopt benchmark feedback verified against 0.16.0
Four judged agent runs against the synced skill surfaced compile-time
failures; each adopted item was verified against this repo first:
The ORM vocabulary (postgres, dataContract) imports from the /orm
subpath, not the package root, and the postgres binding is { url,
client } with a lazy typed client (ADR-0040), not the client itself.
The deploy config is read by dev as well as deploy/destroy. Explicit
.ts import specifiers are now the recommended form; the CLI's .js and
extensionless mapping is noted as CLI-specific. Naming guidance gains
the [A-Za-z0-9] charset rule that fails at load rather than typecheck.
New caveats: install both packages explicitly, Temporal globals for
DateTime columns (verified against the ORM package's column types),
and prepare: false under dev watch-restarts. The building-blocks table
gains the 0.16 auth and email modules.
Not adopted: removing the log command (it exists in this repo's CLI;
the benchmark ran the integrated prisma CLI, so the intro now scopes
command names to the prisma-composer bin) and the state-thunk fix (the
rewritten skill never carried the thunk example).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Tyler Hogarth <5163494+tylerhogarth@users.noreply.github.com>
---------
Signed-off-by: Tyler Hogarth <5163494+tylerhogarth@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
