978325565d
Initialize the llm-multiverse-ui project with: - SvelteKit + Svelte 5 (runes mode enabled) - Tailwind CSS v4 via @tailwindcss/vite plugin - TypeScript strict mode - ESLint 9 flat config with svelte and typescript-eslint plugins - Prettier with svelte plugin - Directory structure: src/lib/components/, src/lib/services/ - All required scripts: dev, build, preview, lint, format, check Closes #1 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
44 lines
1.7 KiB
Markdown
44 lines
1.7 KiB
Markdown
# Shared Agent Context
|
|
|
|
## Gitea Connection
|
|
|
|
- **Owner:** `llm-multiverse`
|
|
- **Repo:** `llm-multiverse-ui`
|
|
|
|
## Mode
|
|
|
|
Every agent operates in one of two modes:
|
|
|
|
- **standalone**: Invoked directly by a user via `/project:<command>`. Interact naturally, ask for confirmation when needed, display formatted reports.
|
|
- **subagent**: Invoked by auto-dev via the Agent tool. Return ONLY a single JSON block as your final output. No conversational text, no questions, no confirmations.
|
|
|
|
Mode is specified in the **Dynamic Context** section at the bottom of your agent prompt. If no mode is specified, default to **standalone**.
|
|
|
|
## Structured Return Contract (subagent mode)
|
|
|
|
When in subagent mode, your final output MUST be a single JSON object:
|
|
|
|
```json
|
|
{
|
|
"status": "success | partial | failed",
|
|
"summary": "3 sentence max description of what happened",
|
|
"artifacts": ["list of file paths created or modified"],
|
|
"phase_data": {},
|
|
"failure_reason": null
|
|
}
|
|
```
|
|
|
|
- `status`: "success" if all objectives met, "partial" if some completed, "failed" if unable to proceed
|
|
- `phase_data`: Agent-specific structured data (see your agent prompt for schema)
|
|
- `failure_reason`: null on success, string describing what went wrong on failure
|
|
|
|
## Architecture Reference
|
|
|
|
All agents MUST respect the project's architecture constraints. Read `CLAUDE.md` if it exists for project-specific rules. Key principles:
|
|
|
|
- Follow the established frontend framework patterns and conventions
|
|
- Use the project's chosen state management approach consistently
|
|
- Follow component composition patterns already established in the codebase
|
|
- Respect the project's API communication layer — do not bypass it
|
|
- Keep UI components focused and composable
|