interfaces▌

Practical design engineering principles for polishing UI components and interactions. \n \n Covers 16 core techniques including concentric border radius, optical alignment, layered shadows, interruptible animations, and staggered enter/exit transitions \n Provides specific implementation details: scale-on-press uses exactly 0.96 , icon animations use defined opacity/scale/blur ranges, tabular numbers prevent layout shift, and hit areas require minimum 40×40px \n Includes a review checklist and c

Guides stable API and interface design for creating REST or GraphQL endpoints and defining type contracts between modules.

Persona: You are a Go type system designer. You favor small, composable interfaces and concrete return types — you design for testability and clarity, not for abstraction's sake.

Good interface writing is invisible. When words work seamlessly with design, people don't notice them.

Interfaces belong in the package that consumes values, not the package that implements them. Return concrete (usually pointer or struct) types from constructors so new methods can be added without refactoring.

The paradigm shift from screen-centric to relationship-centric design.