Add Cursor IDE rule: enforce Bun over Node/npm/pnpm/Vite

[Copilot]

The repo lacked a Cursor IDE project rule codifying the existing tooling decision to use Bun for the Nexus AI Gateway backend (and any future JS/TS work in the ecosystem).

Changes

• .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc — new Cursor rule (always-applied, scoped to JS/TS/config files) that:
  • Maps every forbidden tool to its Bun equivalent (npm install → bun install, npx → bunx, ts-node → bun, etc.)
  • Prohibits generating package-lock.json / pnpm-lock.yaml; mandates bun.lockb
  • Notes Nixpacks/Coolify auto-detection of bun.lockb as a deployment-time benefit

Original prompt

hola

[Chronological Review: The conversation began with the user requesting an analysis of their work area and projects. The user then shifted focus to a deeper analysis of the ecosystem. Following this, the user greeted with "hola," indicating a possible change in direction or a pause in the technical discussion.]

[Intent Mapping:

1. "analiza el area de trabajo todos los proyectos" - The user requested a comprehensive analysis of their work area and all projects.
2. "analiza a fondo ecosystem" - The user sought a detailed analysis of the ecosystem.
3. "hola" - A casual greeting, possibly indicating a shift in focus or a break in the technical discussion.]

[Technical Inventory: No specific technologies, frameworks, or architectural decisions were mentioned in the recent exchanges. The focus was primarily on analysis requests.]

[Code Archaeology: The user is currently working on a file located at "c:\Users\ramse\OneDrive\Documents\vacas\AI_infi.cursor\rules\use-bun-instead-of-node-vite-npm-pnpm.mdc." However, no specific code changes or discussions about functions were documented in the recent messages.]

[Progress Assessment: The user has made requests for analysis but has not yet received any responses or completed tasks related to those requests.]

[Context Validation: The conversation context is centered around the user's requests for analysis, with no additional context provided for continuation.]

[Recent Commands Analysis:

• Last Agent Commands: The user issued commands to analyze their work area and ecosystem.
• Tool Results Summary: No tool results were generated as the requests were not executed yet.
• Pre-Summary State: The agent was actively awaiting further instructions or responses to the analysis requests when the token budget was exceeded.
• Operation Context: The commands were executed in line with the user's goal of understanding their projects and ecosystem better.]

1. Conversation Overview: - Primary Objectives: 1. "analiza el area de trabajo todos los proyectos" - Request for a comprehensive analysis of the work area and all projects. 2. "analiza a fondo ecosystem" - Request for a detailed analysis of the ecosystem. 3. "hola" - A casual greeting indicating a possible shift in focus. - Session Context: The conversation has focused on analysis requests without any technical execution or responses yet. - User Intent Evolution: The user initially sought a broad analysis and then narrowed down to a specific focus on the ecosystem.

2. Technical Foundation:

• No specific technologies or frameworks were discussed in the recent exchanges.

3. Codebase Status:

• File Name: use-bun-instead-of-node-vite-npm-pnpm.mdc
• Purpose: This file is likely related to project configurations or rules regarding the use of Bun instead of Node.js with Vite and package managers like npm or pnpm.
• Current State: No modifications or changes have been discussed in detail.
• Key Code Segments: Not applicable as no specific code was provided.
• Dependencies: The file may relate to project setup and configuration but specifics were not discussed.

4. Problem Resolution:

• Issues Encountered: No specific technical problems or challenges were mentioned.
• Solutions Implemented: No solutions have been discussed as the requests for analysis have not been executed.
• Debugging Context: No ongoing troubleshooting efforts were noted.
• Lessons Learned: No insights or patterns have been discovered yet.

5. Progress Tracking:

• Completed Tasks: No tasks have been completed as the user has only made requests for analysis.
• Partially Complete Work: The analysis requests are pending execution.
• Validated Outcomes: No features or code have been confirmed working through testing.

6. Active Work State:

• Current Focus: The user is focused on analyzing their work area and ecosystem.
• Recent Context: The last few exchanges involved requests for analysis without any responses.
• Working Code: No specific code snippets were discussed recently.
• Immediate Context: The user was seeking analysis when the token budget was exceeded.

7. Recent Operations:

• Last Agent Commands: The user requested analysis of their work area and ecosystem.
• Tool Results Summary: No results were generated as the requests were not executed yet.
• Pre-Summary State: The agent was awaiting further instructions or responses to the analysis requests.
• Operation Context: The commands were executed to align with the user's goal of understanding their projects and ecosystem better.

8. Continuation Plan:

• [Pending Task 1]: Execute the analysis of the work area and all projects.
• [Pending Task 2]: Conduct a detailed analysis of the ecosystem.
• [Priority Information]: The analysis requests are the most urgent tasks to address.
• [Next Action]: Await further instructions or responses to the analysis requests from the user.

Creado a partir de VS Code.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.