cognite-create 0.2.8 → 0.2.9

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 (2) hide show
  1. package/package.json +1 -1
  2. package/templates/.cursor/rules/general.mdc +1 -7
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cognite-create",
3
- "version": "0.2.8",
3
+ "version": "0.2.9",
4
4
  "description": "Create a Next.js app preconfigured with Cognite defaults.",
5
5
  "bin": {
6
6
  "cognite-create": "./bin/index.js"
package/templates/.cursor/rules/general.mdc CHANGED
@@ -4,10 +4,4 @@ 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. 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
- - If references are provided, list all components you can identify in the images that may be needed later, this should include layouts, navigation, headers, actions, copy text.
11
- - Use the ShadCN MCP to list the Cognite components you can use
12
- - Include all Cognite components you will need and fill any gaps with ShadCN
13
- - Make sure to check the globals.css file for any styling gaps
7
+ Use the ShadCN MCP server to list the Cognite registry for components you can use. If there are no Cognite components fit for purpose, fallback to ShadCN registry ones. When building from reference, make sure to include all components in the reference material in your final build.