create-prompt

To create standardized prompts for Sidecar workspaces, you apply a template with fields like name, ticketMode, and body, then save it to project or global config.json files to ensure consistency across agents.

Template variables in Sidecar workspace prompts are placeholders that support flexible initialization and updates. They allow you to inject dynamic values into the prompt body across global and project scopes without rewriting the entire configuration.

You override prompt configurations in a specific project scope by applying scope overrides to the project-level config.json file. This ensures project-specific prompt settings take precedence over global workspace configurations.

Yes, setting up Sidecar workspace prompts requires knowledge of how config.json files are organized. You need to understand prompt fields including name, ticketMode, and body to correctly initialize or update the configuration.

Yes, you can update an existing prompt in a global config file without creating a new one. The process supports modifying current prompts by applying template variables and scope overrides directly to the global configuration.

The best way to standardize agent configuration prompts across multiple workspaces is using standardized templates with scope overrides. This reduces setup time and ensures consistency by managing prompts through global and project config.json files.