PolicyEngine · MaxGhenis · Nov 25, 2025 · Nov 25, 2025 · Nov 25, 2025 · Nov 25, 2025
diff --git a/app/.prettierrc.mjs b/app/.prettierrc.mjs
@@ -33,4 +33,4 @@ const config = {
   ],
 };
 
-export default config;
+export default config;
diff --git a/app/CONTRIBUTING.md b/app/CONTRIBUTING.md
@@ -5,6 +5,7 @@ Welcome to our newest frontend project! We're excited to have you contribute. Th
 ## Project Overview
 
 This project is the next iteration of our application (app-v2), building upon the foundation of app-v1. We're creating a modern, component-based frontend that includes:
+
 - Interactive calculator-related pages with dynamic functionality (Policy, Population, Simulation, etc)
 - Static informational pages (About Us, Learning, API Playground, etc.)
 - Improved user experience and performance
@@ -18,6 +19,7 @@ Before you begin, please refer to the main README.md for development setup and h
 🎨 **Figma Access**: [Design Files Link](https://www.figma.com/design/ZZLB3A5QNYy97d7dBEPpQ8/PE-App-Redesign---Final-Screens?m=auto&t=0MkV9on8ot5RR4Lv-6)
 
 **To get access:**
+
 1. Please visit the link and request access.
 2. Alternatively, please sign up with your email and provide your Figma account email to maintenaners for access. You'll receive an invitation with instructions shortly.
 
@@ -39,14 +41,14 @@ Before you begin, please refer to the main README.md for development setup and h
 
 - For existing contributors: Issues have been or will be assigned to you.
 - For new contributors, look for labels `good first issue` or `help wanted` in our issue tracker and assign yourself.
-These Issues have links and screenshots for the reference app-v1 component that is to be migrated over to app-v2.
+  These Issues have links and screenshots for the reference app-v1 component that is to be migrated over to app-v2.
 
 ### Recommended Progression Path
 
 We recommend contributors follow this learning path:
 
 1. **Start with Components** (Beginner)
-   - Create individual UI components. 
+   - Create individual UI components.
    - Focus on reusability and proper TypeScript types.
    - [Optionally] Write Storybook stories and tests.
 
@@ -57,13 +59,15 @@ We recommend contributors follow this learning path:
 ### Branch Naming Conventions
 
 Use the following format for branch names:
+
 - `feat/[issue-number]-brief-description` (e.g., `feat/123-add-calculator-component`)
 - `fix/[issue-number]-brief-description` (e.g., `fix/456-fix-navigation-bug`)
 - `docs/brief-description` (e.g., `docs/update-contributing-guide`)
 
 ### Development Standards
 
 Our project uses automated code quality tools:
+
 - **ESLint**: `npm run lint` (with eslint-config-mantine)
 - **Prettier**: `npm run prettier` and `npm run prettier:write`
 - **TypeScript**: `npm run typecheck`
-Original file line number
+Diff line change
@@ Expand Up / @@ -33,4 +33,4 @@ const config = { @@
       ],
     };
-    export default config;
+    export default config;