cognite-create 0.1.8 → 0.2.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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "cognite-create",
|
|
3
|
-
"version": "0.1
|
|
3
|
+
"version": "0.2.1",
|
|
4
4
|
"description": "Create a Next.js app preconfigured with Cognite defaults.",
|
|
5
5
|
"private": false,
|
|
6
6
|
"bin": {
|
|
@@ -13,5 +13,6 @@
|
|
|
13
13
|
"engines": {
|
|
14
14
|
"node": ">=18.0.0"
|
|
15
15
|
},
|
|
16
|
-
"license": "UNLICENSED"
|
|
17
|
-
}
|
|
16
|
+
"license": "UNLICENSED",
|
|
17
|
+
"scripts": {}
|
|
18
|
+
}
|
|
@@ -4,4 +4,9 @@ globs:
|
|
|
4
4
|
alwaysApply: true
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
-
Use the ShadCN MCP server to check the Cognite registry for components you could use before making your own. If there are Cognite components available for what you are trying to do you must always use them over alternatives. We want to make sure our app aligns with the Cognite design system.
|
|
7
|
+
Use the ShadCN MCP server to check the Cognite registry for components you could use before making your own. If there are Cognite components available for what you are trying to do you must always use them over alternatives. We want to make sure our app aligns with the Cognite design system. If there are no Cognite components you can fallback to the default ShadCN ones just make sure they align with the consistent style of the Cognite ones.
|
|
8
|
+
|
|
9
|
+
Before generating anything:
|
|
10
|
+
- Use the ShadCN MCP to list the potential Cognite components you can use
|
|
11
|
+
- Take a close look at any references provide and make sure all components and landmarks are accounted for
|
|
12
|
+
- Make sure to check the globals.css file for any styling gaps
|