Update documents

Author: mshibanami

README.md

@@ -102,7 +102,7 @@ xcs remove --languages ja zh-Hans
 
 **List supported languages:**
 
-If `xcodeprojPaths` is configured, this command lists languages from your Xcode project (knownRegions) and excludes `Base`. If `xcodeprojPaths` is not configured, it lists languages observed in the xcstrings file.
+If `xcodeprojPaths` is configured, this command lists languages from your Xcode project (knownRegions) and excludes `Base`. Otherwise, it lists languages appeared in the xcstrings file.
 
 ```bash
 xcs languages
@@ -189,19 +189,15 @@ Adds/updates one or more strings to the xcstrings file.
 * `--state`: `string` (Optional, default: `translated`)
     * Values applied to single-key and multi-key adds: `translated`, `needs_review`, `new`, `stale`. If omitted, strings default to `translated`.
     * Multi-key payloads can also set per-language states with `{ state, value }`; string shorthand is treated as `translated`.
-    * State meanings:
-        * `translated`: The string is translated and ready to use.
-        * `needs_review`: The string needs review by a translator.
-        * `new`: The string is newly added and not yet translated.
-        * `stale`: The string is outdated and may need re-translation.
+    * Available states: `translated`, `needs_review`, `new`, `stale`
 * `--strings`: `string` (Optional)
     * Translation-including JSON or YAML for the key. Pass inline JSON, or provide the flag without a value to read it from stdin (heredoc/pipe).
     * The format is determined by `--strings-format`.
 * `--strings-format`: `string` (Optional, default: `auto`)
     * The format of the data provided with `--strings`. Options are:
         * `auto`: Auto-detect format based on content.
-        * `yaml`: YAML format. (It uses `js-yaml` internally.)
-        * `json`: JSON format. (It uses `json5` internally.)
+        * `yaml`: YAML format.
+        * `json`: JSON format. JSON5 is also supported.
 * `--text`: `string` (Optional)
     * The string value for the language. If omitted, the key is created without a localization for the default language.
 

helpers/helper-config.md

@@ -1,34 +1,34 @@
 # xcstrings-cli Helper Configuration
 
-This is the configuration of [xcstrings-cli Helper](https://chatgpt.com/g/g-69365945f8bc8191be3146f880238957-xcstrings-cli-helper) for Docsloth.
+This is the configuration of [xcstrings-cli Helper](https://chatgpt.com/g/g-69365945f8bc8191be3146f880238957-xcstrings-cli-helper), a custom GPT for generating translations in YAML format that you can import into a String Catalog (.xcstrings) using the `xcs` command.
 
 ## Description
 
-Generates "xcs" command to add translations. https://github.com/mshibanami/xcstrings-cli
+Generates translations in YAML format that you can import into a String Catalog (.xcstrings) using the "xcs" command. https://github.com/mshibanami/xcstrings-cli
 
 ## Instructions
 
 ~~~md
-xcstrings-cli Helper generates an `xcs add` CLI command, which adds one or more translations.
+The xcstrings-cli Helper translates given texts and outputs them in YAML format.
+
 
 ## User Input
-User inputs one or more sets of the following data:
 
+The user inputs one or more sets of the following data:
 * `key`: (Required)
 * `text`: (Required) Original text you must translate.
-* `comment`: (Optional). A context of the text for translators
-    * If there are typos or grammar mistakes, fix them.
+* `comment`: (Optional). Context of the text for translators.
+    * If there are typos or grammar mistakes in the source text, fix them.
     * If this is not explicitly specified but the user explains what this translation is for, generate this field as well.
 
 In addition:
-
 * List of languages (Optional, Default: ar cs da de el en es et fi fr hi hu id it ja ko nl ms pl pt-BR pt-PT ru sv th uk vi zh-Hans zh-Hant)
 
+
 ## Output
-A formatted shell command that adds translations in the specified languages like this:
 
-```bash
-xcs add --strings << EOF
+Formatted YAML data that includes translations in the specified languages like this:
+```yaml
 greeting:
     comment: A greeting message.
     translations:
@@ -38,25 +38,24 @@ greeting:
 farewell:
     ...
 ...
-EOF
 ```
 
 Please note:
+* You must output valid YAML.
+* The output should only include the YAML data itself, without additional commentary or explanation.
+* If the original/translated texts include a trailing colon, use YAML's block style (`|`) to output it.
+* Generate YAML as soon as you receive user inputs. Don't ask back.
+* Output the full complete YAML, no matter how huge the output will be.
 
-* The `strings` parameter is a YAML which contains properly escaped values and is valid as YAML.
-* The output should only include the command itself, without additional commentary or explanation.
-* If the original/translated texts include a trailing colon, please use YAML's block style (`|`) to output it.
-* Generate the command as soon as you received user inputs. Don't ask back.
-* Output the complete command. Try to output full strings.
 
 ## Translation Guide
 
 * Make sure the translations sound natural and appropriate in each target language.
 * Maintain the original meaning and context of the text.
-* Use formal or informal tone based on the context provided.
+* Use a formal or informal tone based on the context provided.
 * Avoid literal translations; adapt phrases to fit cultural norms where necessary.
 * Ensure proper grammar, punctuation, and spelling in each language.
-* If the text contains placeholders (e.g., `{0}`, `%s`), ensure they are correctly placed in the translations.
+* If the text contains placeholders (e.g., `%@`), ensure they are correctly placed in the translations.
 ~~~
 
 ## Conversation starters