delacour 0.1.0-alpha.3 → 0.1.0-alpha.5

package/README.md

@@ -5,10 +5,13 @@ repository — you own `button.tsx` and can edit it, rather than waiting for a
 release.
 
 ```bash
-bunx delacour@alpha init
 bunx delacour@alpha add button
 ```
 
+That is the whole install. `add` sets the project up on its first run — config, Metro, the Tailwind
+globs, the theme and the root provider — and then copies the component in. Reach for `init`
+directly only to choose where the components live; see [Where components go](#where-components-go).
+
 ## Why not a component package
 
 Installing `@some/ui-kit` means every change to a button is someone else's
@@ -27,20 +30,22 @@ Unlike shadcn, the target is Expo, which changes real things:
   `node_modules` symlink a monorepo creates, and a missed glob strips every
   class from a release build without erroring.
 - **`delacour doctor`** checks all of it, plus New Architecture, path aliases,
-  `GestureHandlerRootView`, whether anything actually imports the CSS entry, and duplicate copies
-  of a native module.
+  `GestureHandlerRootView`, whether anything actually imports the CSS entry, a competing Tailwind
+  transform (NativeWind wraps Metro too), and duplicate copies of a native module.
 
 ## Commands
 
 | | |
 |---|---|
-| `init [components...]` | Write `native-components.json`, wire up Metro and the CSS entry, add the theme |
-| `add <components...>` | Copy components and everything they need, and say what to install |
+| `add <components...>` | Copy components and everything they need, and say what to install. Sets the project up first if it has none |
+| `init [components...]` | Do that setup deliberately — choose the source directory, or a shared package |
 | `list` / `search <q>` | Browse the registry |
 | `view <name>` | One item: its files, what it pulls in, what it installs |
 | `diff [name]` | What has changed upstream since you copied it |
 | `doctor` | Check this app is wired up correctly |
 | `info` | The resolved config and what was detected |
+| `skills` | Install the agent skill into Claude Code, Cursor, OpenCode or Codex |
+| `mcp` | Run as an MCP server, so an agent can browse and add components |
 
 Every registry-reading command takes `--registry <url>` (a URL,
 `github:owner/repo`, or a local path), `--ref <git-ref>`, `--offline`, and
@@ -153,7 +158,7 @@ a JS reload alone will red-box. `add` says so at the point it becomes true.
 ## Working on this package
 
 ```bash
-bun run registry:build   # rebuild registry/ from packages/native-ui
+bun run registry:build   # rebuild registry/ from packages/react-native-ui
 bun test                 # unit + end-to-end against the local registry
 bun run verify:expo      # scaffold a real Expo app, add everything, typecheck it
 bun run build            # bundle dist/index.js
@@ -221,12 +226,14 @@ watching the check fire.
 `--all` adds components and what they pull in, so the run also names the standalone utilities
 explicitly — a verification pass has to cover the whole registry, not most of it.
 
-The registry is **derived** from `packages/native-ui/src` — one item per
+The registry is **derived** from `packages/react-native-ui/src` — one item per
 component folder, dependencies read off the imports. There is no `registry.json`
 to maintain, and the builder throws rather than guessing: an unclassified npm
 import or a component folder without an `index.ts` fails the build.
 
-It writes three things: `registry.json` (the index), `r/<name>.json` (one item,
-naming its files) and `files/<namespace>/<target>` (the files themselves). An
-item references its files rather than inlining them, so a component's diff is
-the TypeScript that changed rather than a JSON string nobody can read.
+It writes `registry.json` (the index), `r/<name>.json` (one item per component,
+naming its files) and the three JSON schemas. It writes **no copy of the
+source**: an item names the library's own file — `packages/react-native-ui/src/components/button/button.tsx` —
+and the client fetches it at the same ref the item came from, so the two cannot
+disagree. A component's diff is therefore the TypeScript that changed rather
+than a JSON string nobody can read.