@inneranimalmedia/agentsam-sdk 2.6.7 → 2.6.9

package/skills/grok-design-ui/references/typography.md

@@ -1,123 +0,0 @@
-# Typography
-
-Typography rendering details that make interfaces feel better.
-
-## Text Wrapping
-
-### text-wrap: balance
-
-Distributes text evenly across lines, preventing orphaned words on headings and short text blocks. **Only works on blocks of 6 lines or fewer** (Chromium) or 10 lines or fewer (Firefox) — the balancing algorithm is computationally expensive, so browsers limit it to short text.
-
-```css
-/* Good — even line lengths on short text */
-h1, h2, h3 {
-  text-wrap: balance;
-}
-```
-
-```css
-/* Bad — default wrapping leaves orphans */
-h1 {
-  /* no text-wrap rule → "Read our
-     blog" instead of balanced lines */
-}
-```
-
-```css
-/* Bad — balance on long paragraphs (silently ignored, wastes intent) */
-.article-body p {
-  text-wrap: balance;
-}
-```
-
-**Tailwind:** `text-balance`
-
-### text-wrap: pretty
-
-Optimizes the last line to avoid orphans using a slower algorithm that favors better typography over performance. Unlike `balance`, it works on longer text — use this for body copy where you want to minimize orphans without the 6-line limit.
-
-```css
-p {
-  text-wrap: pretty;
-}
-```
-
-### When to Use Which
-
-| Scenario | Use |
-| --- | --- |
-| Headings, titles, short text (≤6 lines) | `text-wrap: balance` |
-| Body paragraphs, descriptions | `text-wrap: pretty` |
-| Code blocks, pre-formatted text | Neither — leave default |
-
-## Font Smoothing (macOS)
-
-On macOS, text renders heavier than intended by default. Apply antialiased smoothing to the root layout so all text renders crisper and thinner.
-
-```css
-/* CSS */
-html {
-  -webkit-font-smoothing: antialiased;
-  -moz-osx-font-smoothing: grayscale;
-}
-```
-
-```tsx
-// Tailwind — apply to root layout
-<html className="antialiased">
-```
-
-### Good vs. Bad
-
-```css
-/* Good — applied once at the root */
-html {
-  -webkit-font-smoothing: antialiased;
-}
-
-/* Bad — applied per-element, inconsistent */
-.heading {
-  -webkit-font-smoothing: antialiased;
-}
-.body {
-  /* no smoothing → heavier than heading */
-}
-```
-
-**Note:** This only affects macOS rendering. Other platforms ignore these properties, so it's safe to apply universally.
-
-## Tabular Numbers
-
-When numbers update dynamically (counters, prices, timers, table columns), use tabular-nums to make all digits equal width. This prevents layout shift as values change.
-
-```css
-/* CSS */
-.counter {
-  font-variant-numeric: tabular-nums;
-}
-```
-
-```tsx
-// Tailwind
-<span className="tabular-nums">{count}</span>
-```
-
-### When to Use
-
-| Use tabular-nums | Don't use tabular-nums |
-| --- | --- |
-| Counters and timers | Static display numbers |
-| Prices that update | Decorative large numbers |
-| Table columns with numbers | Phone numbers, zip codes |
-| Animated number transitions | Version numbers (v2.1.0) |
-| Scoreboards, dashboards | |
-
-### Caveat
-
-Some fonts (like Inter) change the visual appearance of numerals with this property — specifically, the digit `1` becomes wider and centered. This is expected behavior and usually desirable for alignment, but verify it looks right in your specific font.
-
-```css
-/* With Inter font:
-   Default:  1234  → proportional, "1" is narrow
-   Tabular:  1234  → all digits equal width, "1" centered */
-```

package/skills/grok-game-animation-frames/SKILL.md

@@ -1,84 +0,0 @@
----
-name: game-animation-frames
-description: >
-  Deep guide for game ANIMATION assets: motion cycles, action keyframes,
-  effect sequences, and animation sprite sheets — built around a
-  video-first pipeline. In this app-builder sandbox, execute via the
-  video2dsprite / generate2dsprite skills (magenta + scripts), not ad-hoc
-  ffmpeg. Use whenever generating anything that moves: walk/run cycles,
-  attacks, idles, FX, flags, fire, animation sheets. Complements
-  game-asset-core.
-metadata:
-  short-description: "Video-first animation frames that actually cycle"
-user-invocable: false
----
-
-# Animation Frames — video-first
-
-The image generator draws poses; the VIDEO generator understands motion —
-leg alternation, arc continuity, cloth and fire dynamics come free because
-video must animate them. So don't ask the image model to imagine
-mid-motion poses: animate the base and harvest real frames.
-
-## App-builder execution (read first)
-
-This skill is **doctrine** (motion laws, loop QC, when to use video). In the
-app-builder sandbox, **do not** run a freeform `ffmpeg` harvest or invent a
-random keyable `#hex` background.
-
-| Step | Do this |
-| --- | --- |
-| Production sprites / fixed grids | **`generate2dsprite`** — solid **`#FF00FF`** magenta sheets + chroma scripts |
-| Denser locomotion from video | **`video2dsprite`** — base still on **`#FF00FF`** → `imagine_image_to_video` → skill scripts (ffmpeg + chroma) |
-| Keyable background | Always **`#FF00FF`** when using either pipeline (required for chroma) |
-| This skill | Loop / flip-test / motion laws below — apply after the pipeline runs |
-
-Open `.grok/skills/video2dsprite/SKILL.md` or `.grok/skills/generate2dsprite/SKILL.md`
-and follow their workflows for generation and postprocess. Then apply the
-laws and flip test here before shipping frames into the game.
-
-## Default pipeline (intent)
-
-1. **Base frame.** Subject in neutral/starting pose, full style words, side /
-   game-appropriate view, **solid `#FF00FF` background** (app-builder chroma
-   key). game-asset-core defaults apply.
-2. **Animate.** `imagine_image_to_video` from the base: one clear motion, in place,
-   static camera ("the knight walks in place, side view, camera locked",
-   6s). Keep the shot simple — one subject, one motion. Prefer running this
-   through **`video2dsprite`** so harvest + chroma are consistent.
-3. **Harvest + clean.** Use **`video2dsprite`** scripts (not ad-hoc
-   `ffmpeg -i … fps=12` alone). Magenta flood-fill / despill lives there;
-   do not re-key with a different flat `#hex` unless you leave the magenta
-   pipeline entirely.
-4. **Select.** Pick frames that (a) capture the motion's distinct phases and
-   (b) LOOP — the sequence's end must flow back into its start. Don't force
-   a count: if the motion reads best with 8, 10, or 12 frames, deliver that
-   many (more frames = smoother in-engine). For a cycle, select one full
-   period using motion landmarks (foot contacts, wing extremes, flame peaks).
-5. **Package.** Deliver frames in play order (zero-padded names) and/or a
-   sheet per game-asset-core rules (uniform cells, no dividers) — or the
-   transparent strips/grids emitted by **`video2dsprite`** /
-   **`generate2dsprite`**. State the intended fps.
-
-Fall back to keyframe-by-keyframe `imagine_text_to_image` (still on `#FF00FF` when
-postprocessing with the sprite scripts) only when video fails the motion
-(rare: very stylized poses, single dramatic keyframes) — and then plan
-phases yourself and obey the laws below. Prefer **`generate2dsprite`** for
-crisp production multi-frame grids.
-
-## Motion laws (verify against these, whatever the pipeline)
-
-- Cycles loop; alternating gaits spend half the period mirrored.
-- Continuity: limbs, props, anatomy, effects move on continuous paths —
-  nothing teleports, vanishes, or duplicates between adjacent frames.
-- Physics reads in stills: airborne shows air, anticipation compresses,
-  follow-through overshoots; effects stay anchored to their origin unless
-  the request moves them.
-- Energy matches the ask: idle/subtle means barely-different frames.
-
-## Verify — the flip test
-
-View the final frames strictly in order and narrate the motion; check
-loop closure explicitly (last→first). A hedge in your narration is a
-failed frame. The video pipeline usually passes this on the first try —
-that's why it's the default.

package/skills/grok-game-animation-frames/agentsam.skill.json

@@ -1,25 +0,0 @@
-{
-  "schema": "agentsam.skill.v1",
-  "id": "grok-game-animation-frames",
-  "name": "Grok \u00b7 game-animation-frames",
-  "description": "Video-first animation frames that actually cycle",
-  "icon": "skill",
-  "slash": {
-    "suggested": "/grok-game-animation-frames"
-  },
-  "instructions": {
-    "source": "local_file",
-    "ref": "SKILL.md"
-  },
-  "execution": {
-    "mode": "turn",
-    "tools": [],
-    "operations": [],
-    "capabilities": []
-  },
-  "provenance": {
-    "source": "apps/local-studio/.grok/skills",
-    "vendor": "grok",
-    "status": "imported"
-  }
-}

package/skills/grok-game-asset-core/SKILL.md

@@ -1,69 +0,0 @@
----
-name: game-asset-core
-description: >
-  Core discipline for ANY game-asset generation with Imagine tools: the
-  engine-ready defaults users don't state, spec checklists, style anchoring,
-  read-back verification, honest defect flagging. Use whenever generating
-  any game art (sprites, sheets, animations, tiles, UI, FX) — then ALSO load
-  the matching specialist skill: game-animation-frames for anything that moves,
-  game-tilesets for tiles/terrain, game-character-consistency for recurring characters,
-  game-ui-icons for UI and icons.
-metadata:
-  short-description: "Core rules + engine-ready defaults for game assets"
-user-invocable: false
----
-
-# Asset Core
-
-Game developers ask for WHAT they need, not HOW to make it engine-ready.
-The how is your job. Apply these defaults whenever the request doesn't say
-otherwise — an asset that needs manual cleanup is a miss even if the user
-never mentioned the requirement.
-
-## App-builder note
-
-This skill is **doctrine / QC**. For 2D sprites and motion in this sandbox, also
-run the pipeline skills:
-
-- **`generate2dsprite`** / **`video2dsprite`** for sheets and video harvest
-- Keyable background on those paths is solid **`#FF00FF`** (required for chroma)
-  — not an arbitrary flat hex
-- Motion laws and loop QC live in **`game-animation-frames`** (which defers
-  execution to those pipelines)
-
-## Unprompted engine-ready defaults
-
-| When asked for... | Deliver, without being told... |
-|---|---|
-| a character/creature/prop sprite | isolated subject, flat single-color keyable background (**`#FF00FF`** when using generate2dsprite/video2dsprite), clean silhouette, no baked ground scene or cast shadow |
-| anything that moves/animates | a frame SEQUENCE that loops cleanly (see game-animation-frames; execute via video2dsprite/generate2dsprite) |
-| a sprite sheet | uniform implicit cells, NO divider lines, subject at the identical position per cell so frames crop at width/cols × height/rows — or build it yourself: frames + PIL composite |
-| ground/terrain/water/walls | seamlessly tileable (verify with a real 2×2 composite), no landmark motifs, non-directional lighting where rotation might be used |
-| UI panels/frames/buttons | scale-survivable (9-slice: corner ornament, uniform edges), no text ever (games localize), state variants geometry-identical |
-| the same character/object again | edit-chained from your existing base image, never regenerated fresh |
-| icons | one style contract across the set, uniform padding, legible at 32px |
-
-Deliver organized, exactly-named files; if the request leaves counts or
-naming to you, choose sensible names and document them in a manifest/record.
-
-## Working discipline
-
-1. **Spec checklist (private).** List every stated property PLUS the
-   applicable defaults above. Verify against it; never paste it into
-   prompts.
-2. **Prompt in the generator's language.** 2–5 vivid sentences, always with
-   style/medium words. Express geometry/quantity as nameable visual
-   configurations (clock positions, pie wedges, colored markers), never as
-   numbers or abstractions.
-3. **Verify by describing blind, then diffing.** Write what the image shows
-   before re-reading the spec. Every stated property AND every applicable
-   default is pass/fail — no "good enough", no self-negotiated waivers. A
-   hedge in your own description = failed check.
-4. **Escalate representation, then strategy.** Retry once with a more
-   concrete visual re-expression. If the generator repeats the same failure,
-   it's a prior: build compositionally (parts + PIL rotate/mirror/assemble —
-   mind mirrored asymmetries) or keep the best and FLAG it. ~2 discards max
-   per point being proven.
-5. **Deliver and report.** Final pass across all files for cohesion and the
-   checklist; state every unfixed defect and every default you consciously
-   deviated from.

package/skills/grok-game-asset-core/agentsam.skill.json

@@ -1,25 +0,0 @@
-{
-  "schema": "agentsam.skill.v1",
-  "id": "grok-game-asset-core",
-  "name": "Grok \u00b7 game-asset-core",
-  "description": "Core rules + engine-ready defaults for game assets",
-  "icon": "skill",
-  "slash": {
-    "suggested": "/grok-game-asset-core"
-  },
-  "instructions": {
-    "source": "local_file",
-    "ref": "SKILL.md"
-  },
-  "execution": {
-    "mode": "turn",
-    "tools": [],
-    "operations": [],
-    "capabilities": []
-  },
-  "provenance": {
-    "source": "apps/local-studio/.grok/skills",
-    "vendor": "grok",
-    "status": "imported"
-  }
-}

package/skills/grok-game-character-consistency/SKILL.md

@@ -1,69 +0,0 @@
----
-name: game-character-consistency
-description: >
-  Deep guide for CHARACTER IDENTITY across images: turnarounds (front/side/
-  back), state and damage variants, palette swaps, equipment changes, and
-  same-character-in-context sets. Use whenever generating character
-  turnarounds, character sheets, variants of an existing sprite, or any
-  same-subject multi-image set. Complements game-asset-core.
-metadata:
-  short-description: "Same character, every image"
-user-invocable: false
----
-
-# Character Consistency
-
-The product is the IDENTITY, not any single image.
-Users state WHAT they need, not how — apply everything here even when
-the request never mentions it.
-
-
-## 1. Asymmetry bookkeeping (turnarounds)
-
-Before prompting, write the side-map table for every view. Example: "her
-left arm sleeved" →
-
-| view  | sleeved arm appears on | staff hand appears on |
-|-------|------------------------|----------------------|
-| front | viewer's RIGHT         | (as designed)        |
-| right profile | near side = her right = BARE | ...          |
-| back  | viewer's LEFT          | mirrored from front  |
-
-Prompt each view with VIEWER-relative words from this table, never
-body-relative words. Verify each output against the table, not the original
-sentence.
-
-## 2. Hands and props
-
-- A held item must be GRIPPED: check the hand-object contact point in every
-  image. A staff floating beside an open hand = fail.
-- The item stays in the SAME hand across all views/frames (mirror it
-  correctly in back views).
-
-## 3. Edit-chain protocol
-
-- One base image; every view/variant/state via `imagine_image_to_image` with the base
-  `file_path` (or the nearest neighbor view): "Keep this exact character — same
-  face, colors, proportions, outfit, scale, background — change only <X>."
-- Views must be genuinely rotated (a side view is a strict profile: nose,
-  chest, toes all pointing at the frame edge), not three slightly-turned
-  fronts.
-- KEEP THE STYLE WORDS in every edit prompt ("stylized 2D game art, cel
-  shading" or whatever the set uses). Edits without style words drift
-  toward photorealism.
-
-## 4. Variants (damage / palette / equipment)
-
-- State the freeze-list first in the prompt (pose, framing, background,
-  everything not being changed), then the single change.
-- Damage states are STATES, not action frames: worn, cracked, dented — no
-  debris flying mid-air.
-- Verify by viewing base and variant together: background hue, framing,
-  proportions, and all unrequested details must match. Escalating states
-  (hurt → critical) must be strictly ordered when viewed as a set.
-
-## 5. Verify
-
-For every image in the set, describe blind: which side has the marker
-detail, what's in each hand, face/proportion match to base. One mismatch =
-targeted retry of that image only.

package/skills/grok-game-character-consistency/agentsam.skill.json

@@ -1,25 +0,0 @@
-{
-  "schema": "agentsam.skill.v1",
-  "id": "grok-game-character-consistency",
-  "name": "Grok \u00b7 game-character-consistency",
-  "description": "Same character, every image",
-  "icon": "skill",
-  "slash": {
-    "suggested": "/grok-game-character-consistency"
-  },
-  "instructions": {
-    "source": "local_file",
-    "ref": "SKILL.md"
-  },
-  "execution": {
-    "mode": "turn",
-    "tools": [],
-    "operations": [],
-    "capabilities": []
-  },
-  "provenance": {
-    "source": "apps/local-studio/.grok/skills",
-    "vendor": "grok",
-    "status": "imported"
-  }
-}

package/skills/grok-game-tilesets/SKILL.md

@@ -1,65 +0,0 @@
----
-name: game-tilesets
-description: >
-  Deep guide for game TILE assets: seamless tileable textures, terrain
-  transition tilesets, autotiles, and ground/platform tiles. Use whenever
-  generating tileable textures, tilesets, terrain transitions, or seamless
-  patterns. Complements game-asset-core.
-metadata:
-  short-description: "Seamless tiles and transition sets that actually tile"
-user-invocable: false
----
-
-# Tilesets
-
-A tile's job is invisibility in repetition.
-Users state WHAT they need, not how — apply everything here even when
-the request never mentions it.
- Judge everything by "will the
-player notice the grid?"
-
-## 1. Seamless single tiles
-
-- Prompt for UNIFORM stochastic texture: even density, even lighting, no
-  shadows with direction, "the pattern continues off every edge".
-- The repetition killer is any distinctive motif — one recognizable clump,
-  flower, or rock repeats forever. Prompt for anonymous texture; verify by
-  hunting for anything you could point at twice.
-- MANDATORY check: composite a real 2×2 repeat with PIL to a throwaway file
-  and view it. Look for (a) seam lines at the joins, (b) any motif you can
-  spot in all four quadrants, (c) large-scale tone gradients that create
-  checkerboarding. Any of the three = retry.
-
-## 2. Transition tilesets (grass→dirt etc.)
-
-- Prompt it as ONE continuous painted image that happens to be sliceable —
-  never as "tiles", "cells with borders", or anything inviting separated
-  sticker-tiles with gaps. Cells must be filled edge-to-edge, painted
-  content flowing across cell boundaries so adjacent tiles genuinely match.
-- Layout for a 3×3: center = pure inner material; edge cells = straight
-  transitions facing outward; corner cells = outer corners. Verify
-  DIRECTIONALITY per cell (top-center's grass is along its top edge, etc.).
-
-## 3. Rotation economy — make fewer, better tiles
-
-If lighting is neutral (pure top-down, no directional shading), one straight
-edge and one outer corner can be ROTATED in-engine to produce all four of
-each. So when the tile count is yours to choose:
-
-- Produce: 1 center fill, 1 straight edge, 1 outer corner, 1 inner corner —
-  then spend the remaining budget on VARIATIONS of the center fill (2–3
-  anonymous variants breaks up repetition far better than 4 identical
-  rotated edges).
-- CAVEAT — rotation only works when nothing in the art encodes direction:
-  no directional light, no gravity cues (hanging grass blades, drips), no
-  text/emblems. Side-view (platformer) tiles almost always encode gravity
-  and light, so they need all orientations painted individually. State in
-  your delivery notes which tiles are rotation-safe.
-- If the request explicitly fixes the grid (e.g. "3×3 with all 8
-  transitions"), deliver exactly that — mention rotation economy in notes,
-  don't unilaterally change the deliverable.
-
-## 4. Platforms and props
-
-Isolated on a keyable background, consistent lighting with their tileset,
-no baked ground shadow (engines composite shadows separately).

package/skills/grok-game-tilesets/agentsam.skill.json

@@ -1,25 +0,0 @@
-{
-  "schema": "agentsam.skill.v1",
-  "id": "grok-game-tilesets",
-  "name": "Grok \u00b7 game-tilesets",
-  "description": "Seamless tiles and transition sets that actually tile",
-  "icon": "skill",
-  "slash": {
-    "suggested": "/grok-game-tilesets"
-  },
-  "instructions": {
-    "source": "local_file",
-    "ref": "SKILL.md"
-  },
-  "execution": {
-    "mode": "turn",
-    "tools": [],
-    "operations": [],
-    "capabilities": []
-  },
-  "provenance": {
-    "source": "apps/local-studio/.grok/skills",
-    "vendor": "grok",
-    "status": "imported"
-  }
-}

package/skills/grok-game-ui-icons/SKILL.md

@@ -1,56 +0,0 @@
----
-name: game-ui-icons
-description: >
-  Deep guide for game UI assets: buttons with interaction states, panels,
-  bars, wordmark logos, and icon sets. Use whenever generating game UI
-  elements, HUD assets, inventory icons, icon sets, buttons, or title
-  logos. Complements game-asset-core.
-metadata:
-  short-description: "Game UI kits and icon sets"
-user-invocable: false
----
-
-# Game UI & Icons
-
-UI is a SYSTEM: the set matters more than any piece.
-Users state WHAT they need, not how — apply everything here even when
-the request never mentions it.
-
-
-## 1. Interaction states (normal/hover/pressed)
-
-- Generate NORMAL first; hover and pressed are `imagine_image_to_image` edits of it with an
-  explicit freeze-list: "same shape, same size, same ornament, same frame
-  thickness, same background — change ONLY <state treatment>".
-- Standard treatments: hover = subtle outer glow / slight brighten;
-  pressed = darker + inset/inner shadow. States must be distinguishable at
-  a glance AND identical in geometry — overlay-compare: outlines should
-  coincide, frame thickness included.
-
-## 2. Icon sets
-
-- One style contract for the whole set, decided before generating: same
-  stroke weight, same fill treatment (all outlined OR all solid — never
-  mixed), same palette family, same padding, same background, same visual
-  weight. Verify the set side by side; one icon with a different treatment
-  (e.g. sitting in a filled tile while others float) fails the SET even if
-  it's individually fine.
-- Generate icon 1, then edit-chain the rest from it to inherit the
-  contract.
-- Each icon must read at 32px: squint-test the thumbnail.
-
-## 3. Panels, bars, wordmarks
-
-- Panels/dialogs: blank, text-ready, borders that survive 9-slicing
-  (uniform edges, ornament concentrated in corners).
-- Bars: clear frame vs fill separation; fill design must work at any
-  percentage.
-- Wordmark logos: image models garble text — generate, then READ THE TEXT
-  BACK letter by letter; any wrong/merged/extra letter = retry. Deliver as
-  an isolated asset on flat/keyable background, not a full scene, unless a
-  title SCREEN is requested.
-
-## 4. No text anywhere else
-
-Buttons, panels, icons: no lettering unless explicitly requested — models
-garble it and engines localize it.

package/skills/grok-game-ui-icons/agentsam.skill.json

@@ -1,25 +0,0 @@
-{
-  "schema": "agentsam.skill.v1",
-  "id": "grok-game-ui-icons",
-  "name": "Grok \u00b7 game-ui-icons",
-  "description": "Game UI kits and icon sets",
-  "icon": "skill",
-  "slash": {
-    "suggested": "/grok-game-ui-icons"
-  },
-  "instructions": {
-    "source": "local_file",
-    "ref": "SKILL.md"
-  },
-  "execution": {
-    "mode": "turn",
-    "tools": [],
-    "operations": [],
-    "capabilities": []
-  },
-  "provenance": {
-    "source": "apps/local-studio/.grok/skills",
-    "vendor": "grok",
-    "status": "imported"
-  }
-}

package/skills/grok-generate2dmap/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026 0x0funky
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.