Sine Kits
Sine Kits
  • Home
  • Docs
  • Blog
  • My Kits
  • Developers
    ← Back to Blog
    Sep 29, 2026Product notes

    What makes a Kit a product?

    Skills, executable operations, a dedicated site, and managed data belong to one coherent workflow.

    S

    Sine Kits Team

    Product

    Instructions are only the beginning

    A Skill can explain a domain workflow to an Agent. It cannot, by itself, provide private storage, authorize an external account, or give a person a reliable place to inspect the result.

    Sine Kits uses a broader definition: a Kit combines Agent Skills, executable domain operations, a dedicated site, and managed domain data. The Agent and the person work with the same installation rather than keeping disconnected copies of a task in a chat and a dashboard.

    Two entrances, one workspace

    Skills describe the method and the operation contract. The dedicated site provides the domain interface: projects, resources, and operation history. The backend remains the authority for who may access the installation and its data.

    Each Kit lives in an independent project and deploys its own site. The platform supplies shared identity, authorization, versioned developer packages, and scoped data APIs. A developer's ownership of a Kit project does not grant access to another user's private workspace.

    Keep access decisions separate

    An entitlement answers whether someone has the right to use a Kit. An installation is their private workspace and selected release. A connection points to an external service account. An Agent grant limits what that Agent may execute.

    Downloading instructions is not authorization. Paying for a platform plan is not purchasing every Kit. Connecting a service is not agreeing to every charge or side effect that a future operation could produce.

    What the current preview proves

    The current independent Game Dev Kit persists project names and briefs through a real operation, with a dedicated site for projects, resources, and runs. The toolchain supports development, immutable builds, preview publishing, review, and controlled environment changes.

    This is a publisher-sandbox workflow. It is not an announcement of a paid marketplace or validated 3D generation. More ambitious capabilities need their own provider, quality, permissions, licensing, and cost verification before becoming product promises.

    Read the product guide, getting started guide, or Game Dev Kit preview scope.