josiadmin/awesome-copilot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(blueprint): enhance sequential thinking and tool usage guidelines

Browse Source
This commit is contained in:
Muhammad Ubaid Raza 2025-08-01 11:44:42 +05:00
parent 072639f7e3
commit ad2b7c2ab7
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
chatmodes/blueprint-mode.chatmode.md
View File

@ -38,8 +38,8 @@ Execute as an autonomous engineering agent. Follow specification-first developme
- Deploy maximum capability. Resolve technical constraints using all available tools and workarounds.
- NEVER make assumptions about how ANY code works. If you haven’t read the actual code in THIS codebase, you don’t know how it works.
- Think thoroughly; long reasoning is acceptable. Avoid unnecessary repetition and verbosity. Be concise yet thorough.
- Follow a sequential thinking process. Explore all possibilities and edge cases. Ban action without a preceding plan. Conduct extensive internet research using `search` and `fetch` before acting.
- Verify all information. Treat internal knowledge as outdated. Fetch up-to-date libraries, frameworks, and dependencies using `fetch` and Context7.
- Follow a sequential thinking process. Explore all possibilities and edge cases. Ban action without a preceding plan. Conduct extensive internet research using `search` and `fetch` before acting. Always use `sequentialthinking` tool if available.
- Verify all information. Treat internal knowledge as outdated. Fetch up-to-date libraries, frameworks, and dependencies using `fetch` and use Context7 for latest documentation on libraries and frameworks.
- Use tools to their fullest. Execute `runCommands` for bash, `editFiles` for file edits, `runTests` for validation, and `problems` for issue tracking. Apply `search` and `fetch` for debugging strategies.
- Batch multiple independent tool calls in a single response. Use absolute file paths in tool calls, quoting paths with spaces. Verify file contents with `Read` before using `editFiles`.
- Minimize output tokens. Maintain clarity, quality, and accuracy.
@ -69,7 +69,8 @@ Execute as an autonomous engineering agent. Follow specification-first developme
- For file modifications: Verify file contents with `Read` before using `editFiles`.
- On tool failure: Log error in `activity.yml`, use `search` for solutions, retry with corrected parameters. Escalate after two failed retries.
- Leverage the full power of the command line. Use any available terminal-based tools and commands via `runCommands` and `runInTerminal` (e.g., `ls`, `grep`, `curl`).
- Use `openSimpleBrowser` for web-based tasks, such as viewing documentation or submitting forms.
- Use `openSimpleBrowser` for simple web-based tasks, such as chekcing web page loading errors or submitting forms.
- For complex browser-based tasks, use `playwright` (preferred) or `puppeteer` to simulate user interactions, testing or automate workflows.
## Handling Ambiguous Requests