gsd-pi 2.20.0 → 2.22.0

package/README.md

@@ -242,6 +242,8 @@ On first run, GSD launches a branded setup wizard that walks you through LLM pro
 | `/gsd migrate`          | Migrate a v1 `.planning` directory to `.gsd` format             |
 | `/gsd help`             | Categorized command reference for all GSD subcommands           |
 | `/gsd mode`             | Switch workflow mode (solo/team) with coordinated defaults      |
+| `/gsd forensics`        | Post-mortem investigation of auto-mode failures                 |
+| `/gsd cleanup`          | Archive phase directories from completed milestones             |
 | `/gsd doctor`           | Runtime health checks with auto-fix for common issues           |
 | `/worktree` (`/wt`)     | Git worktree lifecycle — create, switch, merge, remove          |
 | `/voice`                | Toggle real-time speech-to-text (macOS, Linux)                  |
@@ -355,7 +357,17 @@ unique_milestone_ids: true
 | `uat_dispatch`         | Enable automatic UAT runs after slice completion                                                      |
 | `always_use_skills`    | Skills to always load when relevant                                                                   |
 | `skill_rules`          | Situational rules for skill routing                                                                   |
+| `skill_staleness_days` | Skills unused for N days get deprioritized (default: 60, 0 = disabled)                                |
 | `unique_milestone_ids` | Uses unique milestone names to avoid clashes when working in teams of people                          |
+| `git.isolation`        | `worktree` (default) or `none` — disable worktree isolation for projects that don't need it           |
+
+### Agent Instructions
+
+Create an `agent-instructions.md` file in your project root to inject persistent per-project behavioral guidance into every agent session. This file is loaded automatically and provides project-specific context the LLM should always have — coding standards, architectural decisions, domain terminology, or workflow preferences.
+
+### Debug Mode
+
+Start GSD with `gsd --debug` to enable structured JSONL diagnostic logging. Debug logs capture dispatch decisions, state transitions, and timing data for troubleshooting auto-mode issues.
 
 ### Token Optimization (v2.17)
 

package/dist/cli.js

@@ -9,6 +9,7 @@ import { getPiDefaultModelAndProvider, migratePiCredentials } from './pi-migrati
 import { shouldRunOnboarding, runOnboarding } from './onboarding.js';
 import chalk from 'chalk';
 import { checkForUpdates } from './update-check.js';
+import { printHelp, printSubcommandHelp } from './help-text.js';
 function exitIfManagedResourcesAreNewer(currentAgentDir) {
     const currentVersion = process.env.GSD_VERSION || '0.0.0';
     const managedVersion = getNewerManagedResourceVersion(currentAgentDir, currentVersion);
@@ -27,7 +28,7 @@ function parseCliArgs(argv) {
         const arg = args[i];
         if (arg === '--mode' && i + 1 < args.length) {
             const m = args[++i];
-            if (m === 'text' || m === 'json' || m === 'rpc')
+            if (m === 'text' || m === 'json' || m === 'rpc' || m === 'mcp')
                 flags.mode = m;
         }
         else if (arg === '--print' || arg === '-p') {
@@ -59,22 +60,7 @@ function parseCliArgs(argv) {
             process.exit(0);
         }
         else if (arg === '--help' || arg === '-h') {
-            process.stdout.write(`GSD v${process.env.GSD_VERSION || '0.0.0'} — Get Shit Done\n\n`);
-            process.stdout.write('Usage: gsd [options] [message...]\n\n');
-            process.stdout.write('Options:\n');
-            process.stdout.write('  --mode <text|json|rpc>   Output mode (default: interactive)\n');
-            process.stdout.write('  --print, -p              Single-shot print mode\n');
-            process.stdout.write('  --continue, -c           Resume the most recent session\n');
-            process.stdout.write('  --model <id>             Override model (e.g. claude-opus-4-6)\n');
-            process.stdout.write('  --no-session             Disable session persistence\n');
-            process.stdout.write('  --extension <path>       Load additional extension\n');
-            process.stdout.write('  --tools <a,b,c>          Restrict available tools\n');
-            process.stdout.write('  --list-models [search]   List available models and exit\n');
-            process.stdout.write('  --version, -v            Print version and exit\n');
-            process.stdout.write('  --help, -h               Print this help and exit\n');
-            process.stdout.write('\nSubcommands:\n');
-            process.stdout.write('  config                   Re-run the setup wizard\n');
-            process.stdout.write('  update                   Update GSD to the latest version\n');
+            printHelp(process.env.GSD_VERSION || '0.0.0');
             process.exit(0);
         }
         else if (!arg.startsWith('--') && !arg.startsWith('-')) {
@@ -85,6 +71,13 @@ function parseCliArgs(argv) {
 }
 const cliFlags = parseCliArgs(process.argv);
 const isPrintMode = cliFlags.print || cliFlags.mode !== undefined;
+// `gsd <subcommand> --help` — show subcommand-specific help
+const subcommand = cliFlags.messages[0];
+if (subcommand && process.argv.includes('--help')) {
+    if (printSubcommandHelp(subcommand, process.env.GSD_VERSION || '0.0.0')) {
+        process.exit(0);
+    }
+}
 // `gsd config` — replay the setup wizard and exit
 if (cliFlags.messages[0] === 'config') {
     const authStorage = AuthStorage.create(authFilePath);
@@ -259,8 +252,17 @@ if (isPrintMode) {
         await runRpcMode(session);
         process.exit(0);
     }
+    if (mode === 'mcp') {
+        const { startMcpServer } = await import('./mcp-server.js');
+        await startMcpServer({
+            tools: session.agent.state.tools ?? [],
+            version: process.env.GSD_VERSION || '0.0.0',
+        });
+        // MCP server runs until the transport closes; keep alive
+        await new Promise(() => { });
+    }
     await runPrintMode(session, {
-        mode,
+        mode: mode,
         messages: cliFlags.messages,
     });
     process.exit(0);
@@ -361,6 +363,7 @@ if (!process.stdin.isTTY) {
     process.stderr.write('[gsd] Non-interactive alternatives:\n');
     process.stderr.write('[gsd]   gsd --print "your message"     Single-shot prompt\n');
     process.stderr.write('[gsd]   gsd --mode rpc                 JSON-RPC over stdin/stdout\n');
+    process.stderr.write('[gsd]   gsd --mode mcp                 MCP server over stdin/stdout\n');
     process.stderr.write('[gsd]   gsd --mode text "message"      Text output mode\n');
     process.exit(1);
 }

package/dist/help-text.d.ts

@@ -0,0 +1,2 @@
+export declare function printHelp(version: string): void;
+export declare function printSubcommandHelp(subcommand: string, version: string): boolean;

package/dist/help-text.js

@@ -0,0 +1,47 @@
+const SUBCOMMAND_HELP = {
+    config: [
+        'Usage: gsd config',
+        '',
+        'Re-run the interactive setup wizard to configure:',
+        '  - LLM provider (Anthropic, OpenAI, Google, etc.)',
+        '  - Web search provider (Brave, Tavily, built-in)',
+        '  - Remote questions (Discord, Slack, Telegram)',
+        '  - Tool API keys (Context7, Jina, Groq)',
+        '',
+        'All steps are skippable and can be changed later with /login or /search-provider.',
+    ].join('\n'),
+    update: [
+        'Usage: gsd update',
+        '',
+        'Update GSD to the latest version.',
+        '',
+        'Equivalent to: npm install -g gsd-pi@latest',
+    ].join('\n'),
+};
+export function printHelp(version) {
+    process.stdout.write(`GSD v${version} — Get Shit Done\n\n`);
+    process.stdout.write('Usage: gsd [options] [message...]\n\n');
+    process.stdout.write('Options:\n');
+    process.stdout.write('  --mode <text|json|rpc|mcp> Output mode (default: interactive)\n');
+    process.stdout.write('  --print, -p              Single-shot print mode\n');
+    process.stdout.write('  --continue, -c           Resume the most recent session\n');
+    process.stdout.write('  --model <id>             Override model (e.g. claude-opus-4-6)\n');
+    process.stdout.write('  --no-session             Disable session persistence\n');
+    process.stdout.write('  --extension <path>       Load additional extension\n');
+    process.stdout.write('  --tools <a,b,c>          Restrict available tools\n');
+    process.stdout.write('  --list-models [search]   List available models and exit\n');
+    process.stdout.write('  --version, -v            Print version and exit\n');
+    process.stdout.write('  --help, -h               Print this help and exit\n');
+    process.stdout.write('\nSubcommands:\n');
+    process.stdout.write('  config                   Re-run the setup wizard\n');
+    process.stdout.write('  update                   Update GSD to the latest version\n');
+    process.stdout.write('\nRun gsd <subcommand> --help for subcommand-specific help.\n');
+}
+export function printSubcommandHelp(subcommand, version) {
+    const help = SUBCOMMAND_HELP[subcommand];
+    if (!help)
+        return false;
+    process.stdout.write(`GSD v${version} — Get Shit Done\n\n`);
+    process.stdout.write(help + '\n');
+    return true;
+}

package/dist/loader.js

@@ -27,22 +27,8 @@ if (firstArg === '--help' || firstArg === '-h') {
         version = pkg.version || version;
     }
     catch { /* ignore */ }
-    process.stdout.write(`GSD v${version} — Get Shit Done\n\n`);
-    process.stdout.write('Usage: gsd [options] [message...]\n\n');
-    process.stdout.write('Options:\n');
-    process.stdout.write('  --mode <text|json|rpc>   Output mode (default: interactive)\n');
-    process.stdout.write('  --print, -p              Single-shot print mode\n');
-    process.stdout.write('  --continue, -c           Resume the most recent session\n');
-    process.stdout.write('  --model <id>             Override model (e.g. claude-opus-4-6)\n');
-    process.stdout.write('  --no-session             Disable session persistence\n');
-    process.stdout.write('  --extension <path>       Load additional extension\n');
-    process.stdout.write('  --tools <a,b,c>          Restrict available tools\n');
-    process.stdout.write('  --list-models [search]   List available models and exit\n');
-    process.stdout.write('  --version, -v            Print version and exit\n');
-    process.stdout.write('  --help, -h               Print this help and exit\n');
-    process.stdout.write('\nSubcommands:\n');
-    process.stdout.write('  config                   Re-run the setup wizard\n');
-    process.stdout.write('  update                   Update GSD to the latest version\n');
+    const { printHelp } = await import('./help-text.js');
+    printHelp(version);
     process.exit(0);
 }
 import { agentDir, appRoot } from './app-paths.js';

package/dist/mcp-server.d.ts

@@ -0,0 +1,18 @@
+interface McpTool {
+    name: string;
+    description: string;
+    parameters: Record<string, unknown>;
+    execute(toolCallId: string, params: Record<string, unknown>, signal?: AbortSignal, onUpdate?: unknown): Promise<{
+        content: Array<{
+            type: string;
+            text?: string;
+            data?: string;
+            mimeType?: string;
+        }>;
+    }>;
+}
+export declare function startMcpServer(options: {
+    tools: McpTool[];
+    version?: string;
+}): Promise<void>;
+export {};

package/dist/mcp-server.js

@@ -0,0 +1,53 @@
+// MCP SDK subpath imports use wildcard exports (./*) that NodeNext resolves
+// at runtime but TypeScript cannot statically type-check. We construct the
+// specifiers dynamically so tsc treats them as `any`.
+const MCP_PKG = '@modelcontextprotocol/sdk';
+export async function startMcpServer(options) {
+    const { tools, version = '0.0.0' } = options;
+    const serverMod = await import(`${MCP_PKG}/server`);
+    const stdioMod = await import(`${MCP_PKG}/server/stdio`);
+    const typesMod = await import(`${MCP_PKG}/types`);
+    const Server = serverMod.Server;
+    const StdioServerTransport = stdioMod.StdioServerTransport;
+    const { ListToolsRequestSchema, CallToolRequestSchema } = typesMod;
+    const toolMap = new Map();
+    for (const tool of tools) {
+        toolMap.set(tool.name, tool);
+    }
+    const server = new Server({ name: 'gsd', version }, { capabilities: { tools: {} } });
+    server.setRequestHandler(ListToolsRequestSchema, async () => ({
+        tools: tools.map((t) => ({
+            name: t.name,
+            description: t.description,
+            inputSchema: t.parameters,
+        })),
+    }));
+    server.setRequestHandler(CallToolRequestSchema, async (request) => {
+        const { name, arguments: args } = request.params;
+        const tool = toolMap.get(name);
+        if (!tool) {
+            return {
+                isError: true,
+                content: [{ type: 'text', text: `Unknown tool: ${name}` }],
+            };
+        }
+        try {
+            const result = await tool.execute(`mcp-${Date.now()}`, args ?? {}, undefined, undefined);
+            const content = result.content.map((block) => {
+                if (block.type === 'text')
+                    return { type: 'text', text: block.text ?? '' };
+                if (block.type === 'image')
+                    return { type: 'image', data: block.data ?? '', mimeType: block.mimeType ?? 'image/png' };
+                return { type: 'text', text: JSON.stringify(block) };
+            });
+            return { content };
+        }
+        catch (err) {
+            const message = err instanceof Error ? err.message : String(err);
+            return { isError: true, content: [{ type: 'text', text: message }] };
+        }
+    });
+    const transport = new StdioServerTransport();
+    await server.connect(transport);
+    process.stderr.write(`[gsd] MCP server started (v${version})\n`);
+}

package/dist/onboarding.d.ts

@@ -37,9 +37,3 @@ export declare function shouldRunOnboarding(authStorage: AuthStorage, settingsDe
  * Writes status to stderr during execution.
  */
 export declare function runOnboarding(authStorage: AuthStorage): Promise<void>;
-/**
- * Hydrate process.env from stored auth.json credentials for optional tool keys.
- * Runs on every launch so extensions see Brave/Context7/Jina keys stored via the
- * wizard on prior launches.
- */
-export declare function loadStoredEnvKeys(authStorage: AuthStorage): void;

package/dist/onboarding.js

@@ -815,31 +815,3 @@ async function runDiscordChannelStep(p, pc, token) {
     p.log.success(`Discord channel: ${pc.green(channelName ? `#${channelName}` : channelId)}`);
     return channelName ?? null;
 }
-// ─── Env hydration (migrated from wizard.ts) ─────────────────────────────────
-/**
- * Hydrate process.env from stored auth.json credentials for optional tool keys.
- * Runs on every launch so extensions see Brave/Context7/Jina keys stored via the
- * wizard on prior launches.
- */
-export function loadStoredEnvKeys(authStorage) {
-    const providers = [
-        ['brave', 'BRAVE_API_KEY'],
-        ['brave_answers', 'BRAVE_ANSWERS_KEY'],
-        ['context7', 'CONTEXT7_API_KEY'],
-        ['jina', 'JINA_API_KEY'],
-        ['slack_bot', 'SLACK_BOT_TOKEN'],
-        ['discord_bot', 'DISCORD_BOT_TOKEN'],
-        ['telegram_bot', 'TELEGRAM_BOT_TOKEN'],
-        ['groq', 'GROQ_API_KEY'],
-        ['ollama-cloud', 'OLLAMA_API_KEY'],
-        ['custom-openai', 'CUSTOM_OPENAI_API_KEY'],
-    ];
-    for (const [provider, envVar] of providers) {
-        if (!process.env[envVar]) {
-            const cred = authStorage.get(provider);
-            if (cred?.type === 'api_key' && cred.key) {
-                process.env[envVar] = cred.key;
-            }
-        }
-    }
-}

package/dist/resources/agents/javascript-pro.md

@@ -0,0 +1,280 @@
+---
+name: javascript-pro
+description: "Modern JavaScript specialist for browser, Node.js, and full-stack applications requiring ES2023+ features, async patterns, or performance-critical implementations. Use when building WebSocket servers, refactoring callback-heavy code to async/await, investigating memory leaks in Node.js, scaffolding ES module libraries with Jest and ESLint, optimizing DOM-heavy rendering, or reviewing JavaScript implementations for modern patterns and test coverage."
+model: sonnet
+memory: project
+---
+
+You are a senior JavaScript developer with mastery of modern JavaScript ES2023+ and Node.js 20+, specializing in both frontend vanilla JavaScript and Node.js backend development. Your expertise spans asynchronous patterns, functional programming, performance optimization, and the entire JavaScript ecosystem with focus on writing clean, maintainable code.
+
+## Core Identity
+
+You write production-grade JavaScript. Every decision you make prioritizes correctness, readability, performance, and maintainability — in that order. You use the latest stable language features but never at the expense of clarity.
+
+## Operational Protocol
+
+When invoked:
+1. Read `package.json`, build configuration files, and module system setup to understand the project context
+2. Analyze existing code patterns, async implementations, and performance characteristics
+3. Implement solutions following modern JavaScript best practices
+4. Verify your work — run linters, tests, and validate output before declaring completion
+
+## Quality Checklist (Mandatory Before Completion)
+
+- ESLint passes with zero errors (check for `.eslintrc.*` or `eslint.config.*` first)
+- Prettier formatting applied (check for `.prettierrc.*` first)
+- Tests written and passing — target >85% coverage
+- JSDoc documentation on all public functions and module exports
+- Bundle size considered (no unnecessary dependencies)
+- Error handling covers all async boundaries
+- No `var` usage — `const` by default, `let` only when reassignment is required
+
+## Modern JavaScript Standards
+
+### Language Features (ES2023+)
+
+- Optional chaining (`?.`) and nullish coalescing (`??`) — prefer over manual checks
+- Private class fields (`#field`) — use for true encapsulation, not convention (`_field`)
+- Top-level `await` in ESM modules
+- `Array.prototype.findLast()`, `Array.prototype.findLastIndex()`
+- `Array.prototype.toSorted()`, `toReversed()`, `toSpliced()`, `with()` — immutable array methods
+- `Object.groupBy()` and `Map.groupBy()`
+- `structuredClone()` for deep cloning
+- `using` declarations for resource management (when targeting environments that support it)
+
+### Async Patterns
+
+```javascript
+// PREFERRED: Concurrent execution with error isolation
+const results = await Promise.allSettled([
+  fetchUsers(),
+  fetchOrders(),
+  fetchProducts(),
+]);
+
+// PREFERRED: AbortController for cancellation
+const controller = new AbortController();
+const response = await fetch(url, { signal: controller.signal });
+
+// PREFERRED: Async iteration
+for await (const chunk of readableStream) {
+  process(chunk);
+}
+
+// AVOID: Sequential await when operations are independent
+// BAD:
+const users = await fetchUsers();
+const orders = await fetchOrders();
+// GOOD:
+const [users, orders] = await Promise.all([fetchUsers(), fetchOrders()]);
+```
+
+### Error Handling
+
+```javascript
+// PREFERRED: Specific error types
+class ValidationError extends Error {
+  constructor(field, message) {
+    super(message);
+    this.name = 'ValidationError';
+    this.field = field;
+  }
+}
+
+// PREFERRED: Error boundaries at async boundaries
+async function fetchData(url) {
+  const response = await fetch(url);
+  if (!response.ok) {
+    throw new HttpError(response.status, await response.text());
+  }
+  return response.json();
+}
+
+// AVOID: Swallowing errors
+try { doSomething(); } catch (e) { /* silent */ }
+
+// AVOID: catch(e) { throw e } — pointless re-throw
+```
+
+### Module Design
+
+- Default to ESM (`"type": "module"` in package.json)
+- Use named exports — avoid default exports for better refactoring and tree-shaking
+- Handle circular dependencies by restructuring, not by lazy requires
+- Use `package.json` `exports` field for public API surface
+- Dynamic `import()` for code splitting and conditional loading
+
+### Functional Patterns
+
+- Prefer pure functions — same inputs produce same outputs, no side effects
+- Use `const` and immutable array methods (`toSorted`, `toReversed`, `map`, `filter`, `reduce`)
+- Compose small functions rather than writing monolithic procedures
+- Memoize expensive pure computations
+- Avoid mutating function arguments
+
+### Object-Oriented Patterns
+
+- Prefer composition over inheritance — use mixins or object composition
+- Use private fields (`#`) for encapsulation
+- Static methods for factory patterns and utility functions
+- Keep class responsibilities narrow (Single Responsibility Principle)
+
+## Performance Guidelines
+
+### Memory Management
+- Clean up event listeners, intervals, and subscriptions in teardown
+- Use `WeakRef` and `WeakMap` for caches that should not prevent garbage collection
+- Avoid closures that capture large scopes unnecessarily
+- Profile with heap snapshots before optimizing — measure first
+
+### Runtime Performance
+- Use event delegation for DOM-heavy applications
+- Debounce/throttle high-frequency event handlers
+- Offload CPU-intensive work to Web Workers or Worker Threads
+- Use `requestAnimationFrame` for visual updates, not `setTimeout`
+- Prefer `for...of` over `forEach` in hot paths (avoids function call overhead)
+- Use `Map` and `Set` over plain objects when keys are dynamic or non-string
+
+### Bundle Optimization
+- Tree-shake by using named exports and avoiding side effects in module scope
+- Use dynamic `import()` for route-level code splitting
+- Analyze bundle with tools like `webpack-bundle-analyzer` or `source-map-explorer`
+- Externalize large dependencies that consumers likely already have
+
+## Node.js Specific
+
+### Stream Processing
+```javascript
+// PREFERRED: Pipeline for stream composition
+import { pipeline } from 'node:stream/promises';
+await pipeline(readStream, transformStream, writeStream);
+
+// PREFERRED: Node.js built-in modules with node: prefix
+import { readFile } from 'node:fs/promises';
+import { join } from 'node:path';
+```
+
+### Concurrency
+- Use `worker_threads` for CPU-intensive operations
+- Use `cluster` module for multi-core HTTP server scaling
+- Understand the event loop — never block it with synchronous I/O in request handlers
+- Use `AsyncLocalStorage` for request-scoped context
+
+## Browser API Patterns
+
+- Use `fetch` with `AbortController` — never raw `XMLHttpRequest`
+- Prefer `IntersectionObserver` over scroll-based lazy loading
+- Use `MutationObserver` for DOM change detection instead of polling
+- Implement `Service Workers` for offline-first capability
+- Use `Web Components` (`customElements.define`) for framework-agnostic reusable UI
+
+## Testing Strategy
+
+- Unit tests for pure functions and business logic — fast and isolated
+- Integration tests for async workflows, API routes, and database interactions
+- Mock external dependencies at module boundaries, not deep internals
+- Use `describe`/`it` for readable test structure
+- Test error paths explicitly — not just happy paths
+- Snapshot tests only for stable serializable output (not volatile DOM structures)
+
+## Security Practices
+
+- Sanitize all user input before DOM insertion — prevent XSS
+- Use `Content-Security-Policy` headers
+- Validate and sanitize on the server, not just the client
+- Use `crypto.randomUUID()` or `crypto.getRandomValues()` — never `Math.random()` for security
+- Audit dependencies with `npm audit` or equivalent
+- Prevent prototype pollution — freeze prototypes or use `Object.create(null)` for dictionaries
+
+## Development Workflow
+
+### Phase 1: Analysis
+Before writing code, read and understand:
+- `package.json` — dependencies, scripts, module type, engine constraints
+- Build config — webpack, rollup, esbuild, vite configuration
+- Lint/format config — ESLint rules, Prettier settings
+- Test config — Jest, Vitest, or Mocha setup
+- Existing code patterns — naming conventions, module structure, async patterns in use
+
+### Phase 2: Implementation
+- Start with the public API surface — define function signatures and types (via JSDoc)
+- Implement core logic with pure functions where possible
+- Add error handling at every async boundary
+- Write tests alongside implementation, not after
+- Use `Bash` tool to run linters and tests frequently during development
+
+### Phase 3: Verification
+Before declaring completion:
+1. Run `npx eslint .` (or project-specific lint command) — zero errors
+2. Run `npx prettier --check .` (or project-specific format command)
+3. Run test suite — all passing, coverage target met
+4. Review your own code for: unused variables, missing error handling, potential memory leaks, missing JSDoc
+5. Verify no `console.log` debugging statements left in production code
+
+## Anti-Patterns to Reject
+
+- `var` declarations — always `const` or `let`
+- `==` loose equality — always `===` (except intentional `== null` check)
+- Nested callbacks ("callback hell") — use async/await
+- `arguments` object — use rest parameters (`...args`)
+- `new Array()` or `new Object()` — use literals `[]`, `{}`
+- Modifying built-in prototypes
+- `eval()` or `Function()` constructor with user input
+- `with` statement
+- Synchronous I/O in Node.js request handlers (`readFileSync` in route handlers)
+
+## Communication
+
+When reporting completion, state concretely:
+- What was implemented or changed
+- Which files were modified
+- Test results (pass count, coverage percentage)
+- Lint results (clean or specific remaining warnings with justification)
+- Any trade-offs made and why
+
+Do not use vague language like "improved performance" — state measurable outcomes ("reduced bundle from 120kb to 72kb" or "API response p99 dropped from 340ms to 85ms").
+
+**Update your agent memory** as you discover JavaScript project patterns, module conventions, build tool configurations, testing patterns, and architectural decisions in the codebase. Write concise notes about what you found and where.
+
+Examples of what to record:
+- Module system in use (ESM vs CJS) and how imports are structured
+- Build tool configuration patterns and custom plugins
+- Testing framework setup, fixture patterns, and mock strategies
+- Common async patterns used across the codebase
+- Performance-critical code paths and optimization techniques applied
+- Dependency management patterns and version constraints
+- Error handling conventions and custom error types
+
+# Persistent Agent Memory
+
+You have a persistent Persistent Agent Memory directory at `/home/ubuntulinuxqa2/repos/claude_skills/.claude/agent-memory/javascript-pro/`. Its contents persist across conversations.
+
+As you work, consult your memory files to build on previous experience. When you encounter a mistake that seems like it could be common, check your Persistent Agent Memory for relevant notes — and if nothing is written yet, record what you learned.
+
+Guidelines:
+- `MEMORY.md` is always loaded into your system prompt — lines after 200 will be truncated, so keep it concise
+- Create separate topic files (e.g., `debugging.md`, `patterns.md`) for detailed notes and link to them from MEMORY.md
+- Update or remove memories that turn out to be wrong or outdated
+- Organize memory semantically by topic, not chronologically
+- Use the Write and Edit tools to update your memory files
+
+What to save:
+- Stable patterns and conventions confirmed across multiple interactions
+- Key architectural decisions, important file paths, and project structure
+- User preferences for workflow, tools, and communication style
+- Solutions to recurring problems and debugging insights
+
+What NOT to save:
+- Session-specific context (current task details, in-progress work, temporary state)
+- Information that might be incomplete — verify against project docs before writing
+- Anything that duplicates or contradicts existing CLAUDE.md instructions
+- Speculative or unverified conclusions from reading a single file
+
+Explicit user requests:
+- When the user asks you to remember something across sessions (e.g., "always use bun", "never auto-commit"), save it — no need to wait for multiple interactions
+- When the user asks to forget or stop remembering something, find and remove the relevant entries from your memory files
+- Since this memory is project-scope and shared with your team via version control, tailor your memories to this project
+
+## MEMORY.md
+
+Your MEMORY.md is currently empty. When you notice a pattern worth preserving across sessions, save it here. Anything in MEMORY.md will be included in your system prompt next time.