project recommendations using Groq

[Userunknown84]

Summary [required]

->I use the groq api key to show projects simultaneously and no stored project , fetch directly from api.
->Project , code everything fetch thorugh api and no stored project .
-> For this i used a model "llama" to show projects when user enter skill then project show thorugh this model.

Related Issue [required]

Closes #

Type of Change [required]

• Bug fix — resolves a broken behaviour
• Feature — adds new functionality
• Data — adds new projects to data/projects.json
• Documentation — updates docs, README, or code comments only
• Style — CSS or visual changes only, no logic change
• Refactor — restructures code without changing behaviour
• Test — adds or updates tests

What Was Changed [required]

File	Change made
utils/recommender.py	Added clear_cache() function
tests/test_basic.py	Added test for cache invalidation

How to Test This PR [required]

1. Clone this branch: git checkout your-branch-name
2. Install dependencies: pip install -r requirements.txt
3. Run the app: python app.py
4. Open http://127.0.0.1:5000 and...
5. Run the tests: python tests/test_basic.py

Expected test output:

27 passed, 0 failed out of 27 tests

Test Results [required]

paste output here

Screenshots (if UI change)

Before	After
screenshot	screenshot

Self-Review Checklist [required]

• I have read CONTRIBUTING.md and followed all guidelines
• My branch name follows the convention: feat/, fix/, docs/, data/, style/, test/
• I have run python tests/test_basic.py and all 27 tests pass
• I have run flake8 . locally and there are no errors
• I have not introduced any print() or console.log() debug statements
• Every new function I wrote has a docstring
• I have not modified files outside the scope of the linked issue
• If I changed the UI, I tested it at 375px (mobile) and 1280px (desktop)
• If I added a project to the dataset, it has all required JSON fields

Notes for Reviewer

[vercel]

@Userunknown84 is attempting to deploy a commit to the komalsony234-1530's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Userunknown84]

Hi, please tell me if this is okay, as I'm trying with the API this time. Please tell me if it's accepted or rejected.

…

On Thu, 28 May, 2026, 2:54 pm vercel[bot], ***@***.***> wrote: *vercel[bot]* left a comment (komalharshita/DevPath#668) <#668 (comment)> @Userunknown84 <https://github.com/Userunknown84> is attempting to deploy a commit to the *komalsony234-1530's projects* Team on Vercel <https://vercel.com>. A member of the Team first needs to authorize it <https://vercel.com/git/authorize?team=komalsony234-1530's%20projects&slug=komalsony234-1530s-projects&teamId=team_4uoKBbp41VaIZKo2f2nQAKNx&type=github&job=%7B%22headInfo%22%3A%7B%22sha%22%3A%227a1d75698dc8e91049d038974d6d8d3d051c4a01%22%7D%2C%22id%22%3A%22QmcsqnrRtmYQoFKwcD8h8xRdAAVkraVuL4jdHxGFHxqWxd%22%2C%22org%22%3A%22komalharshita%22%2C%22prId%22%3A668%2C%22repo%22%3A%22DevPath%22%7D> . — Reply to this email directly, view it on GitHub <#668?email_source=notifications&email_token=BC5FCOIS7ORVWTIR3RXVK4345AAT7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJWGI2TINZZGQ42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4562547949>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC5FCOMR3U3O5MPAODVGMPT45AAT7AVCNFSM6AAAAACZQSTBD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKNRSGU2DOOJUHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[komalharshita]

Thank you for the contribution.

I reviewed the changes and appreciate the effort to explore AI-generated project recommendations.

However, this PR fundamentally replaces DevPath's existing recommendation engine with an external Groq-based workflow. This introduces a mandatory external dependency, requires API key configuration, removes existing validation logic, changes core application behavior, and adds significant maintenance and deployment complexity.

The implementation also assumes AI responses will always return valid JSON, exposes exception details in API responses, introduces additional frontend changes unrelated to the primary feature, and does not include automated tests to validate the new behavior.

Because this proposal changes the architecture of the project rather than addressing a specific issue within the current system, it is not suitable for merging in its current form.

For these reasons, I’m closing this pull request.

Thank you for contributing to DevPath.