scenario-unity-2d
Use when building a 2D game in Unity 6.3 URP: pixel-art or HD sprite import and PPU, sprite atlases, Tilemaps, Rule Tiles and reskins, the 2D Renderer and 2D lights with normal maps, 2D animation, a platformer or top-down controller ("make a platformer controller that feels good", coyote time, jump…
Install / Use
npx skills add scenario-labs/skills --skill scenario-unity-2dInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OtherSupported Platforms
Tags
Our assessment of scenario-unity-2d
scenario-unity-2d scores 86/100 on our quality scale, 204th of 354 Other skills we index.
Its SKILL.md is 19 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 35 days ago, so scenario-unity-2d is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-20. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-unity-2d compared with similar skills
All 4 of these similar skills score higher than scenario-unity-2d; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-unity-2d (this skill)by scenario-labs | 86 | 1.0k | 35d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install scenario-unity-2d?
- Run
npx skills add scenario-labs/skills --skill scenario-unity-2d. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-unity-2d work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-unity-2d safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-unity-2d still maintained?
- The repository was last updated 35 days ago, so scenario-unity-2d is actively maintained.
Skill content
View source on GitHubname: scenario-unity-2d description: 'Use when building a 2D game in Unity 6.3 URP: pixel-art or HD sprite import and PPU, sprite atlases, Tilemaps, Rule Tiles and reskins, the 2D Renderer and 2D lights with normal maps, 2D animation, a platformer or top-down controller ("make a platformer controller that feels good", coyote time, jump buffer, one-way platforms, spikes), Pixel Perfect Camera, a follow or room camera, hit stop and screen shake; or when pixel art looks blurry or shimmers, tiles show seams, 2D lights do nothing or cost too much, the jump feels floaty, or the camera loses the player when falling.' license: MIT
Unity 2D (developer and artist)
Expert 2D work in Unity 6.3 is a chain of coupled settings proven by numbers and a frame: one PPU
from art to camera, atlases judged by what they save, tiles and lights authored as data and costed,
a camera that moves in whole pixels, and a controller whose feel is measured, not asserted.
Everything below was run in Unity 6000.3.21f1 through batch jobs and PlayMode tests
(references/procedures.md). If a sibling skill named here is missing
from your available skills, load it with skill_get (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag
the gap.
REQUIRED BACKGROUND: scenario-unity-expert (channels, review loop, 6.3 traps).
Stance (the expert delta)
- Pixel perfect is a pipeline, and URP already ships the camera. One PPU on every sprite (tile
px = 1 unit), Point, Compression None, whole-pixel pivots, Assets PPU = sprite PPU. Never install
com.unity.2d.pixel-perfectin URP: it is the Built-in component (6.3 Manual). Measured: 100% uniform 6 x 6 blocks at 1080p. - Pick Grid Snapping by what must be pixelated, and judge pixels in motion. Pixel Snapping snaps sprites only; lights, bloom, particles stay at screen resolution (2qeNu2QApAM [00:01:47]); Upscale Render Texture pixelates everything. Retro AA vs Point is shimmer vs blur (Manual), and in URP 17.3 it only acts under Stretch Fill. Measured over a sub-pixel pan: integer framing moves in whole art pixels (rigid 0.9997); Stretch Fill Point leaves 0.6% of pixels shimmering per frame, Retro AA 0.3% at twice the softness; no Pixel Perfect Camera, 2.8%.
- Under the SRP Batcher an atlas cuts textures, not Batches or SetPass. Measured 21/21 batches,
2/2 SetPass, bound textures 20 to 1 (Unity hXlpnwD-TgY [00:05:55], [00:07:32]); memory only drops
when usage is high. Compress once, on the atlas, except pixel-art pages stay None: compression
shifts pixel colors (2qeNu2QApAM [00:02:24]).
AuditAtlasesreproduces the 6.3 Sprite Atlas Analyzer reports plus Read/Write; grouping by co-visibility is the step no tool does. - The controller owns the velocity; forgiveness is design, each trick behind a toggle. Latch input in Update; collisions, jump, horizontal, gravity, apply in FixedUpdate; coyote and buffer are timestamp windows (Tarodev source). "Working on the player's intent" (Thorson, GMTK yorTG9at90g [00:11:03]), so coyote, buffer, variable jump, fall clamp, apex hang and corner correction each get an on/off toggle for A/B play (Tarodev 3sWTzMsmdx8 [00:02:24]), and hazard hitboxes are smaller than the art (GMTK [00:09:28]). Two choices are feel decisions, never defaults: the variable-height method (velocity cut 50% precise, gravity x3 smooth, sustain while held long; Dawnosaur 2S3g8CgBG1g [00:00:36]) and the air friction (Tarodev AirDeceleration 30 drifts 3.1 units, 5.7 body widths, after release; Celeste's "massive air friction" drops almost straight down, GMTK [00:04:14]; 240 stops in 3 steps).
- Lights are routed by sorting layers and paid per light batch. Consecutive sorting layers share a light batch only if every visible light lights both or neither, and the normal, shadow and light passes run once per batch (URP 17.3 source). A player fill light that skips the Characters layer (Sasquatch 1h-hSlffawM [00:01:35]) split the demo level from 1 batch into 4 and light fill from 0.99 to 3.64 screens. Cost is fill rate (e-book p. 131): bench at 4K over 6 runs, shadows x5.4 to x5.9, the batch split +72 to +101%, normal maps +15 to +36%, large vs small lights +8 to +43% (noisy). Never a pitch-black area (Global 0.25, GDC YhrwKF_i-BI [00:11:43]); enable normal maps on the light (GDC [00:12:31]); Fast on low tiers.
- Sprite animation never blends and follows the controller. Exit time off, duration 0, Any State self-transition off; parameters from what the controller did, not from input (Brackeys hkaysu1Z-N8 [00:16:17], [00:18:57]).
- The camera and the juice are part of feel. Loose vertical damping rising, tight once falling past a speed threshold, back at vertical speed 0 (hysteresis), lerped (Sasquatch 9dzBrLUIF8g [00:05:37], [00:07:14]): in a 40-unit drop a fixed 0.6 s damping let the feet reach the bottom edge, the switch kept 3.2 to 3.4 units below in view. Swap room cameras on trigger EXIT by exit direction ([00:14:43]); bounds end exactly at a secret room ([00:02:10]). Hit stop 20 ms (Nijman AJdEqssNZ-U [00:18:22]) to 67 ms (Celeste, GMTK [00:08:40]) on unscaled time, extend not stack; shake with an off option (Nijman [00:32:14]).
- Be honest about GUI-only editors. Tile Palette, Rule Tile inspector, AutoTile masks, Sprite
Editor, Skinning Editor and the Animator window are mouse tools. Agents author through
Tilemap.SetTiles,RuleTile.m_TilingRules,RuleOverrideTile.ApplyOverrides,ISpriteEditorDataProvider,AnimatorController; rigging and AutoTile masks stay human (references/gui-paths.md).
Establish first
Ask once: pixel art or HD (defaults: pixel, 16 PPU, 320 x 180); target screens including 21:9 and
phones; camera model (static rooms, follow with bias and fall damping, lead toward action);
real-time 2D lights or painted light, and the lowest tier; controller profile (precision: own the
velocity, high air friction; momentum: low air friction; physics-rich: Dynamic body with forces;
top-down: velocity); jump height in tiles and the variable-height method; hazards and one-way
platforms; input devices. Then ut_2d.project(P).
Workflow
- Project.
TwoDSetup.ProjectSetup: sorting layers back to front (few: they drive light batching), Player and Ground layers. GATE: order read back, no pixel-perfect package, Input System, fixed step 0.02 s. - Import.
SpriteJobs.ImportPixelArt(slicing, pixel pivots,_NormalMap) orImportHD(PPU = height / (2 x ortho), e-book p. 21); shaped tiles getSetPhysicsOutline(16 px sprites generate a 4-point rectangle). GATE:AuditSprites0 errors; one PPU. - Atlases.
AtlasJobs.BuildAtlasper co-visible group, lit and plain apart, pixel pages uncompressed. GATE: 1 page, 0 findings, grouping rule written. - Level.
TilemapJobs.CreateRuleTile+BuildLevel; reskins withCreateRuleOverrideTile; Composite Merge, Outlines, Static; per-tile colliders only for runtime edits, then Use Delaunay Mesh. GATE:rule_mismatches == 0(reskin read-back too), drop probe within 0.05 units, capture shows no seams. - Actors and animation.
AnimJobs.BuildSpriteAnimator,LevelJobs.Populate(player,Hazard2Dspikes with inset hitboxes, one-way platforms). GATE:LintAnimator0 errors; hitbox-to-art ratios below 1. - Lights.
LightJobs.LightRig, thenLightJobs.LightCost(tier; engine check once the camera exists). GATE:Audit2D0 errors; replica light batches = URP's own count; every batch break and every light over half the view justified; normals on/off capture pair differs. - Camera.
CameraJobs.SetupPixelPerfect,CapturePixelPerfect; a sub-pixel pan (ut_2d.pan_shots) scored byut_2d.shimmer_check; follow cameras throughCinemachineJobs.Setup(CM 3.1.7 pinned) plusCinemachineFallDampingandCinemachineRoomSwap. GATE:pixel_block_check>= 0.999 at 1080p and 720p, pan min rigid >= 0.99,void_columns0 at 21:9,bounds_hide_secretsok, contact sheet looked at. - Feel. PlayMode tests with simulated input (
ut_run.run_tests(P, "PlayMode", graphics=True)). GATE: apex = 50 Hz prediction, windows within one step, one press = one jump at 30/60/144 fps, each toggle A/B, method and air-drift numbers stated. Feel itself is a human verdict: ship toggles and numbers. - Deliver.
Audit2D.Sceneclean;AgentProfile.PlayModeTimingsbudget pass; report each step with its Unity call, then Verified and Assumed.
Numbers
| Value | Relative to | Source | | ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | ------------------------------ | | PPU = H / (2 x ortho size): 216 at 4K Size 5 | HD art, closest zoom | e-book p. 21 | | 320 x 180: x4 720p, x6 1080p, x8 1440p, x12 4K; ortho 5.625 at 16 PPU | pixel reference | Manual; [added] arithmetic | | MaxSpeed 14, Accel 120, GroundDecel 60, AirDecel 30, JumpPower 36, FallAccel 110, MaxFall 40, release x3, Coyote 0.15 s, Buffer 0.2 s | Tarodev stats (u/s, u/s^2) | Tarodev repo | | apex 5.536 at 50 Hz (formula 5.89), rise 0.32 s; tap: gravity x3 2.08, cut 0.5 1.81, sustain (JumpPower 18.7) 1.78 of 5.52 | those stats | measured, replay | | air drift after release at top speed: AirDecel 30 3.13 units (24 steps), 240 0.27 (3 steps) | 0.55-unit body | measured | | Celeste: about 6 frames to top speed, 3 to stop, jump about 3 body heights (Mario 4, Meat Boy 6) | 60 fps frames | GMTK [00:02:01], [00:03:42] | | apex band gravity x0.5 below 5 u/s held (+0.08 s); corner nudge 0.25 units | added tricks | Dawnosaur [00:02:06]; [added] | | hazard hitbox inset 2 px sides, 3 px top: 0.75 x 0.625 of a 16 x 8 spike | art | [added] values | | fall damping 0.6 s loose, 0.1 s tight, switch below -15 u/s, back at 0, 0.2 s blend | follow camera | [added] values; rule Sasquatch | | hit stop 0.02 to 0.07 s | real time | Nijman; GMTK | | Global light 0.25; light render scale 0.5 (template) | lighting | GDC; observed | | one atlas page; wastage flag > 400 KB | per atlas | hXlpnwD-TgY | | 12 samples per second for sprite clips | frame-by-frame | Brackeys [00:03:42] |
Quality gates
- Measurable: audits at 0 errors (
AuditSprites,AuditAtlases,Audit2D,LintAnimator);rule_mismatches == 0; drop probe < 0.05;pixel_block_check>= 0.999; pan rigid >= 0.99; `void_col
Truncated for display — read the full file on GitHub.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
