openuispec 0.2.9 → 0.2.11

package/examples/taskflow/generated/web/TaskFlow/src/utils.ts

@@ -1,78 +0,0 @@
-import type { Filter, Project, Task } from "./types";
-
-export function matchesFilter(task: Task, filter: Filter) {
-  const due = task.dueDate ? new Date(task.dueDate) : null;
-  const today = new Date();
-  today.setHours(0, 0, 0, 0);
-  if (filter === "all") return true;
-  if (filter === "done") return task.status === "done";
-  if (filter === "today") return Boolean(due && due.toDateString() === today.toDateString() && task.status !== "done");
-  return Boolean(due && due > today && task.status !== "done");
-}
-
-export function matchesQuery(task: Task, projects: Project[], query: string) {
-  if (!query.trim()) return true;
-  const projectName = projects.find((project) => project.id === task.projectId)?.name ?? "";
-  return [task.title, task.description ?? "", projectName, task.tags.join(" ")]
-    .join(" ")
-    .toLowerCase()
-    .includes(query.toLowerCase());
-}
-
-export function buildCounts(tasks: Task[]) {
-  return {
-    all: tasks.length,
-    today: tasks.filter((task) => matchesFilter(task, "today")).length,
-    upcoming: tasks.filter((task) => matchesFilter(task, "upcoming")).length,
-    done: tasks.filter((task) => task.status === "done").length
-  };
-}
-
-export function parseTags(value: string) {
-  return value
-    .split(",")
-    .map((item) => item.trim())
-    .filter(Boolean);
-}
-
-export function initials(name: string) {
-  return name
-    .split(" ")
-    .slice(0, 2)
-    .map((part) => part[0]?.toUpperCase() ?? "")
-    .join("");
-}
-
-export function relativeDate(value: string) {
-  const date = new Date(value);
-  const today = new Date();
-  today.setHours(0, 0, 0, 0);
-  const target = new Date(date);
-  target.setHours(0, 0, 0, 0);
-  const diff = Math.round((target.getTime() - today.getTime()) / 86400000);
-  if (diff === 0) return "Today";
-  if (diff === 1) return "Tomorrow";
-  if (diff === -1) return "Yesterday";
-  if (diff > 1) return `in ${diff} days`;
-  return `${Math.abs(diff)} days ago`;
-}
-
-export function formatDate(value: string) {
-  return new Date(value).toLocaleDateString("en-US", {
-    month: "short",
-    day: "numeric",
-    year: "numeric"
-  });
-}
-
-export function addDays(days: number) {
-  const next = new Date();
-  next.setDate(next.getDate() + days);
-  return next.toISOString();
-}
-
-export function daysAgo(days: number) {
-  const previous = new Date();
-  previous.setDate(previous.getDate() - days);
-  return previous.toISOString();
-}

package/examples/taskflow/generated/web/TaskFlow/tsconfig.json

@@ -1,21 +0,0 @@
-{
-  "compilerOptions": {
-    "target": "ES2020",
-    "useDefineForClassFields": true,
-    "lib": ["ES2020", "DOM", "DOM.Iterable"],
-    "allowJs": false,
-    "skipLibCheck": true,
-    "esModuleInterop": true,
-    "allowSyntheticDefaultImports": true,
-    "strict": true,
-    "forceConsistentCasingInFileNames": true,
-    "module": "ESNext",
-    "moduleResolution": "Node",
-    "resolveJsonModule": true,
-    "isolatedModules": true,
-    "noEmit": true,
-    "jsx": "react-jsx"
-  },
-  "include": ["src"],
-  "references": []
-}

package/examples/taskflow/generated/web/TaskFlow/vite.config.ts

@@ -1,6 +0,0 @@
-import { defineConfig } from "vite";
-import react from "@vitejs/plugin-react";
-
-export default defineConfig({
-  plugins: [react()]
-});

package/examples/todo-orbit/.codex/config.toml

@@ -1,4 +0,0 @@
-
-[mcp_servers.openuispec]
-command = "openuispec"
-args = ["mcp"]

package/examples/todo-orbit/.mcp.json

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

package/examples/todo-orbit/AGENTS.md

@@ -1,124 +0,0 @@
-<!-- openuispec-rules-start -->
-<!-- openuispec-rules-version: 0.2.4 -->
-# 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
-- `openuispec read-specs [paths...]` — read spec file contents
-- `openuispec get-screen <name>` — get a single screen spec
-- `openuispec get-contract <name> [--variant v]` — get a contract spec
-- `openuispec get-tokens <category>` — get tokens for a category
-- `openuispec get-locale <locale> [--keys k1,k2]` — get a locale file
-- `openuispec spec-types` — list available spec types
-- `openuispec spec-schema <type>` — get JSON schema for a spec type
-- `openuispec screenshot --route /path` — screenshot the web app
-- `openuispec screenshot-android [--project-dir path]` — screenshot Android app
-- `openuispec screenshot-ios [--project-dir path]` — screenshot iOS app
-
-### 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/todo-orbit/CLAUDE.md

@@ -1,124 +0,0 @@
-<!-- openuispec-rules-start -->
-<!-- openuispec-rules-version: 0.2.4 -->
-# 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
-- `openuispec read-specs [paths...]` — read spec file contents
-- `openuispec get-screen <name>` — get a single screen spec
-- `openuispec get-contract <name> [--variant v]` — get a contract spec
-- `openuispec get-tokens <category>` — get tokens for a category
-- `openuispec get-locale <locale> [--keys k1,k2]` — get a locale file
-- `openuispec spec-types` — list available spec types
-- `openuispec spec-schema <type>` — get JSON schema for a spec type
-- `openuispec screenshot --route /path` — screenshot the web app
-- `openuispec screenshot-android [--project-dir path]` — screenshot Android app
-- `openuispec screenshot-ios [--project-dir path]` — screenshot iOS app
-
-### 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/todo-orbit/backend/.gitkeep

@@ -1 +0,0 @@
-

package/examples/todo-orbit/generated/android/Todo Orbit/README.md

@@ -1,14 +0,0 @@
-# Todo Orbit Android
-
-Generated Android target for the OpenUISpec Todo Orbit project.
-
-## Structure
-
-- `app/` — Android application module
-- `app/src/main/java/uz/rsteam/todoorbit/MainActivity.kt` — Compose app scaffold
-- `app/src/main/java/uz/rsteam/todoorbit/ui/theme/TodoOrbitTheme.kt` — light/dark theme mapped from spec tokens
-
-## Notes
-
-- The project models the current OpenUISpec surface: tasks, analytics, settings, create/edit flows, recurring rule flow, bilingual strings, theme switching, and the two custom contracts (`x_task_trend_chart`, `x_schedule_preview`).
-- Build verification was limited by the local environment: `gradle`, `kotlinc`, and `sdkmanager` were not installed in the workspace session, so this target was generated as a credible Gradle/Compose project but not compiled here.

package/examples/todo-orbit/generated/android/Todo Orbit/app/build.gradle.kts

@@ -1,58 +0,0 @@
-plugins {
-    id("com.android.application")
-    id("org.jetbrains.kotlin.plugin.compose")
-}
-
-android {
-    namespace = "uz.rsteam.todoorbit"
-    compileSdk = 36
-
-    defaultConfig {
-        applicationId = "uz.rsteam.todoorbit"
-        minSdk = 26
-        targetSdk = 35
-        versionCode = 1
-        versionName = "0.1.0"
-    }
-
-    buildTypes {
-        release {
-            isMinifyEnabled = false
-            proguardFiles(
-                getDefaultProguardFile("proguard-android-optimize.txt"),
-                "proguard-rules.pro"
-            )
-        }
-    }
-
-    compileOptions {
-        sourceCompatibility = JavaVersion.VERSION_17
-        targetCompatibility = JavaVersion.VERSION_17
-    }
-
-    buildFeatures {
-        compose = true
-    }
-
-    packaging {
-        resources {
-            excludes += "/META-INF/{AL2.0,LGPL2.1}"
-        }
-    }
-}
-
-dependencies {
-    implementation(platform("androidx.compose:compose-bom:2026.03.00"))
-    implementation("androidx.appcompat:appcompat:1.7.1")
-    implementation("androidx.core:core-ktx:1.16.0")
-    implementation("androidx.activity:activity-compose:1.11.0")
-    implementation("androidx.lifecycle:lifecycle-runtime-ktx:2.9.4")
-    implementation("androidx.compose.ui:ui")
-    implementation("androidx.compose.ui:ui-tooling-preview")
-    implementation("androidx.compose.foundation:foundation")
-    implementation("androidx.compose.material3:material3")
-    implementation("androidx.compose.material:material-icons-extended")
-
-    debugImplementation("androidx.compose.ui:ui-tooling")
-    debugImplementation("androidx.compose.ui:ui-test-manifest")
-}

package/examples/todo-orbit/generated/android/Todo Orbit/app/proguard-rules.pro

@@ -1 +0,0 @@
-# Intentionally minimal for generated demo output.

package/examples/todo-orbit/generated/android/Todo Orbit/app/src/main/AndroidManifest.xml

@@ -1,20 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<manifest xmlns:android="http://schemas.android.com/apk/res/android">
-
-    <application
-        android:allowBackup="true"
-        android:label="@string/app_name"
-        android:supportsRtl="true"
-        android:theme="@android:style/Theme.Material.Light.NoActionBar">
-        <activity
-            android:name=".MainActivity"
-            android:exported="true">
-            <intent-filter>
-                <action android:name="android.intent.action.MAIN" />
-
-                <category android:name="android.intent.category.LAUNCHER" />
-            </intent-filter>
-        </activity>
-    </application>
-
-</manifest>

package/examples/todo-orbit/generated/android/Todo Orbit/app/src/main/java/uz/rsteam/todoorbit/MainActivity.kt

@@ -1,14 +0,0 @@
-package uz.rsteam.todoorbit
-
-import android.os.Bundle
-import androidx.activity.ComponentActivity
-import androidx.activity.compose.setContent
-
-class MainActivity : ComponentActivity() {
-    override fun onCreate(savedInstanceState: Bundle?) {
-        super.onCreate(savedInstanceState)
-        setContent {
-            TodoOrbitGeneratedApp()
-        }
-    }
-}