openuispec 0.2.3 → 0.2.5

package/examples/social-app/generated/android/social-app/gradlew

@@ -1,25 +1,248 @@
 #!/bin/sh
 
-# Gradle Wrapper shell script
-# This is a minimal wrapper script for Gradle
-# It will download the Gradle distribution from the URL specified in gradle-wrapper.properties
-# and then execute the Gradle executable.
+#
+# Copyright © 2015 the original authors.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#      https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+# SPDX-License-Identifier: Apache-2.0
+#
 
-# For more info see https://gradle.org/docs/current/userguide/gradle_wrapper.html
+##############################################################################
+#
+#   Gradle start up script for POSIX generated by Gradle.
+#
+#   Important for running:
+#
+#   (1) You need a POSIX-compliant shell to run this script. If your /bin/sh is
+#       noncompliant, but you have some other compliant shell such as ksh or
+#       bash, then to run this script, type that shell name before the whole
+#       command line, like:
+#
+#           ksh Gradle
+#
+#       Busybox and similar reduced shells will NOT work, because this script
+#       requires all of these POSIX shell features:
+#         * functions;
+#         * expansions «$var», «${var}», «${var:-default}», «${var+SET}»,
+#           «${var#prefix}», «${var%suffix}», and «$( cmd )»;
+#         * compound commands having a testable exit status, especially «case»;
+#         * various built-in commands including «command», «set», and «ulimit».
+#
+#   Important for patching:
+#
+#   (2) This script targets any POSIX shell, so it avoids extensions provided
+#       by Bash, Ksh, etc; in particular arrays are avoided.
+#
+#       The "traditional" practice of packing multiple parameters into a
+#       space-separated string is a well documented source of bugs and security
+#       problems, so this is (mostly) avoided, by progressively accumulating
+#       options in "$@", and eventually passing that to Java.
+#
+#       Where the inherited environment variables (DEFAULT_JVM_OPTS, JAVA_OPTS,
+#       and GRADLE_OPTS) rely on word-splitting, this is performed explicitly;
+#       see the in-line comments for details.
+#
+#       There are tweaks for specific operating systems such as AIX, CygWin,
+#       Darwin, MinGW, and NonStop.
+#
+#   (3) This script is generated from the Groovy template
+#       https://github.com/gradle/gradle/blob/b5fe9efed6cae7b9f2fbdb2d380fb69af16bb752/platforms/jvm/plugins-application/src/main/resources/org/gradle/api/internal/plugins/unixStartScript.txt
+#       within the Gradle project.
+#
+#       You can find Gradle at https://github.com/gradle/gradle/.
+#
+##############################################################################
 
-if [ -f "gradle/wrapper/gradle-wrapper.properties" ]; then
-    DIST_URL=$(grep distributionUrl gradle/wrapper/gradle-wrapper.properties | cut -d'=' -f2 | sed 's/\\//g')
-else
-    echo "gradle/wrapper/gradle-wrapper.properties not found"
+# Attempt to set APP_HOME
+
+# Resolve links: $0 may be a link
+app_path=$0
+
+# Need this for daisy-chained symlinks.
+while
+    APP_HOME=${app_path%"${app_path##*/}"}  # leaves a trailing /; empty if no leading path
+    [ -h "$app_path" ]
+do
+    ls=$( ls -ld "$app_path" )
+    link=${ls#*' -> '}
+    case $link in             #(
+      /*)   app_path=$link ;; #(
+      *)    app_path=$APP_HOME$link ;;
+    esac
+done
+
+# This is normally unused
+# shellcheck disable=SC2034
+APP_BASE_NAME=${0##*/}
+# Discard cd standard output in case $CDPATH is set (https://github.com/gradle/gradle/issues/25036)
+APP_HOME=$( cd -P "${APP_HOME:-./}" > /dev/null && printf '%s\n' "$PWD" ) || exit
+
+# Use the maximum available, or set MAX_FD != -1 to use that value.
+MAX_FD=maximum
+
+warn () {
+    echo "$*"
+} >&2
+
+die () {
+    echo
+    echo "$*"
+    echo
     exit 1
+} >&2
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false
+msys=false
+darwin=false
+nonstop=false
+case "$( uname )" in                #(
+  CYGWIN* )         cygwin=true  ;; #(
+  Darwin* )         darwin=true  ;; #(
+  MSYS* | MINGW* )  msys=true    ;; #(
+  NONSTOP* )        nonstop=true ;;
+esac
+
+
+
+# Determine the Java command to use to start the JVM.
+if [ -n "$JAVA_HOME" ] ; then
+    if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
+        # IBM's JDK on AIX uses strange locations for the executables
+        JAVACMD=$JAVA_HOME/jre/sh/java
+    else
+        JAVACMD=$JAVA_HOME/bin/java
+    fi
+    if [ ! -x "$JAVACMD" ] ; then
+        die "ERROR: JAVA_HOME is set to an invalid directory: $JAVA_HOME
+
+Please set the JAVA_HOME variable in your environment to match the
+location of your Java installation."
+    fi
+else
+    JAVACMD=java
+    if ! command -v java >/dev/null 2>&1
+    then
+        die "ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.
+
+Please set the JAVA_HOME variable in your environment to match the
+location of your Java installation."
+    fi
+fi
+
+# Increase the maximum file descriptors if we can.
+if ! "$cygwin" && ! "$darwin" && ! "$nonstop" ; then
+    case $MAX_FD in #(
+      max*)
+        # In POSIX sh, ulimit -H is undefined. That's why the result is checked to see if it worked.
+        # shellcheck disable=SC2039,SC3045
+        MAX_FD=$( ulimit -H -n ) ||
+            warn "Could not query maximum file descriptor limit"
+    esac
+    case $MAX_FD in  #(
+      '' | soft) :;; #(
+      *)
+        # In POSIX sh, ulimit -n is undefined. That's why the result is checked to see if it worked.
+        # shellcheck disable=SC2039,SC3045
+        ulimit -n "$MAX_FD" ||
+            warn "Could not set maximum file descriptor limit to $MAX_FD"
+    esac
+fi
+
+# Collect all arguments for the java command, stacking in reverse order:
+#   * args from the command line
+#   * the main class name
+#   * -classpath
+#   * -D...appname settings
+#   * --module-path (only if needed)
+#   * DEFAULT_JVM_OPTS, JAVA_OPTS, and GRADLE_OPTS environment variables.
+
+# For Cygwin or MSYS, switch paths to Windows format before running java
+if "$cygwin" || "$msys" ; then
+    APP_HOME=$( cygpath --path --mixed "$APP_HOME" )
+
+    JAVACMD=$( cygpath --unix "$JAVACMD" )
+
+    # Now convert the arguments - kludge to limit ourselves to /bin/sh
+    for arg do
+        if
+            case $arg in                                #(
+              -*)   false ;;                            # don't mess with options #(
+              /?*)  t=${arg#/} t=/${t%%/*}              # looks like a POSIX filepath
+                    [ -e "$t" ] ;;                      #(
+              *)    false ;;
+            esac
+        then
+            arg=$( cygpath --path --ignore --mixed "$arg" )
+        fi
+        # Roll the args list around exactly as many times as the number of
+        # args, so each arg winds up back in the position where it started, but
+        # possibly modified.
+        #
+        # NB: a `for` loop captures its iteration list before it begins, so
+        # changing the positional parameters here affects neither the number of
+        # iterations, nor the values presented in `arg`.
+        shift                   # remove old arg
+        set -- "$@" "$arg"      # push replacement arg
+    done
+fi
+
+
+# Add default JVM options here. You can also use JAVA_OPTS and GRADLE_OPTS to pass JVM options to this script.
+DEFAULT_JVM_OPTS='-Dfile.encoding=UTF-8 "-Xmx64m" "-Xms64m"'
+
+# Collect all arguments for the java command:
+#   * DEFAULT_JVM_OPTS, JAVA_OPTS, and optsEnvironmentVar are not allowed to contain shell fragments,
+#     and any embedded shellness will be escaped.
+#   * For example: A user cannot expect ${Hostname} to be expanded, as it is an environment variable and will be
+#     treated as '${Hostname}' itself on the command line.
+
+set -- \
+        "-Dorg.gradle.appname=$APP_BASE_NAME" \
+        -jar "$APP_HOME/gradle/wrapper/gradle-wrapper.jar" \
+        "$@"
+
+# Stop when "xargs" is not available.
+if ! command -v xargs >/dev/null 2>&1
+then
+    die "xargs is not available"
 fi
 
-echo "Downloading Gradle from $DIST_URL if needed..."
-# Use gradle's own mechanism if possible, but here we just simulate.
-# In a real environment, you would use 'gradle wrapper' to generate these files.
+# Use "xargs" to parse quoted args.
+#
+# With -n1 it outputs one arg per line, with the quotes and backslashes removed.
+#
+# In Bash we could simply go:
+#
+#   readarray ARGS < <( xargs -n1 <<<"$var" ) &&
+#   set -- "${ARGS[@]}" "$@"
+#
+# but POSIX shell has neither arrays nor command substitution, so instead we
+# post-process each arg (as a line of input to sed) to backslash-escape any
+# character that might be a shell metacharacter, then use eval to reverse
+# that process (while maintaining the separation between arguments), and wrap
+# the whole thing up as a single "set" statement.
+#
+# This will of course break if any of these variables contains a newline or
+# an unmatched quote.
+#
 
-# Since I can't fully emulate the binary gradle-wrapper.jar logic here, 
-# I'll provide the script and you can run it.
-# To actually 'sync' (resolve dependencies), you need the gradle-wrapper.jar as well.
+eval "set -- $(
+        printf '%s\n' "$DEFAULT_JVM_OPTS $JAVA_OPTS $GRADLE_OPTS" |
+        xargs -n1 |
+        sed ' s~[^-[:alnum:]+,./:=@_]~\\&~g; ' |
+        tr '\n' ' '
+    )" '"$@"'
 
-echo "Warning: gradle-wrapper.jar is required in gradle/wrapper/ directory to run this script."
+exec "$JAVACMD" "$@"

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

@@ -21,3 +21,7 @@ dependencyResolutionManagement {
 
 rootProject.name = "social-app"
 include(":app")
+
+
+
+

package/examples/social-app/package.json

@@ -4,9 +4,10 @@
   "version": "0.0.0",
   "description": "OpenUISpec test project wired to the local ../openuispec checkout",
   "scripts": {
-    "openuispec": "node --import ./../openuispec/node_modules/tsx/dist/loader.mjs ./../openuispec/cli/index.ts",
-    "validate": "node --import ./../openuispec/node_modules/tsx/dist/loader.mjs ./../openuispec/cli/index.ts validate",
-    "validate:semantic": "node --import ./../openuispec/node_modules/tsx/dist/loader.mjs ./../openuispec/cli/index.ts validate semantic",
-    "status": "node --import ./../openuispec/node_modules/tsx/dist/loader.mjs ./../openuispec/cli/index.ts status"
+    "openuispec": "node --import ./../../node_modules/tsx/dist/loader.mjs ./../../cli/index.ts",
+    "validate": "node --import ./../../node_modules/tsx/dist/loader.mjs ./../../cli/index.ts validate",
+    "validate:semantic": "node --import ./../../node_modules/tsx/dist/loader.mjs ./../../cli/index.ts validate semantic",
+    "status": "node --import ./../../node_modules/tsx/dist/loader.mjs ./../../cli/index.ts status",
+    "screenshots:web": "node --import ./../../node_modules/tsx/dist/loader.mjs ./take-web-screenshots.ts"
   }
 }

package/examples/social-app/take-web-screenshots.ts

@@ -0,0 +1,97 @@
+import { mkdirSync, writeFileSync } from "node:fs";
+import { join, resolve } from "node:path";
+import { Client } from "@modelcontextprotocol/sdk/client";
+import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
+
+type ImageContent = {
+  type: "image";
+  data: string;
+  mimeType: string;
+};
+
+type TextContent = {
+  type: "text";
+  text: string;
+};
+
+type WebCapture = {
+  name: string;
+  route: string;
+};
+
+const OUTPUT_DIR = resolve("generated/web/social-app/screenshots");
+const VIEWPORT = { width: 1366, height: 900 };
+const captures: WebCapture[] = [
+  { name: "home", route: "/home" },
+  { name: "discover", route: "/discover" },
+  { name: "notifications", route: "/notifications" },
+  { name: "messages", route: "/messages" },
+  { name: "profile", route: "/profile" },
+  { name: "profile-edit", route: "/profile/edit" },
+  { name: "settings", route: "/settings" },
+  { name: "create", route: "/create" },
+  { name: "search-editorial-ui-posts", route: "/search?query=Editorial%20UI&tab=posts" },
+  { name: "post-post-1", route: "/posts/post-1" },
+  { name: "user-lina", route: "/u/user-lina" },
+  { name: "chat-conversation-1", route: "/chat/conversation-1" },
+];
+
+function getImageData(content: Array<ImageContent | TextContent>): string {
+  const image = content.find((item): item is ImageContent => item.type === "image");
+  if (!image) {
+    throw new Error("Screenshot tool did not return image data.");
+  }
+  return image.data;
+}
+
+function getText(content: Array<ImageContent | TextContent>): string | null {
+  const text = content.find((item): item is TextContent => item.type === "text");
+  return text?.text ?? null;
+}
+
+async function main() {
+  mkdirSync(OUTPUT_DIR, { recursive: true });
+
+  const transport = new StdioClientTransport({
+    command: "npm",
+    args: ["run", "openuispec", "--", "mcp"],
+    cwd: process.cwd(),
+    stderr: "inherit",
+  });
+
+  const client = new Client(
+    { name: "social-app-screenshot-runner", version: "0.1.0" },
+    { capabilities: {} },
+  );
+
+  await client.connect(transport);
+
+  try {
+    for (const capture of captures) {
+      const result = await client.callTool({
+        name: "openuispec_screenshot",
+        arguments: {
+          route: capture.route,
+          viewport: VIEWPORT,
+          wait_for: 1200,
+          full_page: true,
+        },
+      });
+
+      if (result.isError) {
+        throw new Error(`Failed to capture ${capture.route}: ${getText(result.content as Array<ImageContent | TextContent>) ?? "Unknown tool error"}`);
+      }
+
+      const outputPath = join(OUTPUT_DIR, `${capture.name}.png`);
+      writeFileSync(outputPath, Buffer.from(getImageData(result.content as Array<ImageContent | TextContent>), "base64"));
+      console.log(`saved ${outputPath}`);
+    }
+  } finally {
+    await transport.close();
+  }
+}
+
+main().catch((error) => {
+  console.error(error instanceof Error ? error.message : error);
+  process.exitCode = 1;
+});

package/examples/taskflow/.codex/config.toml

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

package/examples/taskflow/.mcp.json

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

package/examples/taskflow/AGENTS.md

@@ -1,114 +1,124 @@
 <!-- openuispec-rules-start -->
-<!-- openuispec-rules-version: 0.1.29 -->
+<!-- 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"
 
-## IMPORTANT — Read the specification before working with spec files
+## 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, file schemas, and generation rules are defined in the installed `openuispec` package.
-You MUST read the reference files listed below before creating, editing, or generating from any spec file.
-Do NOT guess the file format — skipping this step will produce invalid YAML that fails validation.
+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 in this order:**
-1. `node_modules/openuispec/` (project dependency)
-2. Run `npm root -g` → `<prefix>/openuispec/` (global install)
-3. Online: `https://openuispec.rsteam.uz/llms-full.txt` (if not installed)
+**Find the package:** `node_modules/openuispec/` or run `npm root -g` → `<prefix>/openuispec/`.
+**Online fallback:** `https://openuispec.rsteam.uz/llms-full.txt`
 
-**Reference files inside the package (read in this order):**
-1. `README.md` — schema tables, file format reference, root wrapper keys
-2. `spec/openuispec-v0.1.md` — full specification (contracts, layout, expressions, adaptive, etc.)
-3. `examples/taskflow/openuispec/` — complete working example with all file types
+**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
 
-These files are updated with each package version. Always read from the installed package,
-not from cached or memorized content, to ensure you use the latest spec.
+## Spec location
+- Spec root: `openuispec/` — read `openuispec/openuispec.yaml` first for actual paths.
+- Default dirs: tokens/, screens/, flows/, contracts/, platform/, locales/
 
-## What is OpenUISpec
-OpenUISpec is a YAML-based spec format that describes an app's UI semantically — tokens, screens, flows, and platform overrides. AI reads the spec and generates native code (SwiftUI, Compose, React). AI reads native code and updates the spec. The spec is the sync layer between platforms.
+## When to start from spec vs platform code
 
-## Spec location
-- Spec root: `openuispec/`
-- Manifest: `openuispec/openuispec.yaml` — always read this first.
-- Tokens: `openuispec/tokens/`
-- Screens: `openuispec/screens/`
-- Flows: `openuispec/flows/`
-- Contracts: `openuispec/contracts/`
-- Platform: `openuispec/platform/`
-- Locales: `openuispec/locales/`
+**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
 
-**Note:** These are the default paths. Actual paths are in `includes:` in `openuispec.yaml` and may use relative paths. Always read `openuispec.yaml` to find the real directories.
+**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)
-This means the project has existing UI code but hasn't been specced yet. Your job:
-
-1. **Read the spec first** — find and read `spec/openuispec-v0.1.md` from the installed package.
-2. **Find existing screens** — scan the codebase for UI screen files.
-3. **Create stubs** — for each screen, create `openuispec/screens/<name>.yaml` with:
-   ```yaml
-   screen_name:
-     semantic: "Brief description of what this screen does"
-     status: stub
-     layout:
-       type: scroll_vertical
-   ```
-4. **Extract tokens** — scan for colors, fonts, spacing and create files in `openuispec/tokens/`.
-5. **Update the manifest** — fill in `data_model`, `api.endpoints`, and `generation.code_roots.backend` in `openuispec/openuispec.yaml`.
-
-## OpenUISpec Source Of Truth
-
-OpenUISpec spec files are the primary source of truth for UI behavior across platforms.
-
-### Start from spec when:
-- the request changes screen structure
-- the request changes navigation
-- the request changes fields, actions, validation, or data binding
-- the request changes tokens, variants, contracts, flows, or localization
-- the request affects more than one platform
-- the request is phrased in product/UI terms rather than platform-code terms
-
-Spec-first workflow:
-1. Read `openuispec/openuispec.yaml` and the relevant spec files first.
-2. Update the spec first.
-3. Update the affected generated/native UI code to match the spec.
-4. Run `openuispec validate`.
-5. Run `openuispec validate semantic`.
-6. Run `openuispec drift --target <target> --explain` to inspect semantic changes since that target's baseline.
-7. Run `openuispec prepare --target <target>` to build the target work bundle for that target. In `bootstrap` mode it provides first-generation constraints; in `update` mode it provides drift-based update scope.
-   If the target stack was filled from defaults, stop and ask the user to confirm or change it before implementation.
-8. Verify the affected UI targets build/run if possible.
-9. Only then run `openuispec drift --snapshot --target <target>` for affected targets, after that target output directory exists.
-10. Run `openuispec drift --target <target> --explain` again to confirm no spec changes remain for that target.
-11. Use `openuispec status` to see which other targets are still behind the updated spec.
-
-### Start from platform code when:
-- the change is platform-specific polish
-- the change is a local bug fix that does not alter shared semantic behavior
-- the request explicitly asks for an iOS-only, Android-only, or web-only adjustment
-
-Platform-first workflow:
-1. Update native/platform code.
-2. If the change affects shared semantics, sync the spec afterward.
-3. If the change is intentionally platform-specific, document it in `platform/*.yaml` when appropriate.
-
-### Never do this:
-- Do not snapshot drift immediately after changing spec unless the UI code has also been updated.
-- Do not treat `openuispec drift` as proof that generated UI matches the spec.
-- Do not skip `--explain` / `prepare` when another platform needs to catch up with shared spec changes.
-- Do not modify generated UI without checking whether the spec must change first.
-- Do not use `configure-target --defaults` as silent approval for implementation. Ask the user to confirm the stack first.
 
-## CLI commands
-- `openuispec init` — scaffold a new spec project
-- `openuispec validate [group...]` — validate spec files against schemas
-- `openuispec validate semantic` — run semantic cross-reference linting
-- `openuispec drift --target <t>` — check for spec drift
-- `openuispec drift --target <t> --explain` — explain semantic spec drift since the target baseline
-- `openuispec drift --snapshot --target <t>` — snapshot current state after the target output exists
-- `openuispec prepare --target <t>` — build the target work bundle and check whether stack confirmation is still pending
-- `openuispec status` — show cross-target baseline/drift status
-- `openuispec update-rules` — update AI rules to match installed package version
-- `openuispec drift --all` — include stubs in drift check
+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 -->