Custom Prompts with .md Extension Not Recognized by Continue IDE Extension

[babblebey]

The Continue IDE extension fails to recognize and load custom prompts when they are saved with a .md extension in the prompts directory, despite documentation indicating this should be supported for multi-line prompts with YAML frontmatter.

Expected Behavior

According to the Continue documentation on prompts, custom prompts should be recognizable when:

1. Placed in the prompts directory
2. Saved as .md files for multi-line content
3. Include YAML frontmatter with invokable: true to make them callable as commands
4. Should provide IDE features like IntelliSense for .md files

Actual Behavior

• Prompts with .md extension (e.g., analyze.md) are not recognized by the Continue extension
• The prompt only becomes available when renamed to use a .prompt extension (e.g., analyze.prompt)
• Using .prompt extension results in:
  • No syntax highlighting
  • No IntelliSense support
  • Poor developer experience due to lack of language server features

Steps to Reproduce

screen-capture.11.webm

1. Create a custom prompt file in your project's working directory's [project]/.continue/prompts/analyze.md with:

   ---
   name: Spec-kit analyze
   description: Perform analysis across project artifacts
   invokable: true
   ---
   
   [Prompt content here]

2. Attempt to invoke the prompt using Continue's command interface

3. Observe that the prompt is not available/recognized

4. Rename file to analyze.prompt

5. Observe that the prompt becomes available but loses IDE support

Environment

• Continue Extension Version: [Please specify your version]

• IDE: VS Code

• OS: Windows

• File Structure:

  .continue/
    prompts/
      analyze.prompt  # Works but no IDE support
      # analyze.md    # Doesn't work despite documentation
  

Current Workaround

Using .prompt extension instead of .md, which works functionally but provides a suboptimal developer experience.

Impact

• Documentation inconsistency: Documented behavior doesn't match actual behavior
• Developer experience: Loss of syntax highlighting and IntelliSense for prompt files
• File organization: .prompt extension is not a standard/documented file type

Proposed Solutions

1. Fix recognition of .md files in prompts directory with YAML frontmatter
2. Update documentation to reflect actual supported file extensions if .md support is not intended
3. Add language server support for .prompt files if this becomes the standard extension
4. Provide clear examples in documentation showing the exact file naming conventions that work