github.com/Facepunch/sbox-public/ (link)

commit signals (14)

source signals (9)

• engine/Launcher/SceneLab/AGENTS.mdvia agents-md

  # SceneLab — agent guide
  
  > Scope: `scenelab.exe`, the proving ground for the managed scene renderer. Last reviewed: 2026-09-29.
  > The renderer's own guide is [`engine/Sandbox.SceneRenderer/README.md`](../../Sandbox.SceneRenderer/README.md);
  > read it first. The details are in [`docs/managed/scene-renderer.md`](../../../docs/managed/scene-renderer.md)
  > (*SceneLab*, *Parity with native*, *Benchmark*).
  
  SceneLab is to the managed renderer what PanelGallery is to panels. It's a borderless `PanelWindow` that

• AGENTS.mdvia agents-md

  # s&box — notes for AI coding agents
  
  s&box is a game engine built on Valve's Source 2 with a .NET 10 managed layer on top. This repo is the
  **managed engine, editor, and tooling** in C#. The native C++ core is not here — `Setup.bat` (`./Setup.sh` on Linux and macOS)
  downloads prebuilt native binaries into `game/bin/win64/`, and the managed side calls into them through a
  generated interop layer (never hand-edit `Interop.*.cs` or anything under `obj/.generated/`).
  
  ## Layout
  
  | Path | What |
  |------|----

• engine/Sandbox.SceneRenderer/AGENTS.mdvia agents-md

  # Sandbox.SceneRenderer
  
  Read [README.md](README.md) before working on this project. Follow its development conventions,
  threading and resource-lifetime requirements, and verification workflow.
  
  For implementation details, read the relevant section of the
  [renderer reference](../../docs/managed/scene-renderer.md).
  

• engine/Sandbox.SceneRenderer/CLAUDE.mdvia claude-code

  @AGENTS.md
  

• CLAUDE.mdvia claude-code

  @AGENTS.md
  

• engine/Launcher/SceneLab/CLAUDE.mdvia claude-code

  @AGENTS.md
  

• engine/Launcher/SboxCli/skills/sbox-cli/SKILL.mdvia unspecified

  ---
  name: sbox-cli
  description: Drives a running s&box editor or game through sbox-cli, the engine's MCP bridge, to inspect and edit scenes, prefabs, assets and Hammer maps, run C# inside the engine, check compile results, enter play mode and take screenshots. Use when working in an s&box project (a folder with a .sbproj file), when asked to do anything in the s&box editor, or when asked to launch, attach to or automate s&box.
  ---
  
  # sbox-cli
  
  `sbox-cli` ships with every s&box installation. It connects to a

• engine/Launcher/SboxCli/skills/sbox-publishing/SKILL.mdvia unspecified

  ---
  name: sbox-publishing
  description: Check that an s&box project's publishing rules include all required content and flag unexpectedly large assets.
  ---
  
  # Check publishing content
  
  Make sure everything the game needs is included. Inspect scenes, code paths and dynamic resource
  loads; don't assume an unreferenced asset is unused. Flag unusually large assets and their
  dependencies for review, even when referenced, rather than removing needed content.
  
  Use `sbox-cli --skill sbox-cli` to connect to the proje

• engine/Launcher/SboxCli/bootstrap/sbox/SKILL.mdvia unspecified

  ---
  name: sbox
  description: Work with s&box game projects and the s&box editor. Use when the folder contains a .sbproj file or the user mentions s&box.
  metadata:
    sbox-bootstrap: "1"
  ---
  
  s&box ships its agent instructions with the engine. From the project folder, run
  `<engine>/bin/managed/sbox-cli --skill` and follow what it prints.
  
  `<engine>` is the s&box install: the `FACEPUNCH_ENGINE` environment variable (on Windows a user
  variable, which a shell started earlier may not have yet), otherwise Steam's
  `

ignorefile signals (0)

none