Repository navigation
Releases
Design Rover 0.5.1
Design Rover 0.5.1
Find the full documentation from the npm package page.
- The package homepage now points to the Design Rover documentation site.
- The published README links to quick start, MCP setup, CLI reference, watch mode and support boundaries.
- CLI behavior and approval rules are unchanged.
Design Rover 0.5.0
Design Rover 0.5.0
Keep the component map updated while editing with bunx design-rover watch.
- Watch refreshes observed component and token inventory after supported source changes settle. It polls complete file contents and the source manifest, covering additions, edits, deletions and renames.
- Approvals remain explicit. Approved or human-annotated records, rejected knowledge and pending policies stay unchanged and receive a review action when their evidence changes.
- CLI and MCP requests read the updated model. Existing freshness checks continue to report changes that still need a decision.
- Generated guidance stays unchanged by default;
watch --generateopts into regeneration. - Polling and stability delays are configurable with
--intervaland--debounce.--jsonemits newline-delimited events for automation. - Invalid syntax and unreadable inputs stop a refresh before observations are saved; conflicting saves are retried. With
--generate, observation updates can be saved before a guidance error, which is reported for retry. Approvals stay unchanged. - SIGINT and SIGTERM stop cleanly after any in-progress write.
Run init before starting watch. Review deferred changes with bunx design-rover diff --json and use an explicit approval or rejection command for each decision.
Validation: 230 tests, 35 release-script tests, workspace typechecks, and installed-package watch/MCP smoke checks. Isolated copies of a Next.js portfolio (303 source/config files) and React browser extension (59 files) passed live add/edit, approval preservation and clean-shutdown checks. Their original projects stayed unchanged.
Design Rover 0.4.0
Design Rover 0.4.0
Agent context now checks whether saved design knowledge matches supported source observations before returning it.
- CLI
contextand MCPget_contextcheck freshness by default. Packets report the check time, source drift, pending reviews and stale generated guidance separately. - Stale observations include review and refresh commands with their working directory. Review the diff, then explicitly apply observed updates with
sync --yesand request context again. Pending knowledge and protected removals still require explicit decisions. - Retrieval preserves canonical knowledge, approvals, history, generated guidance and application source. Only the ignored evidence cache may be refreshed.
- Failed checks return actionable errors. Use CLI
--no-check-freshnessor MCPcheckFreshness: falsefor an explicitly unchecked saved snapshot. - Freshness metadata and actions stay within the requested response budget. The check covers supported observations at a point in time; rejected proposals remain suppressed.
Validation: 211 tests, 35 release-script tests, workspace typechecks, and an installed-package smoke test covering fresh-project initialization and stdio MCP. Isolated copies of a Next.js portfolio (303 source/config files) and a React browser extension (59 files) passed freshness detection and explicit-refresh checks with their original projects unchanged.
Design Rover 0.3.5
Design Rover 0.3.4
Design Rover 0.3.3
Design Rover 0.3.2
Design Rover 0.3.2
This patch addresses the correctness and safety findings from the independent audit of 0.3.1.
Approved knowledge and storage
- Moving source comments or images no longer changes their decision identity solely because line numbers moved. Unambiguous legacy records retain their IDs, approvals and human notes during synchronization.
- Routine synchronization and bulk approval preserve protected removals. Accepting a removal of approved or human-annotated knowledge requires reviewing its specific change ID.
- Concurrent reviews compare the full prior model before saving. A stale reviewer receives a conflict instead of silently overwriting another decision.
- Interrupted saves leave a recovery journal. Clearing a stale lock does not make a partially installed model appear valid. Missing
system.jsonalso requires recovery when existing knowledge remains. - Existing decisions can be explicitly revoked and reapproved, with accurate approval/rejection history. Shared metadata stores the repository root as
..
Analysis and checks
- Local export lists and aliases are included in component discovery. Nested UI and feature-local import paths retain their real directories.
- Static Tailwind configuration extraction preserves nested token names. Context follows CSS-variable dependencies across recorded themes, and relevant component matches rank ahead of supporting token records.
- Confirmed changes to an explicitly approved component API can fail the default gate. Missing local generated snapshots no longer make an otherwise valid fresh checkout fail CI.
- Generated writes reject symlink paths outside the intended project boundary. CLI JSON errors and diagnostics also receive the audit's focused fixes.
Contributions and releases
The release adds contribution guidance, issue forms and a PR template. Conventional Commit changes merged into main now enter a release pipeline that validates four Node/OS combinations before preparing the next version, notes and packaged CLI.
The workflow publishes to npm through OIDC trusted publishing, verifies and smoke-tests the registry download, publishes the scoped @nisargkavi/design-rover GitHub Packages mirror, and attaches the verified npm tarball and SHA256SUMS to a GitHub Release. An incomplete tagged release can resume through the Release workflow's resume_version input, with identity and content checks repeated. Maintainers configure npm trust and GitHub package visibility; the workflow's actual results establish publication status. See development and release operations.
Validation
Local validation passed 196 library tests and 32 release-script tests, including Git-history scenarios, version preparation, release classification and artifact verification. All workspace typechecks and the fresh-project packaged CLI/MCP smoke check passed. The hosted release workflow repeats validation before publishing.
For an existing model, run bunx design-rover@0.3.2 diff and review the proposed changes before synchronizing. Incomplete external types, dynamic styling and CSS class contracts remain limitations; a clean check is not a complete design, accessibility or visual audit.
Design Rover 0.3.1
Design Rover 0.3.1
This patch improves first-run guidance and fixes issues found while checking a real React browser-extension project.
Developer workflow
initexplains what was created, what needs review, which APIs are incomplete, and the next copyable Bun commands. Repeated initialization reports saved knowledge separately from newly observed counts.diffshows change IDs and individual approve/reject commands.sync --yesaccepts observed updates without approving inferred rules; approval requires an explicit decision or--approve.- Status and check output distinguish freshness, pending review, generated guidance and API resolution. Command-specific help is available for
init,syncandcontext. - The README focuses on getting started, agent usage and supported behavior. Detailed Git, development and release workflows live in linked documentation.
Fixes
- Ordinary JSX classes and static conditional template branches now contribute component-token relationships. Tailwind 4 theme namespaces map to their supported static utilities, including variants and opacity modifiers. Token counts no longer treat a declaration alone as a use.
- Existing models can sync changed token links, usage and architecture observations. Context-only updates are distinguished from API contract changes.
- Tests and stories remain usage evidence but do not establish production reuse when classifying a component as shared.
- Short-lived canonical lock contention waits before failing, allowing concurrent queries while preserving consistent snapshots. Stale locks are not removed automatically.
- Image conventions use verified
next/imageimports. Native<img>elements receive neutral guidance in browser extensions and other React projects.
Run bunx design-rover@0.3.1 diff on an existing model to review changed observations. Initialization preserves existing decisions. External package types and CSS class contracts such as .btn variants remain outside complete API resolution; a clean check is not a comprehensive design or accessibility audit.
Design Rover 0.3.0
Design Rover 0.3.0
Design Rover now retrieves bounded design context for a task and resolves more component APIs from local TypeScript modules.
Added
design-rover contextand MCPget_contextshare task/query and repository-path filters, result limits, and a character budget. Output includes source references and explicitly reports omitted records and decisions. Pending knowledge remains opt-in.- Component props can resolve through local imports and re-exports. Records expose resolution status and issues instead of presenting unresolved APIs as complete.
- Local barrel exports preserve component identity and usage attribution. Cycles and ambiguous exports remain unresolved.
- GitHub Releases include the exact npm package tarball and
SHA256SUMS. The workflow checks the tagged source against the public package before releasing assets.
Install
From the project you want to analyze:
bunx design-rover@0.3.0 init
bunx design-rover@0.3.0 context "update the settings form" --path app/settings/page.tsx --max-chars 12000 --jsonRequires Node >=20.19.0. Retrieval reads canonical knowledge; use status and review sync proposals to check freshness. An omitted decision still needs review. Type resolution is limited to scanned local modules and supported static forms; external package declarations and complex dynamic types remain unresolved.