openuispec 0.1.45 → 0.1.47

package/README.md

@@ -82,10 +82,11 @@ This replaces the old approach of writing instructions in CLAUDE.md and hoping t
 | **Claude Code** | `.mcp.json` | Always |
 | **Codex** | `.codex/config.toml` | Always |
 | **VS Code / Copilot** | `.vscode/mcp.json` | If `.vscode/` exists |
+| **Gemini CLI** | `.gemini/settings.json` | If `.gemini/` exists |
 
 Manual setup (if needed):
 
-**Claude Code** (`.mcp.json`), **VS Code / Copilot** (`.vscode/mcp.json`):
+**Claude Code** (`.mcp.json`), **VS Code / Copilot** (`.vscode/mcp.json`), **Gemini CLI** (`.gemini/settings.json`):
 ```json
 {
   "mcpServers": {
@@ -114,10 +115,14 @@ Or run directly: `openuispec mcp`
 | `openuispec_spec_schema` | Before creating/editing spec files | Returns the full JSON schema for a specific spec type — exact structure, required fields, allowed values |
 | `openuispec_prepare` | Before UI code generation | Returns spec context, platform config, generation constraints |
 | `openuispec_read_specs` | Before and after generation | Loads spec file contents — the authoritative source for tokens, screens, contracts |
-| `openuispec_check` | After generation | Schema validation + concrete audit checklist from your spec |
+| `openuispec_check` | After generation | Schema validation + concrete audit checklist from your spec. Optional `screens`/`contracts` params scope the audit |
 | `openuispec_validate` | After spec edits | Schema-only validation, optionally filtered by group |
 | `openuispec_drift` | Before updates | Detect spec drift since last snapshot, with semantic explanation |
 | `openuispec_status` | Anytime | Cross-target summary: baselines, drift, next steps |
+| `openuispec_get_screen` | Incremental edits | Get a single screen spec by name — faster than `read_specs` for targeted work |
+| `openuispec_get_contract` | Incremental edits | Get a single contract spec, optionally filtered to one variant |
+| `openuispec_get_tokens` | Incremental edits | Get tokens for a specific category (color, typography, spacing, etc.) |
+| `openuispec_get_locale` | Incremental edits | Get a single locale file, optionally filtered to specific keys |
 
 The server includes **protocol-level instructions** that trigger on UI-related requests independently of CLAUDE.md rules — so even if CLAUDE.md is buried under other project rules, the MCP enforcement still works.
 
@@ -137,6 +142,7 @@ See the examples for reference:
 
 - [TaskFlow](./examples/taskflow/openuispec/) — compact reference spec covering all 7 contract families
 - [Todo Orbit](./examples/todo-orbit/openuispec/) — bilingual task app with localization, custom contracts, and generated native/web targets
+- [Social App](./examples/social-app/openuispec/) — trilingual social app with feeds, messaging, profiles, and generated Android/web targets
 
 ## Repository structure
 
@@ -174,6 +180,7 @@ openuispec/
 │   │   ├── generated/                   # Generated iOS, Android, and web apps
 │   │   ├── README.md                    # Sample overview and structure
 │   │   └── AGENTS.md / CLAUDE.md        # AI rules generated from the package
+│   ├── social-app/                       # Social app sample (trilingual, Android + Web)
 │   └── todo-orbit/                      # Full showcase sample
 │       ├── openuispec/                  # Source OpenUISpec project
 │       ├── generated/                   # Generated iOS, Android, and web apps
@@ -183,7 +190,7 @@ openuispec/
 │   ├── index.ts                        # Entry point
 │   └── init.ts                         # Project scaffolding + AI rules
 ├── mcp-server/                          # MCP server (openuispec-mcp)
-│   └── index.ts                        # Stdio transport, 8 tools
+│   └── index.ts                        # Stdio transport, 12 tools
 ├── check/                               # Composite validation command
 │   └── index.ts                        # Schema + semantic + readiness
 ├── drift/                               # Drift detection (spec change tracking)
@@ -242,6 +249,8 @@ By default, drift stores state in `generated/<target>/<project>/`. To point targ
 ```yaml
 generation:
   targets: [ios, android, web]
+  extra_rules:
+    - "Generation hint strings may start with [common], [ios], [android], or [web] to indicate scope."
   output_dir:
     web: "../web-ui/"
     android: "../kmp-ui/"
@@ -254,6 +263,8 @@ Paths are relative to `openuispec.yaml`. The `.openuispec-state.json` file is st
 
 If `api.endpoints` are declared, `generation.code_roots.backend` is required. It should point at the backend folder the AI must inspect when generating API clients or wiring request/response behavior.
 
+`generation.extra_rules` can hold project-wide generation conventions for AI and humans. For example, projects may declare that generation hint strings use prefixes such as `[common]`, `[ios]`, `[android]`, and `[web]` to indicate scope.
+
 `openuispec drift --snapshot --target <target>` requires that target output directory to already exist. If it does not, generate the target code first, then snapshot the accepted baseline.
 
 Use the commands like this:
@@ -344,7 +355,7 @@ to see which targets are already up to date and which ones still need to catch u
 
 ## Status
 
-**v0.1 — Draft**. The spec covers all foundational layers. TaskFlow provides a compact reference app, and Todo Orbit extends coverage with localization, recurring-rule flows, custom contracts, and generated native/web targets.
+**v0.1 — Draft**. The spec covers all foundational layers. TaskFlow provides a compact reference app, Todo Orbit extends coverage with localization, recurring-rule flows, custom contracts, and generated native/web targets, and Social App demonstrates a trilingual social feed app with generated Android and web targets.
 
 ### Roadmap
 
@@ -363,7 +374,8 @@ to see which targets are already up to date and which ones still need to catch u
 - [x] CLI tool (`openuispec init` for project scaffolding + AI rules)
 - [x] MCP server for AI tool integration (`openuispec-mcp`)
 - [x] Multi-platform showcase app (`examples/todo-orbit/`)
-- [ ] More example apps (e-commerce, social, dashboard)
+- [x] Social app example (`examples/social-app/`)
+- [ ] More example apps (e-commerce, dashboard)
 
 ## Contributing
 

package/cli/init.ts

@@ -208,6 +208,8 @@ i18n:
 
 generation:
   targets: [${targetList}]
+  # extra_rules:                        # Optional: project-wide AI authoring conventions
+  #   - "Generation hint strings may start with [common], [ios], [android], or [web] to indicate scope."
   # output_dir:                          # Optional: map targets to code directories
   #   ios: "../ios-app/"                  # relative to this file
   #   android: "../android-app/"
@@ -272,10 +274,14 @@ When the openuispec MCP server is configured, AI assistants should use these too
 | \`openuispec_spec_schema\` | Get the full JSON schema for a specific spec type — exact structure, required fields, allowed values. |
 | \`openuispec_prepare\` | **Before any UI code generation.** Returns spec context, platform config, and constraints. |
 | \`openuispec_read_specs\` | Load spec file contents — the authoritative source for tokens, screens, contracts. |
-| \`openuispec_check\` | After editing spec files. Validates schema + semantics + readiness. |
+| \`openuispec_check\` | After editing spec files. Validates schema + semantics + readiness. Optional \`screens\`/\`contracts\` params scope the audit. |
 | \`openuispec_validate\` | Schema-only validation, optionally by group. |
 | \`openuispec_drift\` | Detect spec changes since last snapshot. |
 | \`openuispec_status\` | To understand cross-target state (baselines, drift, next steps). |
+| \`openuispec_get_screen\` | Get a single screen spec by name — faster than \`read_specs\` for targeted edits. |
+| \`openuispec_get_contract\` | Get a single contract spec, optionally filtered to one variant. |
+| \`openuispec_get_tokens\` | Get tokens for a specific category (color, typography, spacing, etc.). |
+| \`openuispec_get_locale\` | Get a single locale file, optionally filtered to specific keys. |
 
 ## CLI commands
 
@@ -345,6 +351,15 @@ Call these MCP tools directly. They return structured JSON with everything you n
 - Call \`openuispec_spec_schema\` with the specific type to get the full JSON schema.
 - Write the spec file following the schema exactly.
 
+**Focused getters (prefer these for incremental edits over \`read_specs\`):**
+- \`openuispec_get_screen(name)\` — single screen spec
+- \`openuispec_get_contract(name, variant?)\` — single contract, optionally one variant
+- \`openuispec_get_tokens(category)\` — single token category (color, typography, spacing, etc.)
+- \`openuispec_get_locale(locale, keys?)\` — single locale file, optionally filtered keys
+- \`openuispec_check(target, screens?, contracts?)\` — scoped audit for specific screens/contracts
+
+Use \`read_specs\` for full-project generation; use focused getters when editing one screen or contract.
+
 **Other tools:**
 - \`openuispec_status\` — cross-target summary, good starting point
 - \`openuispec_drift\` with \`explain: true\` — property-level spec changes
@@ -501,12 +516,14 @@ const EXPECTED_MCP_CONFIG = {
  * MCP config files by agent:
  *   .mcp.json              — Claude Code (project scope)
  *   .vscode/mcp.json       — VS Code / Copilot Chat
+ *   .gemini/settings.json  — Gemini CLI (if .gemini/ exists)
  *
  * All use the same { mcpServers: { openuispec: { command, args } } } shape.
  */
 const JSON_MCP_PATHS = [
   ".mcp.json",
   join(".vscode", "mcp.json"),
+  join(".gemini", "settings.json"),
 ];
 
 /** Codex uses TOML: .codex/config.toml */
@@ -542,8 +559,9 @@ function configureMcp(cwd: string, showRestart: boolean, quiet: boolean = false)
   for (const relPath of JSON_MCP_PATHS) {
     const configPath = join(cwd, relPath);
 
-    // .vscode/mcp.json: only write if .vscode/ already exists
-    if (relPath.startsWith(".vscode") && !existsSync(join(cwd, ".vscode"))) continue;
+    // Optional dirs: only write config if the parent directory already exists
+    const optionalParent = [".vscode", ".gemini"].find((d) => relPath.startsWith(d));
+    if (optionalParent && !existsSync(join(cwd, optionalParent))) continue;
 
     try {
       let config: Record<string, any> = {};

package/examples/social-app/.mcp.json

@@ -0,0 +1,10 @@
+{
+  "mcpServers": {
+    "openuispec": {
+      "command": "openuispec",
+      "args": [
+        "mcp"
+      ]
+    }
+  }
+}

package/examples/social-app/AGENTS.md

@@ -0,0 +1,114 @@
+<!-- openuispec-rules-start -->
+<!-- openuispec-rules-version: 0.1.45 -->
+# OpenUISpec — AI Assistant Rules
+# ================================
+# This project uses OpenUISpec to define UI as a semantic spec.
+# Spec files are the single source of truth for all UI across platforms.
+# Targets: "ios", "android", "web"
+
+## MANDATORY — UI work requires OpenUISpec tools
+
+When the user's request involves UI — screens, navigation, layout, tokens, flows, localization,
+or any visual/structural change — you MUST use the OpenUISpec tools before writing any code.
+
+### MCP Tools (use these when available)
+
+Call these MCP tools directly. They return structured JSON with everything you need.
+
+**Pre-generation:**
+1. Call `openuispec_prepare` with the target platform — returns spec context, platform config, constraints.
+2. Call `openuispec_read_specs` to load spec file contents. Use these as the AUTHORITATIVE source.
+3. If spec changes are needed, update spec files FIRST, then call `openuispec_check`.
+4. Generate or update the platform UI code based on the spec contents.
+
+**Post-generation (EVERY TIME after writing UI code):**
+5. Call `openuispec_check` to validate spec integrity.
+6. Call `openuispec_read_specs` for the screens/contracts you just generated code for.
+7. Audit your generated code against the spec. For each screen, verify:
+   - Every field/action in the spec has a corresponding UI element
+   - Token values (colors, spacing, radii) match exactly — no approximations
+   - Contract `must_handle` states are all implemented (loading, error, empty, etc.)
+   - Adaptive breakpoints match the spec's `size_classes`
+   - Locale keys match `$t:` references
+   - Navigation targets match flow definitions
+8. Report any real gaps found and fix them before finishing.
+
+**Creating new spec files:**
+- Call `openuispec_spec_types` to discover available spec types.
+- Call `openuispec_spec_schema` with the specific type to get the full JSON schema.
+- Write the spec file following the schema exactly.
+
+**Focused getters (prefer these for incremental edits over `read_specs`):**
+- `openuispec_get_screen(name)` — single screen spec
+- `openuispec_get_contract(name, variant?)` — single contract, optionally one variant
+- `openuispec_get_tokens(category)` — single token category (color, typography, spacing, etc.)
+- `openuispec_get_locale(locale, keys?)` — single locale file, optionally filtered keys
+- `openuispec_check(target, screens?, contracts?)` — scoped audit for specific screens/contracts
+
+Use `read_specs` for full-project generation; use focused getters when editing one screen or contract.
+
+**Other tools:**
+- `openuispec_status` — cross-target summary, good starting point
+- `openuispec_drift` with `explain: true` — property-level spec changes
+- `openuispec_validate` — schema-only validation by group
+
+### CLI fallback (when MCP is not available)
+
+If MCP tools are not available, use these CLI commands with `--json` flag:
+- `openuispec prepare --target <t> --json` — build AI-ready work bundle
+- `openuispec check --target <t> --json` — composite validation
+- `openuispec status --json` — cross-target status
+- `openuispec drift --target <t> --explain --json` — semantic drift
+- `openuispec validate [group...] --json` — schema validation
+
+### Other CLI commands
+- `openuispec init` — scaffold a new spec project
+- `openuispec drift --snapshot --target <t>` — snapshot current state (only after UI code is updated)
+- `openuispec configure-target <t>` — configure target platform stack
+- `openuispec update-rules` — update AI rules to match installed package version
+
+## Spec format reference
+
+The spec format, schemas, and generation rules are in the installed `openuispec` package.
+You MUST read the reference files before creating or editing spec files — do NOT guess the format.
+
+**Find the package:** `node_modules/openuispec/` or run `npm root -g` → `<prefix>/openuispec/`.
+**Online fallback:** `https://openuispec.rsteam.uz/llms-full.txt`
+
+**Reference files (read in order):**
+1. `README.md` — schema tables, file format, root wrapper keys
+2. `spec/openuispec-v0.1.md` — full specification
+3. `examples/taskflow/openuispec/` — complete working example
+4. `schema/` — JSON Schemas for every file type
+
+## Spec location
+- Spec root: `openuispec/` — read `openuispec/openuispec.yaml` first for actual paths.
+- Default dirs: tokens/, screens/, flows/, contracts/, platform/, locales/
+
+## When to start from spec vs platform code
+
+**Spec-first** (use `openuispec_prepare` or `openuispec prepare`):
+- Screen structure, navigation, fields, actions, validation, data binding changes
+- Token, variant, contract, flow, or localization changes
+- Changes affecting multiple platforms
+- Requests in product/UI terms
+
+**Platform-first** (skip spec tools):
+- Platform-specific polish (iOS-only, Android-only, web-only)
+- Local bug fixes that don't alter shared semantic behavior
+
+## If spec directories are empty (first-time setup)
+
+Read `spec/openuispec-v0.1.md` from the package first, then:
+1. Scan codebase for UI screens → create `openuispec/screens/<name>.yaml` as `status: stub`
+2. Extract tokens (colors, fonts, spacing) → `openuispec/tokens/`
+3. Create contract extensions → `openuispec/contracts/`
+4. Create locale files → `openuispec/locales/<locale>.json`
+5. Fill in `data_model`, `api.endpoints` in `openuispec/openuispec.yaml`
+
+## Rules
+- Do not snapshot drift unless the UI code has also been updated.
+- Do not modify generated UI without checking whether the spec must change first.
+- Do not use `configure-target --defaults` as silent approval — ask the user to confirm.
+- Always read spec format from the installed package, not from cached/memorized content.
+<!-- openuispec-rules-end -->

package/examples/social-app/CLAUDE.md

@@ -0,0 +1,114 @@
+<!-- openuispec-rules-start -->
+<!-- openuispec-rules-version: 0.1.45 -->
+# OpenUISpec — AI Assistant Rules
+# ================================
+# This project uses OpenUISpec to define UI as a semantic spec.
+# Spec files are the single source of truth for all UI across platforms.
+# Targets: "ios", "android", "web"
+
+## MANDATORY — UI work requires OpenUISpec tools
+
+When the user's request involves UI — screens, navigation, layout, tokens, flows, localization,
+or any visual/structural change — you MUST use the OpenUISpec tools before writing any code.
+
+### MCP Tools (use these when available)
+
+Call these MCP tools directly. They return structured JSON with everything you need.
+
+**Pre-generation:**
+1. Call `openuispec_prepare` with the target platform — returns spec context, platform config, constraints.
+2. Call `openuispec_read_specs` to load spec file contents. Use these as the AUTHORITATIVE source.
+3. If spec changes are needed, update spec files FIRST, then call `openuispec_check`.
+4. Generate or update the platform UI code based on the spec contents.
+
+**Post-generation (EVERY TIME after writing UI code):**
+5. Call `openuispec_check` to validate spec integrity.
+6. Call `openuispec_read_specs` for the screens/contracts you just generated code for.
+7. Audit your generated code against the spec. For each screen, verify:
+   - Every field/action in the spec has a corresponding UI element
+   - Token values (colors, spacing, radii) match exactly — no approximations
+   - Contract `must_handle` states are all implemented (loading, error, empty, etc.)
+   - Adaptive breakpoints match the spec's `size_classes`
+   - Locale keys match `$t:` references
+   - Navigation targets match flow definitions
+8. Report any real gaps found and fix them before finishing.
+
+**Creating new spec files:**
+- Call `openuispec_spec_types` to discover available spec types.
+- Call `openuispec_spec_schema` with the specific type to get the full JSON schema.
+- Write the spec file following the schema exactly.
+
+**Focused getters (prefer these for incremental edits over `read_specs`):**
+- `openuispec_get_screen(name)` — single screen spec
+- `openuispec_get_contract(name, variant?)` — single contract, optionally one variant
+- `openuispec_get_tokens(category)` — single token category (color, typography, spacing, etc.)
+- `openuispec_get_locale(locale, keys?)` — single locale file, optionally filtered keys
+- `openuispec_check(target, screens?, contracts?)` — scoped audit for specific screens/contracts
+
+Use `read_specs` for full-project generation; use focused getters when editing one screen or contract.
+
+**Other tools:**
+- `openuispec_status` — cross-target summary, good starting point
+- `openuispec_drift` with `explain: true` — property-level spec changes
+- `openuispec_validate` — schema-only validation by group
+
+### CLI fallback (when MCP is not available)
+
+If MCP tools are not available, use these CLI commands with `--json` flag:
+- `openuispec prepare --target <t> --json` — build AI-ready work bundle
+- `openuispec check --target <t> --json` — composite validation
+- `openuispec status --json` — cross-target status
+- `openuispec drift --target <t> --explain --json` — semantic drift
+- `openuispec validate [group...] --json` — schema validation
+
+### Other CLI commands
+- `openuispec init` — scaffold a new spec project
+- `openuispec drift --snapshot --target <t>` — snapshot current state (only after UI code is updated)
+- `openuispec configure-target <t>` — configure target platform stack
+- `openuispec update-rules` — update AI rules to match installed package version
+
+## Spec format reference
+
+The spec format, schemas, and generation rules are in the installed `openuispec` package.
+You MUST read the reference files before creating or editing spec files — do NOT guess the format.
+
+**Find the package:** `node_modules/openuispec/` or run `npm root -g` → `<prefix>/openuispec/`.
+**Online fallback:** `https://openuispec.rsteam.uz/llms-full.txt`
+
+**Reference files (read in order):**
+1. `README.md` — schema tables, file format, root wrapper keys
+2. `spec/openuispec-v0.1.md` — full specification
+3. `examples/taskflow/openuispec/` — complete working example
+4. `schema/` — JSON Schemas for every file type
+
+## Spec location
+- Spec root: `openuispec/` — read `openuispec/openuispec.yaml` first for actual paths.
+- Default dirs: tokens/, screens/, flows/, contracts/, platform/, locales/
+
+## When to start from spec vs platform code
+
+**Spec-first** (use `openuispec_prepare` or `openuispec prepare`):
+- Screen structure, navigation, fields, actions, validation, data binding changes
+- Token, variant, contract, flow, or localization changes
+- Changes affecting multiple platforms
+- Requests in product/UI terms
+
+**Platform-first** (skip spec tools):
+- Platform-specific polish (iOS-only, Android-only, web-only)
+- Local bug fixes that don't alter shared semantic behavior
+
+## If spec directories are empty (first-time setup)
+
+Read `spec/openuispec-v0.1.md` from the package first, then:
+1. Scan codebase for UI screens → create `openuispec/screens/<name>.yaml` as `status: stub`
+2. Extract tokens (colors, fonts, spacing) → `openuispec/tokens/`
+3. Create contract extensions → `openuispec/contracts/`
+4. Create locale files → `openuispec/locales/<locale>.json`
+5. Fill in `data_model`, `api.endpoints` in `openuispec/openuispec.yaml`
+
+## Rules
+- Do not snapshot drift unless the UI code has also been updated.
+- Do not modify generated UI without checking whether the spec must change first.
+- Do not use `configure-target --defaults` as silent approval — ask the user to confirm.
+- Always read spec format from the installed package, not from cached/memorized content.
+<!-- openuispec-rules-end -->

package/examples/social-app/README.md

@@ -0,0 +1,19 @@
+# social-app
+
+Test project for exercising the local [`openuispec`](../openuispec) checkout.
+
+## Structure
+
+- `openuispec/` contains the spec scaffold.
+- `AGENTS.md` and `CLAUDE.md` include the OpenUISpec assistant rules generated by the local CLI.
+
+## Commands
+
+```bash
+npm run validate
+npm run validate:semantic
+npm run status
+npm run openuispec -- init
+```
+
+The scripts call the local `../openuispec` repo directly, so this project can be used without installing `openuispec` globally.

package/examples/social-app/backend/.gitkeep

@@ -0,0 +1 @@
+

package/examples/social-app/generated/android/social-app/app/build.gradle.kts

@@ -0,0 +1,92 @@
+plugins {
+    alias(libs.plugins.android.application)
+    alias(libs.plugins.compose.compiler)
+    kotlin("plugin.serialization")
+}
+
+android {
+    namespace = "com.social.app"
+    compileSdk = 36
+
+    defaultConfig {
+        applicationId = "com.social.app"
+        minSdk = 26
+        targetSdk = 36
+        versionCode = 1
+        versionName = "1.0"
+
+        testInstrumentationRunner = "androidx.test.runner.AndroidJUnitRunner"
+        vectorDrawables {
+            useSupportLibrary = true
+        }
+    }
+
+    buildTypes {
+        release {
+            isMinifyEnabled = false
+            proguardFiles(
+                getDefaultProguardFile("proguard-android-optimize.txt"),
+                "proguard-rules.pro"
+            )
+        }
+    }
+    compileOptions {
+        sourceCompatibility = JavaVersion.VERSION_11
+        targetCompatibility = JavaVersion.VERSION_11
+    }
+    kotlin {
+        compilerOptions {
+            jvmTarget.set(org.jetbrains.kotlin.gradle.dsl.JvmTarget.JVM_11)
+        }
+    }
+    buildFeatures {
+        compose = true
+    }
+    packaging {
+        resources {
+            excludes += "/META-INF/{AL2.0,LGPL2.1}"
+        }
+    }
+}
+
+dependencies {
+    implementation(libs.androidx.core.ktx)
+    implementation(libs.androidx.lifecycle.runtime.ktx)
+    implementation(libs.androidx.activity.compose)
+    implementation(platform(libs.androidx.compose.bom))
+    implementation(libs.androidx.ui)
+    implementation(libs.androidx.ui.graphics)
+    implementation(libs.androidx.ui.tooling.preview)
+    implementation(libs.androidx.material3)
+    implementation(libs.androidx.material.icons.extended)
+    implementation(libs.google.material)
+    implementation(libs.coil.compose)
+    implementation(libs.coil.network)
+
+    // Decompose
+    implementation(libs.decompose)
+    implementation(libs.decompose.extensions.compose)
+    implementation("org.jetbrains.kotlinx:kotlinx-serialization-json:1.7.3")
+
+    // MVIKotlin
+    implementation(libs.mvikotlin)
+    implementation(libs.mvikotlin.main)
+    implementation(libs.mvikotlin.logging)
+    implementation("com.arkivanov.mvikotlin:mvikotlin-extensions-coroutines:4.3.0")
+
+    // Essenty
+    implementation(libs.essenty.lifecycle)
+    implementation(libs.essenty.instancekeeper)
+
+    // DataStore
+    implementation(libs.androidx.datastore.preferences)
+    implementation(libs.androidx.datastore.core)
+
+    testImplementation("junit:junit:4.13.2")
+    androidTestImplementation("androidx.test.ext:junit:1.2.1")
+    androidTestImplementation("androidx.test.espresso:espresso-core:3.6.1")
+    androidTestImplementation(platform(libs.androidx.compose.bom))
+    androidTestImplementation("androidx.compose.ui:ui-test-junit4")
+    debugImplementation(libs.androidx.ui.tooling)
+    debugImplementation("androidx.compose.ui:ui-test-manifest")
+}

package/examples/social-app/generated/android/social-app/app/src/main/AndroidManifest.xml

@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="utf-8"?>
+<manifest xmlns:android="http://schemas.android.com/apk/res/android">
+
+    <uses-permission android:name="android.permission.INTERNET" />
+
+    <application
+        android:name=".SocialAppApplication"
+        android:allowBackup="true"
+        android:icon="@mipmap/ic_launcher"
+        android:label="@string/nav_home"
+        android:roundIcon="@mipmap/ic_launcher_round"
+        android:supportsRtl="true"
+        android:theme="@style/Theme.SocialApp">
+        <activity
+            android:name=".MainActivity"
+            android:exported="true"
+            android:label="@string/nav_home"
+            android:theme="@style/Theme.SocialApp">
+            <intent-filter>
+                <action android:name="android.intent.action.MAIN" />
+                <category android:name="android.intent.category.LAUNCHER" />
+            </intent-filter>
+        </activity>
+    </application>
+
+</manifest>

package/examples/social-app/generated/android/social-app/app/src/main/java/com/social/app/AppContainer.kt

@@ -0,0 +1,20 @@
+package com.social.app
+
+import android.content.Context
+import com.arkivanov.decompose.ComponentContext
+import com.arkivanov.mvikotlin.core.store.StoreFactory
+import com.social.app.data.preferences.DataStorePreferencesRepository
+import com.social.app.data.preferences.PreferencesRepository
+import com.social.app.ui.navigation.DefaultRootComponent
+import com.social.app.ui.navigation.RootComponent
+import com.arkivanov.mvikotlin.main.store.DefaultStoreFactory
+import com.arkivanov.mvikotlin.logging.store.LoggingStoreFactory
+
+class AppContainer(
+    context: Context,
+) {
+    val preferencesRepository: PreferencesRepository = DataStorePreferencesRepository(context.applicationContext)
+    val storeFactory: StoreFactory = LoggingStoreFactory(DefaultStoreFactory())
+
+    fun createRootComponent(componentContext: ComponentContext): RootComponent = DefaultRootComponent(componentContext)
+}

package/examples/social-app/generated/android/social-app/app/src/main/java/com/social/app/MainActivity.kt

@@ -0,0 +1,35 @@
+package com.social.app
+
+import android.os.Bundle
+import androidx.activity.ComponentActivity
+import androidx.activity.compose.setContent
+import androidx.activity.enableEdgeToEdge
+import androidx.compose.runtime.collectAsState
+import androidx.compose.runtime.getValue
+import com.arkivanov.decompose.defaultComponentContext
+import com.social.app.data.preferences.AppPreferences
+import com.social.app.ui.MainShell
+import com.social.app.ui.theme.SocialAppTheme
+
+class MainActivity : ComponentActivity() {
+    override fun onCreate(savedInstanceState: Bundle?) {
+        super.onCreate(savedInstanceState)
+        val appContainer = (application as SocialAppApplication).appContainer
+        val root = appContainer.createRootComponent(defaultComponentContext())
+
+        enableEdgeToEdge()
+        setContent {
+            val preferences by appContainer.preferencesRepository.preferences.collectAsState(initial = AppPreferences())
+
+            SocialAppTheme(
+                themeMode = preferences.themeMode,
+            ) {
+                MainShell(
+                    root = root,
+                    preferencesRepository = appContainer.preferencesRepository,
+                    storeFactory = appContainer.storeFactory,
+                )
+            }
+        }
+    }
+}

package/examples/social-app/generated/android/social-app/app/src/main/java/com/social/app/SocialAppApplication.kt

@@ -0,0 +1,13 @@
+package com.social.app
+
+import android.app.Application
+
+class SocialAppApplication : Application() {
+    lateinit var appContainer: AppContainer
+        private set
+
+    override fun onCreate() {
+        super.onCreate()
+        appContainer = AppContainer(this)
+    }
+}