systemlink-cli 1.4.8__tar.gz → 1.5.1__tar.gz

{systemlink_cli-1.4.8 → systemlink_cli-1.5.1}/PKG-INFO

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

{systemlink_cli-1.4.8 → systemlink_cli-1.5.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "systemlink-cli"
-version = "1.4.8"
+version = "1.5.1"
 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.4.8 → systemlink_cli-1.5.1}/slcli/_version.py

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

{systemlink_cli-1.4.8 → systemlink_cli-1.5.1}/slcli/skills/slcli/SKILL.md

@@ -665,18 +665,26 @@ slcli workitem create \
 Scaffold, package, and publish custom web applications to SystemLink.
 
 ```bash
-slcli webapp init [--template html|angular] [--directory DIR]  # Scaffold a new project
-slcli webapp pack [--directory DIR] [-o OUTPUT_FILE]     # Package webapp into a .zip
+slcli webapp init <DIRECTORY>                      # Scaffold the Angular starter
+slcli webapp manifest init <DIRECTORY> [OPTIONS]  # Create manifest.json + nipkg.config.json
+slcli webapp pack [FOLDER] [--config FILE] [-o OUTPUT_FILE]  # Package a webapp into a .nipkg
 slcli webapp list [-w WORKSPACE] [-t INT] [-f json]
 slcli webapp get <WEBAPP_ID> [-f json]
-slcli webapp publish --file PATH [--workspace NAME]      # Upload and publish a webapp
+slcli webapp publish PATH [--workspace NAME]             # Upload and publish a webapp
 slcli webapp delete <WEBAPP_ID>
 slcli webapp open <WEBAPP_ID>                            # Open webapp URL in browser
 ```
 
-Templates:
-- `html` (default) — minimal index.html
-- `angular` — Nimble Angular project with `PROMPTS.md`, `README.md`, and bundled AI skills installed into `.agents/skills/`
+`webapp init` creates the SystemLink Angular starter, not a generic HTML app. The starter installs
+project-scoped skills into `.agents/skills/` and creates `PROMPTS.md` plus `START_HERE.md` so an
+AI assistant can bootstrap the Angular workspace in place with the same Nimble/SystemLink
+conventions described by the `systemlink-webapp` skill.
+
+`webapp manifest init` writes `manifest.json` and `nipkg.config.json` using the Plugin Manager
+field names (`section`, `maintainer`, `homepage`, `xbPlugin`, `slPluginManagerTags`,
+`slPluginManagerMinServerVersion`, `iconFile`). `webapp pack --config ...` consumes that
+metadata, carries the icon into the package, and writes the matching control-file fields into the
+generated `.nipkg`.
 
 ### skill — AI skill installation
 
@@ -693,7 +701,7 @@ Client paths:
 
 Notes:
 - `agents` is the default client in interactive mode.
-- `webapp init --template angular` installs project-scoped skills into `.agents/skills/` by default.
+- `webapp init` installs project-scoped skills into `.agents/skills/` by default.
 
 ### example — Built-in example resource provisioning
 

{systemlink_cli-1.4.8 → systemlink_cli-1.5.1}/slcli/skills/systemlink-webapp/SKILL.md

@@ -19,6 +19,14 @@ SystemLink webapps are Angular Single-Page Applications built with the Nimble de
 connected to SystemLink REST APIs, and deployed via `slcli webapp publish`. This skill captures
 every gotcha learned from building and deploying real apps.
 
+If the user is starting from scratch, prefer `slcli webapp init <app-dir>` first.
+That command lays down the SystemLink starter layer (`.agents/skills/`, `PROMPTS.md`, and
+`START_HERE.md`) while Angular CLI remains responsible for generating the Angular workspace.
+
+When the user wants to package the app for Plugin Manager submission, prefer
+`slcli webapp manifest init <app-dir> ...` to generate `manifest.json` and `nipkg.config.json`
+with the current Plugin Manager field names, then use `slcli webapp pack --config ...`.
+
 ---
 
 ## Step 1: Understand what the user needs
@@ -34,15 +42,49 @@ You do NOT need to ask about Angular version or Nimble versions — always use A
 
 ---
 
-## Step 2: Scaffold the Angular project
+## Step 2: Bootstrap the Angular workspace
+
+When the project was created with `slcli webapp init`, generate Angular in the existing starter
+directory so the starter files and bundled skills remain at the project root.
 
 ```bash
-npx -y @angular/cli@20 new <app-name> --routing --style=scss --skip-git --no-standalone
-cd <app-name>
+npx -y @angular/cli@20 new <app-name> --directory . --routing --style=scss --skip-git --no-standalone --defaults --force
 npm install @ni/nimble-angular
 ```
 
-> Use `--no-standalone` to generate an NgModule-based app. SystemLink webapps work best with NgModule because it makes it easy to register all Nimble modules in one place.
+> Use `--no-standalone` to generate an NgModule-based app. SystemLink webapps work best with
+> NgModule because it makes it easy to register all Nimble modules in one place.
+
+If the user has not run `slcli webapp init` yet and they want a new SystemLink webapp, tell them
+to do that first unless they explicitly want a manual setup.
+
+### Starter shell expectations
+
+Before building feature-specific pages, establish a reusable shell that is aligned with other
+SystemLink apps:
+
+- Root `nimble-theme-provider` that mirrors the host shell theme
+- Responsive page header with title, summary text, and an action area
+- Shared loading, error, and empty states instead of one-off page-specific handling
+- Route-backed top-level navigation only when the app truly has multiple views
+- Reusable API helpers and service-layer code rather than fetch logic embedded in templates
+
+Use Nimble layout tokens and spacing rules consistently across the shell and feature pages:
+
+- Prefer Nimble spacing tokens over ad-hoc pixel values: `smallPadding` for tight inline gaps,
+  `mediumPadding` for default control spacing, `standardPadding` for section padding, and
+  `largePadding` between major content regions.
+- Stack controls vertically with a column layout, `mediumPadding` gap, and `standardPadding`
+  around the control group.
+- Use `mediumPadding` or `standardPadding` gaps for side-by-side controls; prefer CSS grid for
+  aligned multi-column layouts.
+- Inside accordion panels, keep a column layout with `mediumPadding` gaps and
+  `standardPadding` bottom padding.
+- Treat `controlHeight` (32px), `controlSlimHeight` (24px), and `labelHeight` (16px) as the
+  baseline sizing tokens for controls and labels.
+- Separate major sections with `largePadding` and subsections with `standardPadding`.
+
+See [references/layout-patterns.md](references/layout-patterns.md) for the detailed layout guide.
 
 ---
 

systemlink_cli-1.5.1/slcli/skills/systemlink-webapp/references/layout-patterns.md

@@ -0,0 +1,71 @@
+# Layout Patterns
+
+Guidance for spacing between controls vertically and horizontally within Nimble-based
+SystemLink webapps.
+
+## Spacing tokens
+
+Use Nimble design tokens for consistent spacing between controls.
+
+| Token             | Value | Usage                                                  |
+| ----------------- | ----- | ------------------------------------------------------ |
+| `smallPadding`    | 4px   | Tight spacing for icon margins and inline element gaps |
+| `mediumPadding`   | 8px   | Default spacing between stacked controls               |
+| `standardPadding` | 16px  | Section padding and content block margin               |
+| `largePadding`    | 24px  | Separation between major layout sections               |
+
+## Control heights
+
+| Token               | Value | Usage                           |
+| ------------------- | ----- | ------------------------------- |
+| `controlHeight`     | 32px  | Standard height for controls    |
+| `controlSlimHeight` | 24px  | Compact control variants        |
+| `labelHeight`       | 16px  | Height of labels above controls |
+
+## Vertical stacking
+
+When stacking controls vertically, such as text fields, number fields, and checkboxes:
+
+- Use `mediumPadding` (8px) as the gap between controls in a flex column.
+- Use `standardPadding` (16px) for content padding around the group.
+- Labels above controls add `labelHeight` (16px) to the effective row height.
+
+```html
+<div
+  style="display: flex; flex-direction: column; gap: var(--ni-nimble-medium-padding);"
+>
+  <nimble-text-field>Label 1</nimble-text-field>
+  <nimble-text-field>Label 2</nimble-text-field>
+</div>
+```
+
+## Horizontal layout
+
+When placing controls side by side:
+
+- Use `mediumPadding` (8px) or `standardPadding` (16px) as the gap.
+- Prefer CSS grid with equal columns for aligned layouts.
+
+```html
+<div
+  style="display: grid; grid-template-columns: 1fr 1fr; gap: var(--ni-nimble-medium-padding);"
+>
+  <nimble-checkbox>Option A</nimble-checkbox>
+  <nimble-checkbox>Option B</nimble-checkbox>
+</div>
+```
+
+## Accordion content
+
+Inside accordion item content panels:
+
+- Use `flex-direction: column` with `mediumPadding` (8px) gap between controls.
+- Indent content by the icon width plus padding so it aligns with the header text.
+- Use `standardPadding` (16px) for bottom padding before the next section.
+
+## Section spacing
+
+Between major sections or groups of controls:
+
+- Use `largePadding` (24px) between distinct content areas.
+- Use `standardPadding` (16px) for subsections within a group.