pingdotgg / pingdotgg/t3code

Assess composer-to-Stash motion and existing PR

Open
#10,248 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Review existing PR #10134 without editing its dirty worktree or branch. Verify shallow arc, common 550 ms start/deadline, final destination layout, interruption and reduced motion. Reuse the existing PR if it covers the suggestion; only build a separate focused follow-up if a concrete gap remains.

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing PR #10134 without modifying its dirty worktree or branch, then use the installed shadcn-motion-ui skill and Human Interface Craft guidelines to assess the composer-to-Stash motion. Record an independent accept/revise/reject verdict with official source references and check the shallow arc, 550 ms timing, destination layout, interruption, reduced motion, focus, responsiveness, and performance. Done means overlap is resolved and either a focused PR with before/after evidence and checks is linked or the rejection, dependency, and missing evidence are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
accessibility, design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.