@nadicodeai/ui 0.22.0 → 1.0.0

package/skills/nadicodeai-ui/SKILL.md

@@ -40,12 +40,18 @@ Product component imports:
 
 ```tsx
 import { DashboardShell } from "@nadicodeai/ui/components/dashboard-shell";
+import { AgentCard } from "@nadicodeai/ui/components/agent-card";
+import { AgentVisual } from "@nadicodeai/ui/components/agent-visual";
 import { Thread } from "@nadicodeai/ui/agents";
 ```
 
 ## Product Components
 
-- Use `@nadicodeai/ui/agents` for Agent presentation, runtime primitives, providers, hooks, and types. Do not import assistant-ui packages directly or recreate their behavior.
+- Use `@nadicodeai/ui/agents` for assistant-ui conversation primitives, providers, hooks, runtimes, and types. It is a client-only entry; do not import assistant-ui packages directly or recreate their behavior.
+- Import Agent identity from `@nadicodeai/ui/components/agent-card` and `@nadicodeai/ui/components/agent-visual`. Direct subpaths keep the Card composition server-compatible and the animated visual at a client leaf.
+- Use `AgentVisual` with an explicit closed recipe and `registry`, `card`, or `detail` presentation; never infer or randomize identity from a free-form role. Compose it through `AgentCard` when the Agent is a recognizable content object. There is no `AgentGlyph` or `AgentRow`.
+- `Card` defaults to the resting material. Select `surface="raised"` for physically raised/selected work and `surface="plain"` for an intentional structural/auth/website escape. Do not add border, ring, or shadow classes at call sites.
+- Use `Empty scope="page|region|card"` so only the owning container draws a frame. Use `GlassControl shape="control"` for compact floating controls and `shape="bar"` for full-width header chrome, never content or modal bodies.
 - Use first-party shadcn registry source in the consuming app for generic data tables, command palettes, and chart cards; do not import a NadicodeAI package abstraction for those patterns.
 - Keep routes, data, auth, server actions, persistence, permission decisions, runtime adapters, analytics, and product-specific copy in the consuming app.
 - Fixtures must be synthetic or redacted and cover provider, model, plugin, approval, diff, terminal, installer recovery, queued, streaming, and interrupted states. Do not use generic SaaS/card-grid filler, secrets, environment values, raw terminal output, hidden reasoning, user memory, fake customers, or fake proof metrics.