Initial commit

Author: Sahil-u07

.dockerignore

@@ -0,0 +1,5 @@
+node_modules
+.next
+.env
+Dockerfile
+.dockerignore

.eslintrc.json

@@ -0,0 +1,6 @@
+{
+  "extends": "next/core-web-vitals",
+  "rules": {
+    "no-unused-vars": ["warn"]
+  }
+}

.github/ISSUE_TEMPLATE/create-issue-guidelines.md

@@ -0,0 +1,97 @@
+---
+name: "📝 How to Contribute & Create Issues for SSOC S4"
+about: "Step-by-step guide for contributors to help with UniPath during Social Summer of Code Season 4"
+title: "How to Contribute and Create Issues for UniPath | SSOC S4"
+labels: "documentation, help wanted"
+assignees: ""
+
+---
+
+# 👋 Welcome to UniPath Contributors!
+
+Thank you for joining the **UniPath** project and being part of **Social Summer of Code Season 4 (SSOC S4)**!  
+This guide will help you understand **how to contribute** and **how to create or pick issues** to work on easily.
+
+---
+
+## 🔍 What is UniPath?
+
+UniPath is an AI-powered career coach platform that helps users build resumes, get job recommendations, prepare for interviews, and explore career insights — all powered by AI!
+
+Your contributions will help us build new features, fix bugs, improve UI/UX, and make the platform better for everyone.
+
+---
+
+## 🛠️ How to Contribute?
+
+### 1. Fork & Clone the Repository
+
+- Fork the [UniPath GitHub repo](https://github.com/amitkumardemo/UniPath) to your own GitHub account.
+- Clone your fork locally:
+-[git clone](https://github.com/your-username/UniPath.git)
+
+
+### 2. Create a New Branch
+
+- Always create a new branch for your work:
+
+### 3. Work on Your Task
+
+- Build features, fix bugs, or improve documentation.
+- Commit your changes with clear, professional commit messages.
+
+### 4. Push & Make a Pull Request (PR)
+
+- Push your branch:
+
+- Go to the original repo and create a **Pull Request** from your branch.
+- In your PR description, explain what you did and why.
+
+---
+
+## 📝 How to Create Issues?
+
+If you want to add new tasks or improvements, follow these steps:
+
+1. **Write a clear title and description** of the issue.  
+2. Decide the **difficulty level** and add one of these labels:  
+ - 🔰 `Beginner` — for easy tasks, great if you're just starting.  
+ - ⚙️ `Intermediate` — moderate difficulty, for those with some experience.  
+ - 🚀 `Advanced` — challenging tasks, for experienced contributors.  
+3. Add the label **`SSOC S4`** to show it’s part of the Social Summer of Code Season 4.  
+4. Include any helpful links, screenshots, or references to help others understand and start quickly.
+
+---
+
+## 🎯 How to Pick Issues to Work On?
+
+- Browse issues labeled **`Beginner`**, **`Intermediate`**, or **`Advanced`** based on your skill level.  
+- Look for the **`SSOC S4`** label to find tasks eligible for the program.  
+- Comment on the issue if you want to work on it or need help.  
+- Once assigned or approved, start working and follow the contribution steps above.
+
+---
+
+## 💡 Tips for Smooth Contribution
+
+- Always sync your fork before starting new work:
+- Ask questions if you’re stuck — maintainers and PAs are happy to help!  
+- Keep your commits clean and descriptive.  
+- Follow the project's coding style and guidelines.  
+
+---
+
+## 📅 Important Dates
+
+- Contribution period starts: **14th June**  
+- Make sure to complete and submit your PRs within the SSOC S4 timeline.
+
+---
+
+Thanks for contributing to **UniPath**! Your help is valuable in building a powerful AI career platform for everyone.  
+Happy coding! 💙
+
+---
+
+*— UniPath Team 🚀*
+Amit Kumar Project Admin

.github/workflows/auto-ssoc-label.yml

@@ -0,0 +1,19 @@
+name: Auto-label SSOC S4
+
+on:
+  pull_request_target:
+    types: [opened]
+
+jobs:
+  add-label:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+
+    steps:
+      - name: Add SSOC S4 label to PR
+        uses: actions-ecosystem/action-add-labels@v1
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          labels: SSOC S4

.github/workflows/greetings.yml

@@ -0,0 +1,16 @@
+name: Greetings
+
+on: [pull_request_target, issues]
+
+jobs:
+  greeting:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+    steps:
+    - uses: actions/first-interaction@v1
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        issue-message: "Message that will be displayed on users' first issue"
+        pr-message: "Message that will be displayed on users' first pull request"

.github/workflows/label.yml

@@ -0,0 +1,22 @@
+# This workflow will triage pull requests and apply a label based on the
+# paths that are modified in the pull request.
+#
+# To use this workflow, you will need to set up a .github/labeler.yml
+# file with configuration.  For more information, see:
+# https://github.com/actions/labeler
+
+name: Labeler
+on: [pull_request_target]
+
+jobs:
+  label:
+
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+
+    steps:
+    - uses: actions/labeler@v4
+      with:
+        repo-token: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/labeler.yml

@@ -0,0 +1,27 @@
+SSOC S4:
+  - '**'
+
+Beginner:
+  - 'components/**'
+  - 'public/**'
+  - 'starter/**'
+
+Intermediate:
+  - 'hooks/**'
+  - 'data/**'
+  - 'lib/**'
+
+Advanced:
+  - 'prisma/**'
+  - 'middleware.js'
+  - 'next.config.mjs'
+
+documentation:
+  - '**/*.md'
+  - 'docs/**'
+
+bug:
+  - '**/*.js'
+  - '**/*.jsx'
+  - '**/*.mjs'
+  - '**/*.ts'

.github/workflows/summary.yml

@@ -0,0 +1,34 @@
+name: Summarize new issues
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  summary:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      models: read
+      contents: read
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Run AI inference
+        id: inference
+        uses: actions/ai-inference@v1
+        with:
+          prompt: |
+            Summarize the following GitHub issue in one paragraph:
+            Title: ${{ github.event.issue.title }}
+            Body: ${{ github.event.issue.body }}
+
+      - name: Comment with AI summary
+        run: |
+          gh issue comment $ISSUE_NUMBER --body '${{ steps.inference.outputs.response }}'
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          ISSUE_NUMBER: ${{ github.event.issue.number }}
+          RESPONSE: ${{ steps.inference.outputs.response }}

.gitignore

@@ -0,0 +1,44 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.*
+.yarn/*
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/versions
+
+# testing
+/coverage
+
+# next.js
+/.next/
+/out/
+
+# production
+/build
+
+# misc
+.DS_Store
+*.pem
+
+# debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.pnpm-debug.log*
+
+# env files (can opt-in for committing if needed)
+.env*
+
+# vercel
+.vercel
+
+# typescript
+*.tsbuildinfo
+next-env.d.ts
+
+# clerk configuration (can include secrets)
+/.clerk/