claude-code-autoconfig 1.0.60 → 1.0.62

package/.claude/commands/autoconfig.md

@@ -101,9 +101,13 @@ This pointer persists across autoconfig runs and directs Claude to team-maintain
 
 ## Step 4: Create Rules Directory
 
-Create an empty `.claude/rules/` directory if it doesn't exist. Do not create any subdirectories or rule files.
+Create `.claude/rules/` directory if it doesn't exist by writing a `.gitkeep` file to it:
 
-**Important**: Use Glob tool to check if directories exist (e.g., `.claude/rules/**`), not Bash commands. This avoids permission prompts during setup.
+```
+Write .claude/rules/.gitkeep with empty content
+```
+
+**Important**: Use Write tool to create the directory (by creating a placeholder file), not `mkdir` Bash commands. This avoids permission prompts during setup.
 
 Rules are path-scoped context files that load automatically when Claude works on matching files. Effective rules require deep understanding of your codebase patterns, team conventions, and quality goals — they should be crafted intentionally, not auto-generated.
 

package/.claude/settings.json

@@ -27,9 +27,13 @@
       "Bash(ls:*)",
       "Bash(dir:*)",
       "Bash(mkdir:*)",
+      "Bash(mkdir -p:*)",
       "Bash(start:*)",
+      "Bash(start .claude:*)",
       "Bash(open:*)",
-      "Bash(xdg-open:*)"
+      "Bash(open .claude:*)",
+      "Bash(xdg-open:*)",
+      "Bash(xdg-open .claude:*)"
     ],
     "deny": [
       "Read(./.env)",

package/bin/cli.js

@@ -235,14 +235,17 @@ console.log('\x1b[32m%s\x1b[0m', '✅ Prepared /autoconfig command');
 
 // Step 4: Show "READY TO CONFIGURE" message
 console.log();
-console.log('\x1b[33m╔════════════════════════════════════╗');
-console.log('║                                    ║');
-console.log('║         \x1b[1mREADY TO CONFIGURE\x1b[22m         ║');
-console.log('║                                    ║');
-console.log('║\x1b[0m   Press ENTER to launch Claude     \x1b[33m║');
-console.log('║\x1b[0m   and auto-run \x1b[36m/autoconfig\x1b[33m         \x1b[33m║');
-console.log('║                                    ║');
-console.log('╚════════════════════════════════════╝\x1b[0m');
+console.log('\x1b[33m╔════════════════════════════════════════════╗');
+console.log('║                                            ║');
+console.log('║           \x1b[1mREADY TO CONFIGURE\x1b[22m               ║');
+console.log('║                                            ║');
+console.log('║\x1b[0m   Press ENTER to launch Claude and         \x1b[33m║');
+console.log('║\x1b[0m   auto-run \x1b[36m/autoconfig\x1b[33m                      \x1b[33m║');
+console.log('║                                            ║');
+console.log('║\x1b[0m   \x1b[90mFirst run: approve 2-3 file prompts\x1b[33m       ║');
+console.log('║\x1b[0m   \x1b[90mSubsequent runs: fully automated\x1b[33m          ║');
+console.log('║                                            ║');
+console.log('╚════════════════════════════════════════════╝\x1b[0m');
 console.log();
 
 // Step 5: Wait for Enter, then launch Claude Code

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-autoconfig",
-  "version": "1.0.60",
+  "version": "1.0.62",
   "description": "Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.",
   "author": "ADAC 1001 <info@adac1001.com>",
   "license": "MIT",