What problem does it solve?
This skill solves the common problem of over-testing in bklit-ui, where teams waste time writing brittle, low-signal tests that fail to catch real user-facing regressions and add unnecessary maintenance overhead.
Core Features & Use Cases
- Clear testing guardrails: Explicit guidance on what to test (pure functions, formatters, edge cases) and what to skip (component smoke tests, third-party library behavior, trivial wrappers) to avoid wasted effort.
- Repo-specific conventions: Standardized patterns for test runner setup, file placement, and test structure that align with bklit-ui's existing codebase.
- Decision support: A pre-writing checklist to quickly evaluate if a test is worth implementing, ensuring tests only lock in behavior that is easy to break silently.
- Use Case: When adding a new chart formatter function, this skill guides you to write a focused equivalence test instead of brittle component render tests that break on minor UI changes.
Quick Start
Use the unit-tests skill to evaluate if a new utility function in bklit-ui needs a unit test and follow the repo's standard test pattern to implement it correctly.