Glossary
The words you will meet in Alloy and these docs, in one place.
| Term | Meaning |
|---|---|
| Prompt | A description of what to build or change. A new project or a fix. |
| Version | A saved state of the project. Every prompt, import or editor save creates one. |
| Studio | The project screen: Preview, Code, Live, SEO and Git. |
| Preview | A fast render of the current version. |
| Live | The project running in an in-browser sandbox. |
| Kind | Website (frontend only) or App (frontend + REST backend). |
| Stack | The libraries used: ForgeStack (default) or MUI + NestJS. |
| Skeleton | The proven starting project (site, admin or CMS) every generation builds on. |
| alloy-1.5flash | The model setup Alloy uses for every generation and fix. |
| Bear | The ForgeStack UI component library used for every visible element. |
| Lingo | The translation library: English, Hebrew and Spanish with right-to-left. |
| Pull request (PR) | A proposed change on your Git host; Alloy opens one per version. |
| Import | Bringing changes from your repository back into Alloy. |
| [external] | Label for versions that came from an import. |
| Conflict | A file changed both in Alloy and in the repository since they last agreed. |
| Quota | How many prompts your plan includes. |
| MCP | Model Context Protocol: lets AI editors call tools such as Alloy (planned). |