Start free

Rubic is the coding agent platform for software teams.

Start free See how it works

14-day free trial · No credit card required

TASKS/T-184
Add localization to the customer portal DEVELOPING AWAITING APPROVAL
northstar/customer-portal·feat/T-184-portal-localization
AS JL SK
Rubic is working Ready for approval
CHAT PLAN OPEN FILE ⌘P
ALEX SMITH09:14

Add English and Spanish localization to the customer portal. Preserve existing URLs and include regression coverage.

AS
R
RUBIC09:18

The approved plan is running against the portal routing and translation layers.

DEVELOPMENT 1 / 2 2 / 2

Locale foundationCompleted

Translation coverage Running checks… Completed

JORDAN LEE09:23

Please keep existing URLs unchanged and preserve each signed-in user's saved language preference.

JL
R
RUBIC09:24
DECISION REQUIRED How should language preference be resolved?

The answer changes locale precedence and fallback behavior.

1Profile, then browserSELECTED
2Browser only
SAM KIM09:26
DECISION ANSWERED How should language preference be resolved?
1 Profile, then browser SELECTED
SK
R
RUBICNOW

Decision applied. I preserved existing routes, added profile-first locale selection, and reran the affected checks. All 24 checks pass.

Ask Rubic or request a change…

Review the plan before Rubic starts building.

Rubic reviews the relevant code and project rules, proposes implementation steps, risks, and affected files, then waits for approval.

Explore planning and approval →
TASKS/T-184
Add localization to the customer portal AWAITING PLAN APPROVAL
northstar/customer-portal·No branch
CHAT PLAN OPEN FILE ⌘P
PLAN READY FOR REVIEWDECISION REQUIRED

Review the implementation approach before Rubic starts development.

IMPLEMENTATION PLAN

Add English and Spanish localization with profile-first language preference, browser fallback, and unchanged existing routes.

CODE CHANGEPULL REQUEST
STEPS 4FILES 5COMPLEXITY MEDIUM
STEPS0 / 4

Configure locale foundationDefine supported locales, translation catalogs, and a stable default without changing the current route structure.

Resolve the preferred languageRead the signed-in user's profile preference first, then fall back to the browser language and application default.

Localize the customer portalTranslate navigation, account, and order surfaces while preserving existing links and saved URLs.

Verify preference and routing behaviorCover profile selection, browser fallback, missing translations, and existing route regression cases.

RISKS

Existing saved URLs must continue to resolve without locale prefixes.

Missing translations must fall back to English instead of rendering empty labels.

AFFECTED FILES5

src/i18n/config.tsAdd locale registry and fallback rules.

MODIFY

src/i18n/provider.tsxResolve and provide the active locale.

MODIFY

src/i18n/locales/es.tsAdd Spanish customer portal copy.

CREATE

src/account/profile-language.tsRead the saved language preference.

MODIFY

tests/locale-routing.test.tsCover preference, fallback, and routes.

MODIFY
TASKS/T-184
Add localization to the customer portal AWAITING APPROVAL
northstar/customer-portal·feat/T-184-portal-localization
CHAT PLAN
R
RUBIC · WORK COMPLETE

The implementation is complete. The preview is live and the latest review found no blocking issues.

Review completeNo blocking issues found

24 checks passedLocale preference and routing

4 files changedReady for delivery

Ask Rubic or request a change…
config.ts
src/i18n/config.ts
11import { readProfileLocale } from './profile';
22
3- export const locales = ['en'] as const;
3+ export const locales = ['en', 'es'] as const;
44export const defaultLocale = 'en';
55
66export function resolveLocale(request: Request) {
7-  return defaultLocale;
7+  const saved = readProfileLocale(request);
8+  if (saved && locales.includes(saved)) {
9+    return saved;
10+  }
11+  return resolveBrowserLocale(request, locales);
812}

Review the work, not just the result.

Inspect changed files, test results, application logs, and the live application before approving delivery.

Explore review and delivery →
CLOUD APPLICATION WORKSPACE

Rubic runs the application, not just the code.

Every task runs in its own cloud workspace with the application, required services, environment settings, and logs available to your team.

Showing application workspace

TASKS/T-184
Add localization to the customer portal RUNNING
northstar/customer-portal·feat/T-184-localization
WORKSPACE LIVE
CHAT PLAN
AS
ALEX SMITH

Add English and Spanish localization to the customer portal. Preserve existing URLs and include regression coverage.

R
RUBIC

The application is running with its task-scoped environment. Preview and service logs are available for inspection.

Preview readyLIVE
24 checks passedPASS
Ask Rubic or request a change…
LIVE PREVIEW
/dashboard
NorthstarInicio   Pedidos   AyudaES
Portal del clienteGestiona tu cuenta y tus pedidos
PEDIDOS12
ABIERTOS3
MENSAJES2
PEDIDOESTADOTOTAL

48#1048

En camino€128

42#1042

Entregado€84

37#1037

Procesando€56
Explore cloud application workspaces →

Rubic asks your team when a decision is needed.

Answer a question, request a revision, and inspect the files, tests, and log output without taking the task back.

Explore task collaboration →
TASKS/T-184
Add localization to the customer portal NEEDS INPUT
northstar/customer-portal·feat/T-184-portal-localization
Rubic is waiting
CHAT PLAN OPEN FILE ⌘P
JORDAN LEE09:23

Keep existing URLs unchanged and preserve each signed-in user's saved language preference.

JL
R
RUBIC09:24
DECISION REQUIRED How should language preference be resolved?

The answer changes locale precedence and fallback behavior.

1Profile, then browserSELECTED
2Browser only
SAM KIM09:26
DECISION ANSWERED How should language preference be resolved?
1Profile, then browserSELECTED
SK
RUBICNOW

Decision applied. I preserved existing routes, added profile-first locale selection, and reran the affected tests.

Ask Rubic or request another change…
TEAM-SCALE OPERATIONS

Keep your team’s software work in one place.

Track tasks and larger initiatives, surface decisions that need attention, and follow pull requests through delivery.

Showing Tasks List and Board

Tasks

LIST & BOARD

NEEDS ACTION2

TOTAL8

Search ID or Title…
BACKLOG
2
Add audit log export
T-192
AS
Refine member invitations
T-193
JL
IN PROGRESS
ACTIVE2
Add localization to the customer portal
T-184
AS
Improve preview readiness
T-188
SK
NEEDS ACTION
2
Choose migration strategy
T-186Needs Input
AM
Approve delivery evidence
T-189
JL
DELIVERING
CREATING PR…1
Update billing permissions
T-181
AS
Explore team operations →
BUILT FOR REAL SOFTWARE TEAMS

Run and verify real applications in the cloud.

Rubic runs each task with the application services, runtime controls, logs, and inspection tools needed to verify the outcome.

CLOUD WORKSPACE

Runs the real application in isolation.

Every task receives its own workspace for development and preview.

APPLICATION SERVICES

Starts the services the project needs.

Databases and connected services run alongside the application.

RUNTIME VISIBILITY

Keeps application and service logs visible.

Environment settings, logs, and debugging stay inside the task.

QUESTIONS

What software leaders ask first.

01 How does Rubic work with an existing codebase? +

Connect your repositories and define the rules that matter to your team. Rubic uses that context to plan and execute each task against the system you already have.

02 Where does my team stay in control? +

Your team can approve plans, answer questions, request changes, trigger an additional review, review the work and results, and approve the final delivery.

03 How is task execution isolated? +

Each task runs in its own workspace with task-scoped runtime configuration, preview lifecycle, and cleanup. Repository access stays limited to the task and project, and Rubic can only deliver work within those boundaries.

04 Can Rubic run my application and its services? +

Rubic starts the application and the databases or services it needs inside the task workspace. Your team can use Live Preview, inspect the running application, test responsive layouts, and review application and service logs before delivery.

05 How does the free trial work? +

The free trial lasts 14 days and does not require a credit card. Live Preview is available with paid Pro and Business seats.

06 What happens when a decision is ambiguous? +

Rubic pauses and asks a focused question with concrete options. The answer becomes part of the task context before work continues.

07 How are changes validated? +

Each task can include file-level changes, executed test commands, test and log output, and a live preview so your team can evaluate both the implementation and the outcome.

08 Does Rubic support work across multiple repositories? +

Yes. Rubic can plan epics across repositories while keeping each task connected to the relevant codebase context and project rules.

START WITH ONE TASK

Give Rubic its first task.

Start free, connect a repository, and review Rubic's plan before any implementation begins.

Start free Talk to us