Skip to content
SecondStack SecondStack SecondStack Docs

Custom Prompts

Custom Prompts in SecondStack help you automate repetitive tasks by saving frequently used prompts and running them as slash commands from any conversation. Write a prompt once, store it as a /command with fillable {{variables}}, and reuse it in any thread instead of typing it again from scratch.

Full transcript lightly edited for readability

Tutorial overview (00:00). Hi everyone, and welcome to the SecondStack tutorial. In this video I’d like to tell you about custom prompts and commands in SecondStack. I’ll explain the problem this feature solves, and then I’ll show you how to create your own custom prompt and how you can use it in a chat.

Why use Custom Prompts? (00:18). First, let’s take a look at a slide I prepared, just to understand the problem. The main problem is repetition. Sometimes we have long prompts that we have to type from scratch in every new thread, and we don’t want to waste time doing that. The solution is custom prompts: we write a prompt once, store it as a slash command, and then reuse it in the chat. For example, I have a prompt I repeat in chats — translate something into some language. Notice that it uses variables, which is very useful, because we often need the same slash command in different scenarios.

Creating a Custom Prompt (01:25). There are two ways to create a slash command. The first way: type a slash in the message composer, select the create option, and you’ll see the modal for creating a custom prompt. The second way is the settings page, under Custom Prompts — press the button there and you get the same creation modal. Let’s create our first custom prompt; I’ll use the prompt from the slide, and you can see it already uses variables. Once the slash command is saved, it appears in a table where we can manage it: change its visibility or delete it.

Using Slash Commands in a chat (02:38). Back in the chat, let’s use it. I type a slash and select translate. Now I type the text and the language I want to translate into.

Result (03:00). You can see that all the variables we filled in have been substituted into the text. We press enter and get our translation. The test is done, which means we could start a new thread and use the slash command there too.

Summary (03:30). That’s how the Custom Prompts feature works in SecondStack. That’s all I wanted to show you. Thank you for watching, and see you in the next video.

How it works

Section titled “How it works”
  • Create a prompt either from the / menu in the message composer or from Settings → Custom Prompts.
  • Give it a name — it becomes the command itself, shown as /name in the menu (letters, digits, or hyphens; 2–50 characters).
  • Write the prompt text and add fillable fields with {{variable}} syntax — typing {{ auto-completes the closing braces, and the editor validates that every variable is closed.
  • In a chat, type / and select the command. You fill in the variables, the values are substituted into the prompt text, and the message is ready to send.
  • Prompts are reusable across all your threads — create once, run anywhere.

Managing your prompts

Section titled “Managing your prompts”

The Settings → Custom Prompts table lists every prompt with its name, description, and controls:

  • Show in menu — hide a prompt from the / menu without deleting it.
  • Priority — higher values appear higher in the / menu list.
  • Limit to models — optionally show a prompt only for specific models; leave empty to show it everywhere.
  • Delete — remove a prompt permanently (with a confirmation step).
Section titled “Related”