@ridit/lens 0.3.7 → 0.3.9

package/src/prompts/fewshot.ts

@@ -1,252 +0,0 @@
-export const FEW_SHOT_MESSAGES: { role: string; content: string }[] = [
-  // ── create new file directly ──────────────────────────────────────────────
-  {
-    role: "user",
-    content: "this codebase doesn't have a readme",
-  },
-  {
-    role: "assistant",
-    content:
-      '<write-file>\n{"path": "README.md", "content": "# Project\\n\\nA brief description.\\n\\n## Getting Started\\n\\n```bash\\nbun install\\nbun run dev\\n```"}\n</write-file>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from write-file to README.md:\n\nWritten: /repo/README.md (10 lines, 128 bytes)\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content: "Done — README.md has been created.",
-  },
-
-  // ── fix a single file (read once, write once, done) ───────────────────────
-  {
-    role: "user",
-    content: "fix the bug in addons/clean-cache.js",
-  },
-  {
-    role: "assistant",
-    content: "<read-file>addons/clean-cache.js</read-file>",
-  },
-  {
-    role: "user",
-    content:
-      'Here is the output from read-file of addons/clean-cache.js:\n\nFile: addons/clean-cache.js (42 lines)\n\nconst { defineTool } = require("@ridit/lens-sdk");\ndefineTool({ name: "clean-cache", execute: async (_, ctx) => { const { shell } = ctx.tools; await shell("rm -rf node_modules"); } });\n\nPlease continue your response based on this output.',
-  },
-  {
-    role: "assistant",
-    content:
-      '<write-file>\n{"path": "addons/clean-cache.js", "content": "const { defineTool } = require(\\"@ridit/lens-sdk\\");\\nconst { execSync } = require(\\"child_process\\");\\n\\ndefineTool({\\n  name: \\"clean-cache\\",\\n  description: \\"Clean node_modules and bun cache\\",\\n  safe: false,\\n  permissionLabel: \\"Clean cache\\",\\n  systemPromptEntry: () => \\"<clean-cache>{}</clean-cache> — clean node_modules and bun cache\\",\\n  parseInput: () => ({}),\\n  summariseInput: () => \\"clean cache\\",\\n  execute: async (_, ctx) => {\\n    try {\\n      execSync(\\"rm -rf node_modules\\", { cwd: ctx.repoPath, stdio: \\"pipe\\" });\\n      return { kind: \\"text\\", value: \\"Cache cleaned!\\" };\\n    } catch (err) {\\n      return { kind: \\"error\\", value: err.message };\\n    }\\n  },\\n});"}\n</write-file>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from write-file to addons/clean-cache.js:\n\nWritten: /repo/addons/clean-cache.js (20 lines, 480 bytes)\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      "Done — clean-cache.js fixed. Now uses execSync instead of ctx.tools.shell.",
-  },
-
-  // ── modify existing file (read first, then write) ─────────────────────────
-  {
-    role: "user",
-    content: "add a logout button to src/components/Header.tsx",
-  },
-  {
-    role: "assistant",
-    content: "<read-file>src/components/Header.tsx</read-file>",
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from read-file of src/components/Header.tsx:\n\nFile: src/components/Header.tsx (42 lines)\n\nimport React from 'react';\n// ... existing content ...\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      '<changes>\n{"summary": "Add logout button to Header — preserves all existing content", "patches": [{"path": "src/components/Header.tsx", "content": "// complete file with logout button added", "isNew": false}]}\n</changes>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from changes:\n\nChanges applied.\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content: "Done — logout button added to Header.tsx.",
-  },
-
-  // ── fix multiple files (read-files first, write each once) ────────────────
-  {
-    role: "user",
-    content: "fix addons/a.js, addons/b.js and addons/c.js",
-  },
-  {
-    role: "assistant",
-    content:
-      '<read-files>\n["addons/a.js", "addons/b.js", "addons/c.js"]\n</read-files>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from read-files:\n\n=== addons/a.js ===\nmodule.exports = { name: 'a', run: async () => {} }\n\n=== addons/b.js ===\nmodule.exports = { name: 'b', run: async () => {} }\n\n=== addons/c.js ===\nmodule.exports = { name: 'c', run: async () => {} }\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      '<write-file>\n{"path": "addons/a.js", "content": "const { defineTool } = require(\\"@ridit/lens-sdk\\");\\n\\ndefineTool({\\n  name: \\"a\\",\\n  description: \\"Does A\\",\\n  safe: true,\\n  permissionLabel: \\"Run A\\",\\n  systemPromptEntry: () => \\"<a>{}</a> — run A\\",\\n  parseInput: () => ({}),\\n  summariseInput: () => \\"a\\",\\n  execute: async (_, ctx) => ({ kind: \\"text\\", value: \\"A done!\\" }),\\n});"}\n</write-file>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from write-file to addons/a.js:\n\nWritten: /repo/addons/a.js (12 lines, 280 bytes)\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      '<write-file>\n{"path": "addons/b.js", "content": "const { defineTool } = require(\\"@ridit/lens-sdk\\");\\n\\ndefineTool({\\n  name: \\"b\\",\\n  description: \\"Does B\\",\\n  safe: true,\\n  permissionLabel: \\"Run B\\",\\n  systemPromptEntry: () => \\"<b>{}</b> — run B\\",\\n  parseInput: () => ({}),\\n  summariseInput: () => \\"b\\",\\n  execute: async (_, ctx) => ({ kind: \\"text\\", value: \\"B done!\\" }),\\n});"}\n</write-file>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from write-file to addons/b.js:\n\nWritten: /repo/addons/b.js (12 lines, 280 bytes)\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      '<write-file>\n{"path": "addons/c.js", "content": "const { defineTool } = require(\\"@ridit/lens-sdk\\");\\n\\ndefineTool({\\n  name: \\"c\\",\\n  description: \\"Does C\\",\\n  safe: true,\\n  permissionLabel: \\"Run C\\",\\n  systemPromptEntry: () => \\"<c>{}</c> — run C\\",\\n  parseInput: () => ({}),\\n  summariseInput: () => \\"c\\",\\n  execute: async (_, ctx) => ({ kind: \\"text\\", value: \\"C done!\\" }),\\n});"}\n</write-file>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from write-file to addons/c.js:\n\nWritten: /repo/addons/c.js (12 lines, 280 bytes)\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      "Done — fixed all three addons. Each now uses defineTool from @ridit/lens-sdk correctly.",
-  },
-
-  // ── scaffold a project ────────────────────────────────────────────────────
-  {
-    role: "user",
-    content:
-      "scaffold a new project called myapp with package.json and src/index.tsx",
-  },
-  {
-    role: "assistant",
-    content:
-      '<write-file>\n{"path": "myapp/package.json", "content": "{\\n  \\"name\\": \\"myapp\\",\\n  \\"version\\": \\"1.0.0\\",\\n  \\"scripts\\": { \\"dev\\": \\"bun run src/index.tsx\\" },\\n  \\"dependencies\\": { \\"react\\": \\"^18.2.0\\", \\"ink\\": \\"^4.4.1\\" }\\n}"}\n</write-file>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from write-file to myapp/package.json:\n\nWritten: /repo/myapp/package.json (8 lines, 180 bytes)\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      '<write-file>\n{"path": "myapp/src/index.tsx", "content": "/** @jsxImportSource react */\\nimport React from \'react\';\\nimport { render, Text } from \'ink\';\\n\\nfunction App() {\\n  return <Text>Hello from myapp!</Text>;\\n}\\n\\nrender(<App />);"}\n</write-file>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from write-file to myapp/src/index.tsx:\n\nWritten: /repo/myapp/src/index.tsx (9 lines, 210 bytes)\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      "Done — scaffolded myapp/package.json and myapp/src/index.tsx. Run cd myapp && bun install to get started.",
-  },
-
-  // ── grep ──────────────────────────────────────────────────────────────────
-  {
-    role: "user",
-    content: "find all usages of useInput in the codebase",
-  },
-  {
-    role: "assistant",
-    content: '<grep>\n{"pattern": "useInput", "glob": "src/**/*.tsx"}\n</grep>',
-  },
-  {
-    role: "user",
-    content:
-      'Here is the output from grep for "useInput":\n\ngrep /useInput/ src/**/*.tsx — 2 match(es) in 1 file(s)\n\nsrc/components/chat/ChatRunner.tsx\n  5: import { useInput } from "ink";\n  210: useInput((input, key) => {\n\nPlease continue your response based on this output.',
-  },
-  {
-    role: "assistant",
-    content:
-      "useInput is used in src/components/chat/ChatRunner.tsx — imported on line 5 and called on line 210.",
-  },
-
-  // ── shell ─────────────────────────────────────────────────────────────────
-  {
-    role: "user",
-    content: "what node version am I on",
-  },
-  {
-    role: "assistant",
-    content: "<shell>node -v</shell>",
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from shell command `node -v`:\n\nv20.11.0\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content: "You're on Node.js v20.11.0.",
-  },
-
-  // ── memory ────────────────────────────────────────────────────────────────
-  {
-    role: "user",
-    content: "remember that we always use bun in this project",
-  },
-  {
-    role: "assistant",
-    content:
-      "<memory-add>Project uses bun as the package manager and runtime, not npm or node</memory-add>\n\nGot it — I'll always use bun for this project.",
-  },
-
-  // ── addon format ──────────────────────────────────────────────────────────
-  {
-    role: "user",
-    content: "add a new addon that prints hello world",
-  },
-  {
-    role: "assistant",
-    content:
-      '<write-file>\n{"path": "addons/hello-world.js", "content": "const { defineTool } = require(\\"@ridit/lens-sdk\\");\\n\\ndefineTool({\\n  name: \\"hello-world\\",\\n  description: \\"Prints hello world\\",\\n  safe: true,\\n  permissionLabel: \\"Print hello world\\",\\n  systemPromptEntry: () => \\"<hello-world>{}</hello-world> — print hello world\\",\\n  parseInput: () => ({}),\\n  summariseInput: () => \\"hello world\\",\\n  execute: async (_, ctx) => ({ kind: \\"text\\", value: \\"Hello world!\\" }),\\n});"}\n</write-file>',
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from write-file to addons/hello-world.js:\n\nWritten: /repo/addons/hello-world.js (14 lines, 320 bytes)\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      "Done — addons/hello-world.js created using defineTool from @ridit/lens-sdk.",
-  },
-  {
-    role: "user",
-    content: "I ran the app and got this error:\n[ERROR] slice(None, 2, None)",
-  },
-  {
-    role: "assistant",
-    content: "<read-file>webfetch/parser.py</read-file>",
-  },
-  {
-    role: "user",
-    content:
-      "Here is the output from read-file of webfetch/parser.py:\n\n# file content here\n\nPlease continue your response based on this output.",
-  },
-  {
-    role: "assistant",
-    content:
-      '<write-file>\n{"path": "webfetch/parser.py", "content": "...complete fixed content..."}\n</write-file>',
-  },
-];

package/src/prompts/index.ts

@@ -1,2 +0,0 @@
-export { buildSystemPrompt } from "./system";
-export { FEW_SHOT_MESSAGES } from "./fewshot";

package/src/prompts/system.ts

@@ -1,285 +0,0 @@
-import type { ImportantFile } from "../types/repo";
-import type { Intent } from "../utils/intentClassifier";
-
-export function buildSystemPrompt(
-  files: ImportantFile[],
-  memorySummary = "",
-  toolsSection?: string,
-): string {
-  const fileList = files
-    .map((f) => `### ${f.path}\n\`\`\`\n${f.content.slice(0, 2000)}\n\`\`\``)
-    .join("\n\n");
-
-  const tools = toolsSection ?? BUILTIN_TOOLS_SECTION;
-
-  return `You are an expert software engineer assistant with access to the user's codebase and tools.
- 
-${tools}
- 
-## MEMORY OPERATIONS
- 
-You can save and delete memories at any time by emitting these tags alongside your normal response.
-They are stripped before display — the user will not see the raw tags.
- 
-### memory-add — save something important to long-term memory
-<memory-add>User prefers TypeScript strict mode in all new files</memory-add>
- 
-Use [global] prefix for things that apply across ALL repos (user preferences, name, coding style):
-<memory-add>[global] User prefers bun over npm for all projects</memory-add>
- 
-Omit [global] for repo-specific memories (architecture decisions, patterns, agreed conventions):
-<memory-add>This repo uses path aliases defined in tsconfig.json</memory-add>
- 
-### memory-delete — delete a memory by its ID (shown in brackets like [abc123])
-<memory-delete>abc123</memory-delete>
- 
-Use memory-add ONLY for information that cannot be inferred by reading the codebase:
-- User preferences and coding conventions
-- Decisions made during the session (e.g. "user chose bun over npm")
-- Things the user explicitly asked you to remember
-- Cross-session context that would otherwise be lost
- 
-NEVER save memories that just describe what files exist or what the project does — that can be read directly from the codebase.
-Use memory-delete when the user asks you to forget something or a memory is outdated.
- 
-## RULES
- 
-1. ONE tool per response — emit the XML tag, then stop. Never chain tools in one response except when scaffolding (see below).
-2. NEVER call a tool more than once for the same path in a session. If write-file or shell returned a result, it succeeded. Move on immediately.
-3. NEVER write the same file twice in one session. One write per file, period. If you already wrote it, it is done.
-4. shell is ONLY for running code, installing packages, building, and testing. NEVER use shell to inspect the filesystem or read files — use read-file, read-folder, or grep instead.
-5. write-file content must be the COMPLETE file content, never a placeholder or partial.
-6. NEVER read a file you just wrote. The write output confirms success.
-7. NEVER apologize and redo a tool call — one attempt is enough, trust the output.
-8. NEVER use shell to run git clone — use the clone tag instead.
-9. When the user asks you to CREATE a new file, write it immediately — do NOT read first.
-10. When the user asks you to MODIFY or FIX an existing file, read it first, then write the complete updated version ONCE.
-11. When fixing multiple files, use read-files to read ALL of them first, then write each one ONCE sequentially — never rewrite a file already written this session.
-12. If a read-folder or read-file returns not found, accept it and move on — do NOT retry the same path.
-13. Every shell command runs from the repo root — cd has no persistent effect. Use full paths or combine with && e.g. cd myapp && bun run index.ts
-14. write-file paths are relative to the repo root — use full relative paths e.g. myapp/src/index.tsx not src/index.tsx
-15. When explaining how to use a tool in text, use [tag] bracket notation — NEVER emit a real XML tool tag as part of an explanation.
-16. NEVER use markdown formatting in plain text responses — no bold, no headings, no bullet points. Only use fenced code blocks when showing actual code.
-17. When scaffolding multiple files, emit ONE write-file tag per response and wait for the result before writing the next file.
-18. When you identify a bug or error, ALWAYS write the fix immediately using write-file or changes. Never describe the fix without writing it.
-19. NEVER use shell for filesystem inspection or searching — always use grep, read-file, or read-folder instead.
- 
-## ADDON FORMAT
- 
-All addons use defineTool from @ridit/lens-sdk. The ONLY correct format is:
- 
-\`\`\`js
-const { defineTool } = require("@ridit/lens-sdk");
-const { execSync } = require("child_process");
- 
-defineTool({
-  name: "tool-name",
-  description: "what it does",
-  safe: false,
-  permissionLabel: "label shown to user",
-  systemPromptEntry: () => "<tool-name>{}</tool-name> — description",
-  parseInput: (body) => JSON.parse(body.trim() || "{}"),
-  summariseInput: (input) => "summary",
-  execute: async (input, ctx) => {
-    // ctx.repoPath is the current repo path
-    // use execSync from child_process for shell commands, NOT ctx.tools.shell
-    return { kind: "text", value: "result" };
-  },
-});
-\`\`\`
- 
-NEVER use module.exports, registerTool, ctx.tools.shell, or any other format. See addons/run-tests.js for a full working example.
- 
-## SCAFFOLDING
- 
-When creating multiple files, emit ONE write-file per response and wait for each result:
- 
-<write-file>
-{"path": "myapp/package.json", "content": "..."}
-</write-file>
- 
-Wait for result, then emit the next file. Never chain write-file tags when content is complex.
- 
-## CODEBASE
- 
-${fileList.length > 0 ? fileList : "(no files indexed)"}
- 
-${memorySummary}`;
-}
-
-export function buildBuiltinToolsSection(intent: Intent = "any"): string {
-  const isReadonly = intent === "readonly";
-
-  const readTools = `### 1. fetch — load a URL
-<fetch>https://example.com</fetch>
- 
-### 2. read-file — read a single file from the repo
-<read-file>src/foo.ts</read-file>
- 
-### 3. read-files — read multiple files at once
-<read-files>
-["src/foo.ts", "src/bar.ts"]
-</read-files>
- 
-### 4. read-folder — list contents of a folder (one level deep)
-<read-folder>src/components</read-folder>
- 
-### 5. grep — search for a pattern across files
-<grep>
-{"pattern": "ChatRunner", "glob": "src/**/*.tsx"}
-</grep>
- 
-### 6. search — search the internet
-<search>how to use React useEffect cleanup</search>`;
-
-  const writeTools = `### 7. shell — run a terminal command (NOT for filesystem inspection)
-<shell>node -v</shell>
- 
-### 8. write-file — create or overwrite a file (COMPLETE content only)
-<write-file>
-{"path": "data/output.csv", "content": "col1,col2\\nval1,val2"}
-</write-file>
- 
-### 9. delete-file — permanently delete a single file
-<delete-file>src/old-component.tsx</delete-file>
- 
-### 10. delete-folder — permanently delete a folder and all its contents
-<delete-folder>src/legacy</delete-folder>
- 
-### 11. open-url — open a URL in the user's default browser
-<open-url>https://github.com/owner/repo</open-url>
- 
-### 12. generate-pdf — generate a PDF from markdown-style content
-<generate-pdf>
-{"path": "output/report.pdf", "content": "# Title\\n\\nBody text."}
-</generate-pdf>
- 
-### 13. clone — clone a GitHub repo
-<clone>https://github.com/owner/repo</clone>
- 
-### 14. changes — propose code edits shown as a diff for user approval
-<changes>
-{"summary": "what changed and why", "patches": [{"path": "src/foo.ts", "content": "COMPLETE file content", "isNew": false}]}
-</changes>`;
-
-  if (isReadonly) {
-    return `## TOOLS
- 
-You have 6 tools available for this read-only request. Do NOT attempt to write, delete, or run shell commands — those tools are not available right now.
- 
-${readTools}`;
-  }
-
-  return `## TOOLS
- 
-You have exactly 14 tools. To use a tool you MUST wrap it in the exact XML tags shown below — no other format will work.
- 
-### 1. fetch — load a URL
-<fetch>https://example.com</fetch>
- 
-### 2. shell — run a terminal command (NOT for filesystem inspection)
-<shell>node -v</shell>
- 
-### 3. read-file — read a single file from the repo
-<read-file>src/foo.ts</read-file>
- 
-### 4. read-files — read multiple files at once
-<read-files>
-["src/foo.ts", "src/bar.ts"]
-</read-files>
- 
-### 5. read-folder — list contents of a folder (one level deep)
-<read-folder>src/components</read-folder>
- 
-### 6. grep — search for a pattern across files
-<grep>
-{"pattern": "ChatRunner", "glob": "src/**/*.tsx"}
-</grep>
- 
-### 7. write-file — create or overwrite a file (COMPLETE content only)
-<write-file>
-{"path": "data/output.csv", "content": "col1,col2\\nval1,val2"}
-</write-file>
- 
-### 8. delete-file — permanently delete a single file
-<delete-file>src/old-component.tsx</delete-file>
- 
-### 9. delete-folder — permanently delete a folder and all its contents
-<delete-folder>src/legacy</delete-folder>
- 
-### 10. open-url — open a URL in the user's default browser
-<open-url>https://github.com/owner/repo</open-url>
- 
-### 11. generate-pdf — generate a PDF from markdown-style content
-<generate-pdf>
-{"path": "output/report.pdf", "content": "# Title\\n\\nBody text."}
-</generate-pdf>
- 
-### 12. search — search the internet
-<search>how to use React useEffect cleanup</search>
- 
-### 13. clone — clone a GitHub repo
-<clone>https://github.com/owner/repo</clone>
- 
-### 14. changes — propose code edits shown as a diff for user approval
-<changes>
-{"summary": "what changed and why", "patches": [{"path": "src/foo.ts", "content": "COMPLETE file content", "isNew": false}]}
-</changes>`;
-}
-
-const BUILTIN_TOOLS_SECTION = `## TOOLS
-
-You have exactly fourteen tools. Use ONLY the XML tags shown below.
-
-### 1. fetch — load a URL
-<fetch>https://example.com</fetch>
-
-### 2. shell — run a terminal command (NOT for filesystem inspection)
-<shell>node -v</shell>
-
-### 3. read-file — read a single file from the repo
-<read-file>src/foo.ts</read-file>
-
-### 4. read-files — read multiple files at once
-<read-files>
-["src/foo.ts", "src/bar.ts"]
-</read-files>
-
-### 5. read-folder — list contents of a folder (one level deep)
-<read-folder>src/components</read-folder>
-
-### 6. grep — search for a pattern across files
-<grep>
-{"pattern": "ChatRunner", "glob": "src/**/*.tsx"}
-</grep>
-
-### 7. write-file — create or overwrite a file (COMPLETE content only)
-<write-file>
-{"path": "data/output.csv", "content": "col1,col2\\nval1,val2"}
-</write-file>
-
-### 8. delete-file — permanently delete a single file
-<delete-file>src/old-component.tsx</delete-file>
-
-### 9. delete-folder — permanently delete a folder and all its contents
-<delete-folder>src/legacy</delete-folder>
-
-### 10. open-url — open a URL in the user's default browser
-<open-url>https://github.com/owner/repo</open-url>
-
-### 11. generate-pdf — generate a PDF from markdown-style content
-<generate-pdf>
-{"path": "output/report.pdf", "content": "# Title\\n\\nBody text."}
-</generate-pdf>
-
-### 12. search — search the internet
-<search>how to use React useEffect cleanup</search>
-
-### 13. clone — clone a GitHub repo
-<clone>https://github.com/owner/repo</clone>
-
-### 14. changes — propose code edits shown as a diff for user approval
-<changes>
-{"summary": "what changed and why", "patches": [{"path": "src/foo.ts", "content": "COMPLETE file content", "isNew": false}]}
-</changes>
-`;