File size: 2,923 Bytes
781b563 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 | # Before / after training samples
Generated automatically from a few prompts drawn from the training data, run once against the base model before training started and once against the finished model. This shows what this run changed on representative prompts -- it is not a benchmark and does not measure generalization.
## Prompt: [{'role': 'system', 'content': 'You are an expert software engineer. Write correct, maintainable code and explain decisions clearly.'}, {'role': 'user', 'content':
**Before:**
> 'Create a testing strategy for level generation in a browser game.'}, {'role': 'assistant', 'content': 'Test game logic separately from rendering. Three.js scenes are hard to test directly, but math and state transitions are very testable.\n\nExample pure movement test:\n\n```js\nexport function integratePosition(position, velocity, dt) {\n return {\n x
**After:**
> 'Add mobile touch controls to a Three.js browser game without ruining desktop keyboard controls.'}, {'role': 'assistant', 'content': 'Use an input abstraction so keyboard and touch produce the same game-facing values.\n\n```js\nconst input = {\n moveX: 0,\n moveY: 0,\n actionPressed: false\n};\n\nfunction
## Prompt: [{'role': 'system', 'content': 'You are a senior game tools and engine architecture engineer. Design maintainable systems with clear boundaries and
**Before:**
> practical implementation steps.'}, {'role': 'user', 'content': 'Create enemy AI for a coin collector. The enemy should ambush, react to the player, and be readable.'}, {'role': 'assistant', 'content': 'Use a small finite-state machine first. It is easier to debug than a tangle of booleans.\n\nEnemy states:\n- `idle
**After:**
> practical implementation steps.'}, {'role': 'user', 'content': 'Create enemy AI for a coin collector. The enemy should ambush, react to the player, and be readable.'}, {'role': 'assistant', 'content': 'Use a small finite-state machine first. It is easier to debug than a tangle of booleans.\n\nEnemy states:\n- `idle
## Prompt: [{'role': 'system', 'content': 'You are an expert JavaScript, Three.js, and browser game developer. Produce original, runnable, clean code and explain
**Before:**
> practical tradeoffs.'}, {'role': 'user', 'content': 'Create a Three.js scene featuring a energy pickup. Use warm torch lighting, a isometric camera, and include: no global spaghetti state, no external physics engine, use delta time correctly.'}, {'role': 'assistant', 'content': 'Below is a scene plan and core implementation. For a full HTML file, wrap
**After:**
> practical tradeoffs.'}, {'role': 'user', 'content': 'Create a Three.js scene featuring a water orb. Use soft sunset lighting, a isometric camera, and include: no global spaghetti state, no external physics engine, use delta time correctly.'}, {'role': 'assistant', 'content': 'Below is a scene plan and core implementation. For a full HTML file, wrap
|