> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/docs-site/community/packages.md).

# Packages

## On main today

There is one Laravel package:

| Path                | Composer name       | What it is                                                                           |
| ------------------- | ------------------- | ------------------------------------------------------------------------------------ |
| `packages/toshi-ui` | `klassapp/toshi-ui` | Assistant UI only: suggestion chips and the tool confirmation card. No school logic. |

The root `composer.json` loads it as a path repository and requires `klassapp/toshi-ui`. The service provider publishes views and CSS.

Other seams exist in the app and are not packages a contributor can drop in:

* Per-school feature toggles, with a short fixed list of keys.
* A connector catalogue in `config/toshi.php` (Slack, Notion, Google Drive). Each one is off unless that environment flag is set. Only Slack has a skill class.
* Per-school grading rows (`SchoolGradingSystem`). The default scale shipped in config is not yet a package.
* Toshi skills registered in PHP, not discovered from a package.

## Proposal, not built

[Pull request #1119](https://github.com/KlassApp-Foundation/KlassApp/pull/1119) is a docs-only proposal. It is not merged. Nothing in it runs on `main`.

It suggests eight extension points the core would own and a package would implement:

1. Grading scales
2. Curriculum packs
3. Report card templates
4. Connectors
5. Payment gateways
6. WhatsApp commands
7. Toshi tools
8. Dashboard cards

A package would be built, registered, versioned, enabled per school, and tested. The core would still own tenancy, sign-in, permissions, student identity, the marks release gate, WhatsApp transport, and the rule that AI stays off until a school turns it on.

The first extraction it sketches is a grading package. That extraction is not in the pull request. It also waits on the marks-flow proposal ([#1118](https://github.com/KlassApp-Foundation/KlassApp/pull/1118)), which is not on `main`. Marks and report-card help stays a placeholder until that flow lands.

Do not add a package, a registry, or a curriculum pack from this page. Wait until #1119 is accepted.

## Related

[Architecture](https://github.com/KlassApp-Foundation/KlassApp/tree/main/community/architecture/README.md) · [Connectors](https://github.com/KlassApp-Foundation/KlassApp/tree/main/community/connectors/README.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://klassdocs.gitbook.io/klassapp-documentation/docs-site/community/packages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.