react-native-vibe-spec

简体中文

React Native spec programming for Codex through /rns.

react-native-vibe-spec is a command workflow, not an app boilerplate. It gives Codex a React Native-specific specification protocol so a request like /rns build phone login turns into proposal, spec, design, tasks, verification, and archive before code becomes the center of gravity.

Core Idea

The product entrypoint is /rns.

/rns propose phone login
/rns plan auth-login
/rns apply auth-login
/rns verify auth-login
/rns archive auth-login

The CLI exists to install and maintain the local workflow files that Codex reads:

.rns/
  project.md
  commands/rns.md
  rules/
  changes/
  specs/
  archive/

Install In A Project

npx react-native-vibe-spec init

This creates .rns/ and installs a Codex command at .codex/commands/rns.md.

To install only the Codex command:

npx react-native-vibe-spec install codex

Daily Workflow

Create a change:

npx react-native-vibe-spec propose auth-login

This creates:

.rns/changes/auth-login/
  proposal.md
  spec.md
  design.md
  tasks.md
  acceptance.md

Validate workflow structure:

npx react-native-vibe-spec validate
npx react-native-vibe-spec validate auth-login --json

Archive completed work:

npx react-native-vibe-spec archive auth-login

Check status:

npx react-native-vibe-spec status

What /rns Enforces

Every React Native change should make these decisions explicit:

• iOS, Android, and optional web behavior
• Navigation and deep links
• Loading, error, empty, offline, and permission-denied states
• Data contracts and network boundaries
• State owner, mutation boundary, read boundary, persistence, reset, and migration
• Secure storage, token handling, logging, permissions, and bundled-secret boundaries
• Unit, integration, E2E, accessibility, and security tests when relevant
• Release, rollback, monitoring, and store-review impact

CLI

rnvibe init [--force] [--codex=false]
rnvibe install codex [--force]
rnvibe propose <idea> [--force]
rnvibe validate [change] [--json]
rnvibe archive <change> [--force]
rnvibe status

validate --json is deterministic and CI-friendly. It reports missing workflow files, missing change files, TODO counts, and unchecked tasks.

Repository Map

react-native-vibe-spec/
  packages/
    core/      /rns workflow engine
    cli/       rnvibe command
  commands/   source command docs
  rules/      React Native workflow rules
  examples/   sample specs and workflows

Positioning

react-native-vibe-spec is:

• A React Native-specific spec programming workflow for Codex
• A local .rns/ change management convention
• A small CLI that installs, validates, and archives workflow artifacts

It is not:

• A React Native starter app
• A general-purpose project readiness scorer
• A prompt collection without files and validation

Slogan

Use /rns. Spec the React Native change before Codex writes it.