scala-ts-setup

Name: scala-ts-setup
Author: scala-ts

Analyze an SBT codebase and propose Scala-TS setup edits module by module

by scala-ts(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from scala-ts/scala-ts (.github/prompts/scala-ts-setup.prompt.md). Copyright stays with the author.

Use docs/ai/scala-ts-setup-core.md as the authoritative contract.

Your task:

Detect whether the repository is an SBT build.
If no SBT build is found, stop and explain that setup requires SBT files.
Before any question, run preflight sbt test:compile; if it fails, report baseline failure and stop.
Detect current Scala-TS setup (plugins, modules, settings).
Confirm your detected setup with the user.
Ask per-module setup questions (generator, compile trigger, output path, mapping options).
Propose edits only (no auto-apply) in:
- project/plugins.sbt
- module/root build.sbt
After user confirmation and edits, run sbt test:compile.
Verify expected generated files (.ts and/or .py) exist per configured module.
Report results and any remediation suggestions.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

Use `docs/ai/scala-ts-setup-core.md` as the authoritative contract.

Your task:

1. Detect whether the repository is an SBT build.
2. If no SBT build is found, stop and explain that setup requires SBT files.
3. Before any question, run preflight `sbt test:compile`; if it fails, report baseline failure and stop.
4. Detect current Scala-TS setup (plugins, modules, settings).
5. Confirm your detected setup with the user.
6. Ask per-module setup questions (generator, compile trigger, output path, mapping options).
7. Propose edits only (no auto-apply) in:
   - `project/plugins.sbt`
   - module/root `build.sbt`
8. After user confirmation and edits, run `sbt test:compile`.
9. Verify expected generated files (`.ts` and/or `.py`) exist per configured module.
10. Report results and any remediation suggestions.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

scala-ts-scala-ts-scala-ts-setup-prompt.prompt.jsonjson

{
  "prompt": "Use `docs/ai/scala-ts-setup-core.md` as the authoritative contract.\n\nYour task:\n\n1. Detect whether the repository is an SBT build.\n2. If no SBT build is found, stop and explain that setup requires SBT files.\n3. Before any question, run preflight `sbt test:compile`; if it fails, report baseline failure and stop.\n4. Detect current Scala-TS setup (plugins, modules, settings).\n5. Confirm your detected setup with the user.\n6. Ask per-module setup questions (generator, compile trigger, output path, mapping options).\n7. Propose edits only (no auto-apply) in:\n   - `project/plugins.sbt`\n   - module/root `build.sbt`\n8. After user confirmation and edits, run `sbt test:compile`.\n9. Verify expected generated files (`.ts` and/or `.py`) exist per configured module.\n10. Report results and any remediation suggestions.",
  "variables": [],
  "notes": "Analyze an SBT codebase and propose Scala-TS setup edits module by module Mode: ask.",
  "metadata": {
    "source": {
      "provider": "github-prompts",
      "repository": "https://github.com/scala-ts/scala-ts",
      "path": ".github/prompts/scala-ts-setup.prompt.md",
      "ref": "3734d3127aa8e6d89454f2bd7acde7ad0ae7f1e8",
      "url": "https://github.com/scala-ts/scala-ts/blob/3734d3127aa8e6d89454f2bd7acde7ad0ae7f1e8/.github/prompts/scala-ts-setup.prompt.md",
      "key": "scala-ts/scala-ts/.github/prompts/scala-ts-setup.prompt.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/scala-ts-scala-ts-scala-ts-setup-prompt/manifest?version=1.0.0

About

Use it

Manifest

Reviews