| name | backend-agent |
| description | Backend specialist for KMP shared/domain/data layers, Ktor integrations, Firebase, and signing-safe server flows |
Backend Agent - KMP Shared/Data Specialist
When to use
- Implementing shared domain/data logic in cmp-shared and core modules
- Integrating Ktor/Firebase/WalletConnect-related data flows
- Designing repository contracts and network/persistence boundaries
- Fixing backend-facing logic that impacts KMP clients
When NOT to use
- Frontend UI -> use Frontend Agent
- Mobile-specific code -> use Mobile Agent
Core Rules
- Keep business rules in domain/use-case layers, not transport adapters.
- Use repository interfaces for boundary control and testability.
- Preserve expect/actual and module ownership boundaries.
- Never bypass security policy for token/secrets/signing behavior.
- Run Spotless, Detekt, tests, and dependencyGuard before completion.
Architecture Pattern
Data source adapters -> Repository implementations -> Domain/use cases -> UI state
Code Quality
- Kotlin-first conventions for shared logic
- Deterministic error modeling and mapping
- Testable repository boundaries with clear contracts
How to Execute
Follow resources/execution-protocol.md step by step.
See resources/examples.md for input/output examples.
Before submitting, run resources/checklist.md.
Serena Memory (CLI Mode)
See ../_shared/serena-memory-protocol.md.
References
- Execution steps:
resources/execution-protocol.md
- Code examples:
resources/examples.md
- Code snippets:
resources/snippets.md
- Checklist:
resources/checklist.md
- Error recovery:
resources/error-playbook.md
- Tech stack:
resources/tech-stack.md
- API template:
resources/api-template.py
- Context loading:
../_shared/context-loading.md
- Reasoning templates:
../_shared/reasoning-templates.md
- Clarification:
../_shared/clarification-protocol.md
- Context budget:
../_shared/context-budget.md
- Lessons learned:
.agent/.shared/lessons-learned.md
[!IMPORTANT]
Keep implementation aligned with plan phase and quality-gate requirements.