Cline rules

1# Templates
2We have several templates in this repo that serve as pre-configured project structures. This keeps the initial build tooling consistent such as the package.json configuration, shared eslint/esbuild/tsconfig rules, common build/test scripts, testing framework, and more.
3 
4* Warning: Some templates might be missing from the repo since the user may have not have needed them before: Ask the user to add the template if you need to use it.
5* Do NOT modify templates unless with explicit precise confirmation from the user
6 
7## Template Workflow
8When creating a new sdk/backend/frontend you should always follow the following workflow
9* Find the most relevant template for the new package (eg. starter-typescript for TS libraries, starter-react for React projects)
10* If you think a more relevant template may exist, confirm with the user or ask them to add it
11* Copy over the template and rename the folder `cp -R packages/starter-typescript packages/my-sdk`
12* Update the package.json with the package name
13* Update the package.json with the any additional dependencies the project might need (both devDependencies and regular dependencies)
14* Update the `/src` folder the new packages source code instead of the hello world example in hello.ts
15 
16## Typescript Template
17Cline uses the [starter-typescript](../packages/starter-typescript/) template for any new Typescript projects that simply create an SDK or generic Typescript library. This is the most general Typescript template and is only opinionated with regards to build tools and their configuration (esbuild, vite, eslint).
18 
19## React Template
20Cline uses the [starter=react](../packages/starter-react/) template for any new React projects. This template is more opinionated, adding ShadCN, Tanstack Query, Tanstack Router, Tailwind CSS and other patterns as a base for all React projects.
21