Astryx.

The README's own top callout reads: '**Building with an AI agent?** Run `npx astryx init` first.' Run literally as written (bare `npx astryx`, before @astryxdesign/cli is a project dependency), this resolves to a completely different, unaffiliated public npm package named `astryx` (verified on the public npm registry: a single unrelated maintainer, unpacked size 424 bytes, no `bin` entry at all, so it is not even a runnable CLI). The correct scoped form, `npx @astryxdesign/cli init`, appears only later, inside the CLI's own runtime output (the redirect banner printed by docs.mjs), never at the point in the README where the bare instruction is given. This recipe does not run either form; see the last entry below for why.

The README's 'Component Docs' section instructs exactly this for full component documentation: `node node_modules/@astryxdesign/core/docs.mjs Button`. Running that command exactly as documented, immediately after installing the package per the Quick Start, does not print component docs. It always prints a fixed redirect banner instructing you to install and run the CLI instead, regardless of whether @astryxdesign/cli happens to be installed. The documented command never succeeds at its own stated purpose.

The 'Vite' quick-start section is two lines: the install command, then 'Same CSS imports and providers as above. No build plugins needed; Astryx ships pre-built.' The providers.tsx example given 'above' (in the immediately preceding Next.js section) imports `Link from 'next/link'` and opens with `'use client'`, both Next.js-specific and absent from a Vite project (there is no next/link module and no server/client component split to declare). Followed literally, the Vite section point at code that cannot compile outside Next.js. In practice, Astryx's Link component falls back to a plain `<a>` element when no LinkProvider is supplied (confirmed by reading the Link source directly (node_modules/@astryxdesign/core/src/Link/: LinkContext.ts defaults the context to null and useLinkComponent.ts resolves `as ?? ctx?.component ?? 'a'`, so with no provider it falls back to a native anchor); the README never states this default exists), so this recipe's providers.tsx omits LinkProvider entirely for the router-less Vite scaffold. That fallback behavior was filled in from source, not from documentation, because the docs are silent on it.

@astryxdesign/core's package.json declares `@stylexjs/stylex: ^0.19.0` as a required peerDependency, but the Quick Start's pre-built CSS/JS path (the one this recipe follows, for both Next.js and Vite, explicitly billed as needing 'no build plugins, no PostCSS, no Babel config') never mentions installing it and never uses it at runtime (grepped dist/index.js for every occurrence of 'stylex': none). Modern npm (7 and later, used here) auto-installs unmet peer dependencies by default, so @stylexjs/stylex 0.19.0 was silently pulled into node_modules anyway with no error; an npm configuration that does not auto-install peers, or an older npm major version, would instead surface an ERESOLVE-style peer-dependency warning about a package the documented install path does not actually need.