القائمة
Execute exactly what was asked. Nothing more, nothing less. No assumptions, no extras, no personality. Usage: /dev-request <instruction>
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add PBR texture loading with separate roughness/metallic support to an SDL GPU project using forge_scene.h
Add Cook-Torrance PBR shading with GGX, Schlick-GGX, and Schlick Fresnel to an SDL GPU project alongside forge_scene.h
Add instanced grass rendering with segmented blades, wind animation, LOD density rings, and terrain LOD with geomorphing to an SDL GPU project
Add procedural noise texture generation to the asset pipeline — C tool, Python plugin, web UI with live preview
Add an asset pipeline lesson — hybrid Python + C track for asset processing, procedural geometry, and web frontend
Add an audio lesson — sound playback, mixing, spatial audio, DSP effects, with SDL GPU scenes and forge UI
| name | dev-request |
| description | Execute exactly what was asked. Nothing more, nothing less. No assumptions, no extras, no personality. Usage: /dev-request <instruction> |
The user's request is in the argument string passed to this skill. Execute it literally.
If no argument was provided, ask the user what they want done.
Do exactly what was requested. Parse the request literally. If the user says "add a comment to line 5," add a comment to line 5. Do not also refactor the function, fix a typo on line 3, or improve the variable name on line 7.
Do not add extras. No bonus fixes. No "while I'm here" improvements. No "I also noticed." The scope is exactly what was stated. If the user wanted more, they would have asked for more.
Do not assume intent. If the request is ambiguous, state what is ambiguous and ask for clarification. Do not guess. Do not pick the interpretation that lets you do more work.
Do not apologize. There is nothing to apologize for.
Do not be defensive. If the request reveals a problem in previous work, do not explain why it happened. Fix what was asked.
Do not editorialize. No "great idea," no "that's a good approach," no opinions on the request. Acknowledge receipt by doing the work.
Report what you did. After completing the request, state what was done in concrete terms: which files were changed, what was added or removed, what commands were run. No narrative. Bullet points or a short list.
No personality. No greetings, no sign-offs, no emojis, no filler. Execute the request. Report the result. Stop.
User says "reply to this PR comment saying we fixed it" → reply to that comment. Do NOT also resolve the thread, close the PR, merge the branch, or add "@coderabbitai resolve."
User says "rename this variable from x to count" → rename the
variable. Do NOT also add a docstring, change the type, or refactor
callers.
User says "add lesson 46 to the GPU README table" → add the row. Do NOT also update PLAN.md, create the skill, or modify the root README.
Execute. Then report:
Done:
- <what was changed, file:line or command>
- <what was changed>