library-goals · diff
git:20260704.ae8efa1 to git:20261025.e0cfa7e
1 added, 1 removed. Audit A to A.
---
description: Consider project goals when changing library code
globs: packages/**
alwaysApply: false
---
# Library Goals Alignment
When editing library code in `packages/*`, read [GOALS.md](../../GOALS.md) and weigh changes against it. It is the source of truth for project priorities — do not rely on a summary of it.
- Evaluate design decisions (new APIs, abstractions, dependencies) against the goals before implementing.
- - When goals conflict for a given change (e.g. bundle size vs. performance), resolve the trade-off using the priorities expressed in GOALS.md, and note the reasoning.
+ - When goals conflict for a given change (e.g. bundle size vs. performance), resolve the trade-off using the priorities expressed in GOALS.md, and note the reasoning (in a PR, under its GOALS impact section).
- If a requested change works against the goals, say so and propose an alternative that stays aligned.