// Onboard developers and coding agents into Marinara. Use when someone asks how to get started, asks for a repo tour, wants the docs run, needs to run/build the app, wants a first testing checklist, or wants a guided workflow for finding and fixing bugs in this repo.
Protect Marinara's layered Tauri architecture, module ownership, dependency direction, explicit imports, Rust capability boundaries, shared-code placement, and file-splitting discipline. Use when changing folders, imports, shared modules, TypeScript engine layers, Tauri command wrappers, Rust capability crates, repositories, adapters, feature APIs, or any code structure that could widen impact area.
Guide Marinara bug fixes toward root-cause repairs with clear impact areas, focused commits, validation, and no band-aid patches. Use for regressions, broken UI actions, failing checks, provider/transport bugs, storage bugs, import/export bugs, generation bugs, mode behavior bugs, and any change where the fix could affect dependent modules.
Enforce Marinara's strict separation between chat/conversation, roleplay, and game mode. Use when changing mode engines, mode UI, autonomous chat, schedules, summaries, roleplay scenes, sprites, encounters, visual novel choices, game turns, game prompts, game state, generation guide routing, prompt assembly, or any shared code that could affect more than one mode.
| name | marinara-getting-started |
| description | Onboard developers and coding agents into Marinara. Use when someone asks how to get started, asks for a repo tour, wants the docs run, needs to run/build the app, wants a first testing checklist, or wants a guided workflow for finding and fixing bugs in this repo. |
Use this skill to turn a vague "how do I get started?" request into a concrete onboarding session: run the docs, explain the repo, help run the app, guide testing, then switch into bug-fix discipline when a real issue is found.
Read references/onboarding-flow.md when preparing a full onboarding response.
Also load:
skills/marinara-architecture-guard/SKILL.md before explaining module ownership or code boundaries.skills/marinara-bugfix-discipline/SKILL.md before guiding a bug fix.skills/marinara-mode-separation/SKILL.md before testing or fixing chat, roleplay, game, prompts, or generation routing.When the user asks "how do I get started?", "onboard me", "teach me this repo", or similar:
pnpm docs:dev unless the user only wants text instructions.http://127.0.0.1:4174/.pnpm install and pnpm tauri dev.marinara-bugfix-discipline and fix the root cause.Do not start with a generic list of files. Start with the working app and the docs, then connect the user's testing path to module ownership.
Keep the first answer practical:
I’ll start the developer docs at http://127.0.0.1:4174/.
Start here:
1. Read Getting Started, Run and Build, and Architecture.
2. Run pnpm install if dependencies are missing.
3. Run pnpm tauri dev to start the desktop app.
4. Test one workflow at a time and report bugs with steps, expected, actual, and impact area.
Repo tour:
- React UI: src/features and src/app.
- TypeScript engine: src/engine.
- Tauri adapters: src/shared/api.
- Rust capabilities: src-tauri.
When you find a bug, I’ll identify the owner, fix the root cause, and run the right checks.
Then tailor the detail to the user's next action.
Do not move into code edits during onboarding unless the user reports a concrete bug or asks for a feature. If a bug is found, state the impact area before editing.