jekyll-component-mcp 1.2.1 → 1.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -14,6 +14,7 @@ Use this skill to set up `jekyll-component-mcp` as an MCP server and operate it
14
14
  - A Jekyll project directory to use as the server's project root. Ruby/Bundler and Jekyll are only needed for build and doctor operations.
15
15
 
16
16
  The package is an MCP server, not a Jekyll theme or a runtime dependency for the site. Install it globally or let the MCP client run it with `npx`.
17
+ At startup, the server checks the npm registry for a newer release at most once per day and logs an update notice when one is available. Registry or network failures do not prevent startup.
17
18
 
18
19
  ## Install and configure
19
20
 
@@ -55,7 +56,7 @@ Use `--root <path>` to target another project, `--preset auto|standard|chirpy|mi
55
56
  2. Start with `jekyll_project_info`. Use `jekyll_project_scan` when file locations or architecture matter. Use `jekyll_config_get` for site configuration; secrets are redacted.
56
57
  3. Before changing an existing component, inspect it with `jekyll_component_list` and `jekyll_component_get`. Inspect SCSS with `jekyll_scss_list` / `jekyll_scss_get`, tokens with `jekyll_token_list` / `jekyll_token_get`, and Liquid includes or layouts with their corresponding list/get tools.
57
58
  4. Match the repository's existing component, naming, Liquid, SCSS, and documentation conventions. Do not assume default paths when scan results are available.
58
- 5. For requested writes, use the smallest relevant tool. Preview supported mutations with `dry_run: true`, review the reported operations, then run with `dry_run: false` or omit `dry_run` to apply them. Clearly report when the configured write mode prevents a change.
59
+ 5. For requested writes, use the smallest relevant tool. For `jekyll_component_create`, `dry_run: true` returns planned operations and unified diffs; review them before applying. For `jekyll_docs_update`, dry-run reports only the target path, not a content diff, and a normal update regenerates the target file. Clearly report when the configured write mode prevents a change.
59
60
  6. After changes, run `jekyll_component_validate` for a component and/or `jekyll_validate`. If the project has the needed Ruby/Jekyll environment, run `jekyll_build` to verify the site.
60
61
 
61
62
  ## Tool reference
@@ -63,8 +64,9 @@ Use `--root <path>` to target another project, `--preset auto|standard|chirpy|mi
63
64
  | Task | MCP tools |
64
65
  | --- | --- |
65
66
  | Project overview and structure | `jekyll_project_info`, `jekyll_project_scan`, `jekyll_config_get` |
66
- | Components | `jekyll_component_list`, `jekyll_component_get`, `jekyll_component_create`, `jekyll_component_validate`, `jekyll_component_delete` |
67
+ | Components | `jekyll_component_list`, `jekyll_component_get`, `jekyll_component_catalog`, `jekyll_component_create`, `jekyll_component_preview`, `jekyll_component_validate`, `jekyll_component_delete` |
67
68
  | Component aliases | `list_components`, `inspect_component`, `create_component`, `validate_component` |
69
+ | Catalog and preview aliases | `component_catalog`, `preview_component` |
68
70
  | SCSS and design tokens | `jekyll_scss_list`, `jekyll_scss_get`, `jekyll_scss_create`, `jekyll_token_list`, `jekyll_token_get`, `jekyll_token_update` |
69
71
  | Liquid includes and layouts | `jekyll_include_list`, `jekyll_include_get`, `jekyll_layout_list`, `jekyll_layout_get` |
70
72
  | Documentation | `jekyll_docs_create`, `jekyll_docs_update` |
@@ -72,6 +74,8 @@ Use `--root <path>` to target another project, `--preset auto|standard|chirpy|mi
72
74
 
73
75
  For component creation, `jekyll_component_create` or `create_component` accepts `name`, optional `category`, `variants`, `javascript`, `documentation`, `example`, and `dry_run`. Prefer this tool over separate file creation when the user asks for a reusable component; it scaffolds the Liquid component and associated assets/docs/examples. `inspect_component` reports Liquid include parameters and detected defaults/guards alongside source and SCSS details. `validate_component` checks Liquid fallbacks/guards and BEM/SCSS naming.
74
76
 
77
+ Use `jekyll_component_catalog` or `component_catalog` for a read-only overview of discovered components, including status, tags, summaries, path coverage, variants, and parameter counts. Use `jekyll_component_preview` or `preview_component` to generate a lightweight HTML sample with a selected variant and parameters; it is a preview, not a full Jekyll render. `jekyll_docs_update` accepts `category` as well as overview, variants, parameters, accessibility guidance, and notes. Its dry-run only identifies the target path, so inspect the existing documentation before applying an update that could replace authored content.
78
+
75
79
  Use the review prompts when supported by the MCP client: `jekyll_component_review`, `jekyll_accessibility_review`, `jekyll_performance_review`, and `jekyll_production_review`. Available resources include `jekyll://project`, `jekyll://components`, `jekyll://tokens`, `jekyll://config`, and `jekyll://documentation`.
76
80
 
77
81
  ## Write and security rules
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.2.2
4
+
5
+ ### Changed
6
+
7
+ - Updated both distributed skill files for component catalog, HTML preview, documentation update behavior, and daily npm update notices
8
+
3
9
  ## 1.2.1
4
10
 
5
11
  ### Changed
@@ -2,7 +2,7 @@
2
2
  * Project-wide constants for jekyll-component-mcp.
3
3
  */
4
4
  export declare const PACKAGE_NAME = "jekyll-component-mcp";
5
- export declare const PACKAGE_VERSION = "1.2.1";
5
+ export declare const PACKAGE_VERSION = "1.2.2";
6
6
  /** Default write policy when none is specified. */
7
7
  export declare const DEFAULT_WRITE_MODE: "safe-write";
8
8
  /** Default Jekyll build timeout in milliseconds. */
@@ -2,7 +2,7 @@
2
2
  * Project-wide constants for jekyll-component-mcp.
3
3
  */
4
4
  export const PACKAGE_NAME = "jekyll-component-mcp";
5
- export const PACKAGE_VERSION = "1.2.1";
5
+ export const PACKAGE_VERSION = "1.2.2";
6
6
  /** Default write policy when none is specified. */
7
7
  export const DEFAULT_WRITE_MODE = "safe-write";
8
8
  /** Default Jekyll build timeout in milliseconds. */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "jekyll-component-mcp",
3
- "version": "1.2.1",
3
+ "version": "1.2.2",
4
4
  "description": "AI-native development MCP server for Jekyll projects and reusable Liquid/SCSS/JavaScript components.",
5
5
  "homepage": "https://github.com/daffadevhosting/jekyll-component-mcp#readme",
6
6
  "repository": {
package/skills/SKILL.md CHANGED
@@ -14,6 +14,7 @@ Use this skill to set up `jekyll-component-mcp` as an MCP server and operate it
14
14
  - A Jekyll project directory to use as the server's project root. Ruby/Bundler and Jekyll are only needed for build and doctor operations.
15
15
 
16
16
  The package is an MCP server, not a Jekyll theme or a runtime dependency for the site. Install it globally or let the MCP client run it with `npx`.
17
+ At startup, the server checks the npm registry for a newer release at most once per day and logs an update notice when one is available. Registry or network failures do not prevent startup.
17
18
 
18
19
  ## Install and configure
19
20
 
@@ -55,7 +56,7 @@ Use `--root <path>` to target another project, `--preset auto|standard|chirpy|mi
55
56
  2. Start with `jekyll_project_info`. Use `jekyll_project_scan` when file locations or architecture matter. Use `jekyll_config_get` for site configuration; secrets are redacted.
56
57
  3. Before changing an existing component, inspect it with `jekyll_component_list` and `jekyll_component_get`. Inspect SCSS with `jekyll_scss_list` / `jekyll_scss_get`, tokens with `jekyll_token_list` / `jekyll_token_get`, and Liquid includes or layouts with their corresponding list/get tools.
57
58
  4. Match the repository's existing component, naming, Liquid, SCSS, and documentation conventions. Do not assume default paths when scan results are available.
58
- 5. For requested writes, use the smallest relevant tool. Preview supported mutations with `dry_run: true`, review the reported operations, then run with `dry_run: false` or omit `dry_run` to apply them. Clearly report when the configured write mode prevents a change.
59
+ 5. For requested writes, use the smallest relevant tool. For `jekyll_component_create`, `dry_run: true` returns planned operations and unified diffs; review them before applying. For `jekyll_docs_update`, dry-run reports only the target path, not a content diff, and a normal update regenerates the target file. Clearly report when the configured write mode prevents a change.
59
60
  6. After changes, run `jekyll_component_validate` for a component and/or `jekyll_validate`. If the project has the needed Ruby/Jekyll environment, run `jekyll_build` to verify the site.
60
61
 
61
62
  ## Tool reference
@@ -63,8 +64,9 @@ Use `--root <path>` to target another project, `--preset auto|standard|chirpy|mi
63
64
  | Task | MCP tools |
64
65
  | --- | --- |
65
66
  | Project overview and structure | `jekyll_project_info`, `jekyll_project_scan`, `jekyll_config_get` |
66
- | Components | `jekyll_component_list`, `jekyll_component_get`, `jekyll_component_create`, `jekyll_component_validate`, `jekyll_component_delete` |
67
+ | Components | `jekyll_component_list`, `jekyll_component_get`, `jekyll_component_catalog`, `jekyll_component_create`, `jekyll_component_preview`, `jekyll_component_validate`, `jekyll_component_delete` |
67
68
  | Component aliases | `list_components`, `inspect_component`, `create_component`, `validate_component` |
69
+ | Catalog and preview aliases | `component_catalog`, `preview_component` |
68
70
  | SCSS and design tokens | `jekyll_scss_list`, `jekyll_scss_get`, `jekyll_scss_create`, `jekyll_token_list`, `jekyll_token_get`, `jekyll_token_update` |
69
71
  | Liquid includes and layouts | `jekyll_include_list`, `jekyll_include_get`, `jekyll_layout_list`, `jekyll_layout_get` |
70
72
  | Documentation | `jekyll_docs_create`, `jekyll_docs_update` |
@@ -72,6 +74,8 @@ Use `--root <path>` to target another project, `--preset auto|standard|chirpy|mi
72
74
 
73
75
  For component creation, `jekyll_component_create` or `create_component` accepts `name`, optional `category`, `variants`, `javascript`, `documentation`, `example`, and `dry_run`. Prefer this tool over separate file creation when the user asks for a reusable component; it scaffolds the Liquid component and associated assets/docs/examples. `inspect_component` reports Liquid include parameters and detected defaults/guards alongside source and SCSS details. `validate_component` checks Liquid fallbacks/guards and BEM/SCSS naming.
74
76
 
77
+ Use `jekyll_component_catalog` or `component_catalog` for a read-only overview of discovered components, including status, tags, summaries, path coverage, variants, and parameter counts. Use `jekyll_component_preview` or `preview_component` to generate a lightweight HTML sample with a selected variant and parameters; it is a preview, not a full Jekyll render. `jekyll_docs_update` accepts `category` as well as overview, variants, parameters, accessibility guidance, and notes. Its dry-run only identifies the target path, so inspect the existing documentation before applying an update that could replace authored content.
78
+
75
79
  Use the review prompts when supported by the MCP client: `jekyll_component_review`, `jekyll_accessibility_review`, `jekyll_performance_review`, and `jekyll_production_review`. Available resources include `jekyll://project`, `jekyll://components`, `jekyll://tokens`, `jekyll://config`, and `jekyll://documentation`.
76
80
 
77
81
  ## Write and security rules