Getting StartedOwnable model, workflow, and first local install 2
LayoutInstallable layout wrappers with local source ownership 6
OverlayInstallable overlay wrappers with local source ownership 3
FeedbackInstallable feedback wrappers with local source ownership 5
FormInstallable form components 11
UtilityInstallable utility wrappers with local source ownership 6
NavigationInstallable navigation components 6
ToolingCLI and registry contracts 2
ReleasePublishing and workflow structure for the ownable surface 1

Quick Start

The shortest path is: inspect the supported surface, add one component, and review the local files written into your app.

1. List the supported surface

pnpm dlx tailng list

This is the authoritative current ownable surface for the package version you are using.

2. Add a component

pnpm dlx tailng add button --cwd apps/my-app

The CLI resolves aliases, validates the target directory, writes the registry files, and prints the import hint for the generated component.

3. Review the generated files

apps/my-app/src/app/tailng-ui/button/
  tng-press-primitive.ts
  tng-button.ts
  tng-button.html
  tng-button.css
  index.ts

These files are now owned by your app. TailNG does not manage later edits inside that folder.

4. Edit locally

From this point forward, treat the generated files like application code: refactor them, review them, theme them, and test them in the same workflow as the rest of your product.