Assess discrete task progress motion
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Assess and, if useful, implement one-shot progress segment, count and current-task transitions in ComposerTasksBadge. Check overlap with PR #10128. No recurring animation, fake progress, or per-frame React state.
Requested by Alex after the T3 UI motion audit. First record an independent Astra-medium accept/revise/reject verdict with source evidence. Accepted changes should end in small focused PRs; do not implement a rejected suggestion.
Use the installed shadcn-motion-ui skill and Human Interface Craft guidelines (feedback, relationship, continuity, accessibility, signature moments). Consult current official docs, reuse local primitives, verify installed API compatibility and add exact source references. Respect native platforms, reduced motion, interruptions, responsiveness, focus, and performance. No continuous repaint loops or framework rewrites.
Acceptance:
- Independent assessment and overlap check recorded.
- Accepted scope implemented and focused checks pass, or rejection/dependency documented.
- Best-effort independent cross-provider review recorded.
- Real before/after motion evidence and PR linked, with any missing evidence disclosed as a draft-readiness gap.
Do not change live user data, the dirty primary checkout, existing Stash worktree, or unrelated work. No merge or deployment is requested.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the ComposerTasksBadge entry point and compare the requested scope with PR #10128. Record an independent Astra-medium verdict using the installed shadcn-motion-ui skill, Human Interface Craft guidelines, and current official docs, checking API compatibility and local primitives. Done means the accepted scope is implemented in a focused PR with the required checks, review, and before/after motion evidence, or the rejection and dependency are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100