poly-agent 1.0.5 → 1.0.7

package/dist/cli.js

@@ -1,7 +1,8 @@
 #!/usr/bin/env node
-import { intro, select, multiselect, spinner, log, outro, cancel, isCancel } from '@clack/prompts';
+import { intro, select, multiselect, spinner, log, outro, cancel, isCancel, confirm } from '@clack/prompts';
 import fs from 'fs/promises';
 import path from 'path';
+import os from 'os';
 import { PromptLoader } from './lib/prompt-loader.js';
 import { createRequire } from 'module';
 const require = createRequire(import.meta.url);
@@ -40,6 +41,17 @@ const IDE_DIRECTORIES = {
     'Antigravity': '.agent/workflows',
     'Claude': '.claude/skills',
 };
+const IDE_GLOBAL_CONFIG_DIR = {
+    'Cursor': '.cursor',
+    'Antigravity': '.antigravity',
+    'Claude': '.claude',
+};
+function getGlobalRulesPath(ide) {
+    const homeDir = os.homedir();
+    const configDir = IDE_GLOBAL_CONFIG_DIR[ide] || `.${ide.toLowerCase()}`;
+    // Assuming 'rules' directory for all pending further customization
+    return path.join(homeDir, configDir, 'rules');
+}
 async function runInit() {
     // Welcome message
     intro('Welcome to PolyAgent CLI');
@@ -141,6 +153,41 @@ ${prompt.content}`;
         log.error(`Failed to install prompts: ${error instanceof Error ? error.message : String(error)}`);
         process.exit(1);
     }
+    // Step 5: Ask if user wants global context rule
+    const wantsContextRule = await confirm({
+        message: 'Install global context-rule for automatic context management?',
+        initialValue: true
+    });
+    if (isCancel(wantsContextRule)) {
+        cancel('Operation cancelled.');
+        process.exit(0);
+    }
+    if (wantsContextRule) {
+        const globalRuleS = spinner();
+        const globalRulePath = getGlobalRulesPath(selectedIDE);
+        globalRuleS.start(`Installing global context rule to ${globalRulePath}...`);
+        try {
+            await fs.mkdir(globalRulePath, { recursive: true });
+            // Load shared instructions to find context-hook
+            // UPDATED: Copy context-rule.md directly from _shared
+            const contextRulePath = path.join(promptsDir, '_shared', 'context-rule.md');
+            try {
+                const contextRuleContent = await fs.readFile(contextRulePath, 'utf-8');
+                await fs.writeFile(path.join(globalRulePath, 'context-rule.md'), contextRuleContent, 'utf-8');
+                globalRuleS.stop('✓ Global context rule installed successfully');
+                log.info(`  - ${path.join(globalRulePath, 'context-rule.md')}`);
+            }
+            catch (readError) {
+                globalRuleS.stop('! Context rule file not found in _shared but installation continued');
+            }
+        }
+        catch (error) {
+            globalRuleS.stop('✗ Global rule installation failed');
+            log.error(`Failed to install global rule: ${error instanceof Error ? error.message : String(error)}`);
+            // Don't exit process, as local prompts might have been installed successfully
+        }
+    }
+    outro('Installation complete! 🎉');
 }
 function showHelp() {
     console.log(`

package/dist/lib/prompt-loader.js

@@ -82,6 +82,8 @@ export class PromptLoader {
             // Inject variables
             content = this.injectVariables(content, variables);
             // Append shared instructions
+            // logic moved to CLI for global installation
+            /*
             const sharedInstructions = await this.loadSharedInstructions();
             if (sharedInstructions.length > 0) {
                 const sharedContent = sharedInstructions
@@ -89,6 +91,7 @@ export class PromptLoader {
                     .join('\n');
                 content = content + sharedContent;
             }
+            */
             return { name, description, content };
         }
         catch (error) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "poly-agent",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "description": "CLI installer for AI IDE prompts - install commands, skills, and workflows for Cursor, ClaudeCode, and Antigravity",
   "main": "dist/index.js",
   "bin": {
@@ -37,4 +37,4 @@
     "ts-node": "^10.9.2",
     "typescript": "^5.9.3"
   }
-}
+}

package/prompts/_shared/context-hook.md

@@ -82,3 +82,22 @@ status: [in-progress | completed | blocked | paused]
 5. You edit `src/routes/login.ts`
 6. You update `.context/feature-api-auth.md` again
 7. Continue until task complete, then set status to `completed`
+
+## Recalling Context
+
+When a user asks to recall or resume a context (e.g., "recall feature-auth", "continue from context X", "load context"):
+
+1. **Read ONLY the specified context file** from `.context/` - Do NOT scan the entire project
+2. **Trust the context file** - It contains all the information you need
+3. **Summarize the current state** - What was done, what remains
+4. **Confirm understanding** with the user before proceeding
+5. **Only read files listed in "Files Changed"** if you need to check current state
+6. **Continue updating** the same context file as you work
+
+**IMPORTANT**: When recalling context, do NOT:
+- Search or scan the entire codebase
+- Read files not mentioned in the context
+- Run broad exploratory searches
+- Assume information beyond what's in the context file
+
+If asked to **list contexts**, read the `.context/` directory and show available files with their status.

package/prompts/_shared/context-rule.md

@@ -0,0 +1,104 @@
+---
+name: Context Rule
+description: Shared instructions for automatic context dumping after file edits.
+mode: always apply
+type: shared
+---
+
+# Context Management Hook
+
+## Behavior
+
+After **every file edit** you make, you MUST update the project context file. This ensures continuity across conversations and helps maintain a clear record of progress.
+
+## When to Update Context
+
+1. **After any file edit** - Immediately after modifying, creating, or deleting a file
+2. **When the task context changes** - New goals, pivots, or scope changes
+3. **When explicitly mentioned** - If the user references `.context/` or asks about context
+4. **At conversation milestones** - Completing a feature, fixing a bug, reaching a checkpoint
+
+## Context File Location & Naming
+
+- **Directory**: `.context/`
+- **Filename**: Generate a short, descriptive kebab-case name based on the current task
+  - Examples: `feature-auth.md`, `bugfix-api-timeout.md`, `refactor-database-layer.md`, `setup-ci-pipeline.md`
+- **Persistence**: Use the SAME context file throughout a conversation/task. Only create a new one if the task fundamentally changes.
+
+## Context File Format
+
+Use this exact structure:
+
+```markdown
+---
+created: [ISO timestamp when first created]
+updated: [ISO timestamp of last update]
+task: [One-line task description]
+status: [in-progress | completed | blocked | paused]
+---
+
+# Context: [short-name]
+
+## Summary
+[2-3 sentence AI-generated summary of what this task is about and current state]
+
+## Files Changed
+- `path/to/file.ts` - [Brief description of change]
+- `path/to/another.ts` - [Brief description of change]
+
+## Current Goals
+1. [Primary goal]
+2. [Secondary goal]
+3. [etc.]
+
+## Progress
+- [x] [Completed item]
+- [x] [Completed item]
+- [ ] [Pending item]
+- [ ] [Pending item]
+
+## Next Steps
+- [Immediate next action]
+- [Following action]
+
+## Notes
+[Any important context, decisions made, blockers, or things to remember]
+```
+
+## Rules
+
+1. **Always update, never skip** - Even small edits warrant a context update
+2. **Be concise but complete** - Capture essential information without verbosity
+3. **Track ALL file changes** - Every file you touch should be listed
+4. **Maintain history** - Don't remove completed items from Progress, mark them done
+5. **Update timestamps** - Always update the `updated` field in frontmatter
+6. **Create directory if needed** - If `.context/` doesn't exist, create it
+
+## Example Workflow
+
+1. User asks: "Add authentication to the API"
+2. You create/update `.context/feature-api-auth.md` with initial goals
+3. You edit `src/auth/middleware.ts`
+4. You immediately update `.context/feature-api-auth.md` with the file change
+5. You edit `src/routes/login.ts`
+6. You update `.context/feature-api-auth.md` again
+7. Continue until task complete, then set status to `completed`
+
+## Recalling Context
+
+When a user asks to recall or resume a context (e.g., "recall feature-auth", "continue from context X", "load context"):
+
+1. **Read ONLY the specified context file** from `.context/` - Do NOT scan the entire project
+2. **Trust the context file** - It contains all the information you need
+3. **Summarize the current state** - What was done, what remains
+4. **Confirm understanding** with the user before proceeding
+5. **Only read files listed in "Files Changed"** if you need to check current state
+6. **Continue updating** the same context file as you work
+
+**IMPORTANT**: When recalling context, do NOT:
+- Search or scan the entire codebase
+- Read files not mentioned in the context
+- Run broad exploratory searches
+- Assume information beyond what's in the context file
+
+If asked to **list contexts**, read the `.context/` directory and show available files with their status.

package/prompts/context-recall.md

@@ -0,0 +1,82 @@
+---
+name: Context Recall
+description: Load and resume work from a saved context file.
+---
+# Context Recall
+
+You are being asked to **resume work** from a previously saved context.
+
+## Instructions
+
+1. **Read the context file** specified by the user (from `.context/` directory)
+2. **Understand the state** - Review the summary, files changed, goals, and progress
+3. **Identify next steps** - Look at what was marked as pending or in "Next Steps"
+4. **Resume seamlessly** - Continue the work as if you never left
+
+## How to Use
+
+The user will provide one of:
+- A context file name: `feature-auth` or `feature-auth.md`
+- A full path: `.context/feature-auth.md`
+- Or ask you to list available contexts
+
+## If Asked to List Contexts
+
+Read the `.context/` directory and present available context files:
+
+```
+Available contexts:
+- feature-auth.md (updated: 2026-01-12)
+- bugfix-api-timeout.md (updated: 2026-01-11)
+- refactor-database.md (updated: 2026-01-10)
+```
+
+## After Loading Context
+
+1. **Summarize** what you understand about the task
+2. **Confirm** the current state and what remains to be done
+3. **Ask** if the user wants to continue from where it left off, or modify the approach
+4. **Continue updating** the same context file as you make changes
+
+## Example Interaction
+
+**User**: "Recall context feature-auth"
+
+**You**: 
+> I've loaded the context for **feature-auth**:
+> 
+> **Summary**: Implementing JWT-based authentication for the API
+> 
+> **Progress**:
+> - ✅ Created auth middleware
+> - ✅ Set up login route
+> - ⏳ Token refresh logic (in progress)
+> - ⬜ Rate limiting
+> 
+> **Last worked on**: `src/auth/refresh.ts`
+> 
+> Would you like me to continue with the token refresh logic, or would you prefer to work on something else?
+
+## Critical Rules
+
+1. **ONLY read the context file** - Do NOT scan the entire project or codebase
+2. **Trust the context file** - It contains everything you need to understand the task
+3. **Read files listed in "Files Changed"** - Only if you need to understand current state
+4. **Don't guess or make up content** - Only use information from the context file
+5. **If context file doesn't exist** - Inform the user and offer to create one
+6. **Keep the context file updated** - As you continue working
+
+## What NOT To Do
+
+- ❌ Do NOT search the entire codebase to "understand the project"
+- ❌ Do NOT read files that aren't mentioned in the context
+- ❌ Do NOT run broad searches or scans
+- ❌ Do NOT assume context beyond what's in the file
+
+## What TO Do
+
+- ✅ Read ONLY `.context/[name].md` first
+- ✅ Use the "Files Changed" section to know which files are relevant
+- ✅ Read specific files from "Files Changed" if needed for current state
+- ✅ Follow "Next Steps" from the context file
+- ✅ Ask the user if anything is unclear