Skip to content
This repository was archived by the owner on Jul 8, 2025. It is now read-only.
This repository was archived by the owner on Jul 8, 2025. It is now read-only.

[Task]: Make the prompt database more prominent #286

Description

@lukehinds

Description

Prompts should be easier to find / more up front.

The prompt database is a really cool feature, as one thing is clear when browsing reddit, there are a lot of threads of people sharing prompts with each other.

At present the prompts catalog feels a little hidden away:

You need to navigate Workspace -> Manage Workspaces -> Select a Workspace -> Use a Preset

“Use a Present” could, on face value, leave a user thinking its where they set their own presets. It’s not too far a stretch then that they disqualify visiting there, as they have not created any presets yet.

However when you go there, this beauty opens up!

Image

A proposal could be to have a top level ‘Prompts Database’ menu item

This could then open up the above, and instead of ‘Use prompt’ it could be ‘Assign to workspace’.

We can then always keep the existing entry button ‘Use Present’.

Additional Context

No response

Activity

  1. lukehinds commented on Feb 9, 2025

    @lukehinds
    Author
  2. kantord commented on Feb 13, 2025

    @kantord
    Member

    This kinda also relates to @danbarr's ideas about making this feature more generic, such as actually allowing the user to create their own presets as well, and making it a separate feature with it's own table in the database

  3. kantord commented on Feb 13, 2025

    @kantord
    Member

    This is technically a little bit separate from the idea of making it more prominent on the dashboard, but maybe we could also have a "cli" command for this? Like you type this in Cline, or whatever AI assistant:

    codegate workspace prompt
    

    which would give you a localhost link. Clicking that link you are able to pick a preset using this UI and save it for the currently active workspace automatically?

  4. jhrozek commented on Feb 17, 2025

    @jhrozek

    @jtenniswood please move to other columns if you start working on this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions