Add Screen

Templates are available in .agents/templates/new-spec.md for structured input.

Reference Standards

• Naming: .agents/standards/naming-conventions.md
• DI: .agents/standards/dependency-injection.md
• Unit tests: .agents/standards/testing-unit.md
• UI component tests: .agents/standards/testing-ui-component.md
• Design system & adaptive layout: .agents/standards/design-system.md

Reference Implementation

Use existing screens in features/order/ as the pattern reference.

Files to Create

Screen Type Selection

• Screen — standard navigation target (most common)
• ProtectedScreen — requires authentication, triggers AuthInterceptor redirect to login
• TabScreen — bottom navigation tab, needs override val tag: String

Key Conventions

• Screen objects are data objects (not classes) with @Parcelize
• Presenters must have @CircuitInject({Screen}::class, AppScope::class), @Inject, and @Composable
• UiState must implement CircuitUiState and include eventSink: ({Event}) -> Unit
• Events must be sealed class (not sealed interface) for iOS interop
• Ui functions must have @CircuitInject({Screen}::class, AppScope::class) and @Composable

Post-Change Verification — MANDATORY

Work is NEVER complete until verification passes. Run the verify skill to validate all changes. It will:

• Detect which modules were affected by the new screen files
• Run lint, unit tests, and architecture checks scoped to those modules
• Catch naming violations, missing annotations, DI wiring issues, and test convention problems

If ANY check fails, fix the issue and re-run. Do not declare the task complete until verification passes.