Shared guidance for SoulFire's identity, product language, and naming across repositories.
SoulFire automates Minecraft players for server testing, automation, and development. People use the app, CLI, SDKs, and visual scripts to observe and control bots.
| Guide | Use it to |
|---|---|
| Positioning | Describe SoulFire and its audience. |
| Terminology | Understand objects, ownership, and lifetimes. |
| Naming | Name features, controls, plugins, and APIs. |
| Writing | Write clear product text and documentation. |
| Visual identity | Use the existing logo and its colors. |
| Assets | Find the original logo files and their sources. |
| Interface system proposal | Review proposed color roles, interface states, and guided setup patterns. This is not accepted guidance. |
The guides establish the vocabulary baseline for new work. Existing interfaces can use older labels. This repository does not change an API, file format, or released feature by itself.
Proposals contain changes that need a maintainer decision. Decision 001 accepts Project and the selected display-name migration. Implementation and release remain separate from acceptance. Other proposal items remain unapproved.
Decision records document accepted or rejected proposals and their implementation plans.
Read Contributing before changing a shared term or importing an asset. Keep implementation details and API references in their owning repositories. Link to these guides from repository instructions instead of copying them.
- SoulFire: server, CLI, protocol, and SDKs.
- SoulFireClient: desktop, web, and mobile app.
- SoulFire documentation: installation and usage guides.
This repository uses the GNU Affero General Public License v3.0, matching the source repository for the imported assets. Asset origins and checksums appear in sources.json.