systemlink-cli 1.15.2__tar.gz → 1.16.0__tar.gz

{systemlink_cli-1.15.2 → systemlink_cli-1.16.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: systemlink-cli
-Version: 1.15.2
+Version: 1.16.0
 Summary: SystemLink Integrator CLI - cross-platform CLI for SystemLink workflows and templates.
 License-File: LICENSE
 Author: Fred Visser

{systemlink_cli-1.15.2 → systemlink_cli-1.16.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "systemlink-cli"
-version = "1.15.2"
+version = "1.16.0"
 description = "SystemLink Integrator CLI - cross-platform CLI for SystemLink workflows and templates."
 authors = ["Fred Visser <fred.visser@emerson.com>"]
 packages = [{ include = "slcli" }]

{systemlink_cli-1.15.2 → systemlink_cli-1.16.0}/slcli/_version.py

@@ -1,4 +1,4 @@
 """Version information for slcli."""
 
 # This file is auto-generated. Do not edit manually.
-__version__ = "1.15.2"
+__version__ = "1.16.0"

{systemlink_cli-1.15.2 → systemlink_cli-1.16.0}/slcli/skills/slcli/references/webapp/angular-ui-packages.md

@@ -2,6 +2,24 @@
 
 Use this file when you need a quick package-level inventory before choosing components. Load `nimble-angular.md` only after you know which Nimble components you actually need.
 
+## Use published components first
+
+Before styling a `div` into a faux card, tile, accordion, search bar, button row, or summary panel,
+check this file and the Nimble Storybook first.
+
+- Prefer NI components for visible surfaces and interactions.
+- Use raw HTML mainly for layout containers, semantic sections, and text.
+- Treat custom card shells as the exception path, not the default response to a dashboard or layout request.
+
+## Reference links
+
+| Surface                 | Link                                                                         | Use                                                               |
+| ----------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------- |
+| Nimble Storybook        | https://nimble.ni.dev/storybook/index.html                                   | Search the published Nimble components before inventing a surface |
+| Nimble Getting Started  | https://nimble.ni.dev/storybook/index.html?path=/docs/getting-started--docs  | Bootstrap and package expectations                                |
+| Nimble Component APIs   | https://nimble.ni.dev/storybook/index.html?path=/docs/component-apis--docs   | Component inventory and API lookup                                |
+| Nimble Component Status | https://nimble.ni.dev/storybook/index.html?path=/docs/component-status--docs | Check maturity and availability                                   |
+
 ## Install recommendation
 
 For new SystemLink webapps, prefer installing the NI Angular UI packages together:
@@ -10,15 +28,15 @@ For new SystemLink webapps, prefer installing the NI Angular UI packages togethe
 npm install @ni/nimble-angular @ni/spright-angular @ni/ok-angular
 ```
 
-Use Nimble as the default foundation, then pull in Spright and OK Angular when the app needs their specialized components.
+Use Nimble as the default foundation, then pull in Spright and OK Angular when the app needs their specialized surfaces.
 
 ## Package roles
 
-| Package               | Primary role                                           | When to reach for it                                                                                                       |
-| --------------------- | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------- |
-| `@ni/nimble-angular`  | Core SystemLink-aligned component foundation           | Use for the default app shell, tables, buttons, inputs, drawers, banners, dialogs, navigation, and most day-to-day UI work |
-| `@ni/spright-angular` | Spright chat, rectangle, and NI-specific icon wrappers | Use for chat experiences, AI/copilot surfaces, and Spright-specific iconography                                            |
-| `@ni/ok-angular`      | OK-specific interaction components                     | Use when the design needs OK accordion items, OK search input, or OK button primitives                                     |
+| Package               | Primary role                                           | When to reach for it                                                                                                              |
+| --------------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
+| `@ni/nimble-angular`  | Core SystemLink-aligned component foundation           | Use for the default app shell, tables, buttons, inputs, drawers, banners, dialogs, navigation, and most day-to-day UI work        |
+| `@ni/spright-angular` | Spright chat, rectangle, and NI-specific icon wrappers | Use for chat experiences, AI/copilot surfaces, and Spright-specific iconography                                                   |
+| `@ni/ok-angular`      | OK-specific Angular wrappers                           | Use when the design needs OK accordion items, OK search input, OK chip selectors, summary panels, or OK button primitives         |
 
 ## Recommended AppModule example
 
@@ -99,6 +117,16 @@ Representative components already documented there include:
 - `nimble-banner`
 - `nimble-dialog`
 
+Representative layout and navigation surfaces to prefer before bespoke HTML include:
+
+- `nimble-anchor`
+- `nimble-anchor-tabs`
+- `nimble-anchor-tab`
+- `nimble-drawer`
+- `nimble-banner`
+- `nimble-spinner`
+- `nimble-table`
+
 ### `@ni/spright-angular`
 
 Published Angular wrappers currently include:
@@ -126,7 +154,7 @@ Published Spright icon directives currently include:
 
 ### `@ni/ok-angular`
 
-Published Angular wrappers in `@ni/ok-angular@2.4.0` currently include:
+Published Angular wrappers in `@ni/ok-angular@2.5.0` currently include:
 
 | Tag                         | Angular symbol                | Import path                             | Use                                          |
 | --------------------------- | ----------------------------- | --------------------------------------- | -------------------------------------------- |
@@ -135,17 +163,22 @@ Published Angular wrappers in `@ni/ok-angular@2.4.0` currently include:
 | `ok-fv-card`                | `OkFvCardModule`              | `@ni/ok-angular/fv/card`                | OK card surface with title and description   |
 | `ok-fv-chip-selector`       | `OkFvChipSelectorModule`      | `@ni/ok-angular/fv/chip-selector`       | Multi-value chip selector control            |
 | `ok-fv-context-help`        | `OkFvContextHelpModule`       | `@ni/ok-angular/fv/context-help`        | Inline context-help or severity help content |
+| `ok-fv-master-detail-list`  | `OkFvMasterDetailListModule`  | `@ni/ok-angular/fv/master-detail-list`  | Master/detail list container                 |
+| `ok-fv-master-detail-list-item` | `OkFvMasterDetailListItemModule` | `@ni/ok-angular/fv/master-detail-list-item` | Item rows inside the master/detail list |
 | `ok-fv-search-input`        | `OkFvSearchInputModule`       | `@ni/ok-angular/fv/search-input`        | OK search input control                      |
 | `ok-fv-split-button`        | `OkFvSplitButtonModule`       | `@ni/ok-angular/fv/split-button`        | Split button with primary and menu actions   |
 | `ok-fv-split-button-anchor` | `OkFvSplitButtonAnchorModule` | `@ni/ok-angular/fv/split-button-anchor` | Anchor-style split button                    |
 | `ok-fv-summary-panel`       | `OkFvSummaryPanelModule`      | `@ni/ok-angular/fv/summary-panel`       | Summary panel container                      |
 | `ok-fv-summary-panel-tile`  | `OkFvSummaryPanelTileModule`  | `@ni/ok-angular/fv/summary-panel-tile`  | Summary panel metric or status tile          |
 
+Use `@ni/ok-angular` as the default and preferred entry point for OK components in Angular apps. The wrapper package now includes the master-detail list surface as well, so generated apps and skill guidance should stay on `@ni/ok-angular` rather than importing `@ni/ok-components` directly.
+
 ## Selection guidance
 
 - Start with Nimble for the app shell and the majority of controls.
 - Add Spright when the app needs chat UI or Spright-specific iconography.
 - Add OK Angular when the design specifically benefits from its accordion item, search input, chip selector, split button, summary panel, card, or OK button components.
+- Prefer a published component over styling a `div` to imitate the same surface.
 - Keep imports explicit at the module level; do not use `CUSTOM_ELEMENTS_SCHEMA` as a shortcut for missing wrappers.
 
 ## Next step references

{systemlink_cli-1.15.2 → systemlink_cli-1.16.0}/slcli/skills/slcli/references/webapp/layout-patterns.md

@@ -51,10 +51,22 @@ Do not combine multiple starter patterns in the first implementation slice unles
 ## Core rules
 
 - Use Nimble components and Nimble design tokens for primary UI. Avoid generic cards as the default page structure for browse, detail, and settings workflows.
+- Check published Nimble, Spright, and OK components before creating a custom surface from plain `div`s.
+- Use `div`s for flex, grid, spacing, grouping, and semantics, not as a substitute for a published control or design surface.
 - Put toolbars and tab bars in a 40px-tall container with content vertically centered and a `1px solid var(--ni-nimble-divider-background-color)` bottom border.
 - Use `nimble-button` for button affordances. If you need clickable list rows or a section rail, style them as navigation rows rather than faux Nimble buttons.
 - Keep theme-aware aliases on `nimble-theme-provider`, not on `:root`, so custom colors and surfaces follow the active Nimble theme.
 
+## Prefer components over faux cards
+
+When the request sounds like "dashboard", "summary", "overview", or "settings", do not default to wrapping everything in repeated card containers.
+
+- For browse data, start with `nimble-table` plus a toolbar.
+- For selection-driven workflows, start with drawer-detail or master/detail.
+- For grouped configuration, start with accordion items or sectioned form groups.
+- For metrics or status rollups, prefer OK summary panels or a small number of focused summary surfaces.
+- Use cards only when a published card or summary component is the real primitive you need, not as a catch-all page layout pattern.
+
 ## Spacing tokens
 
 Use Nimble design tokens for consistent spacing between controls.

{systemlink_cli-1.15.2 → systemlink_cli-1.16.0}/slcli/skills/slcli/references/webapp/nimble-angular.md

@@ -27,6 +27,8 @@ When building Angular apps with Nimble, use `@ni/nimble-angular` wrapper modules
 - Import the needed Angular module for each Nimble control instead of registering raw custom elements from `@ni/nimble-components`.
 - Do not add `CUSTOM_ELEMENTS_SCHEMA` just to silence unknown Nimble elements in templates. That usually hides a missing module import and weakens Angular's template validation.
 - If a Nimble icon or control is unknown, first look for the matching module in `@ni/nimble-angular` and import it.
+- If a Nimble wrapper does not exist, check `angular-ui-packages.md` and the Nimble Storybook before creating a custom HTML substitute.
+- Prefer a published NI component over styling a `div` to mimic the same interaction or surface.
 
 ## Fonts
 

{systemlink_cli-1.15.2 → systemlink_cli-1.16.0}/slcli/skills/slcli/references/webapp/overview.md

@@ -17,6 +17,23 @@ reference files when the implementation needs them.
 
 If the user only wants planning or a first implementation slice, stay in this file.
 
+## Component-first rule
+
+Before inventing a surface with `div`s, custom borders, or repeated card shells, check whether the
+needed primitive already exists in Nimble, Spright, or OK.
+
+- Use package components for interactive or visual surfaces first.
+- Use raw HTML mostly for semantic grouping, flex/grid layout, and text structure.
+- Do not build custom-styled buttons, inputs, tabs, drawers, search bars, banners, summary tiles,
+  or faux cards when a published NI component already covers the job.
+- Treat `div` wrappers as layout scaffolding, not as the primary design language.
+
+Start with these references before authoring bespoke UI:
+
+- Nimble Storybook: https://nimble.ni.dev/storybook/index.html
+- Nimble Component APIs: https://nimble.ni.dev/storybook/index.html?path=/docs/component-apis--docs
+- Nimble Getting Started: https://nimble.ni.dev/storybook/index.html?path=/docs/getting-started--docs
+
 ## First response checklist
 
 Before generating code, clarify only the details that change the implementation:
@@ -29,7 +46,7 @@ Before generating code, clarify only the details that change the implementation:
 
 Do not ask about Angular or Nimble versions unless the user is constrained by an existing project. Default to Angular 20 and the latest compatible `@ni/nimble-angular`, but verify the installed versions immediately after scaffold instead of assuming the generator produced the expected combination.
 
-For new SystemLink apps, recommend installing the NI Angular UI packages together unless the user is intentionally minimizing dependencies. `@ni/nimble-angular` remains the default foundation, `@ni/spright-angular` adds Spright chat and icon components, and `@ni/ok-angular` adds OK-specific controls such as accordion items and search input.
+For new SystemLink apps, recommend installing the NI UI packages together unless the user is intentionally minimizing dependencies. `@ni/nimble-angular` remains the default foundation, `@ni/spright-angular` adds Spright chat and icon components, and `@ni/ok-angular` is the default entry point for OK surfaces such as accordion items, search input, summary panels, and other OK wrappers. Do not reach for `@ni/ok-components` directly in normal app code.
 
 ## Recommended workflow
 
@@ -60,9 +77,12 @@ For the currently supported path, standardize on:
 
 - Angular 20.x
 - Node 24+
-- `@ni/nimble-angular` 33.2.x
-- `@ni/nimble-components` 35.8.x
-- `@ni/unit-format` 1.0.4+
+- `@ni/nimble-angular` 33.4.x
+- `@ni/nimble-components` 35.12.x
+- `@ni/unit-format` 1.0.5+
+- `@ni/spright-angular` 9.5.x
+- `@ni/ok-angular` 2.5.0+
+- `@ni/systemlink-clients-ts` 3.0.2
 - `@angular/build` for the hosted application builder
 - `@angular/localize` installed and added to build polyfills
 
@@ -76,7 +96,7 @@ Also add `@angular-devkit/build-angular` back to `devDependencies` before switch
 
 This fallback is not optional when the Nimble packages fail under the application builder. Fix the builder mismatch before implementing more UI.
 
-Recommend installing `@ni/spright-angular` and `@ni/ok-angular` early when using the manual `init` path, even if the first slice only uses Nimble. That avoids dependency churn later when the UI needs chat surfaces, product-specific icons, accordion items, or the OK search input.
+Recommend installing `@ni/spright-angular` and `@ni/ok-angular` early when using the manual `init` path, even if the first slice only uses Nimble. That avoids dependency churn later when the UI needs chat surfaces, product-specific icons, or OK wrappers.
 
 If the user has not scaffolded anything yet and explicitly wants a SystemLink-hosted webapp, recommend `slcli webapp new` first. Only fall back to `slcli webapp init` when they ask for manual bootstrapping or need to control the Angular workspace creation themselves.
 
@@ -103,13 +123,16 @@ Use SystemLink-appropriate layout defaults instead of inventing page structure f
 - Use drawers or collapsible side panels for settings and filters.
 - Use accordions for grouped fields and advanced configuration.
 - Use cards sparingly for summaries, not as the default editing or data layout.
+- Prefer NI summary-panel, accordion, table, drawer, tab, banner, and search components before composing a new surface from plain `div`s.
 
 Treat Nimble alignment as a requirement, not a style preference:
 
 - Use Nimble controls for primary actions, selection, inputs, status, and data display.
+- Prefer OK and Spright components when they provide a better fit than generic layout wrappers.
 - Use raw HTML elements mostly for semantic grouping, layout wrappers, and text structure.
 - Do not build custom-styled buttons, inputs, dropdowns, tabs, or pseudo-cards when Nimble already provides the interaction primitive.
 - Prefer Nimble spacing, borders, focus states, and theme tokens over bespoke visual treatments.
+- If an NI component exists for the surface, use it instead of styling a `div` to imitate it.
 - If a page starts to look like a generic marketing dashboard instead of a SystemLink tool, pull it back toward table/list-detail, drawers, banners, tabs, and structured metadata panels.
 
 ### 4. Integrate SystemLink APIs the low-risk way
@@ -176,6 +199,7 @@ Before you consider a SystemLink webapp slice correct, confirm all of the follow
 - Root `src/styles.scss` imports `@use '@ni/nimble-angular/styles/fonts' as *;`.
 - Nimble Angular modules are imported explicitly.
 - Primary interaction controls use Nimble wrappers rather than custom HTML surrogates.
+- When Nimble lacks a needed surface, check `angular-ui-packages.md` and the Nimble Storybook before creating a bespoke `div`-based substitute.
 - No hardcoded colors in component SCSS.
 - Theme-aware aliases live on `nimble-theme-provider`.
 - API client uses the correct SystemLink service base URL.