@c8y/websdk 1024.21.3 → 1024.22.1
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.
- package/dist/templates/ai-configs/claude/CLAUDE.md +3 -3
- package/dist/templates/ai-configs/cursor/cursor.mdc +3 -3
- package/dist/templates/ai-configs/gemini/GEMINI.md +3 -3
- package/dist/templates/ai-configs/github/copilot-instructions.md +3 -3
- package/dist/templates/ai-configs/jetbrains/guidelines.md +3 -3
- package/dist/templates/ai-configs/windsurf/guidelines.md +3 -3
- package/package.json +1 -1
|
@@ -16,8 +16,8 @@
|
|
|
16
16
|
|
|
17
17
|
When the user requests ANY UI work (planning, design, implementation), your **FIRST ACTION** must be:
|
|
18
18
|
|
|
19
|
-
1. **Fetch** https://cumulocity.com/codex/llms.txt
|
|
20
|
-
2. **Search
|
|
19
|
+
1. **Fetch** https://cumulocity.com/codex/llms.txt — the lean root catalog listing the 8 sections and their per-section/full index files
|
|
20
|
+
2. **Search for component keywords** (modal, button, form, table, etc.) in the relevant per-section file first — `https://cumulocity.com/codex/llms-<section>.txt` (e.g. `llms-components.txt`) — the lighter approach; only fall back to `https://cumulocity.com/codex/llms-full.txt` (whole corpus) as a last resort if the section is unknown or nothing matches. The root no longer inlines component-level links.
|
|
21
21
|
3. **If found:** Read the specific `.md` documentation file like `https://cumulocity.com/codex/components/forms/editor.md`
|
|
22
22
|
4. **Read and analyze** the documentation content
|
|
23
23
|
5. **Locate examples** in the public tutorial repository:
|
|
@@ -32,7 +32,7 @@ e.g. for file path './packages/tutorial/src/selector/asset-selector-example/tree
|
|
|
32
32
|
- ❌ Making a plan without actually fetching and reading documentation
|
|
33
33
|
|
|
34
34
|
**✅ VALID:**
|
|
35
|
-
- ✓ Fetch llms.txt → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
35
|
+
- ✓ Fetch llms.txt → keyword-search the section file (llms-components.txt), llms-full.txt only if that fails → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
36
36
|
|
|
37
37
|
### Step 2: Check for Existing Components
|
|
38
38
|
|
|
@@ -16,8 +16,8 @@
|
|
|
16
16
|
|
|
17
17
|
When the user requests ANY UI work (planning, design, implementation), your **FIRST ACTION** must be:
|
|
18
18
|
|
|
19
|
-
1. **Fetch** https://cumulocity.com/codex/llms.txt
|
|
20
|
-
2. **Search
|
|
19
|
+
1. **Fetch** https://cumulocity.com/codex/llms.txt — the lean root catalog listing the 8 sections and their per-section/full index files
|
|
20
|
+
2. **Search for component keywords** (modal, button, form, table, etc.) in the relevant per-section file first — `https://cumulocity.com/codex/llms-<section>.txt` (e.g. `llms-components.txt`) — the lighter approach; only fall back to `https://cumulocity.com/codex/llms-full.txt` (whole corpus) as a last resort if the section is unknown or nothing matches. The root no longer inlines component-level links.
|
|
21
21
|
3. **If found:** Read the specific `.md` documentation file like `https://cumulocity.com/codex/components/forms/editor.md`
|
|
22
22
|
4. **Read and analyze** the documentation content
|
|
23
23
|
5. **Locate examples** in the public tutorial repository:
|
|
@@ -32,7 +32,7 @@ e.g. for file path './packages/tutorial/src/selector/asset-selector-example/tree
|
|
|
32
32
|
- ❌ Making a plan without actually fetching and reading documentation
|
|
33
33
|
|
|
34
34
|
**✅ VALID:**
|
|
35
|
-
- ✓ Fetch llms.txt → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
35
|
+
- ✓ Fetch llms.txt → keyword-search the section file (llms-components.txt), llms-full.txt only if that fails → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
36
36
|
|
|
37
37
|
### Step 2: Check for Existing Components
|
|
38
38
|
|
|
@@ -16,8 +16,8 @@
|
|
|
16
16
|
|
|
17
17
|
When the user requests ANY UI work (planning, design, implementation), your **FIRST ACTION** must be:
|
|
18
18
|
|
|
19
|
-
1. **Fetch** https://cumulocity.com/codex/llms.txt
|
|
20
|
-
2. **Search
|
|
19
|
+
1. **Fetch** https://cumulocity.com/codex/llms.txt — the lean root catalog listing the 8 sections and their per-section/full index files
|
|
20
|
+
2. **Search for component keywords** (modal, button, form, table, etc.) in the relevant per-section file first — `https://cumulocity.com/codex/llms-<section>.txt` (e.g. `llms-components.txt`) — the lighter approach; only fall back to `https://cumulocity.com/codex/llms-full.txt` (whole corpus) as a last resort if the section is unknown or nothing matches. The root no longer inlines component-level links.
|
|
21
21
|
3. **If found:** Read the specific `.md` documentation file like `https://cumulocity.com/codex/components/forms/editor.md`
|
|
22
22
|
4. **Read and analyze** the documentation content
|
|
23
23
|
5. **Locate examples** in the public tutorial repository:
|
|
@@ -32,7 +32,7 @@ e.g. for file path './packages/tutorial/src/selector/asset-selector-example/tree
|
|
|
32
32
|
- ❌ Making a plan without actually fetching and reading documentation
|
|
33
33
|
|
|
34
34
|
**✅ VALID:**
|
|
35
|
-
- ✓ Fetch llms.txt → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
35
|
+
- ✓ Fetch llms.txt → keyword-search the section file (llms-components.txt), llms-full.txt only if that fails → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
36
36
|
|
|
37
37
|
### Step 2: Check for Existing Components
|
|
38
38
|
|
|
@@ -16,8 +16,8 @@
|
|
|
16
16
|
|
|
17
17
|
When the user requests ANY UI work (planning, design, implementation), your **FIRST ACTION** must be:
|
|
18
18
|
|
|
19
|
-
1. **Fetch** https://cumulocity.com/codex/llms.txt
|
|
20
|
-
2. **Search
|
|
19
|
+
1. **Fetch** https://cumulocity.com/codex/llms.txt — the lean root catalog listing the 8 sections and their per-section/full index files
|
|
20
|
+
2. **Search for component keywords** (modal, button, form, table, etc.) in the relevant per-section file first — `https://cumulocity.com/codex/llms-<section>.txt` (e.g. `llms-components.txt`) — the lighter approach; only fall back to `https://cumulocity.com/codex/llms-full.txt` (whole corpus) as a last resort if the section is unknown or nothing matches. The root no longer inlines component-level links.
|
|
21
21
|
3. **If found:** Read the specific `.md` documentation file like `https://cumulocity.com/codex/components/forms/editor.md`
|
|
22
22
|
4. **Read and analyze** the documentation content
|
|
23
23
|
5. **Locate examples** in the public tutorial repository:
|
|
@@ -32,7 +32,7 @@ e.g. for file path './packages/tutorial/src/selector/asset-selector-example/tree
|
|
|
32
32
|
- ❌ Making a plan without actually fetching and reading documentation
|
|
33
33
|
|
|
34
34
|
**✅ VALID:**
|
|
35
|
-
- ✓ Fetch llms.txt → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
35
|
+
- ✓ Fetch llms.txt → keyword-search the section file (llms-components.txt), llms-full.txt only if that fails → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
36
36
|
|
|
37
37
|
### Step 2: Check for Existing Components
|
|
38
38
|
|
|
@@ -16,8 +16,8 @@
|
|
|
16
16
|
|
|
17
17
|
When the user requests ANY UI work (planning, design, implementation), your **FIRST ACTION** must be:
|
|
18
18
|
|
|
19
|
-
1. **Fetch** https://cumulocity.com/codex/llms.txt
|
|
20
|
-
2. **Search
|
|
19
|
+
1. **Fetch** https://cumulocity.com/codex/llms.txt — the lean root catalog listing the 8 sections and their per-section/full index files
|
|
20
|
+
2. **Search for component keywords** (modal, button, form, table, etc.) in the relevant per-section file first — `https://cumulocity.com/codex/llms-<section>.txt` (e.g. `llms-components.txt`) — the lighter approach; only fall back to `https://cumulocity.com/codex/llms-full.txt` (whole corpus) as a last resort if the section is unknown or nothing matches. The root no longer inlines component-level links.
|
|
21
21
|
3. **If found:** Read the specific `.md` documentation file like `https://cumulocity.com/codex/components/forms/editor.md`
|
|
22
22
|
4. **Read and analyze** the documentation content
|
|
23
23
|
5. **Locate examples** in the public tutorial repository:
|
|
@@ -32,7 +32,7 @@ e.g. for file path './packages/tutorial/src/selector/asset-selector-example/tree
|
|
|
32
32
|
- ❌ Making a plan without actually fetching and reading documentation
|
|
33
33
|
|
|
34
34
|
**✅ VALID:**
|
|
35
|
-
- ✓ Fetch llms.txt → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
35
|
+
- ✓ Fetch llms.txt → keyword-search the section file (llms-components.txt), llms-full.txt only if that fails → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
36
36
|
|
|
37
37
|
### Step 2: Check for Existing Components
|
|
38
38
|
|
|
@@ -16,8 +16,8 @@
|
|
|
16
16
|
|
|
17
17
|
When the user requests ANY UI work (planning, design, implementation), your **FIRST ACTION** must be:
|
|
18
18
|
|
|
19
|
-
1. **Fetch** https://cumulocity.com/codex/llms.txt
|
|
20
|
-
2. **Search
|
|
19
|
+
1. **Fetch** https://cumulocity.com/codex/llms.txt — the lean root catalog listing the 8 sections and their per-section/full index files
|
|
20
|
+
2. **Search for component keywords** (modal, button, form, table, etc.) in the relevant per-section file first — `https://cumulocity.com/codex/llms-<section>.txt` (e.g. `llms-components.txt`) — the lighter approach; only fall back to `https://cumulocity.com/codex/llms-full.txt` (whole corpus) as a last resort if the section is unknown or nothing matches. The root no longer inlines component-level links.
|
|
21
21
|
3. **If found:** Read the specific `.md` documentation file like `https://cumulocity.com/codex/components/forms/editor.md`
|
|
22
22
|
4. **Read and analyze** the documentation content
|
|
23
23
|
5. **Locate examples** in the public tutorial repository:
|
|
@@ -32,7 +32,7 @@ e.g. for file path './packages/tutorial/src/selector/asset-selector-example/tree
|
|
|
32
32
|
- ❌ Making a plan without actually fetching and reading documentation
|
|
33
33
|
|
|
34
34
|
**✅ VALID:**
|
|
35
|
-
- ✓ Fetch llms.txt → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
35
|
+
- ✓ Fetch llms.txt → keyword-search the section file (llms-components.txt), llms-full.txt only if that fails → Find modal docs → Read content → Find tutorial examples → Read example code → Then create plan
|
|
36
36
|
|
|
37
37
|
### Step 2: Check for Existing Components
|
|
38
38
|
|