leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add dark mode support using Tailwind dark: variant #415

New Issue
Closed
opened 2026-03-27 18:24:34 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 18:24:34 +00:00
Owner
Copy Link
Copy Source

Summary

Tailwind CSS is configured in the project but no dark: variant classes are applied. Users have no dark mode option.

What to do

  1. Enable darkMode: "class" in tailwind.config.js (or "media" for system preference)
  2. Apply dark: variants to all key UI components: background colors, text colors, borders, cards, inputs, buttons
  3. If using class strategy, add a toggle button to the nav/header that switches a dark class on <html> and persists the preference to localStorage
  4. Test across all main pages (Dashboard, Batch, Analytics, Auth)

Acceptance Criteria

  • Toggling dark mode visually inverts the color scheme across all main pages
  • The preference persists after a page reload
  • No contrast or readability issues in either mode
  • No TypeScript or build errors

Reference

Roadmap: P2 - Frontend / Dark mode

## Summary Tailwind CSS is configured in the project but no `dark:` variant classes are applied. Users have no dark mode option. ## What to do 1. Enable `darkMode: "class"` in `tailwind.config.js` (or `"media"` for system preference) 2. Apply `dark:` variants to all key UI components: background colors, text colors, borders, cards, inputs, buttons 3. If using `class` strategy, add a toggle button to the nav/header that switches a `dark` class on `<html>` and persists the preference to `localStorage` 4. Test across all main pages (Dashboard, Batch, Analytics, Auth) ## Acceptance Criteria - Toggling dark mode visually inverts the color scheme across all main pages - The preference persists after a page reload - No contrast or readability issues in either mode - No TypeScript or build errors ## Reference Roadmap: P2 - Frontend / Dark mode
AI-Manager added the P2agent-readymedium labels 2026-03-27 18:24:34 +00:00
AI-Manager commented 2026-03-27 19:06:09 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already Implemented

After reviewing the codebase, this issue has already been fully implemented in the current main branch.

This issue can be closed.

## Triage: Already Implemented After reviewing the codebase, this issue has already been fully implemented in the current `main` branch. This issue can be closed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#415
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?