Agent discovery

Give a coding agent the llms.txt index to find the guides and registry endpoints. Registry JSON contains the source files an agent needs to inspect before installing components.

Read the catalog

Fetch /r/index.json for item names, types, descriptions, and categories. Fetch /r/{name}.json for an item's files, npm dependencies, and registryDependencies. The catalog is discovery metadata; the individual item payloads contain the installable source.

Start with text.json for a primitive or invoice-minimal.json for a document block. Inspect the files and dependency graph, then choose only the items your document needs. shadcn-vue installs the required registry dependencies with each item.

Install through shadcn-vue

In a Vue project with shadcn-vue initialized, add the namespace to components.json. Keep the existing configuration and registries. This example uses the host serving this page.

components.json

{
  "registries": {
    "@pdfcn-vue": "https://pdfcn-vue.vercel.app/r/{name}.json"
  }
}

Terminal

npx shadcn-vue@latest add @pdfcn-vue/text
npx shadcn-vue@latest add @pdfcn-vue/invoice-minimal

The CLI copies source into your project. Review the resulting changes and run your project's checks. The registry guide explains target paths and hosting.

Choose a rendering path

PDF components use Forme's document tree and theme tokens. Follow the rendering guide for browser or Node PDF output and the Nuxt guide for compiler configuration and client boundaries. Use the Takumi guide for HTML-based PDF rendering. For PDF requirements, read the PDF standards and fillable forms guides before choosing document options.