fix(styles): use semantic colors for plan markdown styling

[MattPua]

TL;DR

Replace hardcoded rgba colors with semantic color variables in plan markdown styling to ensure consistent visibility and appropriate contrast in both light and dark modes.

Problem

Plan highlighting lacks proper contrast and visibility across different color schemes. The hardcoded rgba(0, 0, 0, ...) and rgba(255, 255, 255, ...) values don't adapt well to light and dark modes, resulting in unclear highlighting and jarring visual presentation.

Changes

Before:

After

• Replace background: rgba(0, 0, 0, 0.2) with var(--blue-a5) for code inline background
• Replace background: rgba(0, 0, 0, 0.25) with var(--blue-a3) for pre-formatted code block background
• Replace border: 1px solid rgba(255, 255, 255, 0.2) with var(--blue-a6) for table cell borders
• Replace border-left: 2px solid rgba(255, 255, 255, 0.3) with var(--blue-a6) for blockquote left border

How did you test this?

Visual inspection of plan markdown rendering in both light and dark modes to verify improved contrast and consistent visibility.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog Code

[greptile-apps]

_{Reviews (1): Last reviewed commit: "chore(styles): use semantic color variab..." | Re-trigger Greptile}

[adamleithp]

Hmm not sure if blue is on brand, I was trying to go with more Posthog.com stylin' ala @corywatilo

[MattPua]

Hmm not sure if blue is on brand, I was trying to go with more Posthog.com stylin' ala @corywatilo

i found the styling originally there jarring to read considering the constrast difference, and how often its used in the plan.

plus on dark mode its basically non noticeable.

I agree about whether blue is the right color at all, but the plan was already blue so