Skip to content
SkillModel-led2,339 tokens in use

love2d-core

Helps an agent build and debug LÖVE 11.x games in Lua: main.lua callbacks, conf.lua, fixed steps, pixel-art scaling, saves and a scripted run.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/other-engines/love2d-core
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing love2d-core costs

98tokens idle
2,339tokens in use
3,629tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 126

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill helps an agent build and debug a LÖVE 11.5 game. It reads conf.lua first for the target version and save identity, loads assets once, simulates in fixed steps and wraps world drawing in push and pop with the HUD drawn after.

It includes a conf.lua error hook that prints errors and exits with a status for scripted runs, a frame-counted run that takes a screenshot, and a pixel-art canvas with integer scaling. A gotcha list covers blurry sprites, stack depth errors, missing save files and unseeded random numbers.

What You Get

  • A five-step workflow from reading conf.lua to loading once, simulating in steps, drawing in layers and verifying
  • A conf.lua pattern with a version, a save identity and an error handler for scripted runs
  • A fixed-step accumulator with a frame-count check and screenshot, and a pixel-art canvas with integer scaling
  • A gotcha list for blurry pixel art, push and pop errors, save locations, require spellings, seeding, colour ranges and key repeat

Common Use Cases

  • Starting a LÖVE game with a correct loop and config
  • Fixing blurry pixel art after scaling
  • Debugging the blue error screen or speed that depends on frame rate
  • Saving and loading game data with love.filesystem

What Makes It Unique

The skill gives a scripted run for a game that normally needs a person at the window: a frame budget, a screenshot written to the save folder and a clean exit code, with an error handler so a crash prints and exits. It also lists the 11.x behaviours that differ from older tutorials.

Under The Hood

The agent loads the SKILL.md and, when needed, a reference on a screen stack. It edits Lua files in your project and runs the love command under a timeout with a frame count and a screenshot name, then reads the output, exit code and the screenshot in the save directory. The game writes that screenshot and any save files to the LÖVE save folder. On a Linux machine without a display it suggests running under a virtual display. It fetches no web pages and calls no APIs; input feel and sound need a person to play and report.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers