Skip to content

Teach the sprite skills what a kept background costs - #12

Merged
TheDesignFounder merged 1 commit into
mainfrom
feat/sprite-background-keep
Sep 27, 2026
Merged

TheDesignFounder merged 1 commit into
mainfrom
feat/sprite-background-keep

Conversation

@TheDesignFounder

Copy link
Copy Markdown
Owner

What

background: "keep" is live in the App and the public API, and GET /v1/capabilities advertises sprite_pricing.plain_frame_cents: 7. An agent following the current skill would quote the transparent tier for a plain sheet (roughly twice its price) and would call a sheet fully transparent without checking.

  • sprite-sheet-from-reference now gives both quotes: transparent min(n,14)*14 + max(n-14,0)*7, kept n*7 flat with no tier, both divided by 17 and rounded up once. Twelve frames: 9.9 credits transparent, 5.0 kept.
  • It tells the agent to offer keep only when transparency is not needed, and only if its client exposes the field and capabilities advertise plain_frame_cents. The pinned CLI and MCP builds cannot order it yet, so this stays accurate until those publish.
  • It tells the agent to read kept_background_frames in atlas.json before promising a fully transparent sheet, since one frame that will not cut out now ships with its background instead of failing the sheet.
  • The ClawHub entry point carries the same pricing distinction.
  • .agents/skills, .github/skills and .cline/skills regenerated from the canonical copy, and the OpenAI skills ZIP rebuilt (sha256 07af9a52..., was 32bc2934...).

Verification

scripts/validate.py PASS, pytest tests 9/9.

🤖 Generated with Claude Code

The service now takes background: "keep", which ships plain frames instead of
transparent ones at a flat plain_frame_cents with no tier, and rescues a frame
that will not cut out instead of failing the whole sheet. An agent following
the old skill would quote the tier for a plain sheet, roughly twice its price,
and would promise a fully transparent sheet it had not checked.

The skill says to offer keep only when transparency is not needed and only if
the installed client exposes the field, because the pinned CLI and MCP builds
cannot order it yet, and to read kept_background_frames in atlas.json before
claiming every frame is transparent.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@TheDesignFounder
TheDesignFounder merged commit 30cae0d into main Sep 27, 2026
2 checks passed
@TheDesignFounder
TheDesignFounder deleted the feat/sprite-background-keep branch September 27, 2026 02:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant