Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a small but real component library (5-8 components) packaged for consumption. Components must be ACCESSIBLE by default (semantic HTML, ARIA only where needed, full keyboard + focus management — consider building on a headless base like Radix/React Aria). Document everything in STORYBOOK with controls, props tables, and usage guidelines. Set up the build (bundling with TS types, ESM/CJS, tree-shaking) and PUBLISH to npm (or a private registry) with semantic versioning and a changelog. Add accessibility tests (axe/jest-axe) in CI.
Components accessible by default (keyboard/focus/ARIA correct); a11y tested in CI (axe); often built on a headless base.
Storybook with stories, controls, props tables, and usage guidelines for every component.
Bundled with TS types + ESM/CJS + tree-shaking; published with semantic versioning and a changelog.
Consistent token usage; unit tests for component logic; clean APIs.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A documented, accessible, published component library ## Goal Build a small but real component library (5-8 components) packaged for consumption. Components must be ACCESSIBLE by default (semantic HTML, ARIA only where needed, full keyboard + focus management — consider building on a headless base like Radix/React Aria). Document everything in STORYBOOK with controls, props tables, and usage guidelines. Set up the build (bundling with TS types, ESM/CJS, tree-shaking) and PUBLISH to npm (or a private registry) with semantic versioning and a changelog. Add accessibility tests (axe/jest-axe) in CI. ## Acceptance criteria - [ ] Accessibility: Components accessible by default (keyboard/focus/ARIA correct); a11y tested in CI (axe); often built on a headless base. - [ ] Documentation: Storybook with stories, controls, props tables, and usage guidelines for every component. - [ ] Packaging & versioning: Bundled with TS types + ESM/CJS + tree-shaking; published with semantic versioning and a changelog. - [ ] Quality: Consistent token usage; unit tests for component logic; clean APIs. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.