jobtrackingapp/docs/redesign/ASTRA_HANDOFF.md

Astra / Coding-Agent Handoff

Mission

Redesign Jobjakt into a modern, professional and supportive career SaaS for the Norwegian job market while preserving existing functionality.

This is a UX and frontend architecture redesign, not permission to delete features or rewrite working backend behaviour unnecessarily.

Critical instructions

Do not start by changing code

First audit the repository and produce:

1. Frontend architecture summary.
2. Current styling/component technology.
3. Complete route/page inventory.
4. Complete user-facing functionality inventory.
5. Existing test inventory.
6. API integration map.
7. Authentication/authorisation map.
8. Localisation approach.
9. Responsive/mobile behaviour summary.
10. Major UX and maintainability problems.
11. Risks likely to cause functional regression during redesign.

Do not assume the existing documentation is complete. Verify against the code.

Read these documents first

• PRODUCT_VISION.md
• INFORMATION_ARCHITECTURE.md
• UX_FLOWS.md
• DASHBOARDS.md
• DESIGN_SYSTEM.md
• AI_PRINCIPLES.md
• RESPONSIVE_ACCESSIBILITY.md
• FUNCTIONAL_GUARDRAILS.md
• IMPLEMENTATION_PLAN.md
• OPEN_DECISIONS.md

Protected principles

Existing functionality

Every discovered feature must be preserved, relocated, intentionally merged, or explicitly deprecated. Never silently remove it.

AI truthfulness

AI must never invent user skills, experience, qualifications, history, achievements or other facts.

Career Profile

Career Profile is the canonical career-data source.

CVs and applications are derived outputs and may contain document-specific overrides without silently mutating the master profile.

AI review

AI-generated edits to user-owned content must be previewed/reviewed before being applied.

Navigation

Target a grouped collapsible sidebar on desktop.

Jobs table and Kanban should be two views of the same workspace.

Job detail

Target a dedicated full job workspace/page, with an optional quick-preview drawer if useful.

Dashboard

Personal dashboard should be highly configurable per user.

Admin dashboard should be separate and aggregate-focused.

Mobile

Do not simply compress the desktop UI. Adapt workflows where necessary.

Implementation approach

Follow IMPLEMENTATION_PLAN.md.

Do not make a single massive redesign commit.

Establish the design system and representative screens before migrating the whole application.

Technical freedom

You may significantly restructure the React frontend where justified, including:

• component organisation,
• shared design system,
• route organisation,
• styling technology,
• component library,
• reusable layouts,
• frontend tests.

Do not change backend/API contracts without a documented reason.

Representative screens to build first

1. App shell/sidebar
2. Dashboard
3. Jobs workspace
4. Job detail
5. CV builder

These screens should establish the product's visual and interaction language.

Visual target

Modern SaaS with Scandinavian restraint:

• clean,
• calm,
• data-rich,
• professional,
• supportive,
• polished,
• one primary brand colour,
• strong light and dark themes,
• subtle motion,
• consistent spacing.

Avoid excessive gradients, decorative glass effects, nested cards and generic AI sparkle aesthetics.

Completion standard

A migrated workflow is complete only when:

• functional tests pass,
• no protected functionality has been lost,
• desktop works,
• mobile works,
• light mode works,
• dark mode works,
• English works,
• Norwegian works,
• keyboard interactions are usable,
• obvious overflow/spacing issues are resolved.