@claudetools/tools 0.9.0 → 0.9.1

package/dist/setup.js

@@ -21,6 +21,7 @@ const MCP_CONFIG_PATH = join(CLAUDE_DIR, 'mcp.json');
 const CLAUDE_DESKTOP_CONFIG_PATH = join(CLAUDE_DIR, 'claude_desktop_config.json');
 const SETTINGS_PATH = join(CLAUDE_DIR, 'settings.json');
 const HOOKS_DIR = join(CLAUDE_DIR, 'hooks');
+const COMMANDS_DIR = join(CLAUDE_DIR, 'commands');
 const CLAUDE_MD_PATH = join(CLAUDE_DIR, 'CLAUDE.md');
 const SYSTEM_FILE = join(CLAUDETOOLS_DIR, 'system.json');
 const PROJECTS_FILE = join(CLAUDETOOLS_DIR, 'projects.json');
@@ -920,6 +921,195 @@ exit 0
     writeFileSync(preCompactPath, preCompactHook, { mode: 0o755 });
     success('Installed pre-compact.sh hook');
 }
+// -----------------------------------------------------------------------------
+// Slash Commands Installation
+// -----------------------------------------------------------------------------
+const PROJECT_INIT_COMMAND = `---
+description: Initialize a new project with AI-driven onboarding
+model: claude-sonnet-4-5
+---
+
+# Project Onboarding
+
+Starting interactive onboarding for this project...
+
+## Instructions for Claude
+
+You are beginning an onboarding session for a new or existing project. Your goal is to:
+1. Gather project context through conversational questioning
+2. **Store ALL learned facts in the memory system immediately** (don't batch - store as you learn)
+3. **Cache documentation for libraries/frameworks mentioned** (using \`docs_cache\`)
+4. **Verify ClaudeTools integration is working correctly**
+
+### Phase 1: ClaudeTools Verification
+
+Before starting onboarding, verify the tooling is correctly set up:
+
+\`\`\`bash
+# Check session facts cache exists
+ls -la ~/.claudetools/session-facts.json
+
+# Check hooks are in place
+ls -la ~/.claude/hooks/
+
+# Verify MCP connection
+# (If memory_search works, MCP is connected)
+\`\`\`
+
+If any issues found, help the user fix their ClaudeTools setup before proceeding.
+
+### Phase 2: Onboarding Workflow
+
+**1. Check if project exists**
+- Use \`memory_search\` to check for existing project context
+- If exists, offer to update/extend vs start fresh
+
+**2. Start onboarding conversation**
+Ask about (store facts AS you learn them, not at the end):
+
+- **Project Type**: What kind of project? (web app, API, library, CLI, etc.)
+  → Store: \`[ProjectName] IS_TYPE [ProjectType]\`
+
+- **Tech Stack**: What technologies/frameworks?
+  → Store: \`[ProjectName] USES [Technology]\` for EACH technology
+  → **IMPORTANT**: Call \`docs_cache({ library: "technology-name" })\` for each library mentioned
+
+- **Architecture**: Key patterns, structure, decisions?
+  → Store: \`[ProjectName] USES_PATTERN [Pattern]\`
+  → Store: \`[Component] IMPLEMENTS [Pattern]\`
+
+- **Constraints**: Performance requirements, limitations, must-haves?
+  → Store: \`[ProjectName] HAS_CONSTRAINT [Constraint]\`
+
+- **External Integrations**: APIs, services, databases?
+  → Store: \`[ProjectName] INTEGRATES_WITH [Service]\`
+  → Call \`docs_cache\` if documentation available
+
+- **Development Practices**: Testing, CI/CD, code style?
+  → Store: \`[ProjectName] FOLLOWS [Practice]\`
+
+**3. Research when needed**
+If user mentions:
+- Existing specs/docs → Read and extract facts
+- External libraries → Cache docs with \`docs_cache({ library: "name" })\`
+- Existing code → Analyse patterns and store architectural decisions
+
+**4. Complete onboarding**
+- Summarise what was learned
+- Confirm with user before finalising
+- List all cached documentation
+
+### Memory Storage (CRITICAL)
+
+**Store facts IMMEDIATELY as you learn them, not at the end.**
+
+\`\`\`typescript
+// After learning tech stack
+memory_store_fact({
+  entity1: "MyProject",
+  relationship: "USES",
+  entity2: "React",
+  context: "Frontend framework chosen for component-based architecture"
+})
+
+// Immediately cache React docs
+docs_cache({ library: "react" })
+\`\`\`
+
+**Fact relationship types:**
+- \`IS_TYPE\` - Project classification
+- \`USES\` - Technologies, libraries, frameworks
+- \`USES_PATTERN\` - Architectural patterns
+- \`HAS_CONSTRAINT\` - Requirements, limitations
+- \`INTEGRATES_WITH\` - External services
+- \`FOLLOWS\` - Development practices
+- \`DEPENDS_ON\` - Critical dependencies
+- \`OWNED_BY\` - Team/ownership info
+
+### Documentation Caching
+
+For ANY library/framework mentioned, cache its docs:
+
+\`\`\`typescript
+// Cache documentation for mentioned technologies
+docs_cache({ library: "next.js" })
+docs_cache({ library: "prisma" })
+docs_cache({ library: "zod" })
+docs_cache({ library: "tanstack-query" })
+\`\`\`
+
+This enables future sessions to reference up-to-date documentation.
+
+### Code Generation Tools
+
+**IMPORTANT**: When the project involves APIs, frontends, or full-stack development, inform the user about available code generation tools that can save 95%+ tokens:
+
+**Kappa v2.5** - For full-stack applications:
+- Use when: Multiple entities, pages, forms, API routes
+- Tools: \`kappa_parse\`, \`kappa_generate_all\`, \`kappa_generate_schema\`, etc.
+- Generates: Drizzle schemas, Zod validators, API routes, pages, forms, design tokens
+
+**CodeDNA** - For individual components:
+- Use when: Single entity, specific component, or targeted generation
+- Tools: \`codedna_generate_api\`, \`codedna_generate_frontend\`, \`codedna_generate_component\`
+- Supports: Express, FastAPI, NestJS, Hono, React, Vue, SvelteKit
+
+During onboarding, if the user is building:
+- **Full-stack app with multiple entities** → Suggest Kappa: "For your Next.js app with User, Task, and Project entities, I can use Kappa to generate your entire backend and frontend from a compact spec. Would you like to see an example?"
+- **Single API or component** → Suggest CodeDNA: "For this API, I can use CodeDNA to generate the routes, validation, and types. This saves significant time and tokens."
+
+Store code generation preferences:
+\`\`\`typescript
+memory_store_fact({
+  entity1: "ProjectName",
+  relationship: "PREFERS",
+  entity2: "Kappa",
+  context: "User prefers Kappa for full-stack generation"
+})
+\`\`\`
+
+### Conversation Style
+
+- Be conversational, not interrogative
+- Explain WHY you're asking each question
+- Store facts immediately after each answer (don't wait)
+- Confirm what you've stored: "I've noted that you're using React for..."
+- Offer to skip questions if not relevant
+- Summarise understanding periodically
+
+### Troubleshooting ClaudeTools
+
+If MCP tools aren't available:
+1. Check \`~/.claudetools/config.json\` exists
+2. Verify Claude Code has MCP server configured
+3. Run \`/doctor\` command if available
+
+If hooks aren't triggering:
+1. Check \`~/.claude/hooks/\` directory
+2. Verify hook files are executable
+3. Check hook logs in \`/tmp/claude-*.log\`
+
+### User Request (if provided):
+
+$ARGUMENTS
+`;
+async function installSlashCommands() {
+    header('Slash Commands');
+    // Create commands/project directory
+    const projectCommandsDir = join(COMMANDS_DIR, 'project');
+    if (!existsSync(projectCommandsDir)) {
+        mkdirSync(projectCommandsDir, { recursive: true });
+    }
+    // Install project:init command
+    const initPath = join(projectCommandsDir, 'init.md');
+    if (existsSync(initPath)) {
+        const backup = backupFile(initPath);
+        if (backup)
+            info(`Backed up existing command to ${basename(backup)}`);
+    }
+    writeFileSync(initPath, PROJECT_INIT_COMMAND);
+    success('Installed /project:init slash command');
+}
 async function configureSettings() {
     header('Claude Code Settings');
     // Read existing settings
@@ -1244,11 +1434,13 @@ export async function runSetup() {
         await configureMcpSettings(services);
         // Step 8: Install Hooks
         await installHooks();
-        // Step 9: Configure Settings
+        // Step 9: Install Slash Commands
+        await installSlashCommands();
+        // Step 10: Configure Settings
         await configureSettings();
-        // Step 10: Configure CLAUDE.md
+        // Step 11: Configure CLAUDE.md
         await configureCLAUDEMD();
-        // Step 11: Verify
+        // Step 12: Verify
         await verifySetup(extendedConfig);
         // Done
         header('Setup Complete');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claudetools/tools",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "Persistent AI memory, task management, and codebase intelligence for Claude Code",
   "type": "module",
   "main": "dist/index.js",