Hey, from the screenshot it looks like three commands are missing from the / command list: backend-develop-code, backend-plan-implement, and sdlc-document, even though the matching files are in .cursor/commands.
A couple things to check:
Check the missing files. Open backend-develop-code.md, backend-plan-implement.md, and sdlc-document.md and make sure they contain valid Markdown. Even a small encoding issue or an unexpected character can break parsing.
Try reloading the window. Press Ctrl + Shift + P, then run Developer: Reload Window, and check the list again.
If the commands still don’t show up after that, paste the contents, or just the first few lines, of one of the missing files here and I’ll check for formatting issues.
It looks like this has not been resolved and the bug was closed, so, how do you intend to solve this if the system closes the reported bugs? that’s why I had to go back to version 2.2.44 that is the version this is working fine, and it seems I will have to go back to this version again.
See the content:
name: Backend Code Generation
description: Generates production-ready C# code following the implementation plan.
steps:
instruction: Follow the detailed instructions provided in the markdown body below.
SDLC Command: Backend Code Generation (C#/.NET 9)
Role
You are a Code Generation Engine with deep knowledge of C#/.NET 9 and the project’s AGENTS.md standards (DDD, Hexagonal Architecture, SOLID).
Instructions
Input: The input is a detailed Implementation Plan (e.g., feature-x-backend-plan.md) and a specific file to be generated/modified.
Execution: Generate the clean, production-ready code for the specified file in the user prompt, generate or modify the C# code following the provided plan and the architecture rules. Ensure proper use of C# features and follow the established project structure (e.g., Domain Services, Application Services, Repositories).
Cross-Project Refactoring (CRITICAL ADDITION):
If the Implementation Plan involves changes (new properties, removed properties, or model refactoring) to any Domain Entity (e.g., User, Person, Tenant, Role, Module, Permission), you MUST include a separate step to check and refactor the Conexys.Scripts project, specifically the GlobalSuperUserSeederService.cs file.
The AI must analyze the affected entity and update the corresponding seeding methods (e.g., SeedSystemUserAsync, SeedGlobalSuperUserAccountAsync, SeedFirstClientTenantAsync) to accommodate the new or changed properties, ensuring the seeder remains functional and correctly initializes the database.
Output: Only output the complete, final code for the requested file, including tests if requested in the user prompt. Use a language code block (e.g., ```csharp).
Review: Ensure the generated code is clean, adheres to best practices, and includes necessary documentation comments.
Code Hygiene Mandate: Produce “Naked Code” where possible. Avoid all redundant comments, explanations of removal, or descriptions of self-explanatory methods. The generated file should be production-ready and free of conversational “AI noise.”.
6.1. DTO Generation Rules:
Always generate DTOs without any validation attributes (e.g., no [Required]).
For every new DTO, you MUST also generate a corresponding AbstractValidator<T> class using FluentValidation.
Example: CreateCatalogItemRequestDto requires a CreateCatalogItemRequestDtoValidator.
[Example Usage: Generate the new Domain Service file]
Generate the code for src/Domain/Services/NewFeatureService.cs based on the implementation plan (feature-x-backend-plan.md) pasted below.
[Paste Full Content of Implementation Plan (Output from /backend-plan-implement) Below]
name: Backend Plan Implement
description: Creates a detailed, file-by-file implementation plan from a technical specification.
steps:
instruction: Follow the instructions below to generate a development plan document.
SDLC Command: Implementation Development Plan
Role
You are a Senior Software Developer. Your task is to generate a detailed, file-by-file plan to implement the provided Technical Specification.
Instructions
Read and Understand: Analyze the Technical Specification (pasted input) and the project’s AGENTS.md rules.
Context Extraction (CRITICAL): The AI MUST parse the input content (Technical Specification) to extract the values for Group Sequence and Feature Name from the ### 🏷️ Feature Metadata block. These extracted values will be used for the output file naming and the plan’s internal metadata.
File Modification Plan: List every file that needs to be created, modified, or deleted, focusing ONLY on application code (Domain, Application, Infrastructure/Persistence entities/configs). For each, describe the intended change based on the Hexagonal/DDD architecture (e.g., ‘Create new Domain Service for [Feature]’).
Database Artifact Exclusion (CRITICAL):DO NOT include the EF Core Migration file (*.cs) or its designer file (*.designer.cs) in the list of files to be created/modified in this plan. Migration creation is the exclusive responsibility of the subsequent /backend-generate-migration command.
Code Outline: For complex components (e.g., a new Repository interface/implementation), provide a high-level pseudo-code or code outline.
Testing Strategy: Define the required unit tests, mocking strategy, and coverage goals, linking back to the AGENTS.md testing rules.
Deliverable: The final output is the detailed plan for the next command (/backend-develop-code).
Output Template (Strictly Follow This Structure)
Feature Metadata
Key
Value
Group Sequence
[Extracted Group Sequence]
Feature Name
[Extracted Feature Name]
Development Plan for: [Feature Name]
1. Files to Modify/Create
src/domain/services/NewService.ts: [Action to take]
src/application/controllers/NewController.ts: [Action to take]
src/infrastructure/adapters/Repository.ts: [Action to take]
tests/unit/NewService.test.ts: [Action to take]
// … Ensure NO MIGRATION FILES are listed here.
2. Key Implementation Decisions
DDD/Architecture: [How the change respects the Hexagonal/DDD structure]
Trade-offs: [Any identified design compromises]
3. Testing Plan
Unit Tests: [List key test cases/scenarios]
Mocks: [Identify which dependencies must be mocked]
INPUT: Technical Specification Content Below
[Paste Full Content of Technical Specification (Output from /sdlc-plan-spec) Below]
AGENT INSTRUCTIONS (For Direct File Generation)
When run in Agent Mode, write the final output directly to:
Hey! Sorry the previous thread auto-closed before we could dig into this.
I can see the files you shared. The frontmatter and the markdown structure look correct, so this isn’t a formatting issue on your side.
This is a known bug with global command detection that showed up in version 2.4. The team is aware, and your reports help us prioritize it.
For now, staying on v2.2.44 is a solid workaround. One more thing to try on the latest version: move the affected commands into a project-level .cursor/commands folder inside your workspace, not the global folder, and see if they show up there. It’s possible the regression only affects the global path %USERPROFILE%\.cursor\commands.
SDLC Command: Backend Code Generation (C#/.NET 9)
Role
Instructions
SDLC Command: Implementation Development Plan
Output Template (Strictly Follow This Structure)
Feature Metadata