osg

Plugin osg from marketplace osg in kirkness/osg-plugin. Commands read from the repo's manifest — 18 days ago.

Skills (11)

• osg-assets

  Use when adding or choosing art, sound, music, fonts or libraries: provenance and licensing, vendoring everything locally (no CDN), CREDITS.md, allowed file types, and what the verifier does with screenshots and cover art.

• osg-design

  Run BEFORE writing game code, and again for polish. Aesthetics and ideation for a distinctive, high-quality browser game: hook, friend test, core loop, visual direction with banned generic defaults, juice, screenshot moment, self-critique with osg shot, scoring rubric.

• osg-dev

  Use to run, play, stop, restart, test, check or screenshot the game locally with the bundled osg command ("run my game", "let me play it", "stop the game", "close it", "restart it"): osg dev (emulated shell, rooms, boards, chat, NPCs, simulated players, chaos), osg stop, osg check, osg shot, osg val

• osg-multiplayer

  Use when adding or debugging multiplayer: rooms, lobby and quick play, party codes and invites, host-authoritative vs relay topologies, snapshots and host migration, reconnects and epochs, the 8-seat cap, honest latency limits.

• osg-npcs

  Use when adding NPC opponents, allies or AI-controlled characters: scripted behaviour first, then optional model decisions through declared brains in osg.json, createBrain, the mandatory fallback, confidence gating, batching and budgets.

• osg-pads

  Use when the author wants players to use their phones as controllers (pads), or when an idea would be better with one: QR pairing, built-in layouts (buttons, stick, wheel, reel, swing, tilt, touchpad), motion and gestures, couch and party games, honest latency, keyboard fallback, and custom controll

• osg-publish

  Submit the game for build and review (author-invoked only). Validates, builds and packs locally, confirms the account and game, uploads the source and submits for verification, then explains the 5 minute email. Polls the verification report only if asked.

• osg-rules

  Use before submitting, when something looks risky, or when a game is rejected: the approval rules in plain language (no external calls or CDN, no copied IP, no rude words or imagery), what the cloud review does, rejection and resubmit, topic drift, rollback, plus a local pre-flight checklist.

• osg-scores

  Use when adding leaderboards, scores, high scores, achievements or stats: declaring bounded boards (min, max, maxPerSecond), the start/submit run flow, why client-trusted scores fail, guest lanes, global-rank fairness, achievement and stat design.

• osg-sdk

  Use when writing or changing game code that touches the Our Silly Games SDK (@osg/sdk): ready, player, saves, leaderboards, achievements, stats, rooms, chat, NPC decisions, phones as controllers, analytics, feature detection. Code touches only osg, never fetch or WebSocket.

• osg-start

  Start here when the author wants to make, build or publish a browser game for Our Silly Games ("make me a game about...", "I want to create a game", "new game"). Runs the Bun preflight, forces a creative brief before code, scaffolds the project, explains the submit-to-email timeline.

MCP servers (2)

• osg

  connects to: https://mcp.oursilly.games/mcp

• osg-docs

  connects to: https://mcp.oursilly.games/docs

Hooks (1)

• SessionStart

  sh "${CLAUDE_PLUGIN_ROOT}/scripts/session-start.sh"

Similar plugins