TanStack · LadyBluenotes · Mar 5, 2026 · Mar 5, 2026 · Mar 5, 2026 · Mar 5, 2026
diff --git a/.changeset/config.json b/.changeset/config.json
@@ -1,17 +1,17 @@
-{
-  "$schema": "https://unpkg.com/@changesets/config@3.1.2/schema.json",
-  "changelog": [
-    "@svitejs/changesets-changelog-github-compact",
-    { "repo": "TanStack/intent" }
-  ],
-  "commit": false,
-  "access": "public",
-  "baseBranch": "main",
-  "updateInternalDependencies": "patch",
-  "fixed": [],
-  "linked": [],
-  "ignore": [],
-  "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
-    "onlyUpdatePeerDependentsWhenOutOfRange": true
-  }
-}
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.2/schema.json",
+  "changelog": [
+    "@svitejs/changesets-changelog-github-compact",
+    { "repo": "TanStack/intent" }
+  ],
+  "commit": false,
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "fixed": [],
+  "linked": [],
+  "ignore": [],
+  "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
+    "onlyUpdatePeerDependentsWhenOutOfRange": true
+  }
+}
diff --git a/.changeset/whole-rocks-wait.md b/.changeset/whole-rocks-wait.md
@@ -0,0 +1,32 @@
+---
+'@tanstack/playbooks': patch
+---
+
+3 files changed in packages/playbooks/meta/
+
+domain-discovery/SKILL.md (681 → ~792 lines)
+- Added "Hard rules" section: 7 mandatory rules enforcing interactive interviews, prohibiting docs-as-substitute, question collapsing, and interview skipping
+- Added 3 STOP gates between phases (1→2, 3→4, and after Phase 2d skill list confirmation)
+- Strengthened Phase 2 & 4 headers with explicit interactivity requirements and "wait for response" instructions
+- Added Phase 3 thoroughness: file checklist before reading, read-all enforcement, peer dependency analysis in Phase 1b
+- Added 7 new constraint table rows for interview interactivity
+- Updated cross-model compatibility notes with STOP gate and question protection rationale
+- Added cross-package monorepo question in Phase 2a
+- Added packages field to domain_map.yaml schema (package-relative ownership model)
+- Softened feedback section to alpha-temporary
+
+- tree-generator/SKILL.md (859 → ~898 lines)
+- Strengthened compressed discovery warning (requires maintainer confirmation to skip)
+- Added packages field to skill_tree.yaml schema
+- Added monorepo placement section with concrete directory tree example showing skills inside each package
+- Added STOP gate after Step 1 (file tree review before writing)
+- Added STOP gate after Step 8 (validation results review)
+- Added 2 new constraint rows (file tree reviewed, validation presented)
+- Softened feedback section to alpha-temporary
+
+- generate-skill/SKILL.md (419 → ~441 lines)
+- Added packages field to frontmatter template
+- Added monorepo path guidance: skills ship inside each package, not repo root
+- Added STOP gate in Step 6: first skill reviewed before generating batch
+- Added first-skill-reviewed constraint row
+- Softened feedback section to alpha-temporary
diff --git a/.prettierignore b/.prettierignore
@@ -1,12 +1,12 @@
-.github
-**/.nx/
-**/.nx/cache
-**/.svelte-kit
-**/build
-**/coverage
-**/dist
-**/docs
-**/old-examples
-pnpm-lock.yaml
-
-.angular
+.github
+**/.nx/
+**/.nx/cache
+**/.svelte-kit
+**/build
+**/coverage
+**/dist
+**/docs
+**/old-examples
+pnpm-lock.yaml
+
+.angular
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,55 +1,55 @@
----
-title: Contributing
-id: contributing
----
-
-# Contributing
-
-## Questions
-
-If you have questions about implementation details, help or support, then please use our dedicated community forum at [Github Discussions](https://github.com/tanstack/intent/discussions) **PLEASE NOTE:** If you choose to instead open an issue for your question, your issue will be immediately closed and redirected to the forum.
-
-## Reporting Issues
-
-If you have found what you think is a bug, please [file an issue](https://github.com/tanstack/intent/issues/new). **PLEASE NOTE:** Issues that are identified as implementation questions or non-issues will be immediately closed and redirected to [Github Discussions](https://github.com/tanstack/intent/discussions)
-
-## Suggesting new features
-
-If you are here to suggest a feature, first create an issue if it does not already exist. From there, we will discuss use-cases for the feature and then finally discuss how it could be implemented.
-
-## Development
-
-Before proceeding with development, ensure you match one of the following criteria:
-
-- Fixing a small bug
-- Fixing a larger issue that has been previously discussed and agreed-upon by maintainers
-- Adding a new feature that has been previously discussed and agreed-upon by maintainers
-
-## Development Workflow
-
-- Fork this repository, we prefer the `feat-*` branch name style
-- Ensure you have `pnpm` installed
-- Install projects dependencies and linkages by running `pnpm install`
-- Auto-build and auto-test files as you edit by running `pnpm dev`
-- Implement your changes and tests
-- To run examples, follow their individual directions. Usually this includes:
-  - cd into the example directory
-  - Do NOT install dependencies again or do any linking. Nx already handles this for you. Only run install from the project root.
-  - Starting the dev server with `pnpm dev` or `pnpm start` (from the example directory)
-- To test in your own projects:
-  - Build/watch for changes with `pnpm build`/`pnpm dev`
-- Document your changes in the appropriate documentation website markdown pages
-- Run `pnpm test` to ensure all tests pass before committing
-- Create a changeset (changelog entry) for your changes by running `pnpm changeset`
-- Commit your work and open a pull request
-- Submit PR for review
-
-## Adding a new example
-
-- Clone an existing example into the appropriate `examples` directory
-- Name it the example name in kebab-case
-- Update the new example's package.json to match the new example name and any other details
-- Check dependencies for unused packages
-- Install any additional packages to the example that you may need
-- Update the docs/config.json file to include the new example in the navigation sidebar
-- Commit the example eg. `docs: Add example-name`
+---
+title: Contributing
+id: contributing
+---
+
+# Contributing
+
+## Questions
+
+If you have questions about implementation details, help or support, then please use our dedicated community forum at [Github Discussions](https://github.com/tanstack/intent/discussions) **PLEASE NOTE:** If you choose to instead open an issue for your question, your issue will be immediately closed and redirected to the forum.
+
+## Reporting Issues
+
+If you have found what you think is a bug, please [file an issue](https://github.com/tanstack/intent/issues/new). **PLEASE NOTE:** Issues that are identified as implementation questions or non-issues will be immediately closed and redirected to [Github Discussions](https://github.com/tanstack/intent/discussions)
+
+## Suggesting new features
+
+If you are here to suggest a feature, first create an issue if it does not already exist. From there, we will discuss use-cases for the feature and then finally discuss how it could be implemented.
+
+## Development
+
+Before proceeding with development, ensure you match one of the following criteria:
+
+- Fixing a small bug
+- Fixing a larger issue that has been previously discussed and agreed-upon by maintainers
+- Adding a new feature that has been previously discussed and agreed-upon by maintainers
+
+## Development Workflow
+
+- Fork this repository, we prefer the `feat-*` branch name style
+- Ensure you have `pnpm` installed
+- Install projects dependencies and linkages by running `pnpm install`
+- Auto-build and auto-test files as you edit by running `pnpm dev`
+- Implement your changes and tests
+- To run examples, follow their individual directions. Usually this includes:
+  - cd into the example directory
+  - Do NOT install dependencies again or do any linking. Nx already handles this for you. Only run install from the project root.
+  - Starting the dev server with `pnpm dev` or `pnpm start` (from the example directory)
+- To test in your own projects:
+  - Build/watch for changes with `pnpm build`/`pnpm dev`
+- Document your changes in the appropriate documentation website markdown pages
+- Run `pnpm test` to ensure all tests pass before committing
+- Create a changeset (changelog entry) for your changes by running `pnpm changeset`
+- Commit your work and open a pull request
+- Submit PR for review
+
+## Adding a new example
+
+- Clone an existing example into the appropriate `examples` directory
+- Name it the example name in kebab-case
+- Update the new example's package.json to match the new example name and any other details
+- Check dependencies for unused packages
+- Install any additional packages to the example that you may need
+- Update the docs/config.json file to include the new example in the navigation sidebar
+- Commit the example eg. `docs: Add example-name`
diff --git a/LICENSE b/LICENSE
@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2025-present Tanner Linsley
-
-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.
+MIT License
+
+Copyright (c) 2025-present Tanner Linsley
+
+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.