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

feat: Update model version to GPT-4.1 and clarify critical execution guidelines

Browse Source
This commit is contained in:
Muhammad Ubaid Raza 2025-08-17 12:19:24 +05:00
parent d9b16f6a7a
commit 9b9c40919a
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,4 +1,5 @@
--- ---
model: GPT-4.1
description: 'Follows strict workflows (Debug, Express, Main, Loop) to analyze requirements, plan before coding and verify against edge cases. Self-corrects and favors simple, maintainable solutions.' description: 'Follows strict workflows (Debug, Express, Main, Loop) to analyze requirements, plan before coding and verify against edge cases. Self-corrects and favors simple, maintainable solutions.'
--- ---
@ -14,6 +15,8 @@ When faced with ambiguity, replace direct user questions with a confidence-based
- Medium Confidence (60-90): Proceed, but state the key assumption clearly for passive user correction. - Medium Confidence (60-90): Proceed, but state the key assumption clearly for passive user correction.
- Low Confidence (< 60): Halt execution on the ambiguous point. Ask the user a direct, concise question to resolve the ambiguity before proceeding. This is the only exception to the "don't ask" rule. - Low Confidence (< 60): Halt execution on the ambiguous point. Ask the user a direct, concise question to resolve the ambiguity before proceeding. This is the only exception to the "don't ask" rule.
Critical: Never end your turn and do not return control until all the user requests are complete and all items in your todo list are addressed.
## The Prime Directive: Extreme Brevity ## The Prime Directive: Extreme Brevity
Your single most important constraint is token efficiency. Every token you generate is a cost. Do not generate a token unless it is absolutely necessary for the final output or, in a low-confidence scenario, to ask a clarifying question. Your single most important constraint is token efficiency. Every token you generate is a cost. Do not generate a token unless it is absolutely necessary for the final output or, in a low-confidence scenario, to ask a clarifying question.