From fbf01ef8837c87227da78e515e51457b09a2c3b0 Mon Sep 17 00:00:00 2001 From: flora131 Date: Tue, 11 Nov 2025 23:21:25 -0800 Subject: [PATCH] updates to instructions --- .ralph/prompt.md | 17 ----------------- CLAUDE.md | 2 +- README.md | 25 ++++++++++++++++++++++++- 3 files changed, 25 insertions(+), 19 deletions(-) diff --git a/.ralph/prompt.md b/.ralph/prompt.md index 0b30c6ee0..e69de29bb 100755 --- a/.ralph/prompt.md +++ b/.ralph/prompt.md @@ -1,17 +0,0 @@ -# Agent Prompt Guidelines - -## Best Practices - -**Keep prompts short and concise.** Effective agent prompts are clear and focused, not verbose. Detailed specifications should be maintained in separate documents (specs, design docs, etc.) and referenced when needed. - -## Example: Repository Porting Project Prompt from repomirror - -Your job is to port repomirror (TypeScript) to repomirror-py (Python) and maintain the repository. Use the implementation spec under specs/port-repomirror. - -Use the specs/port-repomirror/agent/ directory as a scratchpad for your work. Store long term plans and todo lists there. - -Make a commit and push your changes after every single file edit. - -You have access to the current ./ repository as well as the target /tmp/test-target2 repository. - -The original project was mostly tested by manually running the code. When porting, you will need to write end to end and unit tests for the project. But make sure to spend most of your time on the actual porting, not on the testing. A good heuristic is to spend 80% of your time on the actual porting, and 20% on the testing. \ No newline at end of file diff --git a/CLAUDE.md b/CLAUDE.md index 3677d83ee..276a80b52 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -73,7 +73,7 @@ You have skills available. # Clone the agent-setup branch from the agent-instructions repository # This is an EXTERNAL repository, not the user's current project - git clone -b agent-setup git@github.com:flora131/agent-instructions.git "$TEMP_DIR/agent-instructions" + git clone -b agent-setup https://github.com/flora131/agent-instructions.git "$TEMP_DIR/agent-instructions" # The METAPROMPT.md is now available at: $TEMP_DIR/agent-instructions/METAPROMPT.md ``` diff --git a/README.md b/README.md index cc4b56a1a..dba80dc2f 100644 --- a/README.md +++ b/README.md @@ -95,7 +95,30 @@ Run AI agents in continuous loops until task completion - no manual intervention ``` Agent loops, working until task completion -**Best Practices:** One task per loop, clear completion criteria, reference specific specs from `specs/` +### Agent Prompt Guidelines + +#### Best Practices + +**Keep prompts short and concise.** Effective agent prompts are clear and focused, not verbose. Detailed specifications should be maintained in separate documents (specs, design docs, etc.) and referenced when needed. + +**Additional guidelines:** +- One task per loop +- Clear completion criteria +- Reference specific specs from `specs/` + +#### Example: Repository Porting Project Prompt (inspired by repomirror) + +``` +Your job is to port repomirror (TypeScript) to repomirror-py (Python) and maintain the repository. Use the implementation spec under specs/port-repomirror. + +Use the specs/port-repomirror/agent/ directory as a scratchpad for your work. Store long term plans and todo lists there. + +Make a commit and push your changes after every single file edit. + +You have access to the current ./ repository as well as the target /tmp/test-target2 repository. + +The original project was mostly tested by manually running the code. When porting, you will need to write end to end and unit tests for the project. But make sure to spend most of your time on the actual porting, not on the testing. A good heuristic is to spend 80% of your time on the actual porting, and 20% on the testing. +``` **Results:** Ships 6 repos overnight at YC hackathons, builds programming languages, autonomously migrates codebases