How akshayxgh/career-execution-system works
1. This repo is a client-side React application built with TypeScript and Vite. The architecture is a single-page UI: src/main.tsx bootstraps the app, and src/App.tsx is the top-level composition point.
2. The app is organized around a shared shell and multiple feature views. src/components/Layout.tsx and src/components/Sidebar.tsx form the persistent navigation frame, while the page bodies live under src/views/*.
3. The main feature areas appear to be a personal/work management dashboard for documents and career tracking. The available views include Dashboard, Analytics, Applications, Interviews, Documents, LearningTracks, PL300Tracker, ProjectTracker, ResumeTracker, and Weaknesses. Each view is likely a self-contained screen rather than a deeply nested module system.
4. State is centralized in src/store/StoreContext.tsx, which is the key application boundary for shared data and actions. That suggests the UI relies on context-based state propagation instead of a separate backend API layer or a heavier state library.
5. Shared domain shapes live in src/types/index.ts. This indicates the app uses explicit TypeScript models for the store and feature data, which is important for understanding the data contract between the context, views, and utility functions.
6. Derived calculations are isolated in src/utils/scoreCalculator.ts. This is the main non-UI logic visible in the tree, and it likely powers analytics or scoring displays in the dashboard/tracker views rather than being embedded directly in components.
7. Styling is split between global and component-level CSS: src/index.css, src/App.css, and src/components/Sidebar.css. That implies the visual system is mostly local to the frontend, with no separate design system package.
8. There is no evidence of a server process, API gateway, or database in this repository tree. The architecture is therefore front-end only, with any persistence likely handled externally, mocked, or absent from the current codebase.
9. Deployment is static-host oriented. The presence of vercel.json and Vite configuration suggests the app is built as static assets and deployed to a platform like Vercel rather than run as a traditional server-rendered app.
10. The public/ folder and src/assets/ directory are the repository’s asset boundaries. These likely hold static images/icons and other non-code resources consumed by the UI shell and views.
11. There is also a complete backup copy under document-center-backup-20260701-174849/ that mirrors the app structure. For architecture purposes, treat it as an archive or snapshot, not part of the active runtime path unless explicitly referenced.
12. A clean way to diagram this repo is: bootstrapping layer at main.tsx, app shell at App.tsx/Layout/Sidebar, shared state in StoreContext, derived logic in scoreCalculator, and feature screens in views/, all packaged as a Vite-built static SPA.
Main entry points: App.tsx App · StoreContext.tsx Store · Dashboard.tsx Dashboard · scoreCalculator.ts Scoring
Components 20
Active app
Primary Vite React SPA source tree
Views
Feature screens rendered inside the shell
- Dashboard · Main summary view
src/views/Dashboard.tsx - Analytics · Metrics and scoring view
src/views/Analytics.tsx - Applications · Application tracking view
src/views/Applications.tsx - Interviews · Interview tracking view
src/views/Interviews.tsx - Documents · Document management view
src/views/Documents.tsx - Learning · Learning path tracking view
src/views/LearningTracks.tsx - PL300 · PL-300 progress tracker
src/views/PL300Tracker.tsx - Projects · Project tracking view
src/views/ProjectTracker.tsx - Resume · Resume tracking and iteration view
src/views/ResumeTracker.tsx - Weaknesses · Gaps and improvement tracking view
src/views/Weaknesses.tsx
Shared core
Cross-cutting application state and domain logic
Assets
Static file boundaries consumed by the UI
Archive
Backup snapshot of the app structure
- Backup copy · Archived mirror of the application tree
document-center-backup-20260701-174849
Connections 32
- main.tsx → App: boots · Entry point mounts the SPA root
- App → Layout: wraps · App composes the persistent shell
- Layout → Sidebar: includes · Shell provides navigation chrome
- App → Store: provides state · Top-level app uses shared context state
- Store → Types: shapes · Context uses shared domain contracts
- Store → Scoring: derives · State feeds computed scoring logic
- App → Dashboard: routes · Primary landing screen
- App → Analytics: routes · Feature view in the SPA
- App → Applications: routes · Feature view in the SPA
- App → Interviews: routes · Feature view in the SPA
- App → Documents: routes · Feature view in the SPA
- App → Learning: routes · Feature view in the SPA
- App → PL300: routes · Feature view in the SPA
- App → Projects: routes · Feature view in the SPA
- App → Resume: routes · Feature view in the SPA
- App → Weaknesses: routes · Feature view in the SPA
- Sidebar → Dashboard: nav · Sidebar links to major screens
- Sidebar → Analytics: nav · Sidebar links to major screens
- Store → Dashboard: feeds · Shared data powers the dashboard
- Store → Analytics: feeds · Shared data powers analytics
- Store → Applications: feeds · Shared data powers tracking views
- Store → Interviews: feeds · Shared data powers tracking views
- Store → Documents: feeds · Shared data powers tracking views
- Store → Learning: feeds · Shared data powers tracking views
- Scoring → Analytics: powers · Derived metrics surface in analytics
- Scoring → Dashboard: powers · Computed scoring influences summary cards
- Scoring → PL300: powers · Scoring logic supports tracker progress
- Types → Dashboard: types · Feature screens share the same models
- Types → Applications: types · Feature screens share the same models
- Public → App: assets · Static files available to the app shell
- Assets → App: assets · Bundled source assets used by components
- Backup copy → App: mirrors · Archived copy of the app structure