figura-cli 0.9.0 → 0.10.0
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 +55 -2
- package/dist/index.js +205 -109
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -100,8 +100,26 @@ the CLI, so they stay in lockstep.
|
|
|
100
100
|
|
|
101
101
|
## MCP server
|
|
102
102
|
|
|
103
|
-
The Figura MCP server ships inside the CLI — no separate install.
|
|
104
|
-
|
|
103
|
+
The Figura MCP server ships inside the CLI — no separate install. The easiest way
|
|
104
|
+
to set a repo up is to log in with `--project`, which does the whole thing from
|
|
105
|
+
one command:
|
|
106
|
+
|
|
107
|
+
```bash
|
|
108
|
+
figura login --project
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
From the current directory it writes `.figura/config.json` (your token), adds
|
|
112
|
+
`.figura/` to `.gitignore`, registers the server in a `.mcp.json` at the repo root
|
|
113
|
+
(so Claude Code discovers it on the next start and prompts you to enable it — no
|
|
114
|
+
manual `claude mcp add`), installs the `/fig` and `/figura-brand` skills into
|
|
115
|
+
`.claude/skills`, and prints a readiness checklist. Pass `--no-mcp` or
|
|
116
|
+
`--no-skills` to skip those steps.
|
|
117
|
+
|
|
118
|
+
`.mcp.json` and `.claude/skills` hold only launch commands / skill files, never a
|
|
119
|
+
token, so they're safe to commit and share with your team — each teammate just
|
|
120
|
+
runs their own `figura login --project` for the credential.
|
|
121
|
+
|
|
122
|
+
To register the MCP yourself instead:
|
|
105
123
|
|
|
106
124
|
```bash
|
|
107
125
|
claude mcp add figura -- figura mcp
|
|
@@ -112,6 +130,41 @@ resolves your token from the nearest `.figura/config.json` (see _Multiple teams_
|
|
|
112
130
|
above), so the MCP uses the right team per project automatically. (The
|
|
113
131
|
`bunx -y figura-mcp` form still works if you'd rather not install the CLI.)
|
|
114
132
|
|
|
133
|
+
## Staying up to date
|
|
134
|
+
|
|
135
|
+
The MCP and skills ship inside the CLI, so a stale `figura-cli` means a stale MCP
|
|
136
|
+
and stale skills. Check anytime with:
|
|
137
|
+
|
|
138
|
+
```bash
|
|
139
|
+
figura doctor # installed vs latest; flags a behind CLI or drifted skills
|
|
140
|
+
figura update # update the CLI + reinstall the skills
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
To automate it, install the Claude Code hook (`figura login --project` does this
|
|
144
|
+
for you):
|
|
145
|
+
|
|
146
|
+
```bash
|
|
147
|
+
figura hook install # add a SessionStart check to ~/.claude/settings.json
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
On each launch it checks — at most once a day, cached, and always in the
|
|
151
|
+
background — whether anything is behind, reinstalls drifted skills in place, and
|
|
152
|
+
kicks off `figura update` if the CLI is stale. It never blocks startup and stays
|
|
153
|
+
silent when everything is current. Remove it with `figura hook install --uninstall`.
|
|
154
|
+
|
|
155
|
+
## Status-bar badge
|
|
156
|
+
|
|
157
|
+
Show a `⬡ figura <version>` badge in the Claude Code status bar (a `↑` appears
|
|
158
|
+
when an update is waiting):
|
|
159
|
+
|
|
160
|
+
```bash
|
|
161
|
+
figura statusline install # --uninstall to remove
|
|
162
|
+
```
|
|
163
|
+
|
|
164
|
+
It never replaces an existing statusline — if you already run one (e.g. a caveman
|
|
165
|
+
badge), it *wraps* it, so both show: `[CAVEMAN] … · ⬡ figura 0.9.0`. `figura login
|
|
166
|
+
--project` installs it for you.
|
|
167
|
+
|
|
115
168
|
## Usage
|
|
116
169
|
|
|
117
170
|
```bash
|