Project Settings

Add new prompts to the project.

:

:

Write here the directive that will be sent to the LLM to accomplish the task.

:

Displays information on the word count and an estimated token cost of the prompt.

Activate or deactivate the task at any time without deleting it.

Note that LLMs always receive task directives with predefined context and rules.

Options for refining these elements are presented later.

Create and select a variable group.

Right-clicking on a group allows you to delete it, as well as all variables it contains.

Once a group is selected, use this button to create a new variable within it.

Variables are displayed in containers, with quick actions in the header to:

Enter the keywords (tags) or regular expression (regex) that will allow the system to identify this variable.

For example, a text capture pattern will rely on these tags or this regex to find a match.

The default mode uses keywords (tags).

Activate this mode to use a regular expression, offering more flexibility and dynamism.

Example: `/actor\\d+/` avoids having to manually define tags like « actor1 », « actor2 », « actor11 », etc.

Write a note for the user, which will be displayed in tooltips but not sent to LLMs.

Avoid describing sensitive content if you are versioning the project, as these notes are saved in `.lsde` files.

This description provides directives to the LLM when the variable is included in the context of a query.

It can describe a character's personality, world elements, or even formatting rules (Markdown, JSX, HTML...).

Associate an icon (image or emoji) that will represent the variable in editors and menus.

Add a larger image, displayed in tooltips to provide better visual context to the user.

Images are automatically compressed and saved with the project to facilitate sharing.

Define a text and background color.

These colors will take priority if the variable is associated with a pattern or another visual element.

Add optional information that will be displayed in the decoration section of the tooltip.

Insert an external link in the tooltip, which will open in your default browser.

Redefine the variable's name when it is associated with a voice.

By default, its label is used; otherwise, its UUID.

Allows the variable to be included in suggestion triggers during input.

The variable's tags will be used as suggestions.

Displays statistics on the variable's usage in the project.

Create a new pattern, either from a predefined template or from scratch.

Define a pattern to reference other project keys (« nesting » mechanism), if your game engine or framework supports it.

For example, if you use

.

Enter your regular expression.

It is not necessary to escape curly braces `{}`.

Add additional decorators in addition to the initial capture, then associate them with the capture groups of your regular expression.

The initial decorator defines the rendering of the text captured by the regular expression in the editor.

Initial decorators must be of « inline » type and cannot be « widgets ».

Assign the capture group and the desired rendering type for additional decorators.

Define the context's ID, label, and separator.

For example, to manage plurals with i18next:

`name_space.folder.key_context`

would become:

`game.common.welcome-to-my-shop_one`

`game.common.welcome-to-my-shop_many`

`game.common.welcome-to-my-shop_other`

More information on

Define the suffixes (tags) that will be used to identify each context variant.

Write here the description that will be sent to the LLM when it processes a key using this context.

Choose the character used as the context delimiter.

Periods are not allowed.

Indicate the path to your project's root folder, containing the source files that use translation keys.

Specify folders and files to exclude from analysis to optimize performance.

Separate entries with commas.

Use full folder names or file names (with extension).

A label or note to easily identify the pattern and its role.

Insert or modify your regular expression.

The number of detected capture groups is displayed below.

Associate the capture group that corresponds to the namespace of your keys (optional).

Automatically suggests the correct namespace when creating keys.

Associate the capture group that corresponds to the key itself (without the namespace).

Keys should not contain a namespace; use the dedicated field for this purpose.

Associate the capture group that corresponds to the default text.

In software projects, developers often insert default text for a quick UI/UX preview.

Associate the capture group that corresponds to the context (e.g., plural).

Name of the class that will export the keys.

Name of the generated file.

Destination folder for the exported file.

Language of the generated JSDOC comments.

Maximum length of JSDOC comments.

Replacement character for periods (`.`).

In JS/TS, periods are not allowed in key names; the converter will automatically create string literals as keys.

Include the namespace in the generated keys.

Include contextual keys (with suffixes).

It is generally not necessary to include these keys, as their management is handled by your internationalization framework.

Define the trigger to display all project keys.

Useful for projects using internal dictionaries and cross-references.

Choose a modifier key (e.g., Ctrl, Alt) for the trigger (optional).

Specify the letter or symbol which, combined with the modifier key, will activate suggestions.

A name to easily identify this trigger in the interface.