You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/customize/deep-dives/prompt-files.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
title: Prompt files
3
3
---
4
4
5
-
Prompt files provide a convenient way to standardize common patterns and share a collection of LLM prompts with your team. They make it easy to build and use these prompts.
5
+
Prompt files allow you to build and use local prompts, and provide a convenient way to test and iterate on prompts before publishing them to the Hub.
6
6
7
-
On the [hub](../../hub/introduction.md), prompt files are stored within [prompt blocks](../../hub/blocks/block-types.md#prompts), which show up as [slash commands](../slash-commands.mdx) in Chat. Visit the hub to [explore prompts](https://hub.continue.dev/explore/prompts) or [create your own](https://hub.continue.dev/new?type=block&blockType=rules).
8
-
9
-
Prompt files can also be stored within your project's root directory as `.prompt` files. See below.
7
+
:::info
8
+
Visit the Hub to [explore prompts](https://hub.continue.dev/explore/prompts) or [create your own](https://hub.continue.dev/new?type=block&blockType=prompts)
9
+
:::
10
10
11
11
## Quick start
12
12
@@ -25,7 +25,7 @@ Attached is a summary of the current Ruby on Rails application, including the @G
25
25
26
26
Now to use this prompt, you can highlight code and use <kbd>cmd/ctrl</kbd> + <kbd>L</kbd> to select it in the Continue sidebar.
27
27
28
-
Then, type "@", select "Prompt files", and choose the one called "Rails Project". You can now ask any question as usual and the LLM will have the information from your .prompt file.
28
+
Then, type <kbd>/</kbd> and choose the "Rails Project" prompt. You can now ask any question as usual and the LLM will have the information from your .prompt file.
Copy file name to clipboardExpand all lines: docs/docs/hub/blocks/block-types.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -43,13 +43,13 @@ Prompts blocks are pre-written, reusable prompts that can be referenced at any t
43
43
44
44
Prompt blocks have the same syntax as [prompt files](../../customize/deep-dives/prompt-files.md). There are two important differences between prompt blocks and prompt files:
45
45
46
-
1.Prompt blocks are stored within `config.yaml` rather than `.continue/prompts` in project directory and
47
-
2. Prompt blocks only show up as slash commands in Chat, not under the `@Prompt Files` context provider
46
+
1.Currently, prompt blocks cannot use context providers
47
+
2. Prompt blocks are stored within `config.yaml` rather than `.continue/prompts` in project directory and
48
48
49
49
The `config.yaml` spec for `prompts` can be found [here](../../yaml-reference.md#prompts).
50
50
51
51
## Data
52
52
53
53
Data blocks allow you send your development data to custom destinations of your choice. Development data can be used for a variety of purposes, including analyzing usage, gathering insights, or fine-tuning models. You can read more about development data [here](../../customize/deep-dives/development-data.md). Explore data block examples [here](https://hub.continue.dev/explore/data).
54
54
55
-
Data destinations are configured in the[`data`](../../yaml-reference.md#data) section of `config.yaml`.
55
+
Data destinations are configured in the[`data`](../../yaml-reference.md#data) section of `config.yaml`.
0 commit comments