Skip to content

Conversation

@gfsxyz
Copy link

@gfsxyz gfsxyz commented Nov 28, 2025

New Themes: Japanese Breeze, Bromo, and Jakarta

Adding three new themes inspired by Indonesian and Japanese locations. All themes include full light and dark mode support.

1. Japanese Breeze

A calm, minimalist palette inspired by Japanese bamboo/forest. It uses soft calm green tones to create a peaceful user experience.

jb jb-dark
2. Bromo

inspired by Bromo National Park, focused on earthy mountain tones and natural landscapes.

bromo bromo-dark
3. Jakarta

jakarta city inspired theme using the Plus Jakarta Sans font. Features vibrant Orange and Coastal Blue (jakarta city main color).

jakarta jakarta-dark

@vercel
Copy link

vercel bot commented Nov 28, 2025

@gfsxyz is attempting to deploy a commit to the tweakcn OSS program Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link

coderabbitai bot commented Nov 28, 2025

Walkthrough

A new theme preset called "japanese-breeze" with light and dark color variants has been added to the theme presets file. The preset includes complete color tokens for UI elements, typography, chart colors, sidebar styling, shadows, and spacing. A duplicate entry of the same preset also appears in the file.

Changes

Cohort / File(s) Change Summary
Japanese Breeze Theme Preset Addition
utils/theme-presets.ts
Added "japanese-breeze" theme preset with full light and dark color token definitions (label: "Japanese Breeze", createdAt: "2025-11-29"). Preset includes 50+ color and style properties for backgrounds, typography, charts, sidebar, shadows, and radius tokens. Duplicate identical entry detected for the same preset key.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

  • Verify if the duplicate preset entry is intentional or an accidental duplication that should be removed
  • Confirm all color hex values follow consistent formatting and contrast requirements
  • Validate that the "japanese-breeze" key naming and structure match existing preset conventions

Poem

🐰 A breeze from the east, in colors so bright,
Light jade and dark tones, from morning to night,
Japanese whispers in every hue,
A preset so pretty, hoppy and new! 🎨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title mentions three themes (japanese breeze, bromo, and jakarta), but the code summary shows only the japanese-breeze theme was added, with a duplicated entry. The bromo and jakarta themes are missing from the changeset. Update the PR title to reflect only the themes actually added (e.g., 'feat: add japanese breeze theme'), or add the missing bromo and jakarta theme implementations to the changeset.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
utils/theme-presets.ts (1)

3597-3699: Japanese Breeze preset is consistent and complete

The token set (light/dark colors, charts, sidebar, fonts, radius, spacing, shadows) aligns with existing themes and looks ready to use. Only very minor nit: createdAt: "2025-11-29" is one day ahead of this PR’s creation date; if you rely on that field for sorting/timelines and care about strict chronology, you may want to align it with the actual merge/release date.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 26028eb and 8a0daca.

📒 Files selected for processing (1)
  • utils/theme-presets.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Vercel Agent Review
🔇 Additional comments (2)
utils/theme-presets.ts (2)

3700-3786: Bromo theme fits the existing preset shape

Bromo’s light/dark variants provide a full, coherent token set (background/foreground, charts, sidebar, typography, radius, spacing, shadows) and follow the established naming and value patterns in this file. No structural or correctness issues spotted.


3787-3873: Jakarta theme is well-structured and uses Plus Jakarta Sans as intended

Jakarta’s palette and tokens (including charts, sidebar, typography, radius, spacing, shadows) match the ThemePreset shape and other presets’ conventions. The Plus Jakarta Sans font wiring via "font-sans" matches how similar fonts are specified elsewhere in the file.

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.

1 participant