lynxprompt 2.1.39 → 2.1.41
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 +59 -1
- package/dist/index.js +931 -477
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -70,6 +70,10 @@ lynxp wizard -f copilot # .github/copilot-instructions.md
|
|
|
70
70
|
# Generate multiple formats
|
|
71
71
|
lynxp wizard -f agents,cursor,copilot
|
|
72
72
|
|
|
73
|
+
# Next to AGENTS.md, CLAUDE.md and GEMINI.md just import it (@AGENTS.md);
|
|
74
|
+
# --no-pointers writes full copies instead
|
|
75
|
+
lynxp wizard -f agents,claude,gemini-cli
|
|
76
|
+
|
|
73
77
|
# Non-interactive with all options
|
|
74
78
|
lynxp wizard \
|
|
75
79
|
--name "my-api" \
|
|
@@ -91,8 +95,13 @@ lynxp check
|
|
|
91
95
|
|
|
92
96
|
# CI mode (exit code 0=pass, 1=fail)
|
|
93
97
|
lynxp check --ci
|
|
98
|
+
|
|
99
|
+
# The result as JSON: { valid, files, errors, warnings }
|
|
100
|
+
lynxp check --json
|
|
94
101
|
```
|
|
95
102
|
|
|
103
|
+
Besides empty files, placeholders and secrets, `check` fails on hidden Unicode: zero-width characters, bidi controls and tag characters that an agent reads as instructions but a reviewer cannot see. Each error names the line, column and code point. Emoji joiners, joiners inside Persian or Indic words and a byte order mark at the start of the file are not reported.
|
|
104
|
+
|
|
96
105
|
### Status (`lynxp status`)
|
|
97
106
|
|
|
98
107
|
Show current AI configuration and tracked blueprints:
|
|
@@ -109,6 +118,9 @@ Download and track a blueprint from the marketplace:
|
|
|
109
118
|
# Download and track
|
|
110
119
|
lynxp pull bp_abc123
|
|
111
120
|
|
|
121
|
+
# Several blueprints and hierarchies in one go
|
|
122
|
+
lynxp pull bp_abc123 bp_def456 ha_xyz789
|
|
123
|
+
|
|
112
124
|
# Push local file to cloud
|
|
113
125
|
lynxp push
|
|
114
126
|
|
|
@@ -117,8 +129,15 @@ lynxp pull bp_abc123 --preview
|
|
|
117
129
|
|
|
118
130
|
# Don't track for future syncs
|
|
119
131
|
lynxp pull bp_abc123 --no-track
|
|
132
|
+
|
|
133
|
+
# Fill [[VARIABLES]] as you download (others get their [[NAME|default]])
|
|
134
|
+
lynxp pull bp_abc123 --vars PROJECT_NAME=acme,TEAM=Platform
|
|
120
135
|
```
|
|
121
136
|
|
|
137
|
+
A file pulled with `--vars` stays tracked: `lynxp sync` refills cloud updates
|
|
138
|
+
with the same values, and `lynxp push` refuses to send your values over the
|
|
139
|
+
blueprint's variables unless you pass `--force`.
|
|
140
|
+
|
|
122
141
|
### Link / Unlink
|
|
123
142
|
|
|
124
143
|
Connect local files to cloud blueprints:
|
|
@@ -146,6 +165,27 @@ lynxp diff bp_abc123
|
|
|
146
165
|
lynxp diff --local
|
|
147
166
|
```
|
|
148
167
|
|
|
168
|
+
### Sync
|
|
169
|
+
|
|
170
|
+
Bring every tracked file and its cloud blueprint together in one step:
|
|
171
|
+
|
|
172
|
+
```bash
|
|
173
|
+
lynxp sync # all tracked files
|
|
174
|
+
lynxp sync AGENTS.md # one file
|
|
175
|
+
lynxp sync --dry-run # show what would happen, change nothing
|
|
176
|
+
```
|
|
177
|
+
|
|
178
|
+
For each file, sync compares the local file and the cloud with the version
|
|
179
|
+
you last pulled or pushed:
|
|
180
|
+
|
|
181
|
+
- only the cloud changed: the file is updated from the cloud
|
|
182
|
+
- only the file changed: your changes are pushed (marketplace blueprints are read-only, so they stay local)
|
|
183
|
+
- both changed: the cloud version is written to `<file>.remote` and your file is left alone.
|
|
184
|
+
Merge what you need into the file, delete `<file>.remote`, and run `lynxp sync` again.
|
|
185
|
+
Until then sync and push leave that file alone.
|
|
186
|
+
|
|
187
|
+
Sync exits with code 1 when a file has a conflict or could not be synced.
|
|
188
|
+
|
|
149
189
|
### Push (`lynxp push`)
|
|
150
190
|
|
|
151
191
|
Upload a local configuration file to LynxPrompt cloud:
|
|
@@ -168,6 +208,22 @@ lynxp push AGENTS.md \
|
|
|
168
208
|
lynxp push -y --name "My Config"
|
|
169
209
|
```
|
|
170
210
|
|
|
211
|
+
### Agent Skills and MCP servers
|
|
212
|
+
|
|
213
|
+
A skill's `SKILL.md` (in `.claude/skills/`, `.agents/skills/`, `.github/skills/`,
|
|
214
|
+
`.cursor/skills/`, `.gemini/skills/` or `.opencode/skills/`) and an MCP config
|
|
215
|
+
(`.mcp.json`, `.cursor/mcp.json`, `.vscode/mcp.json`, `.kiro/settings/mcp.json`)
|
|
216
|
+
push and pull like any rules file, and keep their path.
|
|
217
|
+
|
|
218
|
+
```bash
|
|
219
|
+
lynxp push .claude/skills/release-notes/SKILL.md
|
|
220
|
+
lynxp push .mcp.json
|
|
221
|
+
|
|
222
|
+
# The same MCP servers in another tool's file
|
|
223
|
+
lynxp convert .mcp.json vscode-mcp # .vscode/mcp.json, "servers" key
|
|
224
|
+
lynxp convert cursor-mcp # from the first MCP config found
|
|
225
|
+
```
|
|
226
|
+
|
|
171
227
|
### Search (`lynxp search`)
|
|
172
228
|
|
|
173
229
|
Search public blueprints in the marketplace:
|
|
@@ -175,6 +231,7 @@ Search public blueprints in the marketplace:
|
|
|
175
231
|
```bash
|
|
176
232
|
lynxp search "nextjs typescript"
|
|
177
233
|
lynxp search react --limit 10
|
|
234
|
+
lynxp search react --json
|
|
178
235
|
```
|
|
179
236
|
|
|
180
237
|
### List (`lynxp list`)
|
|
@@ -184,6 +241,7 @@ List your own blueprints:
|
|
|
184
241
|
```bash
|
|
185
242
|
lynxp list
|
|
186
243
|
lynxp list --visibility PUBLIC
|
|
244
|
+
lynxp list --json
|
|
187
245
|
```
|
|
188
246
|
|
|
189
247
|
### Authentication
|
|
@@ -192,7 +250,7 @@ lynxp list --visibility PUBLIC
|
|
|
192
250
|
# Login (opens browser for OAuth)
|
|
193
251
|
lynxp login
|
|
194
252
|
|
|
195
|
-
# Show current user
|
|
253
|
+
# Show current user (--json for scripts)
|
|
196
254
|
lynxp whoami
|
|
197
255
|
|
|
198
256
|
# Logout
|