Writing Introductory Descriptions

Implementation Steps

1. Engaging Title: Use visual Emojis + Core Feature Name (e.g., 🧱 灵活的挖掘与放置系统).
2. Contextual Intro: One sentence setting the stage of what this feature does overall from the user's perspective.
3. Numbered Steps (Focusing on flow):
   • Step 1 (Intent & Targeting): How the user indicates intent (e.g., looking at something, aiming the crosshair).
   • Step 2 (Action & Feedback): The interaction (holding click, pressing a key) and the immediate feedback (highlight, progress bar).
   • Step 3 (Result & Consequence): The final outcome (block placed, resources consumed, inventory updated).
4. Summary: A brief concluding sentence emphasizing the feeling or experience (e.g., "沉浸感", "真实的创造体验").

Quick Reference Checklist

• Are technical terms (Manager, Raycaster, Array, Event Bus) completely removed?
• Are verbs focused on human actions (看向, 点击, 长按)?
• Are emojis used to break up text and make it friendly?
• Is there an analogy comparing the feature to an everyday concept?

Common Mistakes

• Leaking architecture: Mentioning internal variable names or design patterns (e.g., "单向数据流") in the plain language version.
• Overly abstract: Being so high-level that it doesn't describe what the user actually does (e.g., "系统会处理你的输入并改变世界" instead of "你长按鼠标就能改变世界").
• Mechanical tone: Using dry, manual-like language instead of an enthusiastic, conversational, and direct tone.