Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingxling/mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
A puzzle game team wants to lock their mobile UI strictly to landscape orientation, ignoring device rotation settings and player ergonomics. What best practice applies to mobile screen orientation?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends supporting player preference across portrait and landscape modes | Missed | Passed |
The instructions your model reads when the skill loads.
Platform constraints and optimization principles.
| Constraint | Strategy |
|---|---|
| Touch input | Large hit areas, gestures |
| Battery | Limit CPU/GPU usage |
| Thermal | Throttle when hot |
| Screen size | Responsive UI |
| Interruptions | Pause on background |
| Touch | Desktop/Console |
|---|---|
| Imprecise | Precise |
| Occludes screen | No occlusion |
| Limited buttons | Many buttons |
| Gestures available | Buttons/sticks |
test cases passed, vs 21 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.