You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .cursorrules
+27-2
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,30 @@
1
+
You are an expert full-stack web developer focused on producing clear, readable TypeScript code.
2
+
3
+
You always use the latest stable versions of everything, Tailwind CSS, and TypeScript, and you are familiar with the latest features and best practices.
4
+
5
+
You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning.
6
+
7
+
Technical preferences:
8
+
9
+
- Use semantic HTML elements where possible
10
+
- Always use kebab-case for component names (e.g. my-component.tsx)
11
+
- Follow docs from the official TypeScript, React, Remix, Next.js for Data Fetching, Rendering, and Routing
12
+
- Favour using React Server Components features where possible
13
+
- Minimize the usage of client components ('use client') to small, isolated components
14
+
- Always add loading and error states to data fetching components
15
+
- Implement error handling and error logging
16
+
17
+
General preferences:
18
+
19
+
- Follow the user's requirements carefully & to the letter.
20
+
- Always write correct, up-to-date, bug-free, fully functional and working, secure, performant and efficient code.
21
+
- Focus on readability over being performant.
22
+
- Fully implement all requested functionality.
23
+
- Leave NO todo's, placeholders or missing pieces in the code.
24
+
- Be sure to reference file names.
25
+
- Be concise. Minimize any other prose.
26
+
- If you think there might not be a correct answer, you say so. If you do not know the answer, say so instead of guessing.
27
+
1
28
Code Style and Structure:
2
29
3
30
- Write concise, technical TypeScript code with accurate examples
@@ -52,5 +79,3 @@ Key Conventions:
52
79
- Favor server components and Next.js SSR
53
80
- Use only for Web API access in small components
54
81
- Avoid for data fetching or state management
55
-
56
-
Follow React docs, Remix docs, and Next.js docs for Data Fetching, Rendering, and Routing
Copy file name to clipboardExpand all lines: README.md
+61-51
Original file line number
Diff line number
Diff line change
@@ -13,10 +13,11 @@
13
13
14
14
## Goal
15
15
16
-
🐶Dogokit Akita is a comprehensive, opinionated full stack application development kit. Encompassing JavaScript, TypeScript, Node.js, Bun, and more. It serves as a versatile reference for constructing robust web applications, that can scale from zero to millions of users.
16
+
🐶Dogokit Akita is a comprehensive and opinionated full stack application development kit. Encompassing JavaScript/TypeScript, Node.js/Deno/Bun, and more. It serves as a versatile reference for constructing robust web applications, that can scale from zero to millions of users.
17
17
18
18
- Default frontend web with React and Tailwind CSS.
19
-
- Optional backend API with GraphQL or REST API.
19
+
- Optional full-stack web with Next.js or Remix (React Router).
20
+
- Optional backend API with REST API or GraphQL.
20
21
- Interchangeable ORM with Prisma or Drizzle.
21
22
- Bring your own thing from non-JS ecosystem.
22
23
@@ -26,7 +27,7 @@
26
27
2. Optionally scale API complexity with GraphQL/REST/tRPC.
27
28
3. Customize architecture flexibly, with the defaults should not use any 3rd party services.
28
29
4. Deploy anywhere from a single VPS to any cloud provider, no vendor lock-in.
29
-
5. Demonstrate the JavaScript developer experience ecosystem capability, as alternative to existing one like RedwoodJS, and the others such as PHP with Laravel, Ruby with Rails, Python with Django, etc.
30
+
5. Demonstrate the JavaScript developer experience (DX) ecosystem capability. As an alternative to existing one like RedwoodJS, and the others such as PHP with Laravel, Ruby with Rails, Python with Django, etc.
30
31
31
32
## Tech Stack
32
33
@@ -57,12 +58,15 @@
57
58
- Icon: [unplugin-icons](docs/unplugin-icons.md)
58
59
- Email: [React Email](docs/react-email.md)
59
60
- Test: [Storybook](docs/storybook.md)
60
-
6. Format and Lint: [Prettier](docs/prettier.md) / [ESLint](docs/eslint.md) / [Biome](docs/biome.md) / [Oxc](docs/oxc.md)
11. Container: [Docker](docs/docker.md) with [Docker Compose](docs/docker-compose.md), using [OrbStack](docs/orbstack.md) or [Docker Desktop](docs/docker-desktop.md)
61
+
6. Format and Lint: [Biome](docs/biome.md) + [Ultracite](docs/ultracite.md) / [Prettier](docs/prettier.md) / [ESLint](docs/eslint.md) / [Oxc](docs/oxc.md)
`auto` is a tool designed to seamlessly automate the release workflow. It is powered by semantic version labels on pull requests. This approach does not require you to change your code or make any drastic changes to your current workflow.
4
+
5
+
While intended to run in a continuous integration (CI) environment, all auto commands can run locally as well.
0 commit comments