Rewrite the composer skill around core concepts

scripts/check-skill-packaging.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-// The `prisma-composer` skill must arrive in the `@prisma/composer` tarball,
+// The `prisma-composer-core-concepts` skill must arrive in the `@prisma/composer` tarball,
 // carrying the version of the tarball it arrived in.
 //
 // That claim is only worth as much as the artifact that proves it. The

scripts/set-version.ts

@@ -60,7 +60,7 @@ for (const pkg of workspacePackages) {
   updatedCount++;
 }
 
-// The `prisma-composer` skill ships inside the `@prisma/composer` tarball, so
+// The `prisma-composer-core-concepts` skill ships inside the `@prisma/composer` tarball, so
 // its `library_version` is part of the same lockstep stamp as the manifests:
 // the version a reader of the skill sees is the version they installed.
 const skillsDir = path.join(rootDir, 'skills');

scripts/skill-frontmatter.test.ts

@@ -91,7 +91,10 @@ describe('the shipped skill', () => {
     const rootVersion = JSON.parse(
       await readFile(path.join(repoRoot, 'package.json'), 'utf-8'),
     ).version;
-    const source = await readFile(path.join(repoRoot, 'skills/prisma-composer/SKILL.md'), 'utf-8');
+    const source = await readFile(
+      path.join(repoRoot, 'skills/prisma-composer-core-concepts/SKILL.md'),
+      'utf-8',
+    );
 
     assert.deepEqual(readSkillFrontmatter(source), {
       library: '@prisma/composer',

skills/README.md

@@ -6,7 +6,7 @@ App without re-deriving the API from documentation each time.
 
 ## What's in the box
 
-One skill, `prisma-composer`, covering the whole story: the mental model
+One skill, `prisma-composer-core-concepts`, covering the whole story: the mental model
 (Modules, `compute()`, `service.load()`), RPC contracts, databases, reusable
 modules (cron/storage/streams), config params, secrets, testing
 (`mockService`/`bootstrapService`), deploying (`prisma-composer deploy`,
@@ -71,7 +71,8 @@ surface change lands in both. For anyone editing the skill:
   nothing, the surface doesn't ship — name it under *What Composer doesn't do
   yet* instead of extrapolating.
 - **The skill must be self-contained.** It gets installed into other repos, so
-  no link may resolve outside `skills/prisma-composer/`. Repo docs may be
+  no link may resolve outside `skills/prisma-composer-core-concepts/`. Repo
+  docs may be
   named in prose ("`docs/design/10-domains/testing.md` in the prisma/composer
   repo"), never linked relatively.
 - **Teach concepts, not procedures.** Name the moving parts and the command