claude-code-autoconfig 1.0.86 → 1.0.87
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.
|
@@ -309,14 +309,17 @@ NEVER guess the root cause and jump to coding a fix. Ask yourself: is the cause
|
|
|
309
309
|
|
|
310
310
|
## Step 8: Update the Docs
|
|
311
311
|
|
|
312
|
-
After populating CLAUDE.md, update the docs file
|
|
312
|
+
After populating CLAUDE.md, update the docs file previews to show actual project content:
|
|
313
313
|
|
|
314
314
|
1. Open `.claude/docs/autoconfig.docs.html`
|
|
315
|
-
2. Find the `fileContents` JavaScript object
|
|
316
|
-
3.
|
|
315
|
+
2. Find the `fileContents` JavaScript object
|
|
316
|
+
3. Update these entries with the real content just generated:
|
|
317
|
+
- `'claude-md'` → the CLAUDE.md content from Step 3
|
|
318
|
+
- `'memory-md'` → the MEMORY.md content from Step 7
|
|
319
|
+
- `'settings'` → the settings.json content from Step 6
|
|
317
320
|
4. Use template literal syntax and escape any backticks in the content
|
|
318
321
|
|
|
319
|
-
This ensures double-clicking
|
|
322
|
+
This ensures double-clicking these files in the docs shows real project content, not stale placeholders.
|
|
320
323
|
|
|
321
324
|
## After Completion
|
|
322
325
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "claude-code-autoconfig",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.87",
|
|
4
4
|
"description": "Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.",
|
|
5
5
|
"author": "ADAC 1001 <info@adac1001.com>",
|
|
6
6
|
"license": "MIT",
|
|
@@ -35,6 +35,7 @@
|
|
|
35
35
|
".claude",
|
|
36
36
|
"!.claude/settings.local.json",
|
|
37
37
|
"!.claude/commands/publish.md",
|
|
38
|
+
"!.claude/commands/gls.md",
|
|
38
39
|
"CLAUDE.md"
|
|
39
40
|
],
|
|
40
41
|
"engines": {
|
package/.claude/commands/gls.md
DELETED
|
@@ -1,21 +0,0 @@
|
|
|
1
|
-
Get the latest screenshot(s) from the Screenshots folder and display them.
|
|
2
|
-
|
|
3
|
-
Usage:
|
|
4
|
-
- `/gls` - Get and display the most recent screenshot
|
|
5
|
-
- `/gls-2` - Get and display the 2 most recent screenshots
|
|
6
|
-
- `/gls-3` - Get and display the 3 most recent screenshots
|
|
7
|
-
- `/gls-N` - Get and display the N most recent screenshots
|
|
8
|
-
|
|
9
|
-
Screenshot directory: `C:\Users\andre\OneDrive\Pictures\Screenshots 1`
|
|
10
|
-
|
|
11
|
-
Workflow:
|
|
12
|
-
1. List all files in the screenshots directory sorted by modification time (newest first)
|
|
13
|
-
2. If command is `/gls`, get the most recent screenshot (1 file)
|
|
14
|
-
3. If command is `/gls-N` (e.g., `/gls-2`), get the N most recent screenshots
|
|
15
|
-
4. Use the Read tool to display each screenshot
|
|
16
|
-
5. Wait for the user to tell you what to do with the screenshot(s)
|
|
17
|
-
|
|
18
|
-
Important:
|
|
19
|
-
- Always use the Read tool to display screenshots (not Bash cat/echo)
|
|
20
|
-
- Display screenshots in order from newest to oldest
|
|
21
|
-
- After displaying, wait for user instructions - don't make assumptions about what they want done with the screenshots
|