SkillAgentSearch skills...

scenario-godot-2d

Use when building a 2D game in Godot 4.7: make a platformer or top-down controller that feels right (coyote time, jump buffer, jump height), TileMapLayer and TileSet in code, terrains and autotiles that pick wrong tiles, a dual grid, a camera that jitters or stutters, pixel art that looks blurry or…

Install / Use

npx skills add scenario-labs/skills --skill scenario-godot-2d

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Other

Supported Platforms

Universal

Tags

Our assessment of scenario-godot-2d

scenario-godot-2d scores 86/100 on our quality scale, 196th of 354 Other skills we index.

Its SKILL.md is 21 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.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 35 days ago, so scenario-godot-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 found

Our 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-godot-2d compared with similar skills

All 4 of these similar skills score higher than scenario-godot-2d; compare them before choosing.

SkillScoreStarsUpdatedFormat
scenario-godot-2d (this skill)by scenario-labs861.0k35d agoSKILL.md
algorithmic-artby anthropics100177.9k2mo agoSKILL.md
pptxby anthropics100177.9k2mo agoSKILL.md
prospectingby coreyhaines3110060.1k11d agoSKILL.md
ad-creativeby coreyhaines3110060.1k11d agoSKILL.md

Frequently asked questions

How do I install scenario-godot-2d?
Run npx skills add scenario-labs/skills --skill scenario-godot-2d. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-godot-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-godot-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-godot-2d still maintained?
The repository was last updated 35 days ago, so scenario-godot-2d is actively maintained.

name: scenario-godot-2d description: "Use when building a 2D game in Godot 4.7: make a platformer or top-down controller that feels right (coyote time, jump buffer, jump height), TileMapLayer and TileSet in code, terrains and autotiles that pick wrong tiles, a dual grid, a camera that jitters or stutters, pixel art that looks blurry or uneven, stretch and integer scaling, 2D lights and shadows, y-sort order wrong, parallax gaps, or importing AI-generated sprites and tilesets from Scenario." license: MIT

Godot 2D (developer and artist)

Target: Godot 4.7.2 standard build, macOS, run headless or in small windows through the scenario-godot-expert toolkit.

Expert level in 2D means feel and pixels are measured, not eyeballed: a jump has a height in tiles and a coyote window in ticks, a camera has a lag in pixels, a pixel-art screen has an integer factor and a fringe count. The agent builds tiles, controllers and cameras in code, proves them with deterministic physics runs and frame read-backs, and only then calls them done. 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-godot-expert (channels, review loop, toolkit gd_env, gd_run, gd_review, 4.x traps).

Stance (the expert delta)

  1. Feel is numbers you can test. Solve gravity and take-off speed from jump height and time to apex, and make the height a multiple of the tile size (The Shaggy Dev, Bsy8pknHc0M [00:04:13]). Godot then loses about v·dt/2 of it: 53.5 px for a 56 px design at 60 ticks, measured. The kit adds g·dt/2 and lands 56.25 px [added].
  2. Forgive in time and space. Coyote time, jump buffer, corner correction and a jump cut are each a few lines (The Shaggy Dev). Count windows in whole ticks: float timers gave 5 coyote moves for 0.1 s instead of 6 [added, measured].
  3. Top-down: move_toward, not length arithmetic. Additive acceleration needs limit_length; subtracting decel from the length goes negative and vibrates (55 sign flips in 60 ticks, measured). Steering never arrives without a minimum step (BT Plays Games, m71-kZgYXlw [00:07:30], [00:14:08]).
  4. A camera is designed, not parented. Lookahead, ignore jumps and re-baseline on landing, damping, shake with an off switch (Mark Brown, GMTK). Damping lags by speed/damping and eats lookahead: 32 px of lookahead gave a 16 px lead at 120 px/s, so state both numbers. Zoom with Camera2D.zoom (2 zooms in), never by resizing the viewport (DevWorm, RlSpjIb7TLo [00:08:14]).
  5. Jitter is a tick-rate problem. At 144 Hz with 60 physics ticks, physics interpolation gave the ideal 0.289 px RMS for every camera setup. Without it the background stepped 0, 1, 2 px, and Idle camera smoothing made the player wobble 3 px. Camera2D.process_callback defaults to Idle: with interpolation off, set CAMERA2D_PROCESS_PHYSICS yourself (Chris' Tutorials, 43c-Sm5GMbc [00:28:37]); with it on, Godot forces Physics.
  6. Pixel-perfect is a stretch decision. viewport + integer locks everything to art pixels, lights included. 640x360 (the docs' base) and 320x180 both integer-scale to 720p, 1080p, 1440p and 4K with no bars, measured; pick by native art size. Ship Exclusive Fullscreen (window mode 4): a 1 px strip drops 640x360 on 4K from 6x to 5x, measured (docs, Multiple resolutions). canvas_items gives smooth rotation and sub-pixel motion (Heartbeast prefers it). For locked art with a gliding camera, render a SubViewport at base + 2 px and shift the upscaled image by the remainder (Barry's Dev Hell).
  7. Tiles are data you can audit. One TileMapLayer per layer, an external TileSet, terrain mode matched to the tile count, and peering bits checked cell by cell. Paint the land, never the water side (DevWorm, ZutpG0_CYrQ [00:32:47]); in the GUI, paint bits outer ring first, then the center cross (bluuDevGames, CLcFC6ku240 [00:12:28]). Pick a dual grid (16 tiles, display layer offset half a tile) when every corner must round the same (jess::codes, jEWFSv3ivTg [00:02:26]). Then look at a sampler capture, because index checks pass on wrong art [added].
  8. Generated art is checked before import. Find the pixel scale and grid phase, snap if off-grid, register every clip on its feet line, and check the key-color fringe under linear filtering [added, with scenario-sprite-pipeline].
  9. Physics layers are named and single. One collision layer per object, many masks; name layers by what the checker needs ("bombable"), in layer_names/2d_physics/layer_N (Bogner, HFBNd4Z4vXM [00:10:58] to [00:14:17]). A new body starts on layer 1 and mask 1: adding a layer without clearing 1 gives 2 bits, measured.

Establish first

| Question | Why it changes the plan | Default | | ----------------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | Pixel art or smooth 2D? | stretch mode, filter, light resolution, camera method | pixel art: base 640x360 (320x180 for very small art), viewport + keep + integer, Nearest, Exclusive Fullscreen | | Locked grid or smooth camera over pixels? | viewport alone, or pixel_viewport.gd | smooth camera via pixel_viewport.gd when the camera moves slowly | | Platformer or top-down? | GROUNDED or FLOATING, which kit body | from the brief | | Tile size and terrain style | 47-blob, 16-tile sides, or dual grid | 16 px, 47-blob terrain | | Target displays | integer factors and bars | 1280x720, 1366x768, 1920x1080, 2560x1440, 3840x2160 | | Refresh and networking | physics interpolation on or off | on (off for networked games with their own smoothing, docs) | | Art source | Scenario manifest, hand-made, placeholder | gd_2d.make_* placeholders until art lands |

Workflow

  1. Project. P = gd_env.base_project("2d", ...), gd_2d.install_kit(P), gd_2d.pixel_art_settings(P, ...), gd_run.import_project(P). GATE: stretch_matrix.gd shows the root picked up base size, mode, integer stretch, Nearest and interpolation; the integer factor and bars for each target window match gd_2d.integer_scales.
  2. Art in. For each generated image: detect_pixel_scale, pixel_grid_check, and snap_to_grid if the phase or scale is off. Then import, audit_imports, and build SpriteFrames from the manifest with sprite_frames_builder.gd plus register() on each sprite. GATE: audit clean; every clip's lowest ink pixel lands on the same world y; key_fringe = 0 on a capture at a non-integer scale.
  3. Tiles. tileset_builder.gd (tile size first, alpha-derived peering bits, collision, occluders, one-way lips), saved as .tres; paint with set_cells_terrain_connect. Use dual_grid.gd when the art is a 16-tile dual set. GATE: terrain_tools.audit_layer gives 0 side and 0 corner mismatches; a sampler capture (ring, cross, single cells, inner corners) looks right on a contact sheet.
  4. Character. platformer_body.gd + platformer_tuning.gd Resource, or topdown_body.gd. Brain and body are split so tests drive intents. GATE (--fixed-fps 60, one move per await body.stepped): apex within 0.5 px of design; coyote and buffer counted in moves; largest gap in tiles; no snag on tile seams; top-down stops at exactly 0 and diagonal speed equals straight speed.
  5. Camera. follow_camera_2d.gd (physics step, limits from the layer's used rect), or pixel_viewport.gd for a smooth view over locked pixels. GATE: camera y still during a jump in place; re-baseline after landing; a long fall keeps the player on screen; shake off gives offset 0. In a windowed run at --fixed-fps 144, background steps are at most 1 px with interpolation on.
  6. Lights, sort, parallax. CanvasModulate + PointLight2D with a radial GradientTexture2D; occluders from tile alpha; y-sorted container with feet origins; Parallax2D per plane. GATE: luma at probe points (lit, shadowed, owner lit vs a no-occluder control); overlap color test behind and in front; parallax shift equals scroll_scale times camera motion; no gap at the lowest zoom; no seam over 90 autoscroll frames.
  7. Audit and hand over. audit_2d.gd:scenes, gd_run.check_all, kit_compile.gd, then a contact sheet of the captures (at most 1600 px), opened and looked at. GATE: no warn findings, 0 compile errors, and the sheet shows no broken tiles, fringes or gaps. In a written plan, inline the core code (settings keys, jump maths, controller step, camera) so it runs without the kit; name kit files only as shortcuts.

Numbers

| Value | Measured or source | Relative to | | --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | -------------------------------- | | Base 320x180, integer: 4x at 1280x720 and 1366x768 (bars 43, 24), 6x at 1080p, 8x at 1440p, 12x at 4K, 3x at 1170x2532 | live | window size | | Base 640x360, integer: 2x at 720p and 1366x768 (bars 43, 24), 3x at 1080p, 4x at 1440p, 6x at 4K; 3840x2159 gives 5x with 320 and 180 px bars | live | window size | | Jump 56 px, apex 0.35 s, fall 0.28 s: g up 914.3, g down 1428.6 px/s², take-off 327.6 px/s with compensation | live, kit defaults [added] | 16 px tiles, 60 ticks | | Jump cut 0.4: a one-tick tap rises 12.79 px (under a tile); minimum height is about (cut·v)²/2g | live, kit defaults | 16 px tiles | | Coyote 0.1 s = 6 airborne moves; buffer 0.1 s = 5 moves before landing | live | 60 ticks | | Corner correction 4 px: a 3 px head clip goes from 34 px to the full 56 px | live | 10x14 body

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryOther
Updated1mo ago
Forks129

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions