@smartsoft001-mobilems/claude-plugins 2.94.0 → 2.95.0

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.
Files changed (4) hide show
  1. package/package.json +1 -1
  2. package/plugins/mobilems/.claude-plugin/plugin.json +1 -1
  3. package/plugins/mobilems/skills/mobilems-search/SKILL.md +4 -7
  4. package/plugins/mobilems/skills/mobilems-static-pages/SKILL.md +3 -7
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@smartsoft001-mobilems/claude-plugins",
3
- "version": "2.94.0",
3
+ "version": "2.95.0",
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },
package/plugins/mobilems/.claude-plugin/plugin.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "name": "mobilems",
3
3
  "description": "MobilEMS-specific Claude Code skills (MuzaCMS / MobileMS indexer API)",
4
- "version": "2.94.0"
4
+ "version": "2.95.0"
5
5
  }
package/plugins/mobilems/skills/mobilems-search/SKILL.md CHANGED
@@ -41,13 +41,10 @@ representations of the same object.
41
41
 
42
42
  ## Steps
43
43
 
44
- 1. **Read the mockup — once** in `docs/mockups/` and write
45
- `.ai/tasks/<issue>/mockup-notes.md` (layout, spacing, colours as token names,
46
- typography, field order, states) before styling; work from the note and do
47
- not re-read the image in this step. The searchbar and the result list item
48
- are usually exported as separate design-system components rather than a full
49
- screen, so match the component and keep the page layout consistent with the
50
- rest of the portal.
44
+ 1. **Read the mockup** in `docs/mockups/` — the searchbar and the result list
45
+ item are usually exported as separate design-system components rather than a
46
+ full screen, so match the component and keep the page layout consistent with
47
+ the rest of the portal.
51
48
  2. **Tabs come from modules.** Each feature module registers a child route under
52
49
  `wyszukaj/:text` (its search module) and the page builds its tab list from
53
50
  what is registered. When a tab is missing, fix it in that module's skill
package/plugins/mobilems/skills/mobilems-static-pages/SKILL.md CHANGED
@@ -39,13 +39,9 @@ exists. Re-implementing it is a defect, not a shortcut:
39
39
 
40
40
  ## Steps
41
41
 
42
- 1. **Read the mockup — once.** Exports live in `docs/mockups/`; read them (Read)
43
- rather than guessing from the Figma link, then immediately write
44
- `.ai/tasks/<issue>/mockup-notes.md` (layout order, grid and spacing, colours
45
- as token names, typography, field order, states, header and footer) and work
46
- from the note. Note the container width, heading scale, spacing rhythm and
47
- how the page header/hero differs from the module pages. Do not re-read the
48
- image later in this step; `/flow:impl` reads it once more in its comparison.
42
+ 1. **Read the mockup.** Exports live in `docs/mockups/`; read them (Read) rather
43
+ than guessing from the Figma link. Note the container width, heading scale,
44
+ spacing rhythm and how the page header/hero differs from the module pages.
49
45
  2. **CMS data — render everything the API sends.** The page payload carries more
50
46
  than a title and body: `image`, `backgroundImage`, `links`, `slides`.
51
47
  A field that arrives and is not rendered reads to the client as a missing