Studio Best Practices Applies to . Boolean Naming Use descriptive prefixes — derive from existing state rather than storing separately: - — state/identity: , , - — possession: , - — capability: , - — conditional behavior: , Extract complex conditions into named variables: Derive booleans — don't store them: Component Structure See skill for compound component and composition patterns. Keep components under 200–300 lines. Split when you see: - Multiple distinct UI sections - Complex conditional rendering - Multiple unrelated calls - Hard to understand at a glance Co-locate sub-components in th…