Start free

Rubic is the coding agent platform for software teams.

Plan, build, run, and deliver software with Rubic.

Start free See Rubic in action

14-day free trial · No credit card required

TASKS/T-184
Add Spanish and French support to the customer portal DEVELOPING AWAITING APPROVAL
northstar/customer-portal·feat/T-184-portal-localization
AS JL SK
CHAT PLAN OPEN FILE ⌘P
ALEX SMITH09:14

The customer portal already supports English. Add Spanish and French. Keep English as the default language. Keep existing URLs. Add regression tests.

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

Keep existing URLs. Preserve each signed-in user's saved language preference.

JL
R
RUBIC09:24
DECISION REQUIRED Which source should set the language?

This choice sets the language order and fallback.

1Profile, then browserSELECTED
2Browser only
SAM KIM09:26
DECISION ANSWERED Which source should set the language?
1 Profile, then browser SELECTED
SK
R
RUBICNOW

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

Ask Rubic or request a change…
HOW IT WORKS

Move from one task to working software.

  1. Define the result.

    Describe what you need. Select the repository and the people who will follow the task. Rubic reviews the context and prepares a plan.

  2. Rubic builds and runs.

    Rubic changes the code in an isolated cloud workspace. It runs the tests and the application. It asks your team when it needs a decision.

  3. Review and deliver.

    Review the changed files, tests, logs, and Live Preview. Request changes, approve the result, or merge the pull request.

CLOUD APPLICATION WORKSPACE

Rubic runs the application, not just the code.

Each task runs in a separate cloud workspace. Your team can access the application, required services, environment settings, and logs.

Showing application workspace

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

The customer portal already supports English. Add Spanish and French. Keep English as the default language. Keep existing URLs. Add regression tests.

R
RUBIC

The application is running in its task workspace. You can inspect the preview and service logs.

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

Review the plan before Rubic starts building.

Rubic reviews the relevant code and project rules. It lists the steps, risks, and affected files. Then it waits for your approval.

TASKS/T-184
Add Spanish and French support 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 Spanish and French to the existing English customer portal. Keep English as the default language. Use the profile language first and the browser language as a fallback. Keep current routes.

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

Configure locale foundationDefine English, Spanish, and French catalogs. Keep English as the default language. Keep the current route structure.

Resolve the preferred languageRead the signed-in user's profile preference first. If needed, use the browser language. Use the application default last.

Localize the customer portalAdd Spanish and French translations to the navigation, account, and order pages. Keep existing links and saved URLs.

Verify preference and routing behaviorTest profile selection, browser fallback, missing translations, and current routes.

RISKS

Existing saved URLs must continue to resolve without locale prefixes.

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

AFFECTED FILES6

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/i18n/locales/fr.tsAdd French 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 Spanish and French support 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. The latest review found no blocking issues.

Review completeNo blocking issues found

24 checks passedLocale preference and routing

5 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', 'fr'] 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 code and running application.

Review the changed files, test results, application logs, and Live Preview. Approve the delivery when the result is ready.

Rubic asks your team when a decision is needed.

Answer the question or request a change. You can review the files, tests, and logs while Rubic continues the task.

TASKS/T-184
Add Spanish and French support 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. Preserve each signed-in user's saved language preference.

JL
R
RUBIC09:24
DECISION REQUIRED Which source should set the language?

This choice sets the language order and fallback.

1Profile, then browserSELECTED
2Browser only
SAM KIM09:26
DECISION ANSWERED Which source should set the language?
1Profile, then browserSELECTED
SK
RUBICNOW

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

Ask Rubic or request another change…
TEAM-SCALE OPERATIONS

Track tasks, decisions, and pull requests in one place.

See what Rubic is building across Tasks and Epics. Respond when Rubic needs input. Follow each pull request 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 Spanish and French support 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
BUILT FOR REAL SOFTWARE TEAMS

Run and verify real applications in the cloud.

Rubic runs each task with its application services and runtime controls. Your team can use logs and inspection tools to check the result.

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 your team rules. Rubic reads this context before it plans and runs each task.

02 Where does my team stay in control? +

Your team reviews and approves each plan. It can answer questions, request changes, start another review, and approve the final delivery.

03 How is task execution isolated? +

Rubic creates a separate workspace for each task. Task settings control the runtime, preview, and cleanup. Rubic limits repository access to the active task and project. It delivers work only inside these boundaries.

04 Can Rubic run my application and its services? +

Rubic starts the application and any required databases or services in the task workspace. Your team can inspect the running application with Live Preview. It can also test responsive layouts and review service logs.

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 Rubic needs a decision? +

Rubic pauses and asks one clear question with specific options. It adds the answer to the task context before work continues.

07 How are changes validated? +

Each task can show changed files, test commands, test results, logs, and a live preview. Your team can review the code and running result.

08 Does Rubic support work across multiple repositories? +

Yes. Rubic creates an epic for work that affects multiple repositories. Each task uses the relevant code and project rules.

START WITH ONE TASK

Give Rubic its first task.

Start free and connect a repository. Rubic shows you the plan before it changes any code.

Start free Talk to us