Move new-product-repo skill to ergarcade/internal-tools (#13)

Workspace-level tooling doesn't belong in the library repo. Point
README.md/CLAUDE.md at its new home instead.

Co-authored-by: Claude Sonnet 5 <[email protected]>

Author: angrytongan

.claude/skills/new-product-repo/SKILL.md

@@ -69,9 +69,11 @@ populate. Mock can be verified the same way without hardware.
 
 Spinning up a new ergarcade product built on this library (repo creation,
 submodule, topics, README stub) is a checklist, not something to re-derive —
-use the `new-product-repo` skill (`.claude/skills/new-product-repo/SKILL.md`).
-It covers only that scaffolding, not the app itself. README.md keeps a short
-version of the same steps.
+use the `new-product-repo` skill, which lives in the separate
+[`ergarcade/internal-tools`](https://github.com/ergarcade/internal-tools)
+repo (workspace-level tooling, not part of this library). It covers only
+that scaffolding, not the app itself. README.md keeps a short version of the
+same steps.
 
 ## Architecture
 

CLAUDE.md

@@ -194,9 +194,9 @@ See `example/index.html`/`app.js` for the reference wiring.
 
 For a one-off script, copying files out of `lib/` (above) is fine. For a full
 product repo meant to receive ongoing updates, use a git submodule instead.
-Use the `new-product-repo` Claude Code skill
-(`.claude/skills/new-product-repo/SKILL.md`) rather than re-deriving this —
-short version:
+Use the `new-product-repo` Claude Code skill (lives in the
+[`ergarcade/internal-tools`](https://github.com/ergarcade/internal-tools)
+repo, not here) rather than re-deriving this — short version:
 
 1. Create the repo, named after the product (not `pm5-<name>` — that prefix is
    legacy from the pre-submodule `pm5-overlay`/`pm5-detail`/`pm5-dump` repos,