Find Project Files
Know where to edit Views, shared styles, assets, and game data.
Use Studio's Activity Bar and Explorer to find what you want to edit:
| Item | Where to find it |
|---|---|
| A complete menu or HUD | Explorer → select a package → Views |
| A reusable button or panel | Explorer → Components |
| Shared CSS | Explorer → Global Styles |
| Colors and other named style values | Themes |
| Images, fonts, and icons | Assets |
| Game fields, button actions, and sample values | Store |
| Saved UI checks | Tests |
Click the project name or its edit button to change the display name. This does not rename or move its folder.
Packages and Views
Select a package to see its Views. A View in Studio is a Screen in Blueprint. Use its … menu to move, duplicate, detach, or delete it. Optional list folders organize entries without moving source files.
Styles that affect the UI
Create or attach shared styles through Global Styles. Their order matters: later rules can override earlier ones. A CSS file that is not loaded does not affect Preview just because it exists on disk.
styles/tokens.css and styles/global.css are the required first entries.
Additional styles are listed in calmui.config.json under styles. You do not
need a CSS @import to load them.
Files on disk
Studio keeps ordinary project files that you can review in version control:
| File | Contents |
|---|---|
.calmui | View or component source |
.css | Styles |
calmui.config.json | Project settings and file lists |
*.package.json | The Views and settings in a package |
store.schema.json | Game-data fields and action definitions |
| Configured preview-data and preset JSON files | Example values for Studio Preview |
tests/*.test.json | Saved UI tests |
Edit Store values in Store and component sample props in Inspector. The files
under generated/schema are created automatically and should not be edited.