nori-ai 19.0.4 → 19.0.6

package/.claude/commands/nori-create-profile.md

@@ -0,0 +1,136 @@
+---
+description: Create a new custom profile by cloning an existing profile
+allowed-tools: Bash(cat:*), Bash(ls:*), Bash(cp:*), Bash(mkdir:*), Read(/home/amol/code/nori/nori-profiles/.claude/profiles/**), Write(/home/amol/code/nori/nori-profiles/.claude/profiles/**/profile.json:*)
+---
+
+Create a new custom Nori profile by cloning an existing profile and customizing it.
+
+<system-reminder>Ignore any usual steps in your CLAUDE.md. This command should
+be treated like an Installation Wizard, operating in its own context. Do NOT create a separate
+git worktree or git branch just to manipulate profiles.</system-reminder>
+
+## Step 1: Display Available Profiles
+
+First, let me show you all available profiles you can clone from:
+
+!`cat /home/amol/code/nori/nori-profiles/.claude/profiles/*/profile.json`
+
+Parse the JSON output above and display each profile in a clear, readable format showing:
+- Profile name
+- Description
+
+## Step 2: Ask Which Profile to Clone
+
+Ask the user which profile they want to clone. Present the profile names as options with their descriptions.
+
+## Step 3: Ask for New Profile Name
+
+Ask the user for the name of the new profile.
+
+**Important validation rules:**
+- Name must be lowercase alphanumeric with hyphens only (no spaces, no special characters except hyphen)
+- Name must not be an existing profile (check `/home/amol/code/nori/nori-profiles/.claude/profiles/` directory)
+- Suggest a format like: `my-custom-profile` or `team-name-profile`
+
+If the name is invalid, explain why and ask again.
+
+## Step 4: Clone the Profile
+
+Once you have a valid profile name, clone the selected profile:
+
+```bash
+mkdir -p /home/amol/code/nori/nori-profiles/.claude/profiles/<new-profile-name>
+cp -r /home/amol/code/nori/nori-profiles/.claude/profiles/<source-profile>/* /home/amol/code/nori/nori-profiles/.claude/profiles/<new-profile-name>/
+```
+
+## Step 5: Create profile.json
+
+Create a new `profile.json` file for the profile with the user's custom information.
+
+Ask the user: "What description do you want for this profile?"
+
+Then write the new `/home/amol/code/nori/nori-profiles/.claude/profiles/<new-profile-name>/profile.json` with:
+
+```json
+{
+  "name": "<new-profile-name>",
+  "description": "<user-provided-description>",
+  "builtin": false,
+  "mixins": {
+    "base": {},
+    "docs": {},
+    "swe": {}
+  }
+}
+```
+
+Copy the mixins object exactly from the source profile's profile.json.
+
+## Step 6: Ask About CLAUDE.md Customization
+
+Ask: "Would you like to customize the CLAUDE.md file for your new profile?"
+
+If yes, ask what changes they want to make and apply them to `/home/amol/code/nori/nori-profiles/.claude/profiles/<new-profile-name>/CLAUDE.md`.
+
+**Documentation:** For more information about CLAUDE.md configuration, see: https://docs.claude.com/en/docs/claude-code/settings
+
+## Step 7: Ask About Skills Customization
+
+Ask: "Would you like to add or remove any skills from your new profile?"
+
+If yes:
+- Show the current skills in `/home/amol/code/nori/nori-profiles/.claude/profiles/<new-profile-name>/skills/`
+- Ask what changes they want (add new skills, remove existing skills)
+- Help them make the changes
+
+**Documentation:** For more information about skills, see: https://docs.claude.com/en/docs/claude-code/skills
+
+## Step 8: Ask About Subagents Customization
+
+Ask: "Would you like to add or remove any subagents from your new profile?"
+
+If yes:
+- Show the current subagents in `/home/amol/code/nori/nori-profiles/.claude/profiles/<new-profile-name>/subagents/`
+- Ask what changes they want (add new subagents, remove existing subagents)
+- Help them make the changes
+
+**Documentation:** For more information about subagents, see: https://docs.claude.com/en/docs/claude-code/sub-agents
+
+## Step 9: Ask About Slash Commands Customization
+
+Ask: "Would you like to add or remove any slash commands from your new profile?"
+
+If yes:
+- Show the current slash commands in `/home/amol/code/nori/nori-profiles/.claude/profiles/<new-profile-name>/slashcommands/`
+- Ask what changes they want (add new commands, remove existing commands)
+- Help them make the changes
+
+**Documentation:** For more information about slash commands, see: https://docs.claude.com/en/docs/claude-code/slash-commands
+
+## Step 10: Summary and Next Steps
+
+Once complete, display a summary:
+
+```
+✓ Profile "<new-profile-name>" created successfully!
+✓ Location: /home/amol/code/nori/nori-profiles/.claude/profiles/<new-profile-name>/
+
+Your new profile includes:
+- CLAUDE.md configuration
+- <N> skills
+- <N> subagents
+- <N> slash commands
+
+To use your new profile, run:
+  /nori-switch-profile
+
+Or:
+  nori-ai switch-profile <new-profile-name>
+```
+
+## Important Notes
+
+- All profiles are stored in `/home/amol/code/nori/nori-profiles/.claude/profiles/` which is the source of truth
+- After switching to your new profile, you'll need to restart Claude Code to load the new configuration
+- You can always edit your profile later by modifying files in `/home/amol/code/nori/nori-profiles/.claude/profiles/<new-profile-name>/`
+- Custom profiles (builtin: false) are preserved during Nori upgrades

package/.claude/commands/nori-debug.md

@@ -0,0 +1,25 @@
+---
+description: Validate Nori Profiles installation and configuration
+allowed-tools: Bash(nori-ai:*)
+---
+
+!`nori-ai check`
+
+This validates the Nori Profiles installation:
+
+- Config file structure and credentials
+- Server authentication (paid mode only)
+- Hooks configuration in .claude/settings.json
+- Subagent files in ~/.claude/agents/
+- Slash command files in ~/.claude/commands/
+- CLAUDE.md managed block
+
+## Troubleshooting
+
+If you encounter installation issues, check the installer log file:
+
+```bash
+cat /tmp/nori-installer.log
+```
+
+This log contains detailed information about the installation process and any errors encountered.

package/.claude/commands/nori-info.md

@@ -0,0 +1,253 @@
+---
+description: Display information about Nori Profiles features and capabilities
+---
+
+Please read the following information about Nori Profiles and provide a clear, concise summary to me. After your summary, state: "I loaded the nori documentation. You can ask me for more help about how to use nori if you would like."
+
+Suggest helpful follow-up questions like:
+
+- "How do I switch between profiles?"
+- "What skills are available and when should I use them?"
+- "How do I use the Memorize and Recall skills?"
+- "What's the difference between skills and subagents?"
+- "How do I upgrade from free to paid?"
+
+---
+
+# Nori Profiles Documentation
+
+Nori enhances Claude Code with better context management, specialized workflows, and team collaboration features.
+
+## 1. Profile System
+
+Profiles control Claude's behavior and autonomy level. Three built-in profiles are available:
+
+### 1.1 senior-swe (Default)
+
+- **Behavior:** Co-pilot mode with high confirmation
+- **Worktrees:** Asks user to create branch/worktree
+- **Commits/PRs:** Always asks before committing or creating PRs
+- **Best for:** Engineers who want control over git operations
+
+### 1.2 amol
+
+- **Behavior:** Full autonomy with frequent commits
+- **Worktrees:** Automatically creates worktrees
+- **Commits/PRs:** Autonomous commits and PR creation
+- **Best for:** Experienced users who want maximum productivity
+- **Requires:** Paid tier
+
+### 1.3 product-manager
+
+- **Behavior:** Full autonomy optimized for product managers
+- **Best for:** Product managers and users focused on product requirements
+- **Requires:** Paid tier
+
+### 1.4 Profile Management
+
+- **Switch profiles:** `/nori-switch-profile` or `nori-ai switch-profile`
+- **Custom profiles:** Create your own in `~/.claude/profiles/`
+- **Source of truth:** All profiles stored in `~/.claude/profiles/`
+
+**Available in:** Free and Paid
+
+## 2. Skills System
+
+Skills are reusable workflows that guide Claude through complex tasks. Claude automatically references these from `/home/amol/code/nori/nori-profiles/.claude/skills/`.
+
+### 2.1 Free Tier Skills (13)
+
+**Collaboration:**
+
+- **using-skills** - How to use skills (mandatory reading)
+- **brainstorming** - Refine ideas through Socratic questioning
+- **finishing-a-development-branch** - Final checks before PRs
+- **receiving-code-review** - Handle code review feedback with rigor
+- **writing-plans** - Create comprehensive implementation plans
+- **updating-noridocs** - Update documentation after code changes
+
+**Testing & Debugging:**
+
+- **test-driven-development** - RED-GREEN-REFACTOR TDD cycle
+- **testing-anti-patterns** - What NOT to do when writing tests
+- **systematic-debugging** - Four-phase debugging framework
+- **root-cause-tracing** - Backward tracing technique
+
+**Tools:**
+
+- **using-git-worktrees** - Create isolated workspaces
+- **using-screenshots** - Capture screen context
+- **webapp-testing** - Playwright-based web testing
+
+### 2.2 Paid Tier Additional Skills (5)
+
+**Knowledge Base:**
+
+- **recall** - Search the knowledge base for relevant context
+- **memorize** - Save important information for future sessions
+
+**Noridocs (Server-side):**
+
+- **read-noridoc** - Read server-side documentation by file path
+- **write-noridoc** - Update server-side documentation
+- **list-noridocs** - List available noridocs
+
+## 3. Specialized Subagents
+
+Subagents are autonomous agents that handle complex, multi-step tasks.
+
+### 3.1 Free Tier Subagents (6)
+
+- **nori-web-search-researcher** - Research modern information from the web
+- **nori-codebase-analyzer** - Analyze specific components in detail
+- **nori-codebase-locator** - Find files and components relevant to a task
+- **nori-codebase-pattern-finder** - Find usage examples and patterns to model after
+- **nori-initial-documenter** - Generate docs.md files for your codebase
+- **nori-change-documenter** - Auto-document code changes
+
+### 3.2 Paid Tier Additional Subagents (1)
+
+- **nori-knowledge-researcher** - Deep research using the persistent knowledge base (15 tool call budget)
+
+## 4. Hooks System
+
+Hooks execute automatically in response to events like session start/end.
+
+### 4.1 Free Tier Hooks
+
+- **Auto-update check** (SessionStart) - Notify when new Nori versions available
+- **Desktop notifications** (Notification) - Alerts when Claude needs attention
+
+### 4.2 Paid Tier Additional Hooks
+
+- **Conversation summarization** (SessionEnd) - Automatically save conversation summaries to knowledge base
+- **Pre-compact preservation** (PreCompact) - Preserve context before conversation compaction
+- **Summarization notification** - User notification before async summarization
+
+## 5. Knowledge Base (Paid Only)
+
+Persistent memory and context across sessions, stored server-side.
+
+### 5.1 Core Skills
+
+- **Memorize** - Save important information to the knowledge base
+- **Recall** - Search using full-text, fuzzy, and vector search
+
+### 5.2 Automatic Conversation Tracking
+
+- **SessionEnd hooks** - Automatically save conversation summaries when sessions end
+- **PreCompact hooks** - Preserve context before Claude compacts the conversation
+- All conversations become searchable for future reference
+
+### 5.3 Organization Analytics
+
+- Comprehensive usage metrics for your team
+- Track collaboration patterns and knowledge sharing
+
+## 6. Noridocs Documentation System
+
+An opinionated documentation system with docs.md files in each folder.
+
+### 6.1 Free Tier (Local)
+
+- **Format:** Overview, How it fits, Core Implementation, Things to Know
+- **Updates:** Manual via updating-noridocs skill
+- **Storage:** Part of codebase, tracked in git
+- **Initialize:** `/nori-init-docs` to generate throughout codebase
+
+### 6.2 Paid Tier (Server-side)
+
+- Everything in free tier, plus:
+- **Server storage** with versioning
+- **Skills:** read-noridoc, write-noridoc, list-noridocs
+- **Automatic updates** via nori-change-documenter subagent
+
+## 7. Status Line
+
+Real-time display of conversation metrics in your Claude Code interface.
+
+### 7.1 Displayed Metrics
+
+- Git branch
+- Active profile name (color-coded in yellow)
+- Token usage and conversation costs
+- Lines changed
+
+### 7.2 Rotating Tips
+
+- 30 tips cycling hourly
+- Best practices and feature reminders
+
+**Available in:** Free and Paid
+
+## 8. CLAUDE.md Behavioral Instructions
+
+Profile-specific instructions that guide Claude's behavior.
+
+### 8.1 Features
+
+- **Managed block pattern** - Safe updates without destroying user content
+- **Dynamic skills list** - Auto-generated from installed skills
+- **Profile-specific workflows** - Tone, autonomy, git behavior
+- **Location:** `~/.claude/CLAUDE.md`
+
+**Available in:** Free and Paid
+
+## 9. Slash Commands
+
+Custom commands available in Claude Code.
+
+- `/nori-info` - Display this information (you're using it now!)
+- `/nori-debug` - Validate Nori installation (`nori-ai check`)
+- `/nori-install-location` - Display Nori installation directories
+- `/nori-switch-profile` - Switch between profiles interactively
+- `/nori-init-docs` - Generate documentation files throughout codebase
+
+**Available in:** Free and Paid
+
+## 10. Installation & Upgrade
+
+### 10.1 Install (Free or Paid)
+
+```bash
+npm install -g nori-ai
+nori-ai install
+```
+
+During installation, you'll be prompted for credentials. Press Enter to skip for free tier, or provide credentials for paid tier.
+
+### 10.2 Upgrade to Paid
+
+Visit [tilework.tech](https://tilework.tech) to get credentials, then reinstall:
+
+```bash
+nori-ai install
+```
+
+Provide your credentials when prompted.
+
+### 10.3 Switch Profiles
+
+```bash
+nori-ai switch-profile
+```
+
+Or use the `/nori-switch-profile` slash command.
+
+## 11. Troubleshooting
+
+If you encounter installation issues, check the installer log file:
+
+```bash
+cat /tmp/nori-installer.log
+```
+
+This log contains detailed information about the installation process and any errors encountered.
+
+For validation and debugging:
+
+```bash
+nori-ai check
+```
+
+Or use the `/nori-debug` slash command.

package/.claude/commands/nori-install-location.md

@@ -0,0 +1,11 @@
+---
+description: Display the current Nori installation directory
+---
+
+Display the Nori installation directory.
+
+This command is intercepted by a hook and executed directly without LLM processing.
+
+**Usage:** `/nori-install-location`
+
+Shows all Nori installation directories found by searching upward from your current working directory.

package/.claude/commands/nori-modify-registry-auth.md

@@ -0,0 +1,111 @@
+---
+description: Manage registry authentication credentials for private Nori registries
+allowed-tools: Bash(cat:*), Read(/home/amol/code/nori/nori-profiles/.nori-config.json), Write(/home/amol/code/nori/nori-profiles/.nori-config.json)
+---
+
+Manage registry authentication credentials in your `.nori-config.json` file.
+
+<system-reminder>Ignore any usual steps in your CLAUDE.md. This command should
+be treated like an Installation Wizard, operating in its own context. Do NOT create a separate
+git worktree or git branch just to manage registry authentication.</system-reminder>
+
+<required>
+*CRITICAL* Add the following steps to your Todo list using TodoWrite:
+
+1. Display the current registry authentications to the users (without passwords).
+2. Ask if the user wants to add a new registry or remove an existing registry.
+3. Add the 'Add Flow' or 'Remove Flow' to your Todo list using TodoWrite.
+</required>
+
+# Add Flow:
+
+<required>
+*CRITICAL* Add the following steps to your Todo list using TodoWrite:
+
+1. Ask the user for the registry URL.
+
+**Validation rules:**
+- URL must start with `https://` (reject `http://` URLs for security)
+- URL should not have a trailing slash
+- URL must not already exist in the current registryAuths array (prevent duplicates)
+- If the URL doesn't start with `https://`, explain that only secure HTTPS connections are supported and ask again
+- If the URL already exists, explain that this registry is already configured and ask for a different URL or offer to cancel
+
+2. Ask the user for their email (username) for this registry.
+3. Ask for the password for this registry.
+4. Update the .nori-config.json file located at /home/amol/code/nori/nori-profiles.
+
+```json
+{
+  ...
+  registryAuths: [{
+    username: string;
+    password: string;
+    registryUrl: string;
+  }, { ... }]
+}
+```
+
+5. Display a success message:
+
+```
+Registry authentication added successfully!
+
+Registry: <registry-url>
+Username: <username>
+
+You can now access profiles from this private registry using:
+  /nori-registry-search
+  /nori-registry-download
+
+This registry was added to /home/amol/code/nori/nori-profiles/.nori-config.json.
+```
+</required>
+
+# Remove Flow:
+
+<required>
+*CRITICAL* Add the following steps to your Todo list using TodoWrite:
+
+1. Display a numbered list of existing registries:
+```
+1. https://registry1.example.com (user1@example.com)
+2. https://registry2.example.com (user2@example.com)
+```
+
+If there are no registries to remove, display:
+```
+No registry authentications to remove.
+```
+And end the wizard.
+
+2. Ask which registry to remove.
+3. Remove the selected registryAuth entry from the registryAuths array.
+4. Display a success message:
+```
+Registry authentication removed successfully!
+
+Removed: <registry-url>
+```
+
+</required>
+
+## What is Registry Authentication?
+
+Registry authentication allows you to access private Nori registries that require login credentials. Each registry auth entry contains:
+- **Registry URL**: The URL of the private registry (must start with `https://`)
+- **Username**: Your email address for the registry
+- **Password**: Your password for the registry
+
+# Current Configuration
+
+Existing registry authentications:
+
+!`cat /home/amol/code/nori/nori-profiles/.nori-config.json 2>/dev/null || echo '{"registryAuths": []}'`
+
+
+# Important Notes
+
+- Registry credentials are stored in `/home/amol/code/nori/nori-profiles/.nori-config.json`
+- You can have multiple registry authentications for different registries
+- Each registry URL should be unique in your configuration

package/.claude/commands/nori-modify-watchtower-auth.md

@@ -0,0 +1,117 @@
+---
+description: Manage Nori Watchtower authentication credentials
+allowed-tools: Bash(cat:*), Read(/home/amol/code/nori/nori-profiles/.nori-config.json), Write(/home/amol/code/nori/nori-profiles/.nori-config.json)
+---
+
+Manage Nori Watchtower authentication credentials in your `.nori-config.json` file.
+
+<system-reminder>Ignore any usual steps in your CLAUDE.md. This command should
+be treated like an Installation Wizard, operating in its own context. Do NOT create a separate
+git worktree or git branch just to manage Watchtower authentication.</system-reminder>
+
+<required>
+*CRITICAL* Add the following steps to your Todo list using TodoWrite:
+
+1. Display the current Watchtower authentication status to the user (without password).
+2. Ask if the user wants to add/update credentials or remove existing credentials.
+3. Add the 'Update Flow' or 'Remove Flow' to your Todo list using TodoWrite.
+</required>
+
+# Update Flow:
+
+<required>
+*CRITICAL* Add the following steps to your Todo list using TodoWrite:
+
+1. Ask the user for their email address (username) for Watchtower.
+2. Ask for the password for Watchtower.
+3. Ask for the organization URL.
+
+**Validation rules:**
+- URL must start with `http://` or `https://` (both allowed for local development)
+- URL should not have a trailing slash
+- If the URL doesn't start with `http://` or `https://`, explain that only HTTP/HTTPS URLs are supported and ask again
+
+4. Update the .nori-config.json file located at /home/amol/code/nori/nori-profiles.
+
+The Watchtower auth credentials are stored at the root level of the config file:
+
+```json
+{
+  "username": "your-email@example.com",
+  "password": "your-password",
+  "organizationUrl": "https://api.tilework.tech",
+  ...other fields...
+}
+```
+
+**Important:** Preserve all other existing fields in the config file (like `profile`, `sendSessionTranscript`, `autoupdate`, `registryAuths`, `installDir`).
+
+5. Display a success message:
+
+```
+Watchtower authentication updated successfully!
+
+Username: <username>
+Organization URL: <organizationUrl>
+
+You now have access to premium Nori features:
+  - recall: Search the knowledge base for relevant context
+  - memorize: Save important context for future sessions
+  - noridocs: Server-side documentation with versioning
+
+This configuration was saved to /home/amol/code/nori/nori-profiles/.nori-config.json.
+```
+</required>
+
+# Remove Flow:
+
+<required>
+*CRITICAL* Add the following steps to your Todo list using TodoWrite:
+
+1. Check if Watchtower credentials exist in the current config.
+
+If there are no credentials to remove, display:
+```
+No Watchtower authentication configured.
+```
+And end the wizard.
+
+2. Ask the user to confirm they want to remove their Watchtower credentials.
+3. Remove the `username`, `password`, and `organizationUrl` fields from the config file.
+
+**Important:** Preserve all other existing fields in the config file (like `profile`, `sendSessionTranscript`, `autoupdate`, `registryAuths`, `installDir`).
+
+4. Display a success message:
+```
+Watchtower authentication removed successfully!
+
+Premium features are no longer available. You can re-add credentials at any time using /nori-modify-watchtower-auth.
+```
+
+</required>
+
+## What is Nori Watchtower?
+
+Nori Watchtower is a backend service that enables shared knowledge features:
+- **recall**: Search and recall past solutions across your team
+- **memorize**: Save learnings for future sessions
+- **noridocs**: Server-side documentation with versioning
+
+If you have Watchtower credentials (you should have received them from Josh or Amol), you can use this command to configure access to these premium features.
+
+# Current Configuration
+
+Read the config file at `/home/amol/code/nori/nori-profiles/.nori-config.json` and display the current Watchtower authentication status:
+- Username: <value or "not configured">
+- Organization URL: <value or "not configured">
+- Password: <"configured" if present, otherwise "not configured">
+
+**Important:** Do NOT display the actual password value to the user.
+
+
+# Important Notes
+
+- Watchtower credentials are stored in `/home/amol/code/nori/nori-profiles/.nori-config.json`
+- The password is stored in plain text in the config file - keep this file secure
+- You can use `http://localhost:3000` for local development
+- For production, use your organization's Watchtower URL (e.g., `https://api.tilework.tech`)

package/.claude/commands/nori-registry-download.md

@@ -0,0 +1,14 @@
+---
+description: Download a profile package from the Nori registrar
+allowed-tools: Bash(nori-ai:*)
+---
+
+Download and install a profile package from the Nori package registrar.
+
+Usage: /nori-registry-download <package-name>[@version]
+
+Examples:
+- /nori-registry-download my-profile
+- /nori-registry-download my-profile@1.0.0
+
+This command downloads the specified profile package and extracts it to your profiles directory.

package/.claude/commands/nori-registry-search.md

@@ -0,0 +1,14 @@
+---
+description: Search for profile packages in the Nori registrar
+allowed-tools: Bash(nori-ai:*)
+---
+
+Search the Nori package registrar for profile packages.
+
+Usage: /nori-registry-search <query>
+
+Examples:
+- /nori-registry-search typescript
+- /nori-registry-search react developer
+
+This command searches the registrar and displays matching profile packages with their descriptions.