create-claude-rails 0.1.2 → 0.3.0

package/templates/skills/publish/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: publish
+description: |
+  Publish a new version of Claude on Rails to npm. Analyzes changes since
+  last release, suggests a version bump (patch/minor/major), updates
+  package.json, commits, tags, and publishes. Use when: "publish",
+  "release", "ship it", "/publish".
+---
+
+# /publish — Release to npm
+
+## Purpose
+
+Handle the full publish flow for the `create-claude-rails` package:
+analyze what changed, suggest a version, get confirmation, and ship.
+
+This skill only runs from the CoR source repo (`package.json` has
+`name: "create-claude-rails"`). If run elsewhere, say so and stop.
+
+## Workflow
+
+### 1. Analyze Changes
+
+Run `git log` from the last version tag (e.g., `v0.2.0`) to HEAD.
+Summarize what changed in plain language — group by category:
+
+- **Breaking** — renames, removed features, changed file formats
+- **Features** — new flags, new skills, new modules
+- **Fixes** — bug fixes, UX improvements
+- **Internal** — refactors, template updates that don't change behavior
+
+### 2. Suggest Version
+
+Based on the changes:
+
+- **Patch** (0.x.Y) — fixes only, no new features, no breaking changes
+- **Minor** (0.X.0) — new features, backward-compatible
+- **Major** (X.0.0) — breaking changes (renames, removed APIs, format changes)
+
+Note: while pre-1.0, minor can include breaking changes per semver
+convention. Call this out when recommending.
+
+Present the suggestion with reasoning:
+
+> "Since the last release (v0.2.0), there are N breaking changes
+> (list them), N new features, and N fixes. I'd suggest **0.3.0**
+> because [reason]. Want to go with that, or a different version?"
+
+### 3. Pre-Publish Checks
+
+Before publishing, verify:
+
+- `node -c lib/cli.js` passes (syntax check)
+- Working tree is clean (no uncommitted changes) — if dirty, ask
+  whether to commit first
+- Current branch is main
+- `npm whoami` succeeds (logged in to npm)
+
+### 4. Publish
+
+With user confirmation:
+
+1. Update `version` in `package.json`
+2. Commit: `Bump to <version>`
+3. Tag: `git tag v<version>`
+4. `npm publish`
+5. `git push && git push --tags`
+
+### 5. Post-Publish
+
+- Update `system-status.md` if it exists
+- Report the published version and npm URL

package/templates/skills/seed/phases/scan-signals.md

@@ -52,14 +52,18 @@ For each signal source, provide:
 
 | Signal | Suggested Perspective |
 |--------|----------------------|
-| React / Vue / Svelte in deps | accessibility, mobile-responsiveness |
-| UI framework (Mantine, MUI, Chakra, etc.) | framework-quality (project-specific) |
+| React / Vue / Svelte in deps | usability, accessibility, mobile-responsiveness |
+| UI framework (Mantine, MUI, Chakra, etc.) | usability, framework-quality (project-specific) |
 | SQLite / PostgreSQL / MySQL | data-integrity |
-| Docker / Railway / Fly.io / Vercel | deployment, security |
+| Docker / Railway / Fly.io / Vercel | architecture, security |
 | Express / Fastify / Hono | security, performance |
 | Test framework (jest, vitest, mocha) | qa |
 | TypeScript | boundary-conditions |
 | CI/CD configs (.github/workflows, etc.) | process |
+| Complex architecture (3+ services, monorepo) | architecture |
+| Long-running project (6+ months of git history) | historian |
+| Many skills (5+ in .claude/skills/) | skills-coverage |
+| Features shipping regularly | system-advocate |
 
 These mappings are starting points, not prescriptions. A project may
 already cover a signal through an existing broader perspective (e.g.,

package/templates/skills/unlink/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: unlink
+description: |
+  Remove local development linking for Claude on Rails. Returns the
+  project to using the published npm version. Use when: "unlink",
+  "stop using local CoR", "use published version", "/unlink".
+---
+
+# /unlink — Remove Local Development Link
+
+## Purpose
+
+Disconnect from a local Claude on Rails checkout and return to using
+the published npm version.
+
+## Context Detection
+
+**CoR source repo** (`package.json` has `name: "create-claude-rails"`):
+- Run `npm unlink` to remove the global registration
+- Warn: "This will break the link for all consuming projects that depend
+  on it. They'll need to `npm unlink create-claude-rails` too, or
+  they'll get resolution errors."
+
+**Any other project**:
+- Run `npm unlink create-claude-rails`
+- The project returns to using the published npm version
+- Tell the user: "Unlinked. `npx create-claude-rails` will now pull
+  from npm instead of your local checkout."
+
+## When to Use
+
+- Before testing against the published npm version
+- When done with a local development cycle
+- When the local CoR checkout is moving to a branch you don't want
+  consuming projects to track