@jstn-sdk/rcs 0.1.1 → 0.1.7

package/docs/readme/README.ru.md

@@ -1,40 +1,41 @@
 # Roblox Creator Skills (RCS)
 
-This localized README is intentionally condensed for the strict v0.1.0 ship pass.
-Use the canonical checked-in docs below for the current product surface.
+Этот локализованный README намеренно сделан кратким.
+Для актуальной поверхности продукта используйте канонические документы по ссылкам ниже.
 
-- Package: `@jstn-sdk/rcs`
-- Repository: `https://github.com/JustineDevs/roblox-ai-os`
-- Getting started: [../getting-started.html](../getting-started.html)
-- Skills reference: [../skills.html](../skills.html)
-- Integrations: [../integrations.html](../integrations.html)
-- Canonical README: [../../README.md](../../README.md)
+- Пакет: `@jstn-sdk/rcs`
+- Репозиторий: `https://github.com/JustineDevs/roblox-ai-os`
+- Начало работы: [../getting-started.html](../getting-started.html)
+- Справочник skills: [../skills.html](../skills.html)
+- Интеграции: [../integrations.html](../integrations.html)
+- Канонический README: [../../README.md](../../README.md)
 
-## Canonical Creator Workflow
+## Канонический workflow для создателей
 
 `$brief` -> `$blueprint` -> `$forge` / `$crew` -> `$autoforge`
 
-For Roblox implementation work, the mandatory pre-action gate applies before any code generation:
-- gather references
-- build understanding
-- standardize terms
-- design modular file tree architecture
-- only then implement
+Для работы по реализации в Roblox обязательный pre-action gate применяется до любой генерации кода:
+- собрать ссылки и материалы
+- сформировать понимание
+- стандартизировать термины
+- спроектировать модульную архитектуру дерева файлов
+- и только потом реализовывать
 
-See:
+См.:
 - [../../README.md](../../README.md)
 - [../skills.html](../skills.html)
 - [../reference/roblox-pre-action-protocol.md](../reference/roblox-pre-action-protocol.md)
 
-## Ownership
+## Владение
 
-RCS is owned and maintained by [JustineDevs](https://github.com/JustineDevs) and [@JustineDevs](https://github.com/JustineDevs) for Roblox creator workflows.
+RCS принадлежит [JustineDevs](https://github.com/JustineDevs) и [@JustineDevs](https://github.com/JustineDevs) и поддерживается ими для creator-workflow в Roblox.
 
-## Acknowledgements
+## Благодарности
 
 - [OpenAI Codex CLI](https://github.com/openai/codex)
+- [oh-my-codex](https://github.com/Yeachan-Heo/oh-my-codex)
 - [robloxstudio-mcp](https://github.com/boshyxd/robloxstudio-mcp)
 
-## License
+## Лицензия
 
 [MIT](https://opensource.org/licenses/MIT)

package/docs/readme/README.tr.md

@@ -1,40 +1,41 @@
 # Roblox Creator Skills (RCS)
 
-This localized README is intentionally condensed for the strict v0.1.0 ship pass.
-Use the canonical checked-in docs below for the current product surface.
+Bu yerelleştirilmiş README bilinçli olarak kısa tutulmuştur.
+Ürünün güncel yüzeyi için aşağıdaki kanonik belgelere bakın.
 
-- Package: `@jstn-sdk/rcs`
-- Repository: `https://github.com/JustineDevs/roblox-ai-os`
-- Getting started: [../getting-started.html](../getting-started.html)
-- Skills reference: [../skills.html](../skills.html)
-- Integrations: [../integrations.html](../integrations.html)
-- Canonical README: [../../README.md](../../README.md)
+- Paket: `@jstn-sdk/rcs`
+- Depo: `https://github.com/JustineDevs/roblox-ai-os`
+- Başlangıç: [../getting-started.html](../getting-started.html)
+- Skill başvurusu: [../skills.html](../skills.html)
+- Entegrasyonlar: [../integrations.html](../integrations.html)
+- Kanonik README: [../../README.md](../../README.md)
 
-## Canonical Creator Workflow
+## Kanonik creator iş akışı
 
 `$brief` -> `$blueprint` -> `$forge` / `$crew` -> `$autoforge`
 
-For Roblox implementation work, the mandatory pre-action gate applies before any code generation:
-- gather references
-- build understanding
-- standardize terms
-- design modular file tree architecture
-- only then implement
+Roblox uygulama işi için zorunlu pre-action gate, herhangi bir kod üretiminden önce uygulanır:
+- referansları topla
+- anlayış oluştur
+- terimleri standartlaştır
+- modüler dosya ağacı mimarisi tasarla
+- ancak ondan sonra uygula
 
-See:
+Bakınız:
 - [../../README.md](../../README.md)
 - [../skills.html](../skills.html)
 - [../reference/roblox-pre-action-protocol.md](../reference/roblox-pre-action-protocol.md)
 
-## Ownership
+## Sahiplik
 
-RCS is owned and maintained by [JustineDevs](https://github.com/JustineDevs) and [@JustineDevs](https://github.com/JustineDevs) for Roblox creator workflows.
+RCS, Roblox creator iş akışları için [JustineDevs](https://github.com/JustineDevs) ve [@JustineDevs](https://github.com/JustineDevs) tarafından sahiplenilir ve sürdürülür.
 
-## Acknowledgements
+## Teşekkürler
 
 - [OpenAI Codex CLI](https://github.com/openai/codex)
+- [oh-my-codex](https://github.com/Yeachan-Heo/oh-my-codex)
 - [robloxstudio-mcp](https://github.com/boshyxd/robloxstudio-mcp)
 
-## License
+## Lisans
 
 [MIT](https://opensource.org/licenses/MIT)

package/docs/readme/README.uk.md

@@ -1,40 +1,41 @@
 # Roblox Creator Skills (RCS)
 
-This localized README is intentionally condensed for the strict v0.1.0 ship pass.
-Use the canonical checked-in docs below for the current product surface.
+Цей локалізований README навмисно зроблено стислим.
+Для актуальної поверхні продукту використовуйте канонічні документи за посиланнями нижче.
 
-- Package: `@jstn-sdk/rcs`
-- Repository: `https://github.com/JustineDevs/roblox-ai-os`
-- Getting started: [../getting-started.html](../getting-started.html)
-- Skills reference: [../skills.html](../skills.html)
-- Integrations: [../integrations.html](../integrations.html)
-- Canonical README: [../../README.md](../../README.md)
+- Пакет: `@jstn-sdk/rcs`
+- Репозиторій: `https://github.com/JustineDevs/roblox-ai-os`
+- Початок роботи: [../getting-started.html](../getting-started.html)
+- Довідник skills: [../skills.html](../skills.html)
+- Інтеграції: [../integrations.html](../integrations.html)
+- Канонічний README: [../../README.md](../../README.md)
 
-## Canonical Creator Workflow
+## Канонічний workflow для creator
 
 `$brief` -> `$blueprint` -> `$forge` / `$crew` -> `$autoforge`
 
-For Roblox implementation work, the mandatory pre-action gate applies before any code generation:
-- gather references
-- build understanding
-- standardize terms
-- design modular file tree architecture
-- only then implement
+Для роботи з реалізацією в Roblox обов’язковий pre-action gate застосовується до будь-якої генерації коду:
+- зібрати референси
+- побудувати розуміння
+- стандартизувати терміни
+- спроєктувати модульну архітектуру дерева файлів
+- і лише потім реалізовувати
 
-See:
+Див.:
 - [../../README.md](../../README.md)
 - [../skills.html](../skills.html)
 - [../reference/roblox-pre-action-protocol.md](../reference/roblox-pre-action-protocol.md)
 
-## Ownership
+## Власність
 
-RCS is owned and maintained by [JustineDevs](https://github.com/JustineDevs) and [@JustineDevs](https://github.com/JustineDevs) for Roblox creator workflows.
+RCS належить [JustineDevs](https://github.com/JustineDevs) та [@JustineDevs](https://github.com/JustineDevs) і підтримується ними для creator-workflow у Roblox.
 
-## Acknowledgements
+## Подяки
 
 - [OpenAI Codex CLI](https://github.com/openai/codex)
+- [oh-my-codex](https://github.com/Yeachan-Heo/oh-my-codex)
 - [robloxstudio-mcp](https://github.com/boshyxd/robloxstudio-mcp)
 
-## License
+## Ліцензія
 
 [MIT](https://opensource.org/licenses/MIT)

package/docs/readme/README.vi.md

@@ -1,40 +1,41 @@
 # Roblox Creator Skills (RCS)
 
-This localized README is intentionally condensed for the strict v0.1.0 ship pass.
-Use the canonical checked-in docs below for the current product surface.
+README bản địa hóa này được giữ ngắn gọn có chủ đích.
+Hãy dùng các tài liệu chuẩn liên kết bên dưới cho bề mặt sản phẩm hiện tại.
 
-- Package: `@jstn-sdk/rcs`
-- Repository: `https://github.com/JustineDevs/roblox-ai-os`
-- Getting started: [../getting-started.html](../getting-started.html)
-- Skills reference: [../skills.html](../skills.html)
-- Integrations: [../integrations.html](../integrations.html)
-- Canonical README: [../../README.md](../../README.md)
+- Gói: `@jstn-sdk/rcs`
+- Kho mã: `https://github.com/JustineDevs/roblox-ai-os`
+- Bắt đầu: [../getting-started.html](../getting-started.html)
+- Tham chiếu skills: [../skills.html](../skills.html)
+- Tích hợp: [../integrations.html](../integrations.html)
+- README chuẩn: [../../README.md](../../README.md)
 
-## Canonical Creator Workflow
+## Quy trình creator chuẩn
 
 `$brief` -> `$blueprint` -> `$forge` / `$crew` -> `$autoforge`
 
-For Roblox implementation work, the mandatory pre-action gate applies before any code generation:
-- gather references
-- build understanding
-- standardize terms
-- design modular file tree architecture
-- only then implement
+Đối với công việc triển khai Roblox, pre-action gate bắt buộc được áp dụng trước mọi bước sinh mã:
+- thu thập tài liệu tham chiếu
+- xây dựng hiểu biết
+- chuẩn hóa thuật ngữ
+- thiết kế kiến trúc cây tệp dạng mô-đun
+- chỉ sau đó mới triển khai
 
-See:
+Xem:
 - [../../README.md](../../README.md)
 - [../skills.html](../skills.html)
 - [../reference/roblox-pre-action-protocol.md](../reference/roblox-pre-action-protocol.md)
 
-## Ownership
+## Quyền sở hữu
 
-RCS is owned and maintained by [JustineDevs](https://github.com/JustineDevs) and [@JustineDevs](https://github.com/JustineDevs) for Roblox creator workflows.
+RCS thuộc sở hữu và được duy trì bởi [JustineDevs](https://github.com/JustineDevs) và [@JustineDevs](https://github.com/JustineDevs) cho các workflow creator của Roblox.
 
-## Acknowledgements
+## Lời cảm ơn
 
 - [OpenAI Codex CLI](https://github.com/openai/codex)
+- [oh-my-codex](https://github.com/Yeachan-Heo/oh-my-codex)
 - [robloxstudio-mcp](https://github.com/boshyxd/robloxstudio-mcp)
 
-## License
+## Giấy phép
 
 [MIT](https://opensource.org/licenses/MIT)

package/docs/readme/README.zh-TW.md

@@ -1,40 +1,41 @@
 # Roblox Creator Skills (RCS)
 
-This localized README is intentionally condensed for the strict v0.1.0 ship pass.
-Use the canonical checked-in docs below for the current product surface.
+這份在地化 README 刻意保持精簡。
+目前產品表面請以下方連結的正規文件為準。
 
-- Package: `@jstn-sdk/rcs`
-- Repository: `https://github.com/JustineDevs/roblox-ai-os`
-- Getting started: [../getting-started.html](../getting-started.html)
-- Skills reference: [../skills.html](../skills.html)
-- Integrations: [../integrations.html](../integrations.html)
-- Canonical README: [../../README.md](../../README.md)
+- 套件：`@jstn-sdk/rcs`
+- 儲存庫：`https://github.com/JustineDevs/roblox-ai-os`
+- 快速開始： [../getting-started.html](../getting-started.html)
+- Skills 參考： [../skills.html](../skills.html)
+- 整合： [../integrations.html](../integrations.html)
+- 正規 README： [../../README.md](../../README.md)
 
-## Canonical Creator Workflow
+## 正規創作者工作流程
 
 `$brief` -> `$blueprint` -> `$forge` / `$crew` -> `$autoforge`
 
-For Roblox implementation work, the mandatory pre-action gate applies before any code generation:
-- gather references
-- build understanding
-- standardize terms
-- design modular file tree architecture
-- only then implement
+對於 Roblox 實作工作，在任何程式碼產生之前都必須先通過 pre-action gate：
+- 蒐集參考資料
+- 建立理解
+- 統一術語
+- 設計模組化檔案樹架構
+- 然後才開始實作
 
-See:
+請參考：
 - [../../README.md](../../README.md)
 - [../skills.html](../skills.html)
 - [../reference/roblox-pre-action-protocol.md](../reference/roblox-pre-action-protocol.md)
 
-## Ownership
+## 擁有權
 
-RCS is owned and maintained by [JustineDevs](https://github.com/JustineDevs) and [@JustineDevs](https://github.com/JustineDevs) for Roblox creator workflows.
+RCS 由 [JustineDevs](https://github.com/JustineDevs) 與 [@JustineDevs](https://github.com/JustineDevs) 擁有並維護，用於 Roblox 創作者工作流程。
 
-## Acknowledgements
+## 致謝
 
 - [OpenAI Codex CLI](https://github.com/openai/codex)
+- [oh-my-codex](https://github.com/Yeachan-Heo/oh-my-codex)
 - [robloxstudio-mcp](https://github.com/boshyxd/robloxstudio-mcp)
 
-## License
+## 授權
 
 [MIT](https://opensource.org/licenses/MIT)

package/docs/readme/README.zh.md

@@ -1,40 +1,41 @@
 # Roblox Creator Skills (RCS)
 
-This localized README is intentionally condensed for the strict v0.1.0 ship pass.
-Use the canonical checked-in docs below for the current product surface.
+这份本地化 README 有意保持简洁。
+当前产品表面请以下方链接的规范文档为准。
 
-- Package: `@jstn-sdk/rcs`
-- Repository: `https://github.com/JustineDevs/roblox-ai-os`
-- Getting started: [../getting-started.html](../getting-started.html)
-- Skills reference: [../skills.html](../skills.html)
-- Integrations: [../integrations.html](../integrations.html)
-- Canonical README: [../../README.md](../../README.md)
+- 包名：`@jstn-sdk/rcs`
+- 仓库：`https://github.com/JustineDevs/roblox-ai-os`
+- 入门： [../getting-started.html](../getting-started.html)
+- Skills 参考： [../skills.html](../skills.html)
+- 集成： [../integrations.html](../integrations.html)
+- 规范 README： [../../README.md](../../README.md)
 
-## Canonical Creator Workflow
+## 规范的创作者工作流
 
 `$brief` -> `$blueprint` -> `$forge` / `$crew` -> `$autoforge`
 
-For Roblox implementation work, the mandatory pre-action gate applies before any code generation:
-- gather references
-- build understanding
-- standardize terms
-- design modular file tree architecture
-- only then implement
+对于 Roblox 实现工作，任何代码生成之前都必须先通过 pre-action gate：
+- 收集参考资料
+- 建立理解
+- 统一术语
+- 设计模块化文件树架构
+- 然后才开始实现
 
-See:
+参见：
 - [../../README.md](../../README.md)
 - [../skills.html](../skills.html)
 - [../reference/roblox-pre-action-protocol.md](../reference/roblox-pre-action-protocol.md)
 
-## Ownership
+## 所有权
 
-RCS is owned and maintained by [JustineDevs](https://github.com/JustineDevs) and [@JustineDevs](https://github.com/JustineDevs) for Roblox creator workflows.
+RCS 由 [JustineDevs](https://github.com/JustineDevs) 和 [@JustineDevs](https://github.com/JustineDevs) 拥有并维护，用于 Roblox 创作者工作流。
 
-## Acknowledgements
+## 致谢
 
 - [OpenAI Codex CLI](https://github.com/openai/codex)
+- [oh-my-codex](https://github.com/Yeachan-Heo/oh-my-codex)
 - [robloxstudio-mcp](https://github.com/boshyxd/robloxstudio-mcp)
 
-## License
+## 许可证
 
 [MIT](https://opensource.org/licenses/MIT)

package/docs/reference/canonical-vocabulary.md

@@ -102,5 +102,4 @@ Use these classifications consistently:
 - Active prompts/skills/missions should prefer this vocabulary.
 - Active prompts/skills/missions should expose taxonomy frontmatter so generated surface maps and validators can classify them consistently.
 - Generated surface-map output should stay synced with the active taxonomy layer.
-- Historical docs may mention removed or generic terms only as archive/reference context.
 - Tests may mention removed terms in negative assertions, migration guards, or compatibility fixtures, but not as active surface recommendations.

package/docs/reference/semantic-design-system.md

@@ -92,13 +92,6 @@ Every mission bundle should communicate the same semantic shape.
 9. reference layers
 10. vocabulary guardrail
 
-## Archive Rule
-
-Historical surfaces may describe deleted/generic role labels, but:
-- they should be clearly archival
-- they should not be used as active onboarding
-- they should not be required by active runtime/catalog behavior
-
 ## Enforcement
 
 The repo should keep lightweight tests that verify:

package/docs/reference/surface-map.md

@@ -114,18 +114,9 @@ Sources:
 | `prompts/writer.md` | `prompt` | `creator-runtime` | `internal` | writer |
 | `skills/worker/SKILL.md` | `skill` | `creator-runtime` | `internal` | worker |
 
-## Historical Surfaces
-
-| Path | Type | Domain | Audience | Surface |
-| --- | --- | --- | --- | --- |
-| `skills/forge-init/SKILL.md` | `skill` | `archive` | `archive` | forge-init |
-| `skills/swarm/SKILL.md` | `skill` | `archive` | `archive` | swarm |
-| `skills/web-clone/SKILL.md` | `skill` | `archive` | `archive` | web-clone |
-
 ## Additional Repo Lanes
 
 - `AGENTS.md` and `templates/AGENTS.md` remain the orchestration brain and guidance authority.
-- `docs/archive/` is the historical lane; archive content may describe removed surfaces but must not act as active onboarding.
 - `src/catalog/manifest.json`, `templates/catalog-manifest.json`, and `src/catalog/generated/public-catalog.json` are the catalog source/generated contract lane.
 - `dist/` is generated runtime output and should reflect the taxonomy, not redefine it.
 

package/docs/release-notes-v0.1.6.md

@@ -0,0 +1,27 @@
+# Roblox Creator Skills v0.1.6
+
+## Summary
+
+`v0.1.6` is the release-automation follow-up after the `0.1.1` hardening line. It introduces explicit latest-version command triggers, binds automated npm publishing to the guarded `npm-publish` GitHub Actions environment, and finishes the remaining README ownership/acknowledgement consistency work.
+
+## What changed
+
+- Added explicit update aliases:
+  - `rcs latest`
+  - `rcs @latest`
+- Kept the direct npm install path explicit:
+  - `npm install -g @jstn-sdk/rcs@latest`
+- Bound automated npm publishing to:
+  - GitHub Actions environment `npm-publish`
+- Added `oh-my-codex` acknowledgement as a stepping-stone influence
+- Synchronized canonical/localized README ownership, acknowledgement, and linked license surfaces
+
+## Verification
+
+- `npm run build`
+- `node --test dist/cli/__tests__/index.test.js dist/cli/__tests__/update.test.js dist/cli/__tests__/package-bin-contract.test.js`
+- `node --test dist/verification/__tests__/explore-harness-release-workflow.test.js`
+
+## Note on version numbering
+
+This repo history already carried older local tags through `v0.1.5`, while the npm registry only had `0.1.0` and `0.1.1` published. `v0.1.6` was selected to avoid tag collisions and keep the automated release lane clean.

package/docs/release-notes-v0.1.7.md

@@ -0,0 +1,20 @@
+# Roblox Creator Skills v0.1.7
+
+## Summary
+
+`v0.1.7` is the doc/prompt hardening release after the `0.1.6` automation update. It removes the last archive lane, rewrites the demo surface around Roblox-first creator workflows, strengthens Roblox-native framing inside the prompt system, and replaces the placeholder localized README stubs with real translated bodies.
+
+## What changed
+
+- Removed `docs/archive/` from the project surface
+- Reduced active `docs/qa/` to the live gate docs only
+- Rewrote `DEMO.md` into a Roblox-first demo guide
+- Tightened prompt identities/goals for Roblox-native framing across key internal prompts
+- Replaced localized README placeholder stubs with actual localized content
+
+## Verification
+
+- `npm run build`
+- prompt-guidance and taxonomy contract tests
+- semantic/workspace/robloxstudio-mcp verification tests
+- `node dist/scripts/surface-taxonomy.js`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jstn-sdk/rcs",
-  "version": "0.1.1",
+  "version": "0.1.7",
   "description": "Roblox Creator Skills toolkit and workflow layer for Codex CLI",
   "type": "module",
   "main": "dist/index.js",

package/plugins/roblox-ai-os-creator-skills/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "roblox-ai-os-creator-skills",
-  "version": "0.1.1",
+  "version": "0.1.7",
   "description": "Roblox Creator Skills workflow and runtime bundle for Codex CLI",
   "author": {
     "name": "JustineDevs",

package/prompts/analyst.md

@@ -7,7 +7,7 @@ audience: "internal"
 artifact-type: "prompt"
 ---
 <identity>
-You are Analyst (Metis). Your mission is to convert decided product scope into implementable acceptance criteria, catching gaps before planning begins.
+You are Analyst (Metis). Your mission is to convert decided product scope into implementable acceptance criteria for Roblox Studio and creator workflow changes, catching gaps before planning begins.
 You are responsible for identifying missing questions, undefined guardrails, scope risks, unvalidated assumptions, missing acceptance criteria, and edge cases.
 You are not responsible for market/user-value prioritization, code analysis (architect), plan creation (planner), or plan review (critic).
 
@@ -17,7 +17,7 @@ Plans built on incomplete requirements produce implementations that miss the tar
 <constraints>
 <scope_guard>
 - Read-only: Write and Edit tools are blocked.
-- Focus on implementability, not market strategy. "Is this requirement testable?" not "Is this feature valuable?"
+- Focus on implementability, not market strategy. "Is this remote contract or onboarding rule testable?" not "Is this feature valuable?"
 - When receiving a task with architectural context, proceed with best-effort analysis and note any code-context gaps in your output for the leader to route.
 - Escalate findings upward to the leader for routing: planner (requirements gathered), architect (code analysis needed), critic (plan exists and needs review).
 </scope_guard>
@@ -111,7 +111,7 @@ The orchestrator or planner will persist open questions to `.rcs/plans/open-ques
 
 <anti_patterns>
 - Market analysis: Evaluating "should we build this?" instead of "can we build this clearly?" Focus on implementability.
-- Vague findings: "The requirements are unclear." Instead: "The error handling for `createUser()` when email already exists is unspecified. Should it return 409 Conflict or silently update?"
+- Vague findings: "The requirements are unclear." Instead: "The trade remote does not say what the server should do when the offered item is no longer in the player's inventory. Should the request fail loudly, silently reject, or re-sync the inventory UI?"
 - Over-analysis: Finding 50 edge cases for a simple feature. Prioritize by impact and likelihood.
 - Missing the obvious: Catching subtle edge cases but missing that the core happy path is undefined.
 - Upward escalation loop: Re-reporting needs to the leader without processing the requirement gap. Process the request first, then note any routing needs.
@@ -137,6 +137,3 @@ The orchestrator or planner will persist open questions to `.rcs/plans/open-ques
 - Are open questions included in the response output under `### Open Questions`?
 </final_checklist>
 </style>
-surface-class: "internal"
-domain: "creator-runtime"
-audience: "internal"

package/prompts/architect.md

@@ -7,7 +7,8 @@ audience: "internal"
 artifact-type: "prompt"
 ---
 <identity>
-You are Architect (Oracle). Diagnose, analyze, and recommend with file-backed evidence. You are read-only.
+You are Architect (Oracle). Diagnose, analyze, and recommend with file-backed evidence for Roblox Studio, creator runtime, plugin, and Luau surfaces. You are read-only.
+Your primary frame is Roblox-native system design: **ModuleScript boundaries**, **client/server ownership**, **RemoteEvent / RemoteFunction contracts**, **DataStore and economy state**, **plugin widget structure**, and **creator-facing experience loops** before generic software abstractions.
 </identity>
 
 <constraints>
@@ -113,6 +114,3 @@ Default final-output shape: outcome-first and evidence-dense; include the result
 - For blueprint consensus reviews, did I include antithesis, tradeoff tension, and synthesis?
 </final_checklist>
 </style>
-surface-class: "internal"
-domain: "creator-runtime"
-audience: "internal"

package/prompts/build-fixer.md

@@ -8,7 +8,7 @@ artifact-type: "prompt"
 ---
 <identity>
 You are Build Fixer. Your mission is to get a failing build green with the smallest possible changes.
-You are responsible for fixing type errors, compilation failures, import errors, dependency issues, and configuration errors.
+You are responsible for fixing type errors, compilation failures, import errors, dependency issues, and configuration errors across the RCS runtime and its Roblox Studio workspace/toolchain surfaces.
 You are not responsible for refactoring, performance optimization, feature implementation, architecture changes, or code style improvements.
 
 A red build blocks the entire team. These rules exist because the fastest path to green is fixing the error, not redesigning the system. Build fixers who refactor "while they're in there" introduce new failures and slow everyone down. Fix the error, verify the build, move on.
@@ -18,7 +18,10 @@ A red build blocks the entire team. These rules exist because the fastest path t
 <scope_guard>
 - Fix with minimal diff. Do not refactor, rename variables, add features, optimize, or redesign.
 - Do not change logic flow unless it directly fixes the build error.
-- Detect language/framework from manifest files (package.json, Cargo.toml, go.mod, pyproject.toml) before choosing tools.
+- Detect the active surface from repo evidence before choosing tools:
+  - `package.json` / Node runtime
+  - `Cargo.toml` / Rust binaries
+  - `default.project.json`, `wally.toml`, `aftman.toml`, `stylua.toml`, `selene.toml` / Roblox Studio workspace toolchain
 - Track progress: "X/Y errors fixed" after each fix.
 </scope_guard>
 
@@ -117,6 +120,3 @@ Default final-output shape: outcome-first and evidence-dense; include the result
 - Is fresh build output shown as evidence?
 </final_checklist>
 </style>
-surface-class: "internal"
-domain: "creator-runtime"
-audience: "internal"

package/prompts/code-reviewer.md

@@ -7,7 +7,8 @@ audience: "internal"
 artifact-type: "prompt"
 ---
 <identity>
-You are Code Reviewer. Your mission is to ensure code quality and security through systematic, severity-rated review.
+You are Code Reviewer. Your mission is to ensure Roblox Studio, Luau, and creator-runtime code quality through systematic, severity-rated review.
+Your primary frame is Roblox-specific: **server authority**, **remote validation**, **DataStore/economy safety**, **client/server ownership**, **plugin/widget boundaries**, and **creator workflow correctness** before generic style concerns.
 You are responsible for spec compliance verification, security checks, code quality assessment, performance review, and best practice enforcement.
 You are not responsible for implementing fixes (executor), architecture design (architect), or writing tests (test-engineer).
 When paired with an `architect` lane in the `code-review` workflow, you own the code/spec/security lane and must report architectural concerns upward instead of turning them into the final design verdict yourself.
@@ -22,6 +23,7 @@ Code review is the last line of defense before bugs and vulnerabilities reach pr
 - Never skip Stage 1 (spec compliance) to jump to style nitpicks.
 - For trivial changes (single line, typo fix, no behavior change): skip Stage 1, brief Stage 2 only.
 - Be constructive: explain WHY something is an issue and HOW to fix it.
+- Review Roblox truth first: remotes, authoritative state mutation, replicated data exposure, economy/progression safety, and plugin/widget ownership come before generic style notes.
 </scope_guard>
 
 <ask_gate>
@@ -139,6 +141,3 @@ APPROVE / REQUEST CHANGES / COMMENT
 - Did I check for **Roblox security** issues (secrets on client/replicated trees, unvalidated remotes, unsafe DataStore/economy paths)?
 </final_checklist>
 </style>
-surface-class: "internal"
-domain: "creator-runtime"
-audience: "internal"

package/prompts/critic.md

@@ -82,6 +82,3 @@ Use Read for plans/referenced files, Grep/Glob for referenced patterns, and Bash
 Stop when all referenced evidence and representative simulations support a clear verdict.
 </stop_rules>
 </style>
-surface-class: "internal"
-domain: "creator-runtime"
-audience: "internal"