# @docs on per project base **URL:** \ **Category:** Feature Requests\ **Created:** [January 2, 2024, 1:01pm UTC](https://forum.cursor.com/t/docs-on-per-project-base/2257 "2024-01-02T13:01:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![leoing](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leoing](https://forum.cursor.com/u/leoing)\ **Post date:** [January 2, 2024, 1:01pm UTC](https://forum.cursor.com/t/docs-on-per-project-base/2257/1 "2024-01-02T13:01:00Z")
I switch back between BE (django + extensions docs) and FE (flutter + packages docs) work often. As I understand, too much context can confuse the LLM. Thus I would like to have - django docs context only in my django project - flutter docs context only in flutter project Just like last chats are bound to project. TY! ---
**Author:** ![Jakob](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jakob/32/93_2.png) [@Jakob](https://forum.cursor.com/u/Jakob)\ **Post date:** [January 11, 2024, 9:55pm UTC](https://forum.cursor.com/t/docs-on-per-project-base/2257/2 "2024-01-11T21:55:56Z")
When you @ a doc in chat it’s bound to that chat convo and will be used for every message. So you could @ the Django docs in your Django project chats and the Flutter docs in your Flutter project chats. ---
**Author:** ![Willardgmoore](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/willardgmoore/32/16456_2.png) [@Willardgmoore](https://forum.cursor.com/u/Willardgmoore)\ **Post date:** [December 18, 2024, 6:27pm UTC](https://forum.cursor.com/t/docs-on-per-project-base/2257/3 "2024-12-18T18:27:56Z")
@leoing Yes! this is exactly what I want to see as well. I would love to have `.cursordocs` file in my repo to manage the docs! I [prematurely created an issue ticket in github](https://github.com/PatrickJS/awesome-cursorrules/issues/21) before I found this forum. I have found the `.cursorreules` file to be amazingly helpful for defining app configurations like which dependencies I am using on a per project basis. I have been relying on docs for any of the more domain specific language needs for each dependency. Here is an example with some wishful thinking about implementation. ```auto .cursorrules ... 6. Error Handling: - Use Honeybadger.notify for exceptional cases ``` ```auto .cursordocs ... { "honeybadger gem docs": "https://docs.honeybadger.io/lib/ruby/" } ``` If I am not mistaken, the docs helps reduce the scope of what the AI is focusing on which is very helpful for guiding it to do specific things. I do not use the same tools in every project and would like to help the AI understand the configuration of the app as well as be able to refer to various docs on an as needed basis. * * * _**Porting comment from [Github Issue](https://github.com/PatrickJS/awesome-cursorrules/issues/21)**_ > I have found that including docs in my requests have made cursor so much better and would love to have them included in the repo by default. When I am working with a specific API, I add the docs to the cursor docs, but then I have to let the rest of the team know to do the same. It has helped immensely. I also have specific configurations I use for the tech stack of a project. I may use Stripe, braintree, paypall, paddle or something else on a per project basis and having the docs be dynamically included in a .cursordocs file would be awesome! > > ![Screenshot 2024-12-18 at 10.13.01 AM](https://us1.discourse-cdn.com/cursor1/original/3X/a/5/a521ba247d5bddb78458593ae2029b89a148986c.png) ---
**Author:** ![leoing](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leoing](https://forum.cursor.com/u/leoing)\ **Post date:** [December 19, 2024, 3:08pm UTC](https://forum.cursor.com/t/docs-on-per-project-base/2257/4 "2024-12-19T15:08:45Z")
Can actually stay like it is. Need to @ mention anyway, so all docs all the time is fine. ---
**Author:** ![Willardgmoore](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/willardgmoore/32/16456_2.png) [@Willardgmoore](https://forum.cursor.com/u/Willardgmoore)\ **Post date:** [January 28, 2025, 8:51am UTC](https://forum.cursor.com/t/docs-on-per-project-base/2257/5 "2025-01-28T08:51:18Z")
The issue is in collaborating across a team. All docs all the time is great, but what about adding them to each machine for each member of the team? Or when additional docs are added? It doesn’t necessarily need to be project-specific, but that seems the easiest way to share the context with others. ---
**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\ **Post date:** [January 28, 2025, 9:01pm UTC](https://forum.cursor.com/t/docs-on-per-project-base/2257/6 "2025-01-28T21:01:15Z")
When you add docs to your Cursor instance, you should have a ‘Share with Team’ toggle, which will make them available to all the members of your team! ---
**Author:** ![jefer94](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jefer94/32/38100_2.png) [@jefer94](https://forum.cursor.com/u/jefer94)\ **Post date:** [March 24, 2025, 8:22pm UTC](https://forum.cursor.com/t/docs-on-per-project-base/2257/7 "2025-03-24T20:22:05Z")
I added a doc and no one file was created or edited, `.cursordocs` does not do anything ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [June 18, 2026, 10:35am UTC](https://forum.cursor.com/t/docs-on-per-project-base/2257/8 "2026-06-18T10:35:09Z")