Update to Uniform

{
  "description": "Uniform SDK developer reference covering authentication, CLI configuration, routing, and the content API clients that read and write compositions, entries, and content types. Use when setting up Uniform in a frontend project, configuring the CLI, working with the Route API, or reading or writing Uniform content in code with EntryManagementClient, EntryDeliveryClient, CompositionManagementClient, or the deprecated CanvasClient and ContentClient.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 171
    },
    {
      "relative_path": "references/authentication.md",
      "size_in_bytes": 1468
    },
    {
      "relative_path": "references/cli-reference.md",
      "size_in_bytes": 9715
    },
    {
      "relative_path": "references/clients.md",
      "size_in_bytes": 7975
    },
    {
      "relative_path": "references/routing.md",
      "size_in_bytes": 4031
    }
  ],
  "name": "uniform-sdk",
  "skill_md_contents": "---\nname: uniform-sdk\ndescription: Uniform SDK developer reference covering authentication, CLI configuration, routing, and the content API clients that read and write compositions, entries, and content types. Use when setting up Uniform in a frontend project, configuring the CLI, working with the Route API, or reading or writing Uniform content in code with EntryManagementClient, EntryDeliveryClient, CompositionManagementClient, or the deprecated CanvasClient and ContentClient.\nlicense: MIT\n---\n\n# Uniform SDK\n\nFramework-agnostic developer reference for integrating Uniform into applications. Covers authentication, the Uniform CLI, routing via Project Map, and the content API clients used to read and write Uniform content from code.\n\n\n## Key principles\n\n### Always use MCP tools for content operations\n\nCRITICAL: Never manipulate YAML or JSON files in the `uniform-data` folder directly. Always use the Uniform MCP tool for creating, modifying, or deleting components, content types, or any other Uniform entity. After making changes via MCP, run `npm run uniform:pull` to sync the latest state to disk.\n\n### Pin all Uniform packages to the same version\n\nAll `@uniformdev/*` npm packages in a project must use the same version. Mismatched versions cause hard-to-debug dependency conflicts and runtime errors. When installing or upgrading, ensure every Uniform package resolves to the identical version number.\n\n### SDK setup checklist\n\nWhen adding Uniform SDK to a project:\n1. Install the appropriate framework-specific packages (all at the same version)\n2. Create a component in code for every composition component found in the Uniform project\n3. Add all slots from the component definition\n4. This ensures preview works correctly\n\n## Resources\n\nSee `references/` for detailed guidance:\n- [Authentication](references/authentication.md) — API keys, `.env` setup, permissions\n- [CLI reference](references/cli-reference.md) — Configuration, push/pull commands, help system\n- [Routing](references/routing.md) — Project Map and dynamic route delegation\n- [Content API clients](references/clients.md) — Delivery vs management, reading and writing entries, field shapes, deprecated predecessors\n"
}