How to define prompts in project directory / Git working copy?

[stefan-girlich]

I'd like to define prompts in my repository so I can

1. share them with my team
2. maintain and version them
3. create project-specific prompts

E.g. with Cline rules, I simply have a root-level directory in my project:

.clinerules/workflows
├── fetch-notion-task.md
├── i18n.md
├── migrate-server-action-to-api-route.md
├── product-summary.md
├── read-the-docs.md
└── smart-copy-paste.md

It seems that per-project config is not planned, so I wonder if there is a different method to achieve this.

I already tried referencing a prompt file by absolute path in ~/.continue/config.yaml, using explain-invokable.md prompt content from the docs:

# ...

prompts:
  - uses: /Users/me/projects/myproject/.continue/prompts/explain-invokable.md

Unfortunately, this results in an error Failed to load config due to missing blocks, see which blocks are missing below in the Continue panel in VS Code, using extension v1.2.10 or v1.3.24 (pre-release). The error only appears when the prompt file exists.

any ideas?

[stefan-girlich]

I just learned that anything in .continue/prompts does indeed get picked up.
The problem was that I tried to register the prompt explicitly in my config.yaml as the documentation implied:

If you are using a local config.yaml, you can add it to your config like this:

-- https://docs.continue.dev/customize/deep-dives/prompts