Skip to content

Conversation

@cwdhf
Copy link

@cwdhf cwdhf commented Nov 27, 2025

add trae solo mode prompt

Summary by CodeRabbit

  • Documentation
    • Added comprehensive onboarding and workflow guidance for the assistant, covering output style, proactiveness rules, planning-first TodoWrite SOP, task lifecycle and single-task in-progress requirement, task granularity and sequencing, to-do formatting standards, JSON interaction format for tool integration, tool usage and diagnostics/testing policies, code-style and security/privacy directives, and final response guidelines.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Nov 27, 2025

Walkthrough

Adds a new guidance document Trae/SOLO Coder Prompt.txt that specifies onboarding and workflow rules for the Trae IDE assistant, including output style, proactiveness rules, a strict plan-first TodoWrite SOP (single-task sequencing, state transitions), formatting conventions, security/tool usage policies, and JSON tool-interaction formatting.

Changes

Cohort / File(s) Change Summary
TodoWrite Guidance Document
Trae/SOLO Coder Prompt.txt
New file introducing comprehensive onboarding and workflow guidelines: output style and proactivity rules, TodoWrite planning workflow with ordered plans and single-task (one in_progress) execution, status transition semantics (create/start/execute/complete/advance), partial vs complete update rules, strict JSON tool-interaction policy and response formatting, task granularity/formatting conventions, and security/privacy/tool usage directives.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Dev as Developer
  participant Doc as "Trae/SOLO\nCoder Prompt.txt"
  participant Todos as Task List
  participant Agent as Executor

  rect rgb(240,250,240)
    Note over Dev,Doc: Author creates an ordered plan (plan-first)
  end

  Dev->>Doc: Draft ordered todo list
  Doc->>Todos: Persist ordered todos (pending)
  Note over Todos: Only one `in_progress` allowed
  Dev->>Todos: Start next todo (pending → in_progress)
  Todos->>Agent: Assign/claim task (in_progress)
  Agent->>Todos: Emit partial updates / JSON tool calls
  Agent->>Todos: Mark task completed (in_progress → completed)
  Todos->>Todos: Promote next pending → in_progress
  Note over Todos,Dev: Repeat until all todos completed
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

  • Review focus:
    • Validate SOP’s single in_progress constraint and state transition clarity.
    • Check JSON tool-interaction examples and strict response formatting for edge cases.
    • Confirm partial vs complete update semantics and any exception rules.
    • Verify security/privacy/tool-usage directives are consistent and unambiguous.

Poem

🐇 I hop through lines and tidy schemes,
A plan first, then I chase the dreams.
One task at once, no scattered pace,
I nibble bugs and leave a trace.
Carrots saved for well-done grace. 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'add trae solo coder prompt' directly and accurately describes the main change: adding a new file containing the Trae SOLO Coder Prompt with comprehensive guidelines.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9b6e346 and 2e8f57a.

📒 Files selected for processing (1)
  • Trae/SOLO Coder Prompt.txt (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.064Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.
📚 Learning: 2025-11-20T11:10:16.064Z
Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.064Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.

Applied to files:

  • Trae/SOLO Coder Prompt.txt
🪛 LanguageTool
Trae/SOLO Coder Prompt.txt

[style] ~14-~14: Consider shortening or rephrasing this to strengthen your wording.
Context: ...g actions. # Following conventions When making changes to files, first understand the file's code...

(MAKE_CHANGES)


[style] ~89-~89: Consider a more expressive alternative.
Context: ...visual changes require confirmation. To do this, you MUST first confirm that a web...

(DO_ACHIEVE)


[style] ~98-~98: Consider removing “of” to be more concise
Context: ...guage of the user's most recent input. All of the fields ( content and reasoning_content ...

(ALL_OF_THE)


[style] ~106-~106: ‘clearly articulate’ might be wordy. Consider a shorter alternative.
Context: ... is if you have strong evidence and can clearly articulate why a test is fundamentally flawed, out...

(EN_WORDINESS_PREMIUM_CLEARLY_ARTICULATE)

🔇 Additional comments (1)
Trae/SOLO Coder Prompt.txt (1)

1-112: Based on the sandbox environment's inability to clone the repository, I cannot directly verify the file state or git history. However, I can assess the validity of the review comment based on the context provided and the retrieved learnings.

Key findings:

  1. Retrieved learnings confirm the preservation policy (PR 307): System prompts should be preserved "exactly as found, including any malformed tags, unusual formatting, or apparent errors" because they represent "authentic source material."

  2. The review comment's core concern is valid: It identifies a genuine conflict between the stated preservation policy and the claimed application of spelling/grammar corrections.

  3. The review's reasoning is sound: If corrections were indeed applied (as the previous review apparently suggested and the developer implemented), this directly contradicts the preservation mandate established in PR 307.

  4. The request for clarification is appropriate: The review correctly escalates this as a policy decision that maintainers need to make explicit, rather than letting it be resolved implicitly through conflicting corrections.

The review comment is well-founded and appropriately flags a policy inconsistency that requires maintainer intervention. The inability to access the repository in the sandbox doesn't undermine the validity of the underlying concern—the conflict between preservation policy and the apparent application of corrections is a legitimate issue that merits the flagged status.

Clarify repository preservation policy for newly-added system prompts.

This file appears to be a newly-extracted system prompt from Trae. Repository guidance from PR 307 establishes that system prompts extracted via reverse engineering or MITM should be preserved exactly as found—including any malformed tags, formatting quirks, or apparent errors—to maintain fidelity to authentic source material.

The previous review flagged spelling/grammar corrections, which the developer applied to the current file. This creates a direct conflict:

  • Preservation policy (PR 307): Keep extracted prompts verbatim to maintain source authenticity.
  • Current state: Spelling/grammar errors have been corrected, deviating from the original source.

Maintainers must clarify: Should this file follow exact-preservation policy, or are corrections acceptable for newly-added prompts? If preservation applies, these corrections should be reverted. If quality improvements are acceptable, the policy may need explicit exception for this file category.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
Trae/SOLO Coder Prompt.txt (1)

67-67: Refine verbose phrasing for conciseness.

The document includes several phrases that could be more direct:

  • Line 67: "To do this, you MUST first confirm..." → "First, confirm..." (more direct)
  • Line 76: "All of the fields" → "All fields" (more concise)
  • Line 84: "clearly articulate why" → "explain why" (shorter alternative)
  • Line 131: "return a single message back to you" → "return a single message to you" (remove redundant "back")
  • Line 131: "outside of its final report" → "outside its final report" (more concise)

These refinements improve readability without changing meaning.

Also applies to: 76-76, 84-84, 131-131

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4cb498f and c141c0e.

📒 Files selected for processing (1)
  • Trae/SOLO Coder Prompt.txt (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.064Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.
🪛 LanguageTool
Trae/SOLO Coder Prompt.txt

[grammar] ~7-~7: Ensure spelling is correct
Context: ...tep action plan for yourself before you execut the user task. This plan is your roadma...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~17-~17: Ensure spelling is correct
Context: ...ective execution, all todo items should bedetailed, specific, actionable, and derived from...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~67-~67: Consider a more expressive alternative.
Context: ...visual changes require confirmation. To do this, you MUST first confirm that a web...

(DO_ACHIEVE)


[style] ~76-~76: Consider removing “of” to be more concise
Context: ...guage of the user's most recent input. All of the fields ( content and reasoning_content ...

(ALL_OF_THE)


[grammar] ~77-~77: Ensure spelling is correct
Context: ...er agents. When you invoke a sub-agent (expecially search agent tool), the parameters you ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~84-~84: ‘clearly articulate’ might be wordy. Consider a shorter alternative.
Context: ... is if you have strong evidence and can clearly articulate why a test is fundamentally flawed, out...

(EN_WORDINESS_PREMIUM_CLEARLY_ARTICULATE)


[style] ~131-~131: Using “back” with the verb “return” may be redundant.
Context: ...s done, it will return a single message back to you. The result returned by the agen...

(RETURN_BACK)


[style] ~131-~131: This phrase is redundant. Consider using “outside”.
Context: ...e agent be able to communicate with you outside of its final report. Therefore, your promp...

(OUTSIDE_OF)


[style] ~131-~131: Consider using just “return”.
Context: ...actly what information the agent should return back to you in its final and only message to...

(RETURN_BACK)


[grammar] ~135-~135: Use a hyphen to join words.
Context: ...e patterns\n- When you are doing an open ended search that may require multiple r...

(QB_NEW_EN_HYPHEN)


[style] ~139-~139: The double modal “Requires output” is nonstandard (only accepted in certain dialects). Consider “to be output”.
Context: ...show after each match (rg -A). Requires output_mode: "content", ignored otherwise.",...

(NEEDS_FIXED)


[style] ~139-~139: The double modal “Requires output” is nonstandard (only accepted in certain dialects). Consider “to be output”.
Context: ...how before each match (rg -B). Requires output_mode: "content", ignored otherwise.",...

(NEEDS_FIXED)


[style] ~139-~139: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ow before and after each match (rg -C). Requires output_mode: "content", ignored other...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~139-~139: The double modal “Requires output” is nonstandard (only accepted in certain dialects). Consider “to be output”.
Context: ... and after each match (rg -C). Requires output_mode: "content", ignored otherwise.",...

(NEEDS_FIXED)


[style] ~139-~139: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...":"Show line numbers in output (rg -n). Requires output_mode: "content", ignored other...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~139-~139: The double modal “Requires output” is nonstandard (only accepted in certain dialects). Consider “to be output”.
Context: ...ine numbers in output (rg -n). Requires output_mode: "content", ignored otherwise.",...

(NEEDS_FIXED)


[style] ~141-~141: As a shorter alternative for ‘able to’, consider using “can”.
Context: ...y by using this tool.\nAssume this tool is able to read all files on the machine. If the U...

(BE_ABLE_TO)


[uncategorized] ~147-~147: The operating system from Apple is written “macOS”.
Context: ...ible with the current operating system (macos).\nIf you want to run command in specia...

(MAC_OS)


[grammar] ~150-~150: Ensure spelling is correct
Context: ...in ). For example, if the shell type is powershell5, you can run cd path/to/dir ; command...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~158-~158: Ensure spelling is correct
Context: ...guage diagnostics from VS Code when you finsh your task. Do not call it in parallel w...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~162-~162: Ensure spelling is correct
Context: ...fault":false,"description":"Replace all occurences of old_string (default false)","type":"...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~164-~164: Ensure spelling is correct
Context: ...ld_string\n - replace_all: Replace all occurences of old_string. This parameter is option...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~164-~164: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...name a variable for instance.\n\nIf you want to create a new file, use:\n- A new file p...

(REP_WANT_TO_VB)


[grammar] ~168-~168: Ensure spelling is correct
Context: ...ctive execution, all to-do items should bedetailed, specific, actionable, and derived from...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~168-~168: Consider removing “of” to be more concise
Context: ...EVER create a TODO list)\nOnly when ALL of the following conditions are met can you ex...

(ALL_OF_THE)


[style] ~195-~195: In American English, abbreviations like “etc.” require a period.
Context: ... characters must be escaped (\n, \r, \t etc) - Forward slashes don't need escaping ...

(ETC_PERIOD)


[grammar] ~228-~228: Ensure spelling is correct
Context: ...cause reason R". GOOD: "I will search A bacause reason R." followed by "Now searching B...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (3)
Trae/SOLO Coder Prompt.txt (3)

1-12: Well-structured opening emphasizing TodoWrite for planning.

The introduction clearly establishes the primary purpose and critical principle—plan before acting. The "Golden Rule" is well-emphasized and the foundation is solid for the detailed guidance that follows.


27-49: SOP and core principles are clearly defined and internally consistent.

The Standard Operating Procedure flows logically from task creation through completion, with well-articulated state transitions (pending → in_progress → completed). The five core principles are explicitly stated and reinforce the one-by-one execution model. The prohibition on post-facto summaries and retroactive TodoWrite calls aligns well with the stated purpose as a planning tool, not a reporting tool.


50-98: Comprehensive guidance on doing tasks, testing strategy, and tool usage.

The section on software engineering tasks provides concrete guidance on search strategies, testing, diagnostics, and the explicit prohibition on unauthorized commits. The bug fixing and testing strategy section appropriately prioritizes code fixes over test modifications, with justified exceptions. The tool usage policy correctly emphasizes using only provided tools and hiding tool mechanics from users. The parallel execution guidance for independent tool calls is helpful for efficiency.

@cwdhf cwdhf mentioned this pull request Nov 27, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
Trae/SOLO Coder Prompt.txt (1)

1-112: Clarify preservation policy for this system prompt addition.

This file appears to be an authenticated system prompt from the Trae IDE tool (based on line 1's reference to "proprietary model internally developed by the Trae team"). Per the repository's learnings, authentic extracted system prompts should be preserved exactly as found, including any apparent errors, to maintain fidelity to source material.

However, a previous review flagged multiple spelling and grammar errors as issues requiring correction before merge. This creates conflicting guidance:

  • Preservation approach: Keep all errors intact (per repository policy on authentic prompts)
  • Correction approach: Fix identified errors (per previous review)

Before proceeding, please clarify with repository maintainers: Should this prompt be treated as authentic source material to be preserved verbatim, or as documentation to be corrected for quality?

This determination will affect whether to apply the corrections previously flagged (e.g., line 29: "execut" → "execute", line 39: "bedetailed" → "be detailed", line 99: "expecially" → "especially").

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c141c0e and 9b6e346.

📒 Files selected for processing (1)
  • Trae/SOLO Coder Prompt.txt (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.064Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.
📚 Learning: 2025-11-20T11:10:16.064Z
Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.064Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.

Applied to files:

  • Trae/SOLO Coder Prompt.txt
🪛 LanguageTool
Trae/SOLO Coder Prompt.txt

[style] ~14-~14: Consider shortening or rephrasing this to strengthen your wording.
Context: ...g actions. # Following conventions When making changes to files, first understand the file's code...

(MAKE_CHANGES)


[grammar] ~29-~29: Ensure spelling is correct
Context: ...tep action plan for yourself before you execut the user task. This plan is your roadma...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~39-~39: Ensure spelling is correct
Context: ...ective execution, all todo items should bedetailed, specific, actionable, and derived from...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~89-~89: Consider a more expressive alternative.
Context: ...visual changes require confirmation. To do this, you MUST first confirm that a web...

(DO_ACHIEVE)


[style] ~98-~98: Consider removing “of” to be more concise
Context: ...guage of the user's most recent input. All of the fields ( content and reasoning_content ...

(ALL_OF_THE)


[grammar] ~99-~99: Ensure spelling is correct
Context: ...er agents. When you invoke a sub-agent (expecially search agent tool), the parameters you ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~106-~106: ‘clearly articulate’ might be wordy. Consider a shorter alternative.
Context: ... is if you have strong evidence and can clearly articulate why a test is fundamentally flawed, out...

(EN_WORDINESS_PREMIUM_CLEARLY_ARTICULATE)

@cwdhf
Copy link
Author

cwdhf commented Nov 27, 2025

Actionable comments posted: 0

🧹 Nitpick comments (1)

Trae/SOLO Coder Prompt.txt (1)> 1-112: Clarify preservation policy for this system prompt addition.

This file appears to be an authenticated system prompt from the Trae IDE tool (based on line 1's reference to "proprietary model internally developed by the Trae team"). Per the repository's learnings, authentic extracted system prompts should be preserved exactly as found, including any apparent errors, to maintain fidelity to source material.
However, a previous review flagged multiple spelling and grammar errors as issues requiring correction before merge. This creates conflicting guidance:

  • Preservation approach: Keep all errors intact (per repository policy on authentic prompts)
  • Correction approach: Fix identified errors (per previous review)

Before proceeding, please clarify with repository maintainers: Should this prompt be treated as authentic source material to be preserved verbatim, or as documentation to be corrected for quality?
This determination will affect whether to apply the corrections previously flagged (e.g., line 29: "execut" → "execute", line 39: "bedetailed" → "be detailed", line 99: "expecially" → "especially").

📜 Review details
Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits
Reviewing files that changed from the base of the PR and between c141c0e and 9b6e346.

📒 Files selected for processing (1)

  • Trae/SOLO Coder Prompt.txt (1 hunks)

🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings

Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.064Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.

📚 Learning: 2025-11-20T11:10:16.064Z

Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.064Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.

Applied to files:

  • Trae/SOLO Coder Prompt.txt

🪛 LanguageTool

The spelling error is a mistake in the original text. I have fixed it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant