@gspothq/cli 0.0.0-stage → 0.1.1

package/configurations/general/naming/manifest.toml

@@ -0,0 +1,35 @@
+[configuration]
+title = "Naming"
+always_selected = true
+description = "The naming engine: banned terms, case rules, length and word ceilings over every identifier, file, and folder."
+
+[files]
+languages = true
+
+[[check]]
+name = "identifiers"
+example = "`export const userHelper = 1;` reports the banned term `helper`. Rename it after what it holds, such as `userCount`."
+level = "all"
+stage = "commit"
+summary = "Checks every identifier against the naming settings: banned terms, case, length, and word count."
+why = "Names such as `enhancedHandler`, `ensureConfigIfNeeded`, and `utils` do not explain the value or behavior a reader needs to understand."
+help = "Rename after what the thing is or does. Write the exact names under allowed_names in a [[naming.override]] record with a reason, or adjust a ceiling with gspot set naming.`<language>`.max_words."
+
+[[check]]
+name = "paths"
+example = "`utils/format.js` reports `utils`. Move it into the folder of the feature it serves, such as `invoices/format.js`."
+level = "all"
+stage = "commit"
+summary = "Checks every file stem and folder name against the language's case rules and the banned terms."
+why = "A file named `enhanced-utils.ts` is a home for code nobody placed; the case rule keeps imports predictable."
+help = "Rename the file or folder, or add a path rule under [[naming.override]] with a reason."
+
+[[check]]
+name = "settings"
+example = "A naming allowance for an identifier that no selected source contains reports an unmatched settings entry. Remove the obsolete allowance or correct it to the exact required identifier and scope."
+level = "recommended"
+stage = "commit"
+runs = "once"
+summary = "Reports allowed names that no selected source uses."
+why = "An allowed name that nothing uses hides an obsolete exception."
+help = "Remove the entry that matches nothing, or fix its name or path."

package/configurations/general/naming/rules/NAMING.md

@@ -0,0 +1,179 @@
+# Naming
+
+## Casing across languages
+
+<!-- level: all -->
+
+Each language naming file states its own case table. These decisions hold across every language so
+the same concept reads the same way throughout the program.
+
+| Concern               | Rule                                                                                                                                                                                                                                                                                                                                            |
+| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Acronyms              | Follow the language: TypeScript, JavaScript treat them as words such as `parseHttpUrl`, `userId`; Swift keeps uppercase initialisms (`avatarURL`, `userID`, `apiClient` at the start of a name); Python, SQL, Bash lowercase them inside snake_case such as `http_url`, `user_id`. A platform name keeps its spelling such as `XMLHttpRequest`. |
+| Directories           | kebab-case for TypeScript, JavaScript, Bash, HTML, CSS, and static sites; snake_case for Python packages; PascalCase for Swift directories, which mirror type names.                                                                                                                                                                            |
+| On the wire           | Preserve existing external interfaces. For interfaces defined by the project, use camelCase JSON fields, kebab-case URL segments.                                                                                                                                                                                                               |
+| Environment variables | `UPPER_SNAKE_CASE`, named by the external interface. No application prefix is required; names defined by the platform are kept verbatim.                                                                                                                                                                                                        |
+| Constants             | Module-level constants bound to a literal or a frozen object are `UPPER_SNAKE_CASE` in TypeScript, JavaScript, Python, and Bash, and lowerCamelCase in Swift.                                                                                                                                                                                   |
+
+## Authority
+
+<!-- level: all -->
+
+The naming check enforces banned words, case, and length. Fix a finding by renaming. Never hide a
+bad name in a string key, an alias, or a file name.
+
+## Principles
+
+<!-- level: all -->
+
+A name lets a reader understand the concept, scope, role, and expected value without reading
+the implementation. Name by role, responsibility, and domain meaning, never by storage type,
+UI framework type, collection shape, or implementation accident. Use English unless an
+external identifier keeps another spelling. Prefer the shortest name that gives a clear meaning at the use
+site, and add a qualifier only when the bare name has more than one meaning there. Never invent private
+shorthand or drop letters from a word.
+
+Do not repeat context the enclosing type, module, directory, or package already supplies, and
+do not encode every implementation detail. One concept keeps one word across a feature. Use singular names for single values, plural names for collections, and
+named by their contents. A role word carries meaning where a primitive or weak type does not.
+
+| Avoid               | Prefer                        | Why                                 |
+| ------------------- | ----------------------------- | ----------------------------------- |
+| `string`, `dict`    | `welcomeMessage`, `usersById` | The role, not the type.             |
+| `u`, `tmp`, `cfg`   | `user`, `accountSummary`      | Whole words a stranger can read.    |
+| `userArray`         | `users`                       | The type already says array.        |
+| `Car.carMake`       | `Car.make`                    | The type supplies the context.      |
+| `optionalAvatarURL` | `avatarURL`                   | Optionality lives in the type.      |
+| `UserManager`       | `UserRepository`              | The real responsibility.            |
+| `DataProcessor`     | `ProfileImageClient`          | An external API.                    |
+| `CommonUtils`       | `DateRangeFormatter`          | A capability, not a dumping ground. |
+
+## Role words
+
+<!-- level: all -->
+
+A suffix names the role of a type. Use each suffix for one meaning. Name a type with no such role for its concrete domain concept.
+
+| Role word    | Use when                                                             |
+| ------------ | -------------------------------------------------------------------- |
+| `UseCase`    | Application operation or business workflow.                          |
+| `Repository` | Domain-facing access to persisted, cached, or remote domain data.    |
+| `Client`     | External API, SDK, HTTP, storage, or platform protocol.              |
+| `Factory`    | Type that constructs instances and assembles dependencies.           |
+| `Formatter`  | Converts a value into a display or wire representation.              |
+| `Parser`     | Converts raw input into structured data.                             |
+| `Validator`  | Checks a value and returns or throws validation failure.             |
+| `Mapper`     | Converts between explicit layers, such as record to domain.          |
+| `Store`      | Holds local mutable state or persistence mechanics.                  |
+| `Provider`   | Supplies a capability or value, especially when the source may vary. |
+| `Adapter`    | Bridges one interface or framework shape to another.                 |
+
+Use `Route`, `Callback`, `Observer`, and `Listener` only for the corresponding framework shape. The language file for the framework defines UI role words such as `View`, `ViewModel`, `ViewController`, and `Coordinator`. Never use `Manager`. Use `Service` only
+where the framework uses it, such as a NestJS provider. Preserve external names such as Apple's
+`FileManager`.
+
+## Functions and methods
+
+<!-- level: all -->
+
+A function name starts with the action and carries enough domain context to read at the call
+site without repeating the enclosing type or module. A generic verb such as `process`, `handle`, `run`, `execute`,
+`manage`, `perform` never stands where the name can state the action. `handle` exists only in a
+framework callback such as a React `handleSubmit` or a UIKit `@objc handleConfirmButtonTapped`.
+Never use `Handler` as a type suffix. A name that needs `and`, `or`, `with`, or an umbrella verb
+marks a function that combines too many concepts.
+
+A fixed verb vocabulary spares the reader a guess at which synonym a module chose:
+
+| Verb                 | Meaning                                                                         |
+| -------------------- | ------------------------------------------------------------------------------- |
+| `get`                | Retrieve an existing value from memory, cache, file, database, SDK, or API.     |
+| `set`                | Assign or replace current state with the supplied value.                        |
+| `insert`, `update`   | Add or change a row or item in persisted data.                                  |
+| `delete`             | Destroy a durable row, object, or domain value.                                 |
+| `add`, `remove`      | In-memory collection membership only.                                           |
+| `create`             | Make a new independent domain value before persistence.                         |
+| `make`, `build`      | Construct an object or dependency; construct a value from existing values.      |
+| `parse`, `decode`    | Raw input to structured data; encoded bytes or payloads to typed values.        |
+| `encode`             | Typed values to bytes or serialized payloads.                                   |
+| `validate`, `assert` | Report invalidity; stop execution on failure.                                   |
+| `refresh`, `prepare` | Replace presentation state from a source; set up local state before a workflow. |
+| `reset`              | Return to an initial state.                                                     |
+
+Each act keeps one verb across the codebase: once retrieval uses `get`, no module reads, finds,
+fetches, or loads instead. The noun and the return type carry multiplicity and optionality
+such as `getSession`, `getSessions`, and a qualifier appears only to tell apart two operations at one
+use site. Give a domain operation that combines create, read, update, and delete (CRUD) acts its precise domain verb.
+Preserve framework, SDK, generated, and external names exactly.
+
+| Avoid                    | Prefer                   | Meaning                        |
+| ------------------------ | ------------------------ | ------------------------------ |
+| `saveCall`               | `insertCall`             | Insert a new call.             |
+| `handleData`             | `decodeAccountResponse`  | Decode account response bytes. |
+| `process`                | `validateEmailAddress`   | Validate an email address.     |
+| `update`                 | `updateDraftMessageText` | Replace draft message text.    |
+| `mapUserRowToUserDomain` | `mapUser`                | The parameter type says row.   |
+
+Where external data enters, name the conversion for the operation and the concept, `decodeUserResponse`
+rather than `transform`. Shape suffixes such as `Row`, `DTO`, `Request`, and `Response` stay on
+the type that declares the shape and never travel onto domain entities, view models, or the
+functions that accept the shape.
+
+## Booleans and predicates
+
+<!-- level: all -->
+
+Name stored boolean columns and direct domain mappings as concise positive states without a
+prefix: `enabled`, `active`, `retryable`, `webSearchEnabled`. Predicates, computed
+predicates, and presentation-state assertions ask their question with `is` for state, `has`
+for presence, and `can` for capability. Name an action for what it does even when it
+returns a boolean such as `sendInvite`. Name a proposed answer or control parameter
+for its role such as `defaultCountry`; a boolean type does not make a function a
+predicate.
+
+Negative names such as `isNotReady`, `isEmailNotUsed` give way to the positive form that
+matches the branch without double negation. A boolean never reads like a noun value. Preserve external boolean names exactly, including framework, SDK,
+protocol, wire, and generated relationship names.
+
+| Avoid                    | Prefer                 | Meaning                                        |
+| ------------------------ | ---------------------- | ---------------------------------------------- |
+| `SearchPolicy.isEnabled` | `SearchPolicy.enabled` | Stored policy state.                           |
+| `email`                  | `hasEmailAddress`      | Presence of an email address.                  |
+| `textFile`               | `isTextFile`           | Whether a file meets the text-file definition. |
+| `isEmailNotUsed`         | `isEmailUsed`          | Whether an email address is already used.      |
+| `ready`                  | `is_ready`             | A computed readiness predicate in Bash.        |
+
+## Files and directories
+
+<!-- level: all -->
+
+Name files and directories for the behavior or entity they contain, not for reuse.
+
+- Name a file with one primary type after that type where the language does so. Name a module
+  after the capability it implements. Prefer feature folders to top-level type buckets.
+- Move code to a shared place only for a repeated concept with one module that implements it, never for a caller
+  that does not exist yet.
+- A file name avoids the banned terms identifiers avoid. Only a generated artifact may carry a
+  timestamp in its name.
+
+| Avoid              | Prefer                        | Meaning                |
+| ------------------ | ----------------------------- | ---------------------- |
+| `Helpers.swift`    | `DateRangeFormatter.swift`    | Date range formatting. |
+| `LoginStuff.swift` | `LoginView.swift`             | Login presentation.    |
+| `common-utils.ts`  | `email-address-validation.ts` | Email validation.      |
+| `src/helpers/`     | `src/accounts/`               | Account behavior.      |
+
+## External names
+
+<!-- level: all -->
+
+External systems use names that do not match the domain language. Keep those names in code that reads or writes external data.
+
+DTOs, SQL rows, generated types, wire payloads, and validation schemas keep the external field names.
+Renaming one changes the public interface. Translate them into domain names, through explicitly
+named mappings, before the values reach domain or presentation code; provider, database, and HTTP
+mechanics stay out of domain names.
+
+A wire shape such as `MessageAttachmentDTO` keeps `storage_object_path`. The validated
+`MessageAttachment` uses `attachmentPath`, and the module that implements the storage protocol
+converts one into the other.

package/configurations/general/prose/manifest.toml

@@ -0,0 +1,86 @@
+allowed_words = ["Vale", "DOM", "DTO", "RPC"]
+
+[configuration]
+title = "Prose"
+always_selected = true
+description = "Vale over every comment and every documentation file, with the gspot style, and the upstream packages."
+
+[files]
+extensions = [".md", ".mdx", ".ts", ".tsx", ".mts", ".cts", ".js", ".mjs", ".cjs", ".jsx", ".swift", ".css", ".sh", ".bash", ".zsh", ".py", ".sql", ".pgsql", ".psql"]
+tags = ["shebang:shell"]
+
+[[tool]]
+name = "vale"
+version = "3.21.0"
+mise = "vale"
+brew = "vale"
+winget = "errata-ai.Vale"
+scoop = "vale"
+github = { name = "errata-ai/vale", version = "v3.21.0" }
+suppression = { marker = "^<!--\\s*vale\\b", reason = "reason: (?<reason>\\S.*)", forbidden = true }
+[[tool.replace]]
+file = ".vale.ini"
+shared = false
+
+[[tool.replace]]
+file = "_vale.ini"
+shared = false
+
+[[tool.replace]]
+file = "vale.ini"
+shared = false
+
+[[tool_file]]
+target = ".gspot/config/vale.ini"
+tool = "vale"
+rule_keys = ["*.rules", "*.BasedOnStyles"]
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/gspot/acronyms.yml"
+tool = "vale"
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/gspot/alt-text.yml"
+tool = "vale"
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/gspot/banned-headings.yml"
+tool = "vale"
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/gspot/heading-case.yml"
+tool = "vale"
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/gspot/item-length.yml"
+tool = "vale"
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/gspot/paragraph-length.yml"
+tool = "vale"
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/gspot/possessives.yml"
+tool = "vale"
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/gspot/sentence-length.yml"
+tool = "vale"
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/gspot/title-case.yml"
+tool = "vale"
+
+[[tool_file]]
+target = ".gspot/config/vale/styles/config/vocabularies/words/accept.txt"
+tool = "vale"
+
+[[check]]
+name = "vale"
+tool = "vale"
+example = "The sentence `Release on 03/04/2026.` reports an ambiguous date at the recommended level. Write `Release on March 4, 2026.` when March 4 is the intended date, then rerun. Write legitimate project names in the root allowed_words setting."
+level = "recommended"
+stage = "commit"
+summary = "Checks ambiguous dates, link text, and alternative text with bundled Vale styles at level `recommended`. Level `all` adds the complete style and upstream packages."
+why = "Prose that hedges, markets or wanders is read by everyone who reads the code, and nothing else checks it."
+help = "Rewrite the sentence the alert names, write a real name and its reason in the root allowed_words setting, or use gspot ignore prose/vale --rule `<rule>` --reason \"`<why>`\"."

package/configurations/general/prose/rules/WRITING.md

@@ -0,0 +1,31 @@
+# Writing
+
+Write in plain language under `ISO 24495-1`: short sentences and common words. State the action or result early.
+Use familiar words and explain a technical term when the reader needs it.
+
+## Evidence
+
+Check commands, fields, defaults, limits, and supported versions against the implementation that defines them.
+A measurement does not guarantee future results. When evidence lacks required facts, narrow the claim. Link external
+facts to the primary source; never invent behavior to complete a page.
+
+Preserve exact API identifiers, public messages, official product names, and legal license text.
+Keep private reasoning, temporary acceptance notes out of shipped content.
+Examples use fictional people, safe values, and `example.com` addresses.
+
+## Voice
+
+<!-- level: all -->
+
+Use active voice when the actor matters. Address the reader as you in procedures. Use imperatives
+for requirements and label optional steps. Put a condition before its action and keep one main
+idea per sentence. Name the subject instead of relying on an ambiguous pronoun.
+
+Avoid idioms, unexplained abbreviations, and decorative wording. Use literal terms that survive
+translation. Keep one term for each concept. Dates shown to people include their time zone;
+machine values retain their required format.
+
+## References
+
+See the [Google developer documentation style guide](https://developers.google.com/style)
+for general writing guidance. Project-specific requirements take precedence.

package/configurations/general/prose/vale/styles/LICENSES.md

@@ -0,0 +1,55 @@
+# Vale Style Notices
+
+The shipped gspot style includes rules adapted from the Microsoft and Red Hat Vale styles.
+
+## Microsoft
+
+Source: <https://github.com/errata-ai/Microsoft>
+
+MIT License
+
+Copyright (c) 2018 - 2019 Joseph Kato
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+## Red Hat
+
+Source: <https://github.com/redhat-documentation/vale-at-red-hat>
+
+MIT License
+
+Copyright (c) 2021 Rolfe Dlugy-Hegwer
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/configurations/general/prose/vale/styles/gspot/ampm.yml

@@ -0,0 +1,8 @@
+# Adapted from Microsoft.AMPM; see ../LICENSES.md.
+extends: existence
+message: Use 'AM' or 'PM' (preceded by a space).
+link: https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/date-time-terms
+level: error
+nonword: true
+tokens:
+    - \d{1,2} [ap]m\B

package/configurations/general/prose/vale/styles/gspot/conscious-language.yml

@@ -0,0 +1,16 @@
+# Adapted from RedHat.ConsciousLanguage; see ../LICENSES.md.
+extends: substitution
+ignorecase: true
+level: warning
+link: https://redhat-documentation.github.io/vale-at-red-hat/reference-guide.html#conscious-language
+message: Use %s rather than '%s'.
+action:
+    name: replace
+swap:
+    blacklist: blocklist
+    master(?! broker| boot record): primary|source|initiator|requester|controller|host|director|supplier
+    slave(?! broker): secondary|replica|responder|device|worker|proxy|performer|consumer|child
+    whitelist: allowlist
+    (?:demilitarized zone|DMZ): perimeter network
+    spirit animal: role model
+    mans: operates

package/configurations/general/prose/vale/styles/gspot/contractions.yml

@@ -0,0 +1,43 @@
+# Adapted from RedHat.Contractions; see ../LICENSES.md.
+extends: substitution
+ignorecase: true
+level: suggestion
+link: https://redhat-documentation.github.io/vale-at-red-hat/reference-guide.html#contractions
+message: Avoid contractions. Use '%s' rather than '%s.'
+action:
+    name: replace
+swap:
+    aren't: are not
+    can't: cannot
+    couldn't: could not
+    didn't: did not
+    doesn't: does not
+    don't: do not
+    hasn't: has not
+    haven't: have not
+    how'll: how will
+    how's: how is
+    isn't: is not
+    it'll: it will
+    it's: it is
+    shouldn't: should not
+    that'll: that will
+    that's: that is
+    they'll: they will
+    they're: they are
+    wasn't: was not
+    we'll: we will
+    we're: we are
+    we've: we have
+    weren't: were not
+    what'll: what will
+    what's: what is
+    when'll: when will
+    when's: when is
+    where'll: where will
+    where's: where is
+    who'll: who will
+    who's: who is
+    why'll: why will
+    why's: why is
+    won't: will not

package/configurations/general/prose/vale/styles/gspot/currency.yml

@@ -0,0 +1,8 @@
+extends: existence
+message: "Ambiguous currency '%s'. Write the ISO code (USD 5)."
+level: error
+scope: paragraph
+nonword: true
+tokens:
+    - "(?<![A-Z])\\$(?:\\d{2,}(?:\\.\\d+)?|\\d\\.\\d+)\\b"
+    - "\\d\\s?(?:dollars|euros|pounds)\\b"

package/configurations/general/prose/vale/styles/gspot/dashes.yml

@@ -0,0 +1,8 @@
+extends: existence
+message: 'Em dash or double hyphen. Use a comma, colon, or period.'
+level: error
+nonword: true
+tokens:
+    - '—'
+    - '(?<!eslint-(?:disable|enable)(?:-next-line|-line)?(?:[ \t]+[@\w/-]+(?:[ \t]*,[ \t]*[@\w/-]+)*)?) -- '
+    - '–'

package/configurations/general/prose/vale/styles/gspot/date-ordinals.yml

@@ -0,0 +1,41 @@
+# Adapted from Microsoft.DateNumbers; see ../LICENSES.md.
+extends: existence
+message: 'Write the day of a date as a plain number, not an ordinal.'
+link: https://learn.microsoft.com/en-us/style-guide/numbers#numbers-in-dates
+level: error
+nonword: true
+ignorecase: true
+raw:
+    - \b(?:Jan(?:uary)?|Feb(?:ruary)?|Mar(?:ch)?|Apr(?:il)?|May|Jun(?:e)?|Jul(?:y)?|Aug(?:ust)?|Sep(?:tember)?|Oct(?:ober)?|Nov(?:ember)?|Dec(?:ember)?)\b\s*
+tokens:
+    - first
+    - second
+    - third
+    - fourth
+    - fifth
+    - sixth
+    - seventh
+    - eighth
+    - ninth
+    - tenth
+    - eleventh
+    - twelfth
+    - thirteenth
+    - fourteenth
+    - fifteenth
+    - sixteenth
+    - seventeenth
+    - eighteenth
+    - nineteenth
+    - twentieth
+    - twenty-first
+    - twenty-second
+    - twenty-third
+    - twenty-fourth
+    - twenty-fifth
+    - twenty-sixth
+    - twenty-seventh
+    - twenty-eighth
+    - twenty-ninth
+    - thirtieth
+    - thirty-first

package/configurations/general/prose/vale/styles/gspot/dates.yml

@@ -0,0 +1,7 @@
+extends: existence
+message: "Ambiguous date '%s'. Write ISO dates (2026-09-17) or the month name."
+level: error
+nonword: true
+tokens:
+    - "\\b\\d{1,2}/\\d{1,2}/\\d{2,4}\\b"
+    - "\\b\\d{1,2}\\.\\d{1,2}\\.\\d{4}\\b"

package/configurations/general/prose/vale/styles/gspot/file-paths.yml

@@ -0,0 +1,7 @@
+extends: existence
+message: "A file path in prose goes stale: '%s'. Name the concept, or put the path in code formatting only where the reader must open it."
+level: error
+scope: paragraph
+nonword: true
+tokens:
+    - "(?<!`)\\b[a-z0-9_-]+/[a-z0-9_./-]+\\.[a-z]{1,5}\\b(?!`)"

package/configurations/general/prose/vale/styles/gspot/future.yml

@@ -0,0 +1,17 @@
+extends: existence
+message: "Future promise '%s'. Document what exists."
+level: error
+ignorecase: true
+tokens:
+    - will be added
+    - will be supported
+    - coming soon
+    - in the future
+    - is planned
+    - are planned
+    - planned for
+    - planned to
+    - roadmap
+    - eventually
+    - for now
+    - later on

package/configurations/general/prose/vale/styles/gspot/hedging.yml

@@ -0,0 +1,22 @@
+extends: existence
+message: "Hedge '%s'. Say when, or drop it."
+level: error
+ignorecase: true
+tokens:
+    - probably
+    - usually
+    - generally
+    - typically
+    - where practical
+    - when practical
+    - where possible
+    - when possible
+    - if needed
+    - as needed
+    - if possible
+    - in most cases
+    - for the most part
+    - somewhat
+    - fairly
+    - quite
+    - very

package/configurations/general/prose/vale/styles/gspot/history.yml

@@ -0,0 +1,16 @@
+extends: existence
+message: "History in prose: '%s'. Describe the present state."
+level: error
+ignorecase: true
+tokens:
+    - previously
+    - formerly
+    - used to
+    - no longer
+    - refactored from
+    - renamed from
+    - moved from
+    - legacy
+    - was removed
+    - was replaced
+    - migrated from

package/configurations/general/prose/vale/styles/gspot/idioms.yml

@@ -0,0 +1,21 @@
+extends: existence
+message: "Idiom '%s'. Say the plain thing."
+level: error
+ignorecase: true
+tokens:
+    - belt and suspenders
+    - belt and braces
+    - sanity check
+    - sanity-check
+    - low-hanging fruit
+    - under the hood
+    - out of the box
+    - load-bearing
+    - load bearing
+    - rule of thumb
+    - silver bullet
+    - moving parts
+    - at the end of the day
+    - in a nutshell
+    - touch base
+    - deep dive

package/configurations/general/prose/vale/styles/gspot/interface-verbs.yml

@@ -0,0 +1,11 @@
+extends: substitution
+message: "Use '%s' instead of '%s' for interface actions."
+level: error
+ignorecase: true
+swap:
+    click on: select
+    hit enter: press Enter
+    hit return: press Return
+    tap on: select
+    key in your: enter your
+    type in your: enter your

package/configurations/general/prose/vale/styles/gspot/jargon.yml

@@ -0,0 +1,11 @@
+# Adapted from Microsoft.Jargon; see ../LICENSES.md.
+extends: substitution
+message: Consider using '%s' instead of the jargon '%s'.
+link: https://learn.microsoft.com/en-us/style-guide/word-choice/avoid-jargon
+level: suggestion
+ignorecase: true
+action:
+    name: replace
+swap:
+    bucketize: group
+    glyph: symbol

package/configurations/general/prose/vale/styles/gspot/leading-conjunctions.yml

@@ -0,0 +1,12 @@
+# Adapted from RedHat.Conjunctions; see ../LICENSES.md.
+extends: existence
+level: suggestion
+link: https://redhat-documentation.github.io/vale-at-red-hat/reference-guide.html#conjunctions
+message: Do not overuse beginning sentences with '%s'.
+scope: paragraph
+action:
+    name: remove
+tokens:
+    - ^And
+    - ^Or
+    - ^So(?! that)(?![\s,])