# Overview

The schema has two uses in your project:

1. As a basis for *code generation*, creating various structs and methods that can be used in your project to communicate with the replication server.
2. As a description for the Replication Server, telling it how the data in your project looks like – to receive, store, and send this data to its clients.

When using MonoBehaviours and CoherenceSync you often don't need to interact with the schema directly. 

If you're writing your game using ECS/DOTS you will have to create and modify it yourself. Here's an example of a small schema:

```
component Player
  name String64
  score Int
  
component Enemy
  speed Float
  hp Int
  poisonous Bool
```

To learn more about the types and definitions available in a schema, see the [specification](/0.5.2/schema-reference/specification.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.coherence.io/0.5.2/schema-reference/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.