@baseline-studio/cli 2.2.2 → 2.2.3
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/README.md +54 -0
- package/dist/index.js +1 -1
- package/package.json +3 -2
package/README.md
ADDED
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
# @baseline-studio/cli
|
|
2
|
+
|
|
3
|
+
> CLI for the Baseline System — an AI-powered workflow system for product teams.
|
|
4
|
+
|
|
5
|
+
## Quick Start
|
|
6
|
+
|
|
7
|
+
Create a new Baseline System:
|
|
8
|
+
|
|
9
|
+
```bash
|
|
10
|
+
npx @baseline-studio/cli init
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
You'll be asked for your company name, then guided through context questions to personalize your system. When it's done, you'll have a complete system with skills, frameworks, scripts, and context files — ready to use with Claude Code, Cursor, ChatGPT, or any AI tool.
|
|
14
|
+
|
|
15
|
+
## Commands
|
|
16
|
+
|
|
17
|
+
Once you have a Baseline System, the CLI is bundled locally. Run commands from your system's root directory:
|
|
18
|
+
|
|
19
|
+
| Command | What It Does |
|
|
20
|
+
|---------|-------------|
|
|
21
|
+
| `npx baseline status` | Show current version and check for updates |
|
|
22
|
+
| `npx baseline update` | Pull latest skills, frameworks, scripts, and CLI |
|
|
23
|
+
| `npx baseline context` | Re-run context prompts to update existing files |
|
|
24
|
+
| `npx baseline context add <name>` | Create a new context file and wire it to skills |
|
|
25
|
+
|
|
26
|
+
## How It Works
|
|
27
|
+
|
|
28
|
+
There are two copies of the CLI serving different purposes:
|
|
29
|
+
|
|
30
|
+
- **This npm package** (`@baseline-studio/cli`) is the entry point for first-time setup. It downloads temporarily via `npx`, runs `init`, and scaffolds your system.
|
|
31
|
+
- **The bundled CLI** (inside each system at `cli/`) is the daily driver. After init, all commands (`status`, `update`, `context`) run from the local copy — no npm dependency needed.
|
|
32
|
+
|
|
33
|
+
Updates come from git tags via `npx baseline update`, not from npm.
|
|
34
|
+
|
|
35
|
+
## What Gets Created
|
|
36
|
+
|
|
37
|
+
```
|
|
38
|
+
your-system/
|
|
39
|
+
├── CLAUDE.md # Claude Code automation (don't edit)
|
|
40
|
+
├── baseline.config.json # Version tracking
|
|
41
|
+
├── skills/ # 12 domain expertise modules
|
|
42
|
+
├── context/ # Your business knowledge (you own this)
|
|
43
|
+
├── frameworks/ # Reusable methodologies
|
|
44
|
+
├── scripts/ # Delivery to external tools
|
|
45
|
+
└── cli/ # Bundled CLI for daily use
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
## Learn More
|
|
49
|
+
|
|
50
|
+
See the [Baseline System documentation](https://github.com/TrentM6/baseline-core#readme) for the full guide — skills, context, frameworks, scripts, and tool-by-tool usage instructions.
|
|
51
|
+
|
|
52
|
+
## License
|
|
53
|
+
|
|
54
|
+
MIT
|
package/dist/index.js
CHANGED
|
@@ -9,7 +9,7 @@ const program = new commander_1.Command();
|
|
|
9
9
|
program
|
|
10
10
|
.name("baseline")
|
|
11
11
|
.description("Distribute and update the Baseline System")
|
|
12
|
-
.version("2.2.
|
|
12
|
+
.version("2.2.3");
|
|
13
13
|
program
|
|
14
14
|
.command("status")
|
|
15
15
|
.description("Show current version and check for updates")
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@baseline-studio/cli",
|
|
3
|
-
"version": "2.2.
|
|
3
|
+
"version": "2.2.3",
|
|
4
4
|
"description": "CLI for distributing and updating the Baseline System — an AI-powered workflow system for product teams",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"baseline",
|
|
@@ -26,7 +26,8 @@
|
|
|
26
26
|
},
|
|
27
27
|
"files": [
|
|
28
28
|
"bin/",
|
|
29
|
-
"dist/"
|
|
29
|
+
"dist/",
|
|
30
|
+
"README.md"
|
|
30
31
|
],
|
|
31
32
|
"scripts": {
|
|
32
33
|
"build": "tsc",
|