Repository navigation
chore(design): routines in the design system - #124
Merged
Merged
Conversation
CrewRoutines joins the claude.ai/design design system, with the routine request card (chat.askRoutine). BotloftProvider takes routines, seeded before the app's store connects like the browsers. makeRoutine and schedule build them in the protocol's shape; with no explicit next run, it follows the schedule, so a row's "Next" agrees with its schedule. The routine builders and the shared id helpers move out of scene.ts, which had grown past the file size limit.
httpsphl
enabled auto-merge
October 2, 2026 18:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
The explainer video shows a routine running ("Close the app. They keep working, on a schedule."), so routines join the claude.ai/design design system:
CrewRoutines, the app's real list: each routine with its bot, its schedule in words, the next run and the last run (fine, failed, skipped, running now).ApprovalCard(chat.askRoutine).BotloftProvidertakesroutines, seeded into the fake daemon before the store connects (the same first-answer race as the browsers).makeRoutineandschedule(.design-sync/pkg/routines.ts) build them in the protocol's shape. Without an explicit next run, it follows the schedule, so the row's "Next" agrees with it.scene.tshad grown past ~300 lines: the routine builders and the shared id helpers (ids.ts) move out.Nothing under
app/orcrates/changes.How it was tested
Converter validation passes; all 26 previews render and were graded from screenshots, including the routines list (light, dark, a run in progress) and the routine request card. The claude.ai/design project was updated against its sync anchor: CrewRoutines added, ApprovalCard and BotloftProvider changed, nothing to delete.
Checklist
cargo fmt,clippy -D warningsandcargo testpass (no Rust changes)pnpm checkpasses (no app changes)docs/spec.mdstill matches the code