1) Naming conventions
Current UI kit (Review screen)
- Shadow atoms are named:
shadow-none, shadow-sm, shadow-md, shadow-lg, shadow-xl, shadow-2xl
DaisyUI
- Uses Tailwind’s shadow utilities directly (same naming family).
Direct takeaway
- Shadow naming in your system is already aligned with Tailwind/DaisyUI naming style. This part does not look like a mismatch.
2) Reusability in components
Current UI kit
- Since the shadow atoms are already discrete (and named like Tailwind), they are naturally reusable across components.
- The open question is not naming, it is whether component specs consistently reference these shadow names versus hardcoded one-off shadow values.
DaisyUI
- Also expects reuse via
shadow-* utilities.
Direct takeaway
- Structurally, your shadows are already set up in the same reusable way DaisyUI expects.
3) Missing elements (relative to DaisyUI/Tailwind defaults)
This is the one place where there is a concrete “missing” relative to Tailwind’s standard set.
Tailwind default shadows include shadow (the base default), and shadow-inner in addition to the sizes.