From f491615403a2f0ef3d03a0a59510f7455149dbbb Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Mon, 20 Apr 2026 17:51:27 +0000
Subject: [PATCH] chore: sync repo state [ci skip]

---
 README.md                                     |  1 +
 .../skills/prompt-engineer/SKILL.md           | 28 +++++++++++++++++++
 .../skills/prompt-engineer/SKILL.md           | 28 +++++++++++++++++++
 3 files changed, 57 insertions(+)

diff --git a/README.md b/README.md
index d6aeb9ec..da023b95 100644
--- a/README.md
+++ b/README.md
@@ -571,6 +571,7 @@ We officially thank the following contributors for their help in making this rep
 - [@Imasaikiran](https://github.com/Imasaikiran)
 - [@justmiroslav](https://github.com/justmiroslav)
 - [@1bcMax](https://github.com/1bcMax)
+- [@xiaolai](https://github.com/xiaolai)
 
 ## Star History
 
diff --git a/plugins/antigravity-awesome-skills-claude/skills/prompt-engineer/SKILL.md b/plugins/antigravity-awesome-skills-claude/skills/prompt-engineer/SKILL.md
index 8c0d45f1..9a116e43 100644
--- a/plugins/antigravity-awesome-skills-claude/skills/prompt-engineer/SKILL.md
+++ b/plugins/antigravity-awesome-skills-claude/skills/prompt-engineer/SKILL.md
@@ -53,6 +53,34 @@ Invoke this skill when:
 - **Structured tasks:** Mentions steps, phases, deliverables, stakeholders
 
 
+### Step 2: Ask Clarifying Questions (Conditional)
+
+**Objective:** Gather missing information only when it is critical to framework selection or prompt quality.
+
+**Trigger Conditions** — ask only if:
+- Task type is completely ambiguous (cannot determine coding vs. writing vs. analysis)
+- Target audience is unknown and materially affects the output
+- Scope is undefined and choosing wrong scope would invalidate the prompt
+- Requested output format conflicts or is missing and cannot be inferred
+
+**Question Limits:**
+- Maximum 3 questions per invocation
+- Combine related questions into one when possible
+- If enough context exists, skip this step entirely (most cases)
+
+**Example Clarifying Exchange:**
+
+```
+User: "help me with AI"
+
+Step 2 (triggered — task type ambiguous):
+"To craft the best prompt, I need one quick clarification:
+1. What do you want to do with AI — build something, learn about it, or use an AI tool for a task?"
+```
+
+**Critical Rule:** When in doubt, skip clarification and generate the best prompt with available context. Over-asking breaks the "magic mode" experience.
+
+
 ### Step 3: Select Framework(s)
 
 **Objective:** Map task characteristics to optimal prompting framework(s).
diff --git a/plugins/antigravity-awesome-skills/skills/prompt-engineer/SKILL.md b/plugins/antigravity-awesome-skills/skills/prompt-engineer/SKILL.md
index 8c0d45f1..9a116e43 100644
--- a/plugins/antigravity-awesome-skills/skills/prompt-engineer/SKILL.md
+++ b/plugins/antigravity-awesome-skills/skills/prompt-engineer/SKILL.md
@@ -53,6 +53,34 @@ Invoke this skill when:
 - **Structured tasks:** Mentions steps, phases, deliverables, stakeholders
 
 
+### Step 2: Ask Clarifying Questions (Conditional)
+
+**Objective:** Gather missing information only when it is critical to framework selection or prompt quality.
+
+**Trigger Conditions** — ask only if:
+- Task type is completely ambiguous (cannot determine coding vs. writing vs. analysis)
+- Target audience is unknown and materially affects the output
+- Scope is undefined and choosing wrong scope would invalidate the prompt
+- Requested output format conflicts or is missing and cannot be inferred
+
+**Question Limits:**
+- Maximum 3 questions per invocation
+- Combine related questions into one when possible
+- If enough context exists, skip this step entirely (most cases)
+
+**Example Clarifying Exchange:**
+
+```
+User: "help me with AI"
+
+Step 2 (triggered — task type ambiguous):
+"To craft the best prompt, I need one quick clarification:
+1. What do you want to do with AI — build something, learn about it, or use an AI tool for a task?"
+```
+
+**Critical Rule:** When in doubt, skip clarification and generate the best prompt with available context. Over-asking breaks the "magic mode" experience.
+
+
 ### Step 3: Select Framework(s)
 
 **Objective:** Map task characteristics to optimal prompting framework(s).