promptbridge-mcp 0.2.0__tar.gz

promptbridge_mcp-0.2.0/.gitignore

@@ -0,0 +1,8 @@
+.venv/
+__pycache__/
+*.pyc
+.pytest_cache/
+dist/
+build/
+*.egg-info/
+.promptbridge/pb.db

promptbridge_mcp-0.2.0/CHANGELOG.md

@@ -0,0 +1,29 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project uses [Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+## [0.2.0] — first public release
+
+### Changed
+- Published on PyPI as **`promptbridge-mcp`** (the name `promptbridge` is taken). Install with `uvx promptbridge-mcp`. The import package and the `promptbridge` command are unchanged; a `promptbridge-mcp` command alias is added.
+- README is now in English; the Thai README moved to `README.th.md`.
+
+### Added
+- CI on Python 3.10–3.13 (Linux, macOS) and tag-triggered PyPI release via trusted publishing.
+- CONTRIBUTING, Code of Conduct, Security policy, issue and pull request templates.
+
+## [0.1.1]
+
+### Changed
+- **Breaking:** tool argument `session_id` renamed to `spec_id` in `pb_clarify`, `pb_compile` and `pb_save`, and `pb_capture` now returns `spec_id`. Some MCP bridges strip arguments named `session_id`, which made these tools fail when proxied.
+
+## [0.1.0]
+
+### Added
+- MCP server with six tools: `pb_capture`, `pb_clarify`, `pb_compile`, `pb_save`, `pb_glossary`, `pb_library`.
+- Task types `bug_fix`, `feature`, `refactor`, `test`, `explain`.
+- Thai and English question phrasing; other languages fall back to English phrasing translated by the host model.
+- Personal (SQLite) and repo (YAML) glossary; spec library.
+- `/spec` skill for Claude Code.

promptbridge_mcp-0.2.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Endy
+
+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.

promptbridge_mcp-0.2.0/PKG-INFO

@@ -0,0 +1,160 @@
+Metadata-Version: 2.5
+Name: promptbridge-mcp
+Version: 0.2.0
+Summary: Type coding requests in your own language; get a clear English task spec for AI coding agents (MCP server).
+Project-URL: Homepage, https://github.com/Endistic/promptbridge
+Project-URL: Issues, https://github.com/Endistic/promptbridge/issues
+Project-URL: Changelog, https://github.com/Endistic/promptbridge/blob/main/CHANGELOG.md
+Author: Endy
+License: MIT
+License-File: LICENSE
+Keywords: claude,coding-agent,i18n,mcp,model-context-protocol,prompt,spec,thai
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Natural Language :: English
+Classifier: Natural Language :: Thai
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Requires-Python: >=3.10
+Requires-Dist: jinja2>=3
+Requires-Dist: mcp>=1.2
+Requires-Dist: pydantic>=2
+Requires-Dist: pyyaml>=6
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# promptbridge
+
+**Type coding requests in your own language. Get a clear English task spec your AI coding agent can execute without guessing.**
+
+[ภาษาไทย](README.th.md) · [Changelog](CHANGELOG.md) · [Contributing](CONTRIBUTING.md)
+
+Many developers read English fine but don't *think* in it fast enough to write precise prompts. promptbridge sits between you and your coding agent (Claude Code, Claude Desktop, Cursor, any MCP client):
+
+```
+/spec หน้า login อยากให้ถ้าใส่รหัสผิดหลายครั้งมันล็อคไว้ก่อน
+      (login page: lock it after too many wrong passwords)
+```
+
+1. It asks **only what is ambiguous** — at most 3 tap-to-answer questions, in your language: *how many attempts? lock for how long? per account or per IP?*
+2. It shows a **2–3 line summary in your language** plus the English spec: Goal · Context · Requirements · Constraints · Acceptance criteria · Assumptions.
+3. You approve, and the agent does the work — **reporting back in your language**, with code, paths and errors left untouched.
+
+It also learns your vocabulary: tell it once that «ตะกร้า» means `CartStore`, and every future spec uses the real name.
+
+## How it works
+
+| Part | Does |
+| --- | --- |
+| **Host model** (the Claude/LLM you already use) | Reads your language, fills spec slots in English, asks the questions, summarizes results |
+| **promptbridge MCP server** (Python) | Task templates, decides which questions matter, renders the spec deterministically, remembers your glossary and specs that worked |
+
+The server never calls an LLM itself — no extra API cost, no data leaves your machine. Everything is stored locally in `~/.promptbridge/`.
+
+## Install
+
+You need [uv](https://docs.astral.sh/uv/).
+
+### Claude Code
+
+```bash
+# 1) Register the MCP server for all projects
+claude mcp add promptbridge -s user -- uvx promptbridge-mcp
+
+# 2) Install the /spec skill
+mkdir -p ~/.claude/skills/spec
+curl -fsSL https://raw.githubusercontent.com/Endistic/promptbridge/main/skills/spec/SKILL.md \
+  -o ~/.claude/skills/spec/SKILL.md
+
+# 3) In any project
+/spec ปุ่มบันทึกในหน้าโปรไฟล์กดแล้วขึ้น error 500
+```
+
+### Claude Desktop
+
+Claude menu (macOS menu bar) → **Settings… → Developer → Edit Config**, add the server, then quit (⌘Q) and reopen:
+
+```json
+{
+  "mcpServers": {
+    "promptbridge": { "command": "/opt/homebrew/bin/uvx", "args": ["promptbridge-mcp"] }
+  }
+}
+```
+
+Use the full path from `which uvx` — Claude Desktop does not see your shell's `PATH`. Then ask: *"Use promptbridge to make a spec for: …"*
+
+### Cursor and other MCP clients
+
+```json
+{ "mcpServers": { "promptbridge": { "command": "uvx", "args": ["promptbridge-mcp"] } } }
+```
+
+Clients without the skill follow the workflow described in the tools themselves.
+
+### From source
+
+```bash
+git clone https://github.com/Endistic/promptbridge
+claude mcp add promptbridge -s user -- uvx --from ./promptbridge promptbridge
+```
+
+Or load it as a Claude Code plugin (server + skill): `claude --plugin-dir ./promptbridge`, then `/promptbridge:spec`.
+
+## Usage
+
+| Type | Result |
+| --- | --- |
+| `/spec <request>` | Full flow: ask → summarize → do |
+| `/spec --quick <request>` | Skip questions; unknowns become visible Assumptions in the spec |
+| "remember: ตะกร้า = CartStore" | Add a glossary term |
+| "show my glossary" | List glossary terms |
+| "have I asked for something like this before?" | Search specs that worked |
+
+### Task types
+
+`bug_fix` · `feature` · `refactor` · `test` · `explain` — each has its own required facts ([`src/promptbridge/templates/`](src/promptbridge/templates/)). Adding a type is one YAML file.
+
+### Glossary
+
+- **personal** — `~/.promptbridge/pb.db`, follows you across projects
+- **repo** — `<repo>/.promptbridge/glossary.yaml`, commit it so the whole team shares one vocabulary
+
+When you edit a spec and add a real name (e.g. `LoginAttemptService`), promptbridge offers to remember the pairing.
+
+## Languages
+
+Built around a `locale` from day one. Thai and English have hand-written question phrasing; any other language (Japanese, Vietnamese, Indonesian, Korean, Spanish, …) works today — the host model translates the questions. Adding native phrasing for a language is one file: [`src/promptbridge/locales/`](src/promptbridge/locales/). See [CONTRIBUTING.md](CONTRIBUTING.md#add-a-language).
+
+## MCP tools
+
+| Tool | Purpose |
+| --- | --- |
+| `pb_capture` | Start from the user's raw request: guess task type, match glossary, scan the repo |
+| `pb_clarify` | Decide which questions to ask (max 3 per round, max 2 rounds) |
+| `pb_compile` | Render the English spec; unconfirmed guesses become Assumptions |
+| `pb_save` | Record accepted / edited / rejected; suggest glossary terms from edits |
+| `pb_glossary` | List / add / remove terms (personal or repo scope) |
+| `pb_library` | Search specs that worked before |
+
+Resource `promptbridge://stats` reports accepted / edited / rejected counts.
+
+## Configuration
+
+| Variable | Default | Meaning |
+| --- | --- | --- |
+| `PROMPTBRIDGE_HOME` | `~/.promptbridge` | Where the local database lives |
+
+Works with MCP Python SDK 1.x and 2.x.
+
+## License
+
+[MIT](LICENSE)

promptbridge_mcp-0.2.0/README.md

@@ -0,0 +1,127 @@
+# promptbridge
+
+**Type coding requests in your own language. Get a clear English task spec your AI coding agent can execute without guessing.**
+
+[ภาษาไทย](README.th.md) · [Changelog](CHANGELOG.md) · [Contributing](CONTRIBUTING.md)
+
+Many developers read English fine but don't *think* in it fast enough to write precise prompts. promptbridge sits between you and your coding agent (Claude Code, Claude Desktop, Cursor, any MCP client):
+
+```
+/spec หน้า login อยากให้ถ้าใส่รหัสผิดหลายครั้งมันล็อคไว้ก่อน
+      (login page: lock it after too many wrong passwords)
+```
+
+1. It asks **only what is ambiguous** — at most 3 tap-to-answer questions, in your language: *how many attempts? lock for how long? per account or per IP?*
+2. It shows a **2–3 line summary in your language** plus the English spec: Goal · Context · Requirements · Constraints · Acceptance criteria · Assumptions.
+3. You approve, and the agent does the work — **reporting back in your language**, with code, paths and errors left untouched.
+
+It also learns your vocabulary: tell it once that «ตะกร้า» means `CartStore`, and every future spec uses the real name.
+
+## How it works
+
+| Part | Does |
+| --- | --- |
+| **Host model** (the Claude/LLM you already use) | Reads your language, fills spec slots in English, asks the questions, summarizes results |
+| **promptbridge MCP server** (Python) | Task templates, decides which questions matter, renders the spec deterministically, remembers your glossary and specs that worked |
+
+The server never calls an LLM itself — no extra API cost, no data leaves your machine. Everything is stored locally in `~/.promptbridge/`.
+
+## Install
+
+You need [uv](https://docs.astral.sh/uv/).
+
+### Claude Code
+
+```bash
+# 1) Register the MCP server for all projects
+claude mcp add promptbridge -s user -- uvx promptbridge-mcp
+
+# 2) Install the /spec skill
+mkdir -p ~/.claude/skills/spec
+curl -fsSL https://raw.githubusercontent.com/Endistic/promptbridge/main/skills/spec/SKILL.md \
+  -o ~/.claude/skills/spec/SKILL.md
+
+# 3) In any project
+/spec ปุ่มบันทึกในหน้าโปรไฟล์กดแล้วขึ้น error 500
+```
+
+### Claude Desktop
+
+Claude menu (macOS menu bar) → **Settings… → Developer → Edit Config**, add the server, then quit (⌘Q) and reopen:
+
+```json
+{
+  "mcpServers": {
+    "promptbridge": { "command": "/opt/homebrew/bin/uvx", "args": ["promptbridge-mcp"] }
+  }
+}
+```
+
+Use the full path from `which uvx` — Claude Desktop does not see your shell's `PATH`. Then ask: *"Use promptbridge to make a spec for: …"*
+
+### Cursor and other MCP clients
+
+```json
+{ "mcpServers": { "promptbridge": { "command": "uvx", "args": ["promptbridge-mcp"] } } }
+```
+
+Clients without the skill follow the workflow described in the tools themselves.
+
+### From source
+
+```bash
+git clone https://github.com/Endistic/promptbridge
+claude mcp add promptbridge -s user -- uvx --from ./promptbridge promptbridge
+```
+
+Or load it as a Claude Code plugin (server + skill): `claude --plugin-dir ./promptbridge`, then `/promptbridge:spec`.
+
+## Usage
+
+| Type | Result |
+| --- | --- |
+| `/spec <request>` | Full flow: ask → summarize → do |
+| `/spec --quick <request>` | Skip questions; unknowns become visible Assumptions in the spec |
+| "remember: ตะกร้า = CartStore" | Add a glossary term |
+| "show my glossary" | List glossary terms |
+| "have I asked for something like this before?" | Search specs that worked |
+
+### Task types
+
+`bug_fix` · `feature` · `refactor` · `test` · `explain` — each has its own required facts ([`src/promptbridge/templates/`](src/promptbridge/templates/)). Adding a type is one YAML file.
+
+### Glossary
+
+- **personal** — `~/.promptbridge/pb.db`, follows you across projects
+- **repo** — `<repo>/.promptbridge/glossary.yaml`, commit it so the whole team shares one vocabulary
+
+When you edit a spec and add a real name (e.g. `LoginAttemptService`), promptbridge offers to remember the pairing.
+
+## Languages
+
+Built around a `locale` from day one. Thai and English have hand-written question phrasing; any other language (Japanese, Vietnamese, Indonesian, Korean, Spanish, …) works today — the host model translates the questions. Adding native phrasing for a language is one file: [`src/promptbridge/locales/`](src/promptbridge/locales/). See [CONTRIBUTING.md](CONTRIBUTING.md#add-a-language).
+
+## MCP tools
+
+| Tool | Purpose |
+| --- | --- |
+| `pb_capture` | Start from the user's raw request: guess task type, match glossary, scan the repo |
+| `pb_clarify` | Decide which questions to ask (max 3 per round, max 2 rounds) |
+| `pb_compile` | Render the English spec; unconfirmed guesses become Assumptions |
+| `pb_save` | Record accepted / edited / rejected; suggest glossary terms from edits |
+| `pb_glossary` | List / add / remove terms (personal or repo scope) |
+| `pb_library` | Search specs that worked before |
+
+Resource `promptbridge://stats` reports accepted / edited / rejected counts.
+
+## Configuration
+
+| Variable | Default | Meaning |
+| --- | --- | --- |
+| `PROMPTBRIDGE_HOME` | `~/.promptbridge` | Where the local database lives |
+
+Works with MCP Python SDK 1.x and 2.x.
+
+## License
+
+[MIT](LICENSE)

promptbridge_mcp-0.2.0/README.th.md

@@ -0,0 +1,111 @@
+# promptbridge
+
+**พิมพ์สั่งงาน AI coding เป็นภาษาไทย แล้วได้ task spec ภาษาอังกฤษที่ชัดเจน ให้ agent ทำงานได้โดยไม่ต้องเดา**
+
+[English](README.md) · [Changelog](CHANGELOG.md) · [ร่วมพัฒนา](CONTRIBUTING.md)
+
+```
+/spec หน้า login อยากให้ถ้าใส่รหัสผิดหลายครั้งมันล็อคไว้ก่อน
+```
+
+1. ถามกลับเฉพาะจุดที่กำกวม ไม่เกิน 3 ข้อแบบกดเลือก เป็นภาษาไทย (ผิดกี่ครั้ง? ล็อคนานแค่ไหน? นับต่อ account หรือ IP?)
+2. สรุปไทย 2–3 บรรทัดให้ตรวจ พร้อม spec อังกฤษ (Goal / Context / Requirements / Constraints / Acceptance criteria / Assumptions)
+3. กด "ลงมือเลย" แล้ว agent ทำตาม spec และรายงานกลับเป็นไทย ส่วนโค้ด ชื่อไฟล์ และ error คงเป็นต้นฉบับ
+
+สอนคำศัพท์ครั้งเดียว เช่น «ตะกร้า» = `CartStore` แล้ว spec ครั้งต่อ ๆ ไปจะใช้ชื่อจริงในโค้ดเอง
+
+## ทำงานอย่างไร
+
+| ส่วน | หน้าที่ |
+| --- | --- |
+| **Host model** (Claude หรือ LLM ที่คุณใช้อยู่) | อ่านภาษาไทย, เติม slot เป็นอังกฤษ, ถามคำถามเป็นไทย, สรุปผลเป็นไทย |
+| **MCP server** (`promptbridge`, Python) | template ตาม task type, เลือกว่าจะถามอะไร, render spec แบบ deterministic, จำ glossary และ spec ที่เคยใช้ได้ผล |
+
+Server ไม่เรียก LLM เอง จึงไม่มีค่า API เพิ่ม และข้อมูลทั้งหมดเก็บในเครื่องที่ `~/.promptbridge/`
+
+## ติดตั้ง
+
+ต้องมี [uv](https://docs.astral.sh/uv/) (`brew install uv`)
+
+### Claude Code
+
+```bash
+# 1) ลงทะเบียน MCP server (ครั้งเดียว ใช้ได้ทุกโปรเจกต์)
+claude mcp add promptbridge -s user -- uvx promptbridge-mcp
+
+# 2) ติดตั้ง skill /spec
+mkdir -p ~/.claude/skills/spec
+curl -fsSL https://raw.githubusercontent.com/Endistic/promptbridge/main/skills/spec/SKILL.md \
+  -o ~/.claude/skills/spec/SKILL.md
+
+# 3) เปิด Claude Code ในโปรเจกต์ไหนก็ได้ แล้วพิมพ์
+/spec ปุ่มบันทึกในหน้าโปรไฟล์กดแล้วขึ้น error 500
+```
+
+### Claude Desktop
+
+เมนู **Claude** ที่แถบเมนูบนของ Mac → **Settings… → Developer → Edit Config** ใส่ config นี้ แล้วปิดแอปด้วย ⌘Q และเปิดใหม่
+
+```json
+{
+  "mcpServers": {
+    "promptbridge": { "command": "/opt/homebrew/bin/uvx", "args": ["promptbridge-mcp"] }
+  }
+}
+```
+
+ใส่ path เต็มจากคำสั่ง `which uvx` เพราะ Claude Desktop ไม่เห็น `PATH` ของ terminal จากนั้นพิมพ์ว่า "ใช้ promptbridge ทำ spec จากคำขอนี้: …"
+
+### Cursor / client อื่นที่รองรับ MCP
+
+```json
+{ "mcpServers": { "promptbridge": { "command": "uvx", "args": ["promptbridge-mcp"] } } }
+```
+
+Client ที่ไม่มี skill จะทำตามขั้นตอนที่อธิบายไว้ใน tool แทน
+
+### ติดตั้งจาก source
+
+```bash
+git clone https://github.com/Endistic/promptbridge
+claude mcp add promptbridge -s user -- uvx --from ./promptbridge promptbridge
+```
+
+หรือโหลดเป็น Claude Code plugin (รวม server + skill): `claude --plugin-dir ./promptbridge` แล้วใช้ `/promptbridge:spec`
+
+## คำสั่งที่ใช้บ่อย
+
+| พิมพ์ | ผล |
+| --- | --- |
+| `/spec <ข้อความ>` | flow เต็ม: ถาม → สรุป → ลงมือ |
+| `/spec --quick <ข้อความ>` | ข้ามคำถาม ช่องที่ไม่รู้จะถูกเขียนเป็น Assumptions ให้เห็น |
+| "จำคำนี้ไว้: ตะกร้า = CartStore" | เพิ่ม glossary |
+| "ดูคำที่จำไว้" | แสดง glossary ทั้งหมด |
+| "เคยสั่งงานคล้าย ๆ นี้ไหม" | ค้น spec เก่าที่เคยใช้ได้ผล |
+
+## Task types
+
+`bug_fix` · `feature` · `refactor` · `test` · `explain` — แต่ละแบบมีข้อมูลที่ต้องมีต่างกัน (ดู `src/promptbridge/templates/*.yaml`) เพิ่ม type ใหม่ได้ด้วยไฟล์ YAML หนึ่งไฟล์
+
+## Glossary
+
+- **personal** — เก็บใน `~/.promptbridge/pb.db` ตามคุณไปทุกโปรเจกต์
+- **repo** — เก็บใน `<repo>/.promptbridge/glossary.yaml` commit เข้า repo เพื่อให้ทั้งทีมใช้ศัพท์ชุดเดียวกัน
+
+เมื่อคุณแก้ spec แล้วใส่ชื่อจริง (เช่น `LoginAttemptService`) ระบบจะเสนอให้จำคู่คำนั้นไว้ใช้ครั้งหน้า
+
+## ภาษาอื่น
+
+ออกแบบเป็น `locale` ตั้งแต่ต้น ตอนนี้มีคำถามสำเร็จรูปภาษาไทยและอังกฤษ ภาษาอื่น (ja, vi, id, ko, …) ใช้ได้เลยโดย host model แปลคำถามให้ เพิ่มภาษาใหม่ได้ด้วยไฟล์ `src/promptbridge/locales/<code>.yaml` หนึ่งไฟล์ ดู [CONTRIBUTING.md](CONTRIBUTING.md#add-a-language)
+
+## ตั้งค่า
+
+| ตัวแปร | ค่าเริ่มต้น | ความหมาย |
+| --- | --- | --- |
+| `PROMPTBRIDGE_HOME` | `~/.promptbridge` | ที่เก็บฐานข้อมูล |
+
+ดูสถิติ accepted / edited / rejected ได้จาก MCP resource `promptbridge://stats` รองรับ MCP Python SDK ทั้ง 1.x และ 2.x
+
+## License
+
+[MIT](LICENSE)

promptbridge_mcp-0.2.0/pyproject.toml

@@ -0,0 +1,55 @@
+[project]
+name = "promptbridge-mcp"
+version = "0.2.0"
+description = "Type coding requests in your own language; get a clear English task spec for AI coding agents (MCP server)."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "MIT" }
+authors = [{ name = "Endy" }]
+keywords = ["mcp", "model-context-protocol", "claude", "prompt", "spec", "i18n", "thai", "coding-agent"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Natural Language :: English",
+    "Natural Language :: Thai",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development",
+]
+dependencies = [
+    "mcp>=1.2",
+    "pydantic>=2",
+    "jinja2>=3",
+    "pyyaml>=6",
+]
+
+[project.urls]
+Homepage = "https://github.com/Endistic/promptbridge"
+Issues = "https://github.com/Endistic/promptbridge/issues"
+Changelog = "https://github.com/Endistic/promptbridge/blob/main/CHANGELOG.md"
+
+[project.optional-dependencies]
+dev = ["pytest>=8", "pytest-asyncio>=0.23"]
+
+[project.scripts]
+promptbridge = "promptbridge.server:main"
+promptbridge-mcp = "promptbridge.server:main"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/promptbridge"]
+
+[tool.hatch.build.targets.sdist]
+include = ["src/", "tests/", "skills/", "README.md", "README.th.md", "LICENSE", "CHANGELOG.md", "pyproject.toml"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+asyncio_mode = "auto"

promptbridge_mcp-0.2.0/skills/spec/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: spec
+description: Turn a request the user wrote in their own language (Thai by default) into a clear English task spec, ask only the questions that matter, then carry it out. Use when the user types /spec, or writes a coding request in Thai or another non-English language and wants it done properly.
+---
+
+# /spec — native-language request → English task spec → done
+
+The user thinks in their own language. Your job is to turn what they wrote into a spec a coding
+agent can execute without guessing, check it with them in their language, then do the work.
+The `promptbridge` MCP server owns the structure (templates, which questions, rendering, memory).
+You own the language work.
+
+## Language rules (whole session)
+
+- Talk to the user in their language (the `locale`; default Thai). Short sentences, plain words.
+- Everything you send to the pb_* tools as `value_en` is **English**. Translate; never paste Thai into slots.
+- Keep code, file paths, identifiers, commands, error messages and numbers exactly as they are.
+- Technical terms with no common Thai word (API, endpoint, cache, deploy) stay in English inside Thai sentences.
+
+## Steps
+
+### 1. Capture
+Call `pb_capture` with:
+- `raw_text`: the user's request exactly as typed (everything after `/spec`)
+- `locale`: `th` unless the user writes in another language (`ja`, `vi`, `id`, …)
+- `cwd`: the current working directory
+
+If the user wrote `/spec --quick …`, remember `quick=true` for step 3 and strip the flag from `raw_text`.
+
+### 2. Fill slots (silently)
+From `raw_text`, the returned `glossary_hits`, `repo_context` and — if it helps — a quick look at the
+repo (Glob/Grep for the obvious files), fill the `slot_schema`:
+
+```json
+{"goal": {"value_en": "Lock a user account after repeated failed logins.", "status": "stated"},
+ "behavior": {"value_en": ["Lock after 5 failures"], "status": "inferred"}}
+```
+
+- `stated` = the user actually said it. `inferred` = you guessed it (from context or code). Be honest; the
+  server uses this to decide what to confirm.
+- Omit slots you know nothing about. Do not invent requirements to look complete.
+- Use glossary `term_en` names and real file paths you found.
+- If `task_type` is clearly wrong (e.g. the user describes a bug but it guessed `feature`), pass the right
+  one to `pb_clarify`.
+
+### 3. Clarify (max 2 rounds)
+Call `pb_clarify(spec_id, slots, task_type?, quick?)`.
+
+If `ready` is false, ask the returned `questions` with **AskUserQuestion** in one call:
+- One question per item, in the user's language. Start from `prompt`, adapt it to this task.
+- Give 2–4 concrete options that make sense for *this* code (e.g. "5 ครั้ง", "10 ครั้ง"), put the most
+  likely first. The user can always type their own answer.
+- `kind: "confirm"` → show your inferred value as the first option ("ใช่ ตามนี้") and alternatives after it.
+- Keep headers ≤ 12 characters.
+
+Translate the answers to English, update those slots with `status: "stated"`, and call `pb_clarify` again
+with the full slot set. Stop when `ready` is true. If the user says "ไปเลย", "ข้ามได้", or similar,
+call again with `quick: true`.
+
+If AskUserQuestion is not available, ask in plain text as a numbered list with the options.
+
+### 4. Compile and confirm
+Call `pb_compile(spec_id)`. Then show the user:
+
+1. A 2–3 line summary in their language, following `summary_instruction`.
+2. The assumptions, if any, as a short list in their language — these are the things they should check.
+3. The English spec in a ```markdown code block, so they can glance at it.
+
+Then ask with AskUserQuestion: **ลงมือเลย / แก้ไข spec / ยกเลิก** (in their language).
+
+If `validation.warnings` mentions untranslated text, fix the slot and compile again before showing it.
+
+### 5. Do the work
+- **Approve** → treat `spec_markdown` as your task and carry it out. Follow its "How to work" section.
+  Follow `reflect_instruction` for everything you say along the way: plans, questions and the final
+  report are in the user's language; code stays as-is.
+- **Edit** → apply the user's change to the spec (they may describe it in their language; you update the
+  English), show the updated summary, confirm again. Record it as `edited` in step 6.
+- **Cancel** → call `pb_save(outcome="rejected")` and stop.
+
+### 6. Save and learn
+After the work (or after cancel), call `pb_save(spec_id, outcome, final_spec?)`:
+- `accepted` if the spec was used as compiled, `edited` + `final_spec` if it changed, `rejected` if cancelled.
+- If it returns `glossary_candidates`, match each to the word the user used in `raw_text`, then ask once:
+  "จำคำเหล่านี้ไว้ไหม? «ตะกร้า» = `CartStore`". On yes, call `pb_glossary(action="add", …)`.
+  Use `scope="repo"` (with `cwd`) for names specific to this codebase the team would share; otherwise `personal`.
+
+## Other commands the user may ask for
+
+- "จำคำนี้ไว้: X = Y" → `pb_glossary(action="add", term_native="X", term_en="Y", kind=...)`
+- "ดูคำที่จำไว้" → `pb_glossary(action="list", cwd=...)` and show a small table.
+- "เคยสั่งงานคล้าย ๆ นี้ไหม" → `pb_library(query=...)`; offer to reuse a result as the starting slots.
+
+## Don't
+
+- Don't ask more than the server returned, and never more than 2 rounds.
+- Don't start coding before the user approves the spec (except task_type `explain`, which needs no approval).
+- Don't show the English spec without the summary in their language.

promptbridge_mcp-0.2.0/src/promptbridge/__init__.py

@@ -0,0 +1,3 @@
+"""promptbridge — native-language intent to structured English specs for coding agents."""
+
+__version__ = "0.2.0"