Create invokable markdown prompt instead of .prompt file

[RomneyDa]

Description

Re-implementation of #9677 with fixes:

1. Changed to create invokable markdown prompt files instead of legacy .prompt files

   • Uses config/addLocalWorkspaceBlock with blockType: 'prompts'
   • Creates markdown-based prompt files in .continue/prompts/ directory
   • These prompts are invokable via slash commands (e.g., /new-prompt)
   • Follows the current Continue configuration system

2. Removed Continue Hub link from Help section

   • The hub is no longer actively maintained
   • Removed unhelpful link to reduce UI clutter

Changes

• gui/src/components/mainInput/TipTapEditor/utils/getSuggestion.ts: Changed "Explore prompts" button to "Create a prompt" that creates a local invokable markdown prompt file
• gui/src/pages/config/sections/HelpSection.tsx: Removed Continue Hub link from Resources section

Why markdown prompts instead of .prompt files?

The new system uses markdown files with YAML frontmatter:

• More flexible and maintainable
• Supports invokable: true flag for slash command access
• Integrates better with the current workspace block system
• Consistent with rules and other configuration files

Testing

Manually tested:

1. Empty slash command dropdown shows "Create a prompt" option
2. Clicking creates a new invokable markdown prompt file in .continue/prompts/
3. Help section no longer shows Continue Hub link

---

Fixes #9677

Co-authored-by: dallin dallin@continue.dev

---

Continue Tasks: ▶️ 2 queued — View all

---

Summary by cubic

Replaced the legacy .prompt flow with invokable markdown prompts and removed the outdated Continue Hub link. Users can now create local prompts that work with slash commands.

• New Features

  • Added “Create a prompt” in the empty slash-command dropdown. Generates a markdown prompt in .continue/prompts via config/addLocalWorkspaceBlock (blockType: prompts). Prompts are invokable (e.g., /new-prompt).

• Refactors

  • Removed the Continue Hub link from Help > Resources.

^{Written for commit 8e80187. Summary will update on new commits.}

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ Continue API authentication failed. Please check your CONTINUE_API_KEY.

---

[cubic-dev-ai]

No issues found across 2 files