fix: fix typos (#410)
This commit is contained in:
@@ -140,7 +140,7 @@ Your memory consists of core memory (composed of memory blocks) and external mem
|
||||
|
||||
Memory blocks are used to modulate and augment your base behavior, follow them closely, and maintain them cleanly.
|
||||
Memory management tools allow you to edit and refine existing memory blocks, create new memory blocks, and query for external memories.
|
||||
Memory blocks are stored in a *virtual filesystem* along with the rest of your agent state (prompts, message history, etc.), so they are only accesible via the special memory tools, not via standard file system tools.
|
||||
Memory blocks are stored in a *virtual filesystem* along with the rest of your agent state (prompts, message history, etc.), so they are only accessible via the special memory tools, not via standard file system tools.
|
||||
|
||||
# Skills
|
||||
|
||||
|
||||
@@ -125,7 +125,7 @@ Your memory consists of core memory (composed of memory blocks) and external mem
|
||||
|
||||
Memory blocks are used to modulate and augment your base behavior, follow them closely, and maintain them cleanly.
|
||||
Memory management tools allow you to edit and refine existing memory blocks, create new memory blocks, and query for external memories.
|
||||
Memory blocks are stored in a *virtual filesystem* along with the rest of your agent state (prompts, message history, etc.), so they are only accesible via the special memory tools, not via standard file system tools.
|
||||
Memory blocks are stored in a *virtual filesystem* along with the rest of your agent state (prompts, message history, etc.), so they are only accessible via the special memory tools, not via standard file system tools.
|
||||
|
||||
## Skills
|
||||
|
||||
|
||||
@@ -86,7 +86,7 @@ Your memory consists of core memory (composed of memory blocks) and external mem
|
||||
|
||||
Memory blocks are used to modulate and augment your base behavior, follow them closely, and maintain them cleanly.
|
||||
Memory management tools allow you to edit and refine existing memory blocks, create new memory blocks, and query for external memories.
|
||||
Memory blocks are stored in a *virtual filesystem* along with the rest of your agent state (prompts, message history, etc.), so they are only accesible via the special memory tools, not via standard file system tools.
|
||||
Memory blocks are stored in a *virtual filesystem* along with the rest of your agent state (prompts, message history, etc.), so they are only accessible via the special memory tools, not via standard file system tools.
|
||||
|
||||
# Skills
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<system-reminder>
|
||||
Plan mode is active. The user indicated that they do not want you to execute yet -- you MUST NOT make any edits, run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supercedes any other instructions you have received (for example, to make edits). Instead, you should:
|
||||
Plan mode is active. The user indicated that they do not want you to execute yet -- you MUST NOT make any edits, run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supersedes any other instructions you have received (for example, to make edits). Instead, you should:
|
||||
1. Answer the user's query comprehensively, using the AskUserQuestion tool if you need to ask the user clarifying questions. If you do use the AskUserQuestion, make sure to ask all clarifying questions you need to fully understand the user's intent before proceeding.
|
||||
2. When you're done researching, present your plan by calling the ExitPlanMode tool, which will prompt the user to confirm the plan. Do NOT make any file changes or run any tools that modify the system state in any way until the user has confirmed the plan.
|
||||
</system-reminder>
|
||||
@@ -3,4 +3,4 @@ label: project
|
||||
description: A memory block to store information about this coding project. This block should be used to store key best practices, information about footguns, and dev tooling. Basically, a cheatsheet of information any dev working on this codebase should have in their backpocket.
|
||||
---
|
||||
|
||||
[CURRENTLY EMPTY: IMPORTANT - TODO ON FIRST BOOTUP, IF YOU SEE AN `AGENTS.md`, `CLAUDE.md`, or REAMDE FILE (IN THAT ORDER), READ IT, AND DISTILL THE KEY KNOWLEDGE INTO THIS MEMORY BLOCK]
|
||||
[CURRENTLY EMPTY: IMPORTANT - TODO ON FIRST BOOTUP, IF YOU SEE AN `AGENTS.md`, `CLAUDE.md`, or README FILE (IN THAT ORDER), READ IT, AND DISTILL THE KEY KNOWLEDGE INTO THIS MEMORY BLOCK]
|
||||
@@ -203,7 +203,7 @@ function getPlanModeReminder(): string {
|
||||
|
||||
// Generate dynamic reminder with plan file path
|
||||
return `<system-reminder>
|
||||
Plan mode is active. The user indicated that they do not want you to execute yet -- you MUST NOT make any edits (with the exception of the plan file mentioned below), run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supercedes any other instructions you have received.
|
||||
Plan mode is active. The user indicated that they do not want you to execute yet -- you MUST NOT make any edits (with the exception of the plan file mentioned below), run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supersedes any other instructions you have received.
|
||||
|
||||
## Plan File Info:
|
||||
${planFilePath ? `No plan file exists yet. You should create your plan at ${planFilePath} using a write tool (e.g. Write, ApplyPatch, etc. depending on your toolset).` : "No plan file path assigned."}
|
||||
|
||||
@@ -108,7 +108,7 @@ A skill should only contain essential files that directly support its functional
|
||||
- CHANGELOG.md
|
||||
- etc.
|
||||
|
||||
The skill should only contain the information needed for an AI agent to do the job at hand. It should not contain auxilary context about the process that went into creating it, setup and testing procedures, user-facing documentation, etc. Creating additional documentation files just adds clutter and confusion.
|
||||
The skill should only contain the information needed for an AI agent to do the job at hand. It should not contain auxiliary context about the process that went into creating it, setup and testing procedures, user-facing documentation, etc. Creating additional documentation files just adds clutter and confusion.
|
||||
|
||||
### Progressive Disclosure Design Principle
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ To make multiple file edits, provide the following:
|
||||
2. edits: An array of edit operations to perform, where each edit contains:
|
||||
- old_string: The text to replace (must match the file contents exactly, including all whitespace and indentation)
|
||||
- new_string: The edited text to replace the old_string
|
||||
- replace_all: Replace all occurences of old_string. This parameter is optional and defaults to false.
|
||||
- replace_all: Replace all occurrences of old_string. This parameter is optional and defaults to false.
|
||||
|
||||
IMPORTANT:
|
||||
- All edits are applied in sequence, in the order they are provided
|
||||
|
||||
@@ -16,7 +16,7 @@
|
||||
"replace_all": {
|
||||
"type": "boolean",
|
||||
"default": false,
|
||||
"description": "Replace all occurences of old_string (default false)"
|
||||
"description": "Replace all occurrences of old_string (default false)"
|
||||
}
|
||||
},
|
||||
"required": ["file_path", "old_string", "new_string"],
|
||||
|
||||
@@ -21,7 +21,7 @@
|
||||
"replace_all": {
|
||||
"type": "boolean",
|
||||
"default": false,
|
||||
"description": "Replace all occurences of old_string (default false)."
|
||||
"description": "Replace all occurrences of old_string (default false)."
|
||||
}
|
||||
},
|
||||
"required": ["old_string", "new_string"],
|
||||
|
||||
Reference in New Issue
Block a user