Skip to content

fix: brand consistency, new components, and accessibility (issues #80, #82, #83, #86)#142

Merged
jbdevprimary merged 3 commits intomainfrom
claude/triage-pull-requests-gKQEA
Feb 16, 2026
Merged

fix: brand consistency, new components, and accessibility (issues #80, #82, #83, #86)#142
jbdevprimary merged 3 commits intomainfrom
claude/triage-pull-requests-gKQEA

Conversation

@jbdevprimary
Copy link
Contributor

Summary

Files Changed (15)

  • tailwind.config.ts — New organic border-radius classes
  • src/components/feedback/Loading.tsx — SkeletonText, SkeletonCard
  • src/components/feedback/Pagination.tsx — New component
  • src/components/feedback/index.ts — Updated exports
  • src/pages/NotFound.tsx — Use organic Tailwind classes
  • src/pages/detail/AgentDetail.tsx — Shadows, a11y, organic hero class
  • src/pages/detail/ProjectDetail.tsx — Shadows on cards
  • src/pages/onboarding/*.tsx — Shadows, organic hero class
  • src/pages/tabs/*.tsx — A11y fixes, shadows

Test plan

  • Verify all pages render correctly with new shadow and border-radius classes
  • Check Pagination component renders with proper page navigation
  • Verify SkeletonCard and SkeletonText render animated placeholders
  • Screen reader testing: verify aria-live announces typing/progress updates
  • Verify search input is properly labeled for assistive technology

Closes #80, closes #82, partially addresses #83 and #86.

https://claude.ai/code/session_01PQd4hGQQpmGTgpHc7kGjAE

- OrchestrationState: use getTask() helper instead of direct taskQueue.find()
  to correctly detect cancelled deps in completedTasks (CodeRabbit #134)
- DiffViewer: combine additions/deletions into single-pass useMemo (Gemini #134)
- DiffViewer: export parseDiff for testability
- diff-viewer.perf.test: rename to kebab-case, add memoization spy test
  verifying parseDiff is NOT called on re-render (Amazon Q + Gemini #134)
- FileTree: pass selectedPath directly instead of converting undefined
  to empty string which changes "no selection" semantics (Amazon Q #139)
- sonar-project.properties: remove stale app/_layout.tsx comment (CodeRabbit #139)
- create-project: add auth error detection with recovery guidance (Amazon Q #132)

https://claude.ai/code/session_01PQd4hGQQpmGTgpHc7kGjAE
…ibility

- Add missing organic border-radius variants to Tailwind config (hero, cta,
  modal, toast, code) and replace inline/arbitrary values in NotFound,
  welcome, complete, and AgentDetail pages (#80)
- Add shadow-organic-card to card surfaces across detail pages, onboarding
  screens, and settings for proper visual hierarchy (#82)
- Enhance Skeleton with SkeletonText and SkeletonCard compound components,
  build Pagination component with organic styling (#83)
- Fix accessibility: aria-hidden on decorative dots, aria-live on typing
  indicator and progress, aria-label on search input and role icon,
  progressbar role on task progress (#86)

https://claude.ai/code/session_01PQd4hGQQpmGTgpHc7kGjAE
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 16, 2026

Warning

Rate limit exceeded

@jbdevprimary has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minutes and 58 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch claude/triage-pull-requests-gKQEA

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@jbdevprimary jbdevprimary merged commit 65b0538 into main Feb 16, 2026
13 of 18 checks passed
@jbdevprimary jbdevprimary deleted the claude/triage-pull-requests-gKQEA branch February 16, 2026 00:54
@gemini-code-assist
Copy link

Summary of Changes

Hello @jbdevprimary, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly refines the application's user interface and experience by standardizing visual elements and introducing new UI components. It ensures brand consistency through unified border-radius styles and improved visual hierarchy with consistent card shadows. Furthermore, it boosts the application's usability and inclusivity by implementing crucial accessibility features across various interactive elements and dynamic content.

Highlights

  • Brand Consistency: Introduced new organic border-radius variants in Tailwind config and applied them across various pages, replacing inline styles for a unified visual aesthetic.
  • Visual Hierarchy: Implemented shadow-organic-card across numerous card surfaces on detail pages, onboarding screens, and settings to enhance visual depth and consistency.
  • New Components: Developed SkeletonText and SkeletonCard as compound components for the Skeleton loader, and created a new, accessible Pagination component for improved navigation.
  • Accessibility Enhancements: Addressed several accessibility issues by adding aria-hidden to decorative elements, aria-live to dynamic content, aria-label to interactive elements, and progressbar role to progress indicators.
Changelog
  • packages/agent-intelligence/src/services/orchestrator/OrchestrationState.ts
    • Updated task dependency checks to use getTask for broader search.
  • sonar-project.properties
    • Removed an outdated comment regarding _layout.tsx exclusion.
  • src/components/code/DiffViewer.tsx
    • Exported parseDiff for external use.
    • Optimized the calculation of additions and deletions for performance.
  • src/components/code/FileTree.tsx
    • Refined setSelectedPath logic by removing unnecessary empty string fallback.
  • src/components/code/tests/diff-viewer.perf.test.tsx
    • Renamed the performance test file for DiffViewer.
    • Added a test to verify parseDiff memoization, ensuring it's not re-parsed on re-renders.
    • Adjusted performance assertion to expect re-render time to be faster than initial render.
  • src/components/feedback/Loading.tsx
    • Introduced SkeletonText and SkeletonCard components.
    • Updated LoadingOverlay's border-radius to use rem units.
  • src/components/feedback/Pagination.tsx
    • Added a new Pagination component with organic styling and accessibility features.
  • src/components/feedback/index.ts
    • Exported SkeletonCard, SkeletonText, and Pagination components.
  • src/pages/NotFound.tsx
    • Applied new organic border-radius classes (rounded-organic-hero, rounded-organic-cta).
  • src/pages/detail/AgentDetail.tsx
    • Applied rounded-organic-hero and shadow-organic-card classes.
    • Added aria-label to agent role icon and aria-live and progressbar roles to task progress.
  • src/pages/detail/ProjectDetail.tsx
    • Applied shadow-organic-card to various card elements.
  • src/pages/onboarding/api-keys.tsx
    • Applied shadow-organic-card to the tip card.
    • Improved GitHub authentication error messages for clarity.
  • src/pages/onboarding/complete.tsx
    • Applied rounded-organic-hero and shadow-organic-card classes.
  • src/pages/onboarding/create-project.tsx
    • Enhanced error handling for GitHub authentication failures.
  • src/pages/onboarding/github-auth.tsx
    • Applied shadow-organic-card to authentication display cards.
  • src/pages/onboarding/welcome.tsx
    • Applied rounded-organic-hero and shadow-organic-card classes.
  • src/pages/tabs/chat.tsx
    • Added aria-hidden to decorative status dots and aria-live to the typing indicator.
  • src/pages/tabs/home.tsx
    • Added aria-hidden to agent status dots.
  • src/pages/tabs/projects.tsx
    • Added aria-hidden to the search icon and aria-label to the search input.
  • src/pages/tabs/settings.tsx
    • Applied shadow-organic-card to settings section groups.
  • tailwind.config.ts
    • Added new organic-hero, organic-cta, organic-modal, organic-toast, and organic-code border-radius variants.
Activity
  • Added 5 missing organic border-radius variants to Tailwind config and replaced inline/arbitrary border-radius values in NotFound, welcome, complete, and AgentDetail pages (Issue [Brand] Phase 1: Standardize border-radius using Tailwind organic classes #80).
  • Applied shadow-organic-card to card surfaces across detail pages, onboarding screens, and settings to establish proper visual hierarchy (Issue [Brand] Phase 3: Apply organic shadow system for visual depth #82).
  • Enhanced Skeleton with SkeletonText and SkeletonCard compound components; built new Pagination component with organic styling and full accessibility (Partially addresses Issue [UI] Implement missing components for v1.0 production readiness #83).
  • Fixed accessibility: aria-hidden on decorative status dots, aria-live on typing indicator and progress updates, aria-label on search input and agent role icon, progressbar role on task progress bar (Partially addresses Issue [Accessibility] WCAG AA compliance audit and validation #86).
  • Verified all pages render correctly with new shadow and border-radius classes.
  • Checked Pagination component renders with proper page navigation.
  • Verified SkeletonCard and SkeletonText render animated placeholders.
  • Performed screen reader testing to verify aria-live announces typing/progress updates.
  • Verified search input is properly labeled for assistive technology.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@amazon-q-developer amazon-q-developer bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unable to Complete Review

I encountered a technical issue while attempting to review PR #142. While the PR diff was successfully retrieved (21 files changed), I was unable to access the file contents from the repository's head branch. This prevented me from performing a thorough code review with proper context.

PR Summary:

  • Addresses issues #80, #82, #83, and #86
  • Adds organic border-radius variants to Tailwind config
  • Implements new Pagination component and enhanced Skeleton components
  • Applies shadow styling for visual hierarchy
  • Adds accessibility improvements (aria-hidden, aria-live, aria-label, progressbar roles)

Technical Issue:
All attempts to retrieve file contents resulted in "File not found" errors, despite the diff being successfully retrieved. This may indicate:

  • Repository access permissions issue
  • Branch synchronization problem
  • API connectivity issue

Recommendation:
Please retry the review process or check repository access permissions. The changes appear to be focused on UI consistency and accessibility improvements, which are valuable additions that should be properly reviewed once file access is restored.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This is a great pull request that delivers on multiple fronts. The introduction of new border-radius variants to the Tailwind config and the consistent application of these and the new shadow classes significantly improve brand consistency and maintainability by removing hardcoded styles. The new Pagination, SkeletonText, and SkeletonCard components are well-implemented and valuable additions. I'm particularly impressed with the numerous accessibility improvements across the application, such as adding ARIA attributes for screen readers. The code is clean and the changes are well-aligned with the stated goals. I've only found one minor opportunity for improvement.

Comment on lines 116 to +117
className="bg-surface-elevated p-6 flex flex-col items-center"
style={{ borderRadius: '16px 12px 20px 8px' }}
style={{ borderRadius: '1rem 0.75rem 1.25rem 0.5rem' }}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While this change correctly updates the border-radius to use rem units, it misses the opportunity to fully embrace the new Tailwind configuration. To improve maintainability and align with the goal of replacing inline styles, it would be better to use the rounded-organic-card class directly, which is now available in tailwind.config.ts.

Suggested change
className="bg-surface-elevated p-6 flex flex-col items-center"
style={{ borderRadius: '16px 12px 20px 8px' }}
style={{ borderRadius: '1rem 0.75rem 1.25rem 0.5rem' }}
className="bg-surface-elevated p-6 flex flex-col items-center rounded-organic-card"

@jbdevprimary jbdevprimary mentioned this pull request Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Brand] Phase 3: Apply organic shadow system for visual depth [Brand] Phase 1: Standardize border-radius using Tailwind organic classes

2 participants