File Tree

A nested file and folder tree with expand/collapse.

Data Display custom custom Tailwind component
AI Prompt
Create a File Tree component for an AI-generated interface using shadcn-style composition. Use custom Tailwind component as the implementation base. The component should support default, muted, outline, ghost, destructive variants and default, hover, focus-visible, active, disabled, loading states. Include clear anatomy for Root, Folder, File, Icon, Indent. Keep the visual language black, white, and gray with subtle borders, practical spacing, accessible focus states, and no decorative noise.
Negative Prompt
Do not invent a custom component API when custom Tailwind component already covers the base behavior. Avoid random gradients, oversized radii, unclear disabled states, missing labels, icon-only controls without accessible names, and variants that change layout unexpectedly.
Implementation Notes
Base: custom Tailwind component
Primitive: none
Tailwind: Use shadcn tokens for background, border, ring, muted text, radius, and state variants. Keep component-specific classes local and copyable.
Dependency: No extra primitive required beyond React and Tailwind.
Tokens
{
  "id": "file-tree",
  "category": "components",
  "trigger": "user interaction",
  "target": "file tree",
  "feeling": [
    "polished",
    "practical",
    "precise"
  ],
  "palette": [
    "black",
    "white",
    "gray"
  ],
  "radius": "8px or less",
  "border": "1px solid rgba(237, 237, 236, 0.14)",
  "background": "neutral surface with subtle contrast",
  "foreground": "high-contrast text",
  "mutedForeground": "secondary text at 68-74% contrast",
  "focusRing": "2px neutral ring with offset",
  "shadow": "soft elevation only when interaction needs tactility",
  "motionDuration": "120ms-220ms"
}
copy-ready details

Component spec

component

Overview

A nested file and folder tree with expand/collapse. This entry is written as a registry-ready component spec: useful to humans, copyable by AI tools, and easy to map to a future shadcn registry item.

structure

Anatomy

  • Root
  • Folder
  • File
  • Icon
  • Indent
visual API

Variants

  • default
  • muted
  • outline
  • ghost
  • destructive
behavior

States

  • default
  • hover
  • focus-visible
  • active
  • disabled
  • loading
tokens

Styling tokens

radius8px or less
border1px solid rgba(237, 237, 236, 0.14)
backgroundneutral surface with subtle contrast
foregroundhigh-contrast text
mutedForegroundsecondary text at 68-74% contrast
focusRing2px neutral ring with offset
shadowsoft elevation only when interaction needs tactility
motionDuration120ms-220ms
a11y

Accessibility notes

  • Use semantic HTML or the matching Radix primitive before custom roles.
  • Keep focus-visible states obvious without adding decorative glow.
  • Ensure icon-only controls have an accessible label.
  • Do not rely on color alone for state or validation.
custom Tailwind component

shadcn implementation

No extra primitive required beyond React and Tailwind.

Use shadcn tokens for background, border, ring, muted text, radius, and state variants. Keep component-specific classes local and copyable.

optional adapter

HeroUI mapping

File Tree can map to a HeroUI component only as an optional adapter. Keep UnBoring copy and token language framework-neutral.

Usage notes

Short guidance for humans and AI tools before copying the component.

File Tree helps teams a nested file and folder tree with expand/collapse. It should feel like a reusable product primitive, not a one-off decoration.

Start from custom Tailwind component. No extra primitive required beyond React and Tailwind. Keep variants token-driven and keep states predictable.

Do not invent a custom component API when custom Tailwind component already covers the base behavior. Avoid random gradients, oversized radii, unclear disabled states, missing labels, icon-only controls without accessible names, and variants that change layout unexpectedly.