@craft-ts/mcp 0.8.6 → 0.8.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@craft-ts/mcp",
-  "version": "0.8.6",
+  "version": "0.8.8",
   "description": "MCP server, Agent Skills, and LLM files for coding agents using @craft-ts/core",
   "author": "Romain Geffrault",
   "license": "MIT",
@@ -35,7 +35,7 @@
     "test": "vitest run --config vitest.config.mts"
   },
   "dependencies": {
-    "@craft-ts/dev-tools": "^0.8.6",
+    "@craft-ts/dev-tools": "^0.8.8",
     "@modelcontextprotocol/sdk": "1.26.0",
     "zod": "4.3.6"
   },

package/skills/craft-ts/SKILL.md

@@ -21,8 +21,8 @@ required and must not be introduced just to solve a Craft problem.
    - `migrate-to-craft-ts` — run `craft-migrate`, then finish diagnostics
    - `craft-ts-effect-v4` — use Effect v4 services, Layers, `queryEffect`, and
      the synchronous-member declaration (`SyncOp` / `computedEffect`)
-   - `craft-ts-style` — the typed design system: sheets, axes, the visual
-     matrix, context obligations
+   - `craft-ts-style` — the typed design system: sheets, axes, static text
+     contrast, the visual matrix, context obligations
    - `craft-ts-i18n` — typed catalogues, locale parity, semantic tokens
 
 For a project created by `craft create`, keep the generated development
@@ -57,7 +57,9 @@ If MCP is not configured, read https://ng-angular-stack.github.io/craft/llms.txt
   Never assemble a class string at render time — the template sets one constant
   class and a `data-*` attribute. `@craft-ts/style` is a **build step**: without
   `craftStyle()` from `@craft-ts/style/vite` in the Vite config, the sheets
-  typecheck and emit nothing. Load `craft-ts-style` before touching one.
+  typecheck and emit nothing. Load `craft-ts-style` before touching one. When
+  the project exposes `npm run style:check`, run it after changing colours,
+  typography, template classes, themes, hover or another visual axis.
 - Translations live in a `@craft-ts/i18n` catalogue: `defineCatalog` + `msg` for
   the reference locale, `defineLocaleLike` for every other one, so a missing key
   is a compile error. A token may validate or parse its parameter with a

package/skills/craft-ts-style/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: craft-ts-style
-description: Build and review the typed design system of a CraftTS project with @craft-ts/style — palettes, axes, typed custom properties, sheets, context obligations, the visual matrix, and the style_impact / style_matrix / style_debt MCP tools. Use when adding or changing visual rules, a variant, a theme, dark mode, or a visual test.
+description: Build and review the typed design system of a CraftTS project with @craft-ts/style — palettes, axes, typed custom properties, sheets, static text-contrast checks, context obligations, the visual matrix, and style graph tools. Use when adding or changing visual rules, colours, typography, a variant, hover, a theme, dark mode, or a visual test.
 ---
 
 # CraftTS typed styles
@@ -15,14 +15,17 @@ emitted from.
 The system is a **build step**, not a runtime library. Before writing a rule,
 confirm three things exist; without them the sheets typecheck and emit nothing.
 
-1. `@craft-ts/style` in `dependencies`, `@craft-ts/style-testing` in
-   `devDependencies`.
+1. `@craft-ts/style` in `dependencies`. Static contrast additionally needs
+   `@craft-ts/dev-tools` in `devDependencies`; `@craft-ts/style-testing` is
+   needed only for visual scenarios or attestation.
 2. `craftStyle()` from `@craft-ts/style/vite` in the Vite `plugins` array, with
    a `dumpPath`. The dump is what the graph and the MCP tools below read; no
    `dumpPath`, no answers.
 3. `import 'virtual:craft-style.css'` once, at the app entry.
 
-A project created by `craft create` already has all three.
+A current project created by `craft create` with typed CSS already has the
+required wiring. An older project must be migrated explicitly; do not assume
+updating the package rewrites its Vite, ESLint or CI configuration.
 
 ## Hard rules
 
@@ -52,7 +55,7 @@ A project created by `craft create` already has all three.
 
 | you need              | call                                        |
 | --------------------- | ------------------------------------------- |
-| colours               | `definePalette({ group: { token: { light, dark } } })` |
+| colours               | `definePalette('ui', { group: { token: { light, dark } } })` |
 | viewport breakpoints  | `defineBreakpoints({ md: at.minInlineSize(unit.rem(48)) })` |
 | a state variant       | `defineStateAxis('tone', ['neutral', 'danger'])` |
 | an axis that may only write one kind | `defineAxis(name, values, onlyVarsOfKind(kind.color))` |
@@ -60,8 +63,8 @@ A project created by `craft create` already has all three.
 | typed custom properties | `cssVars('prefix', { ink: kind.color(token) })` |
 | the rules themselves  | `craftStyles('name', { root: [...] }, { axes: [...] })` |
 
-`scheme`, `motion`, `forcedColors`, `contrast`, `scrollState` and `descendant`
-ship with the package and need no declaration.
+`scheme`, `motion`, `forcedColors`, `contrast`, `interaction`, `scrollState`
+and `descendant` ship with the package and need no declaration.
 
 Two details the types cannot enforce and the browser does:
 
@@ -82,6 +85,56 @@ Level 3 is a **per-route** guarantee. One component in the path handing back a
 loosely typed subtree stops the requirement travelling, and a partial adoption
 gives zero of the guarantee, not most of it.
 
+## Static text contrast
+
+`npm run style:check` is the blocking WCAG 2.2 AA text-contrast proof. It builds
+once so `craftStyle({ dumpPath: '.craft/style-graph.json' })` writes the style
+dump, then runs:
+
+```bash
+craft-graph --style-contrast --style-dump .craft/style-graph.json --project tsconfig.app.json
+```
+
+It reads typed sheets and the TypeScript template graph; it does not need a
+browser, screenshots or Playwright. It checks `4.5:1` for normal text and `3:1`
+for text at least 24px, or at least 18.5px with weight 700 or above.
+
+When changing a palette, `color`, `background-color`, font size/weight, a
+template class, theme or visual axis, run `npm run style:check` after the
+focused tests. A failure should be fixed at the named token or state, not hidden
+with a local colour override.
+
+Model hover through `when(interaction.hover, [...])`, nest it inside the tone
+or other state it combines with, and add `interaction` to the sheet's `axes`
+budget. A hand-written `:hover` emits CSS but is invisible to the scenario
+contract. Enable `craftRules.configs.typedCss.rules` so raw hover and contrast
+properties in component styles fail lint.
+
+Indeterminate rows fail by default. `--allow-indeterminate` is only for the
+first migration inventory; remove it before adding the check to CI. An empty
+report also fails, because zero checked elements is normally broken wiring, not
+a clean application.
+
+Do not overstate coverage. Background images, alpha, unknown sizes, dynamic
+classes and incomplete render contexts become indeterminate when they reach the
+graph. External CSS, inline styles outside CraftTS, canvas/SVG text, generated
+content, filters and blend modes may be invisible altogether. The ESLint
+`uncovered` option only suppresses lint for a path; it does not add a gap to the
+contrast report. Font-script and cap-height differences, including CJK, are not
+detected from the CSS size/weight convention.
+
+### Retrofitting an older project
+
+1. Align installed `@craft-ts/*` packages on one current version.
+2. Name palettes with `definePalette('name', spec)`.
+3. Add the dump path to `craftStyle()` and keep
+   `virtual:craft-style.css` imported once at app entry.
+4. Enable the `typedCss` ESLint preset and migrate hand-written hover to
+   `interaction.hover`.
+5. Add the build-plus-`craft-graph --style-contrast` command as `style:check`.
+6. Run once with `--allow-indeterminate`, close visible gaps, remove the flag,
+   then add `npm run style:check` to CI.
+
 ## Testing
 
 ```ts
@@ -113,4 +166,5 @@ Three MCP tools read the dump, so you do not have to write a script:
 An empty `style_matrix` is the signature of a missing `dumpPath`.
 
 Full guide: `/guide/style/setup`, `/guide/style/define`, `/guide/style/tokens`,
-`/guide/style/variants`, `/guide/style/obligations`, `/guide/style/testing`.
+`/guide/style/variants`, `/guide/style/obligations`, `/guide/style/testing`,
+`/guide/style/contrast`.

package/skills/translate-spec-to-craft-ts/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: translate-spec-to-craft-ts
-description: Translate functional specifications, user stories, page requirements, CRUD flows, list/detail screens, filters, pagination, bulk actions, optimistic updates, forms, and Angular feature-store architecture into @craft-ts/core primitives, insertions, store utilities, and source helpers. Use when a request asks which craft-ts utility to choose, or when wording such as "afficher", "liste", "detail", "supprimer", "selection multiple", "pagination", "filtre URL", "formulaire", "recharger en cas d'erreur", or "feature store" must be mapped to `query`, `mutation`, `state`, `queryParams`, `craft*`, form helpers, or entity helpers.
+description: Translate functional specifications, user stories, page requirements, CRUD flows, list/detail screens, filters, pagination, bulk actions, optimistic updates, forms, and Angular feature architecture into @craft-ts/core primitives, insertions, services, and source helpers. Use when a request asks which craft-ts utility to choose, or when wording such as "afficher", "liste", "detail", "supprimer", "selection multiple", "pagination", "filtre URL", "formulaire", "recharger en cas d'erreur", or "feature" must be mapped to `query`, `mutation`, `state`, `queryParams`, `craftService`, form helpers, or entity helpers.
 ---
 
 # Translate Spec To Ng Craft
@@ -33,12 +33,12 @@ the published docs (MCP `search_documentation`, or https://ng-angular-stack.gith
 - Match generic asynchronous client tasks to `asyncProcess`.
 - Match local UI-only state to `state`.
 - Match URL-backed state to `queryParams`.
-- Match reusable, page-level, or global store requirements to `craft` plus `craft*` helpers.
+- Match reusable, page-level, or global feature requirements to `craftService` plus the primitives it owns.
 - Match event buses, resets, refreshes, and hidden triggers to `source$` and `on$`.
 - Match list collection semantics to `insertEntities` and the entity helpers when the spec explicitly talks about add, remove, update, upsert, replace, or clear.
 - Match nested sub-state behavior to `insertSelect`.
 - Match forms to `insertForm`, `insertSelectFormTree`, `insertFormAttributes`, and `insertFormSubmit`.
-- Treat `computedSource`, `toSource`, `signalSource`, `linkedSource`, `resourceById`, `toInject`, and other infra helpers as advanced choices. Do not choose them first unless the spec is about plumbing.
+- Treat `computedSource`, `toSource`, `signalSource`, `linkedSource`, `resourceById`, and other infra helpers as advanced choices. Do not choose them first unless the spec is about plumbing.
 
 ## Default Heuristics
 
@@ -49,8 +49,8 @@ the published docs (MCP `search_documentation`, or https://ng-angular-stack.gith
 - When optimistic deletion can empty the current page, consider a second `insertReactOnMutation(..., { reload: { onMutationResolved: true } })`.
 - When the spec mentions pagination or page transitions, consider `identifier` on the `query` and `insertPaginationPlaceholderData`.
 - When the spec mentions remembered filters, remembered results, refresh survival, or lightweight cache, consider `insertLocalStoragePersister`.
-- When the spec mentions parent-provided values or route or context values that are not URL query params, consider `craftInputs`.
-- When the spec mentions Angular services or a facade over a service, consider `craftInject` or `injectService`.
+- When the spec mentions parent-provided values or route or context values that are not URL query params, consider `CraftServiceInput` in a `craftService` factory.
+- When the spec mentions Angular services or a facade over a service, consider `craftService` and its generated dependency helpers.
 
 ## Output Contract
 
@@ -73,11 +73,11 @@ Spec: `Creer une page qui affiche une liste d'utilisateurs.`
 Mapping: `query` for remote list loading. Add `queryParams` only if pagination, filters, sort, or shareable URL state are part of the spec.
 
 Spec: `Creer une page qui affiche une liste d'utilisateurs. On peut supprimer un utilisateur via un bouton, ou en selectionner plusieurs pour en supprimer plusieurs.`
-Mapping: `query` for the list, one `mutation` for single delete, one `mutation` for bulk delete, one selection `state` or `craftState` for selected ids, and `insertReactOnMutation` on the `query` with optimistic removal plus `reload.onMutationError = true`. Use `removeOne` and `removeMany` for the optimistic transforms.
+Mapping: `query` for the list, one `mutation` for single delete, one `mutation` for bulk delete, one selection `state` for selected ids, and `insertReactOnMutation` on the `query` with optimistic removal plus `reload.onMutationError = true`. Use `removeOne` and `removeMany` for the optimistic transforms.
 Baseline helper already covering this: `assertMutationHasReactOn` (and `assertHttpEndpointUnique` if the list HTTP is owned once). Do not add an architecture rule for the feature.
 
 Spec: `Creer une page de recherche avec filtres dans l'URL et pagination sans flicker.`
-Mapping: `queryParams` for filter and pagination state, `query` for results, `insertPaginationPlaceholderData` to keep previous page data visible during transitions, `craftSetAllQueriesParamsStandalone` if the page must generate URLs outside injection context.
+Mapping: `queryParams` for filter and pagination state, `query` for results, and `insertPaginationPlaceholderData` to keep previous page data visible during transitions.
 
 ## References
 

package/skills/translate-spec-to-craft-ts/references/lexical-map.md

@@ -10,124 +10,78 @@ Prefer the documented APIs first. Use the advanced exports only when the request
 ### `query`
 
 Match: `afficher`, `liste`, `tableau`, `detail`, `charger`, `recuperer`, `fetch`, `read`, `dashboard`, `feed`, `resultats`, `historique`, `stats`, `donnees serveur`, `recharger`, `rafraichir`.
-Pair with: `queryParams`, `insertReactOnMutation`, `insertPaginationPlaceholderData`, `insertLocalStoragePersister`, `craftQuery`.
+Pair with: `queryParams`, `insertReactOnMutation`, `insertPaginationPlaceholderData`, `insertLocalStoragePersister`.
 Default: Use `params` for reactive inputs, `method` for explicit trigger flows, `identifier` for pagination or parallel instances, and `preservePreviousValue` or placeholder strategies when flicker matters.
 
 ### `mutation`
 
 Match: `creer`, `ajouter`, `enregistrer`, `modifier`, `mettre a jour`, `editer`, `patcher`, `supprimer`, `archiver`, `activer`, `desactiver`, `publier`, `bulk action`, `submit`, `confirmer`.
-Pair with: `insertReactOnMutation`, `insertFormSubmit`, `craftMutations`, `query`.
+Pair with: `insertReactOnMutation`, `insertFormSubmit`, `query`.
 Default: Create one mutation per server intent. Add `identifier` when row-level actions need independent loading states or cancellation semantics.
 
 ### `asyncProcess`
 
 Match: `debounce`, `temporiser`, `retarder`, `valider en asynchrone`, `autosave`, `partager`, `clipboard`, `native API`, `background task`, `processus asynchrone`, `polling`.
-Pair with: `source$`, `afterRecomputation`, `craftAsyncProcesses`.
+Pair with: `source$`, `afterRecomputation`.
 Default: Choose this when the flow is asynchronous but is not the canonical server read cache and is not a write that should drive query synchronization.
 
 ### `state`
 
 Match: `etat local`, `selection`, `toggle`, `ouvert`, `ferme`, `modal`, `onglet actif`, `draft`, `brouillon`, `checkbox`, `expanded`, `wizard step`, `current tab`, `UI state`.
-Pair with: `insertSelect`, `insertEntities`, `insertForm`, `craftState`.
+Pair with: `insertSelect`, `insertEntities`, `insertForm`.
 Default: Keep the state granular. Use it for client-only state and view state that should not live in the URL.
 
 ### `queryParams`
 
 Match: `URL`, `query string`, `search params`, `filtre URL`, `pagination URL`, `tri dans l'URL`, `onglet partageable`, `deep link`, `etat partageable`, `back-forward`.
-Pair with: `query`, `craftQueryParams`, `craftQueryParams`, `craftSetAllQueriesParamsStandalone`.
+Pair with: `query`.
 Default: Split URL concerns by group when useful. Put `page`, `pageSize`, `sort`, `search`, `filters`, `tab`, and similar shareable state here.
 
 ### `source$`
 
 Match: `trigger`, `refresh`, `reset`, `bus evenementiel`, `broadcast`, `declencher`, `signal d'action`, `event stream`, `cross feature trigger`.
-Pair with: `on$`, `afterRecomputation`, `craftSources`.
+Pair with: `on$`, `afterRecomputation`.
 Default: Choose this when the spec describes an event, not a persistent state.
 
 ### `on$`
 
 Match: `quand X arrive alors`, `react to`, `reset on`, `sync on`, `internal reaction`, `hidden binding`, `do not expose this method`.
-Pair with: `source$`, `state`, `mutation`, `asyncProcess`, `injectService`.
+Pair with: `source$`, `state`, `mutation`, `asyncProcess`, `craftService`.
 Default: Use this for hidden reactive wiring that should run from a source but should not become part of the public API.
 
-### `injectService`
+### `craftService` facade
 
 Match: `facade`, `wrapper de service`, `exposer une petite API`, `renommer des methodes`, `derive from service signals`, `hide imperative router/service API`.
-Pair with: `on$`, `computed`, `craftInject`.
+Pair with: `on$`, `craftComputed`, and generated service dependencies.
 Default: Choose this outside store composition when the user wants a smaller typed service-facing API.
 
-## Store Composition
+## Feature composition
 
-### `craft`
+### `craftService`
 
-Match: `feature store`, `page store`, `global store`, `store reutilisable`, `compose store`, `DI`, `providedIn`, `scope`, `reusable state module`.
-Pair with: `craftState`, `craftQuery`, `craftMutations`, `craftSources`, `craftInputs`, `craftQueryParams`, `craftQueryParams`, `craftInject`, `craftComputedStates`, `craftAsyncProcesses`.
-Default: Use `providedIn: 'feature'` for page or route scoped logic and `providedIn: 'root'` for global shared logic.
+Match: `feature`, `page logic`, `reusable state module`, `providedIn`, `scope`,
+`dependency injection`, or a domain facade shared by several components.
+Pair with: `state`, `query`, `mutation`, `asyncProcess`, `queryParams`,
+`source$`, and `craftYieldRecord`.
+Default: use `craftService` as the named boundary and return the primitives or
+facade methods that the feature actually exposes. Do not invent a separate
+store wrapper around each primitive.
 
-### `craftState`
+### `CraftServiceInput`
 
-Match: `etat local dans le store`, `selection store`, `modal store`, `draft store`, `store-owned UI state`.
-Pair with: `state`, `on$`.
-Default: Use when the state belongs inside a `craft` store and should be exposed as store entries and prefixed methods.
+Match: `parent provides id`, `route provides id`, `component input`, `external
+signal`, `context value`, or `page receives userId`.
+Pair with: `craftService` and the primitive that consumes the value.
+Default: declare changing service inputs as `CraftServiceInput<T>` and yield
+`inputs.value()` inside the service factory. Use `queryParams` only when the
+value belongs in the URL.
 
-### `craftQuery`
+### Derived and injected service logic
 
-Match: `requete dans le store`, `server state in store`, `cached resource in feature store`, `page query`.
-Pair with: `query`, `craftInputs`, `craftInject`, `craftQueryParams`, `insertReactOnMutation`.
-Default: Use when a `query` belongs inside a composed store boundary.
-
-### `craftMutations`
-
-Match: `actions serveur du store`, `store mutations`, `CRUD actions grouped in store`, `row actions in store`.
-Pair with: `mutation`, `craftQuery`, `insertReactOnMutation`.
-Default: Group server write actions here so the store gets prefixed trigger methods and typed state access.
-
-### `craftAsyncProcesses`
-
-Match: `async workflow in store`, `debounced action in store`, `delayed delete`, `background task in store`.
-Pair with: `asyncProcess`, `craftSources`.
-Default: Use when async client tasks belong to a `craft` store but are not the primary server-read/write state.
-
-### `craftSources`
-
-Match: `reset event`, `refresh event`, `select event`, `open modal event`, `trigger inside store`.
-Pair with: `source$`, `on$`, `afterRecomputation`.
-Default: Use this to define event channels inside a store and to auto-generate `emit*`, `set*`, or `next*` methods.
-
-### `craftInputs`
-
-Match: `parent provides id`, `route provides id`, `component input`, `external signal`, `context value`, `page receives userId`.
-Pair with: `craftQuery`, `craftState`, `craftMutations`.
-Default: Use this instead of `queryParams` when the value does not belong in the URL.
-
-### `craftQueryParams`
-
-Match: `one query param group in store`, `pagination in store`, `filters in store`, `search params in store`.
-Pair with: `queryParams`, `craftQuery`, `craftSetAllQueriesParamsStandalone`.
-Default: Use when one named query-params group should live inside a `craft` store.
-
-### `craftQueryParams`
-
-Match: `several URL state groups`, `pagination + filters + active tab`, `multiple query param groups`.
-Pair with: `queryParams`, `craftSetAllQueriesParamsStandalone`.
-Default: Use when the store needs several named query-params groups.
-
-### `craftComputedStates`
-
-Match: `derived store data`, `isAllSelected`, `count`, `filtered count`, `UI flags`, `aggregation`, `composed loading state`.
-Pair with: `computed`, `craftState`, `craftQuery`.
-Default: Use for derived store-level signals instead of duplicating state.
-
-### `craftInject`
-
-Match: `inject ApiService`, `inject Router`, `inject HttpClient`, `inject token`, `service dependency in store`.
-Pair with: `craft`, `craftQuery`, `craftMutations`.
-Default: Use inside `craft` when store factories need Angular services or tokens.
-
-### `craftSetAllQueriesParamsStandalone`
-
-Match: `generate URL`, `router navigate queryParams`, `shareable link`, `build full query string outside injection context`.
-Pair with: `craftQueryParams`, `craftQueryParams`.
-Default: Use when the spec mentions programmatic navigation or link generation from the current query-params model.
+Match: `derived data`, `count`, `filtered count`, `UI flags`, or a service
+dependency. Use `craftComputed` for derived values, and yield the generated
+service dependency from a `craftService` generator. Use `on$` and `source$` for
+internal event wiring rather than store-specific source helpers.
 
 ## Insertions
 
@@ -280,7 +234,7 @@ Default: Use when the spec is explicit about source transformation pipelines.
 ### `signalSource`
 
 Match: `source with signal shape`, `event source with set`, `lazy event signal`, `source semantics with preserveLastValue`.
-Pair with: `craftSources`, `afterRecomputation`, `linkedSource`.
+Pair with: `source$`, `afterRecomputation`, `linkedSource`.
 Default: Choose this only when the implementation specifically wants signal-like source behavior rather than `source$`.
 
 ### `linkedSource`
@@ -314,9 +268,3 @@ Default: Prefer the insertion for product specs. Use this lower-level factory on
 Match: `low-level resource registry`, `resources keyed by identifier`, `manual per-id cache infrastructure`, `bind one resource-by-id to another`.
 Pair with: `query.identifier`, `mutation.identifier`.
 Default: Prefer ordinary `query` and `mutation` with `identifier` until the request explicitly asks for custom resource infrastructure.
-
-### `toInject`
-
-Match: `bind external signals into service entries`, `service ...Entry wiring`, `service adapter for signals`.
-Pair with: Angular services exposing writable `...Entry` signals.
-Default: Use only when the service API already follows the `...Entry` convention and the request is about service binding infrastructure.

package/skills/translate-spec-to-craft-ts/references/pattern-recipes.md

@@ -27,7 +27,7 @@ Use:
 - `query` for the entity detail.
 - `mutation` for update or delete intents.
 - `insertReactOnMutation` on the detail `query` when edits should be reflected immediately.
-- `craftInputs` when the entity id comes from component or route context but does not belong in query params.
+- `CraftServiceInput` when the entity id comes from component or route context but does not belong in query params.
 
 Default policy:
 - Keep one detail `query` per detail intent.
@@ -39,7 +39,7 @@ Use:
 - one `query` for the list.
 - one `mutation` for single delete.
 - one `mutation` for bulk delete.
-- one selection `state` or `craftState` holding selected ids.
+- one selection `state` holding selected ids.
 - `insertReactOnMutation` on the list `query` for each mutation.
 
 Default policy:
@@ -67,35 +67,35 @@ Default policy:
 ## Search Page With URL Filters
 
 Use:
-- `queryParams` or `craftQueryParams` for the filters.
+- `queryParams` for the filters.
 - `query` for the result list.
-- `craftSetAllQueriesParamsStandalone` when links or router navigation must be generated outside injection context.
+- the router service when links or navigation must be generated outside a component template.
 
 Default policy:
 - Reset `page` to `1` when a search term or filter changes.
 - Keep URL parsing and serialization explicit for each field.
-- Choose `craftQueryParams` when the page has several named query-params groups.
+- Use separate named `queryParams` primitives when the page has several query-params groups.
 
-## Feature Or Page Store
+## Feature Or Page Service
 
 Use:
-- `craft` as the boundary.
-- `craftInject` for services and tokens.
-- `craftInputs` for non-URL external values.
-- `craftQueryParams` or `craftQueryParams` for URL-backed state.
-- `craftSources` for reset, refresh, and cross-entry triggers.
-- `craftQuery`, `craftMutations`, `craftState`, and `craftComputedStates` for the actual feature logic.
+- `craftService` as the boundary.
+- generated service dependencies for services and tokens.
+- `CraftServiceInput` for non-URL external values.
+- `queryParams` for URL-backed state.
+- `source$` and `on$` for reset, refresh, and cross-entry triggers.
+- `query`, `mutation`, `state`, and `craftComputed` for the actual feature logic.
 
 Default policy:
-- Choose `providedIn: 'feature'` for page or route scoped stores.
-- Choose `providedIn: 'root'` for global shared stores.
-- Keep remote state in `craftQuery` and `craftMutations`, not in ad-hoc service fields.
+- Choose a scoped `craftService` for page or route scoped logic.
+- Choose `providedIn: 'root'` for globally shared services.
+- Keep remote state in `query` and `mutation`, not in ad-hoc service fields.
 
 ## Smaller Facade Over An Angular Service
 
 Use:
-- `injectService` when no `craft` store is needed.
-- `craftInject` when the service participates in a store composition.
+- `craftService` when the facade needs to own primitives or dependencies.
+- a plain adapter when no reactive service boundary is needed.
 
 Default policy:
 - Expose only the service surface the feature actually needs.

package/skills/translate-spec-to-craft-ts/references/project-index.md

@@ -48,5 +48,5 @@ MCP `find_examples` searches the same Learn + examples corpus.
 - Favor symbol names from the installed package over older or shorter doc titles.
 - The public insertion name is `insertLocalStoragePersister`.
 - Reach for advanced exports such as `toSource`, `computedSource`, `signalSource`,
-  `linkedSource`, `resourceById`, and `toInject` only when the request is
+  `linkedSource`, and `resourceById` only when the request is
   explicitly about infrastructure or source plumbing.