create-claude-rails 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -9,6 +9,20 @@ standard PIB artifact set, classify each artifact's richness, and
|
|
|
9
9
|
determine the mode. To explicitly skip state detection (force first-run
|
|
10
10
|
mode), write only `skip: true`.
|
|
11
11
|
|
|
12
|
+
## Pre-Check: CLI Metadata
|
|
13
|
+
|
|
14
|
+
Before scanning artifacts, read `.pibrc.json` at the project root. This
|
|
15
|
+
file is created by `npx create-claude-rails` and records which modules
|
|
16
|
+
were installed, which were skipped (with reasons), and the package version.
|
|
17
|
+
|
|
18
|
+
If `.pibrc.json` is absent, this skill was installed manually (not via
|
|
19
|
+
the CLI). That's fine — proceed with the artifact scan. The interview
|
|
20
|
+
and modularity menu will handle module decisions.
|
|
21
|
+
|
|
22
|
+
If `.pibrc.json` exists, note the installed and skipped modules. The
|
|
23
|
+
interview phase uses this to skip redundant questions and the modularity
|
|
24
|
+
menu uses `skipped` reasons to ask about alternatives.
|
|
25
|
+
|
|
12
26
|
## What to Scan
|
|
13
27
|
|
|
14
28
|
Check for these artifacts and classify each as absent, empty, or populated:
|