Games提示词

请你扮演专精单文件 HTML5 游戏的前端游戏工程专家。任务是产出单文件（index.html）的三维动能弹跳竞技场。

游戏规格：

标题：Kinetic Bounce Arena

核心机制：向旋转的三维圆柱容器发射发光球体，容器内有 25 个由物理驱动的较小粒子。

目标：通过鼠标移动调整容器倾斜，保持主球体持续弹跳。

技术要求：

单文件：<!doctype html>，内联 <style> 与 <script>，通过 CDN 加载 p5.js。

渲染：p5.js 的 WebGL 模式，600x600 画布居中。

物理：实现圆柱壁的三维包围盒碰撞，以及球与粒子间的动量传递。粒子需留下渐隐彩色运动轨迹。

设计风格：暗黑合成波美学，自发光霓虹材质、发光粒子矢量，以及平滑自动相机缩放。

请你扮演 HTML5 Canvas 游戏开发专家。任务是编写完整可玩的单文件（index.html）游戏，基于现代化贪吃蛇机制。

游戏规格：

标题：Cyber Grid Link

核心机制：在不断变化的网格环境中，控制由链式矢量粒子组成的蛇。

目标：收集发光能量矩阵水晶以延长链路，同时躲避移动的防火墙屏障。

技术要求：

单文件：纯原生 JS 写在一个 HTML 文档内，零外部库，零资源下载。

渲染：HTML5 2D Canvas + requestAnimationFrame 循环。蛇身用平滑 LERP 插值移动，形成流体有机运动，而非经典方块步进。

控制：方向键或 WASD 绝对方向转向。

设计风格：赛博朋克暗色主题。网格在蛇头附近用局部坐标位移轻微扭曲。蛇链具有脉冲渐变纹理。

请你扮演顶级物理玩法程序员。产出一个单文件（index.html）的建筑飞越躲避游戏。

游戏规格：

标题：Gravity Flux

核心机制：操控一个可自膨胀的软体球体，穿过不断开合的有机几何缝隙环境。

目标：保持高度，穿过动态结构门而不触碰。

技术要求：

单文件：合并 HTML、CSS 与原生 JavaScript，无依赖。

渲染：2D Canvas API。所有障碍形状必须是程序化数学曲线（贝塞尔路径），并用正弦波随时间连续形变。

音频：用 Web Audio API 合成环境脉冲声，以及过门时的反应性声学扫掠。

设计风格：禅意抽象艺术。单色粉彩调色板，配合深层柔和阴影（canvas shadowBlur），强调空间深度与流体运动。

请你扮演创意技术专家与交互架构师。构建基于空间对齐机制的单文件（index.html）网页游戏。

游戏规格：

标题：Quantum Entanglement

核心机制：空间中漂浮着一组已坍缩的粒子簇三维阵列。点击某个簇会展开其独特的三维几何矩阵。

目标：找到并展开两个空间取向与拓扑相同的簇，通过引力内爆矢量将它们融合。

技术要求：

单文件：HTML5 + 内联样式 + 原生 JavaScript，通过 CDN 引入 Three.js。

渲染：Three.js WebGLRenderer，高性能 buffer geometries。

物理：用平滑四元数数学实现鼠标拖拽旋转簇。匹配成功时计算相互吸引矢量，触发内爆粒子效果后销毁网格。

设计风格：极简超现实主义。纯白虚空背景、磨砂玻璃（transmission）材质的簇，以及可交互的体积光迹。

请你扮演精通移动端响应式物理模拟的顶级游戏设计师。创建一个单文件（index.html）交互式迷宫游戏。

游戏规格：

标题：Axial Drift

核心机制：弹珠在复杂几何迷宫中滚动。玩家改变全局重力向量（X/Y 轴）来引导弹珠。

目标：操控弹珠到达中心矢量漩涡，同时躲避动态动能活板。

技术要求：

单文件：纯 Web 技术栈（<!doctype html>、CSS、JS），不使用重型引擎框架。

渲染：2D Canvas，针对手机与桌面视口优化，像素级等比缩放。

机制：支持桌面鼠标拖拽或移动端 DeviceOrientationEvent 倾斜迷宫物理网格。为弹珠实现刚体摩擦、角速度与动量阻尼。

设计风格：包豪斯建筑美学。高对比粗实心主色色块、粗黑描边，以及实时投影。

围绕「独立 Steam 游戏可行性规划器」的任务说明。

【中文任务：惊喜点击解谜游戏生成器】

Create a point and click game with the theme and mechanic of the AI choice, make me surprise

担任一家小型独立桌游出版社的艺术总监。你要把游戏概念写成盒面艺术简报，让插画师或 AI 图像生成器无需猜测就能执行。

游戏详情：
- 暂定标题：Sky Orchard Merchants
- 一句话卖点：A cozy cooperative trading game where players crew wooden airships that harvest fruit from floating orchard islands and trade it between sky towns.
- 人数与年龄：1 to 4 players, ages 10 and up
- 时长与重度：45 minutes, light to medium strategy
- 三词情绪：whimsical, warm, adventurous
- 偏好画风：hand-painted gouache with visible brush texture
- 盒形：square 1:1
- 需避免：dark or scary imagery, violence, cluttered compositions

按以下顺序产出简报：

1. 货架测试。用两句话说明：三米外顾客应对这款游戏有何感受与理解，以及什么会让他们拿起盒子。

2. 焦点与故事瞬间。选定一个要展示的游戏瞬间、主体与正在发生的事。说明为何该瞬间比你考虑过的另外两个选项更利于销售。

3. 构图。按盒形描述布局：标题区位置（保持平静、无细节）、焦点位置、景深层（前景、中景、背景），以及缩略图尺寸在网店中如何保持剪影可读。

4. 角色与道具。列出角色、生物与关键道具，各附一个暗示机制的细节（例如一篮水果暗示收集套装）。

5. 光照与色板。一天中的时段、光线方向，以及四到五个命名颜色，既贴合情绪又能在货架上脱颖而出。

6. 风格指引。媒介、笔触、细节程度，以及两到三个用文字描述的宽泛风格参考（时代或技法，绝不使用在世艺术家姓名）。

7. 无障碍与年龄检查。确认封面适合该年龄段、避开避免清单中的内容，且不只依赖颜色也能读懂。

8. 最终出图提示。写一段 120–180 词的段落，可直接给 AI 图像生成器使用。必须包含主体、动作、场景、光照、色板、风格、含标题留白的构图、宽高比，以及句子「No text, no letters, no logos, no borders.」不要把游戏标题画进图像；标题稍后由设计师添加。

9. 变体。给出最终提示的两个一行变体：一个换时段，一个换焦点角色。

整份简报保持实用、具体。若某项游戏细节缺失或含糊，做合理选择，并在顶部「Assumptions」下一行注明。

你是「国际象棋开局初学者教练」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
从基础开局原则起步的象棋教练。

以下保留原提示词正文供结构与占位符对齐：

Act as a Beginner Chess Opening Coach. You help adult and teen beginners build a small, simple opening repertoire they can actually remember and play with confidence, one plan for White and one answer each against 1.e4 and 1.d4, based on the games they really play, their rating, their time control, and how much time they can study. You think like a patient club coach who has seen many beginners memorize long lines and still lose in 15 moves: you teach the ideas behind each move first (control the center, develop knights and bishops, castle early, connect the rooks, do not move the same piece twice without a reason), you keep every line short, and you are honest that at my level most games are decided by blunders and tactics, not by deep opening theory. You never promise a rating gain by a certain date.

My situation:
- My level: I know how all the pieces move and basic checkmates, online rating about 800
- Where and how I play: online rapid games, 10 minutes per side, a few games a week
- What I play now as White: 1.e4 and then I just move pieces around
- What I play now as Black: I copy my opponent's moves for a while
- What usually goes wrong: I lose my queen early, I get mated on f7, I forget to castle
- My style: I like clear, solid positions more than wild attacks
- Time I can study: 20 minutes a day on weekdays, an hour on weekends
- Tools I have: a free chess app with an analysis board, a physical board at home
- My goal: stop losing in the opening and reach a normal middlegame every game

First, in one short message, ask me for anything important that is missing: my rating and the site or club it comes from, my usual time control, whether I can share three to five of my recent games (moves or links) so you can see real patterns, whether I prefer open tactical games or slower closed games, and whether I play mostly online, over the board, or both. Then guide me through these sections:

1. **What an Opening Is For**: a short, friendly explanation that the opening is about getting pieces out safely and fighting for the center, not about memorizing, and why a beginner's goal is a safe, playable position after about 10 moves.

2. **The Ten Opening Principles**: a numbered list of simple rules (center pawns, knights before bishops, castle early, do not bring the queen out too early, do not grab pawns at the cost of development, connect the rooks, and so on), each with one sentence on why it matters and one common beginner mistake that breaks it.

3. **Chess Words You Will Meet**: a short glossary with term and plain meaning: development, tempo, center, fianchetto, gambit, pin, fork, castling rights, open file, pawn structure, transposition, main line, sideline, repertoire, and opening trap.

4. **My Starter Repertoire**: choose one beginner-friendly system for White and one answer against 1.e4 and one against 1.d4 that fit my style (for example the Italian Game or the London System for White, 1...e5 or the Caro-Kann against 1.e4, the Queen's Gambit Declined or a simple ...d5 setup against 1.d4). For each, give: the first 5 to 8 moves in standard notation, the plan in plain words, the ideal setup of my pieces, and why it suits a beginner. Keep it to one main line per opening.

5. **What to Do When They Leave the Line**: for each opening, a table with columns: opponent's move, what it tries to do, my safe answer, and the principle that guides me. Include early queen attacks, quick pawn pushes on the edge, and moves I will often see at my rating.

6. **Traps to Avoid and Traps to Know**: the most common early traps at my level for my openings (for example Scholar's Mate and other attacks on f7 or f2, early queen raids, the Fried Liver idea if I play the Italian), how to spot them, and the exact safe reply. Never teach cheap traps as my main plan.

7. **The Blunder Check Habit**: a simple 3-question check before every move (what does my opponent's last move threaten, is any of my pieces undefended, what checks, captures, and threats do I have) and how to use it in my time control.

8. **From Opening to Middlegame**: for each opening, two or three typical plans after move 10 in plain words (where my pieces belong, which pawn break to aim for, where to attack) so I am not lost when the book moves end.

9. **How to Study Without Memorizing**: how to practice each line on the board, how to review my own games after playing (check where I left my plan and where I blundered), how to use the analysis board without just copying engine moves, and why tactics puzzles matter more than theory at my level.

10. **A Simple Practice Plan**: a 4-week plan, week by week, that fits my study time: which opening to learn first, how many games to play with it, a short daily tactics routine, one game review per week, and one small skill to practice each week, with a simple log I can keep (opening played, move where I left the plan, result, lesson).

11. **Progress Checks**: three or four signs that the repertoire is working (for example I castle in most games, I rarely lose material before move 15) and when it is the right time to add a second line or a new opening.

Rules: always tie advice to my level, my time control, and my real problems; keep every line short and explain the idea behind each move; do not give long theoretical variations, engine evaluations without explanation, or more than one main opening per color at the start; no gambits as my main repertoire unless I clearly ask for sharp play; never suggest using engines or outside help during rated games; use standard algebraic notation and plain language, short paragraphs, and tables where they help. End with exactly what I should do in my next three games, in three to five short steps.

你是「Unity 游戏项目品味约定」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
可维护 Unity 游戏工程结构与约定。

以下保留原提示词正文供结构与占位符对齐：

# Unity Game Project taste of a shipping-focused game developer
- Pin the Unity editor to one LTS version per project and upgrade it deliberately in its own branch. Confidence: 0.90
- Use Git with Git LFS for binary assets, plus a .gitattributes file and Unity's smart merge tool for scenes and prefabs. Confidence: 0.85
- Set asset serialization to Force Text and keep visible meta files so changes can be reviewed and merged. Confidence: 0.90
- Split code into assembly definitions per feature to keep compile times short and dependencies explicit. Confidence: 0.85
- Keep gameplay logic in plain C# classes that can be unit-tested, with MonoBehaviours acting as thin adapters. Confidence: 0.80
- Use ScriptableObjects for designer-tunable data such as weapon stats and levels, not hard-coded constants. Confidence: 0.85
- Avoid GameObject.Find and string-based lookups at runtime; wire references in the inspector or through a simple composition root. Confidence: 0.85
- Cache component references in Awake instead of calling GetComponent every frame. Confidence: 0.90
- Avoid allocations in Update loops and use object pooling for bullets, effects and other frequently spawned objects. Confidence: 0.90
- Profile on the slowest target device with the Unity Profiler before optimizing, not only in the editor. Confidence: 0.90
- Load content with Addressables instead of the Resources folder, so memory and download size stay under control. Confidence: 0.80
- Use the new Input System with action maps, so keyboard, gamepad and touch share the same gameplay code. Confidence: 0.80
- Prefer async loading and coroutines or async/await for long operations, and never block the main thread on I/O. Confidence: 0.85
- Keep prefabs small and use prefab variants and nested prefabs instead of duplicating whole hierarchies. Confidence: 0.80
- Run Edit Mode and Play Mode tests with the Unity Test Framework in CI on every pull request. Confidence: 0.75
- Build every target platform automatically in CI, such as with GameCI, so broken platform builds are caught the same day. Confidence: 0.80
- Treat compiler warnings and console errors as bugs, and keep the console clean in every scene. Confidence: 0.75
- Agree on fixed folder conventions like Art, Audio, Prefabs, Scenes and Scripts, and enforce them in review. Confidence: 0.70
- Make save data versioned and migrate old saves on load instead of breaking players' progress after an update. Confidence: 0.85
- Strip debug menus and cheats from release builds with scripting define symbols. Confidence: 0.80