@stacksjs/defaults 0.70.206 → 0.70.208

package/ide/cursor/rules/code-style.mdc

@@ -0,0 +1,12 @@
+---
+description: Code Style & Structure specifics
+globs: 
+---
+## Code Style & Structure
+
+- Write concise, technical TypeScript code with accurate examples in the docblock
+- If Bun native modules are available, use them
+- Use functional and declarative programming patterns; avoid classes unless needed
+- Prefer iteration and modularization over code duplication
+- Use descriptive variable names with auxiliary verbs (e.g., `isLoading`, `hasError`)
+- Use proper jsdoc comments for functions, types, interfaces, and ensure examples are accurate

package/ide/cursor/rules/documentation.mdc

@@ -0,0 +1,9 @@
+---
+description: Documentation specific rules
+globs: docs/**/*.md
+---
+## Documentation
+
+- Write documentation for all functions, types, interfaces, and ensure examples are accurate
+- The `./docs` directory contains the BunPress Markdown documentation
+- Make sure to update the docs markdown files

package/ide/cursor/rules/error-handling-validation.mdc

@@ -0,0 +1,11 @@
+---
+description: Error Handling and Validation specifics
+globs: 
+---
+## Error Handling and Validation
+
+- Prioritize error handling: handle errors and edge cases early
+- Use early returns and guard clauses
+- Implement proper error logging and user-friendly messages
+- Use error boundaries for unexpected errors
+- Use `@stacksjs/error-handling`, which is similar to neverthrow, to handle errors and responses 

package/ide/cursor/rules/key-conventions.mdc

@@ -0,0 +1,11 @@
+---
+description: Key code conventions
+globs: 
+---
+## Key Conventions
+
+- If there are two equally valid implementations, the browser version should be preferred
+- Aim for 100% test coverage
+- Avoid usage of `any`
+- Reuse eslint-ignore comments where present, unless not needed
+- ensure we log everything properly, including for debug reasons

package/ide/cursor/rules/project-structure.mdc

@@ -0,0 +1,169 @@
+---
+description: Project structure information
+globs: 
+---
+## Project Structure
+
+### App Directory
+
+`./app` directory is the source where the business logic resides.
+
+- `./app/Actions` directory is the source of truth for all actions
+- `./app/Commands` directory is the source of truth for all commands
+- `./app/Jobs` directory is the source of truth for all jobs
+- `./app/Listeners` directory is the source of truth for all listeners
+- `./app/Models` directory is the source of truth for all models
+- `./app/Notifications` directory is the source of truth for all notifications
+
+### Cloud Directory
+
+`./cloud` directory is the source where the cloud logic resides.
+
+- `./cloud/recipes` directory is where the cloud recipes reside that can be used when creating a new server. Similar to Laravel Forge recipes
+- `./cloud/deploy-script.ts` is the scripts that is triggered when a deployment in the cloud is made
+- `./cloud/Dockerfile` is the Dockerfile that is used to build the Docker image for the cloud
+- `./cloud/serverless.ts` is where the automated CDK stack is defined. Used to define the serverless services
+- `./cloud/servers.ts` is where the servers are defined that can be used when creating a new server. Define EC2 instances, load balancers, web servers, app servers, worker servers, etc.
+
+### Config Directory
+
+`./config` directory is where the configuration for the project resides.
+
+- `./config/ai.ts` is where the AI configuration is defined
+- `./config/app.ts` is where the application configuration is defined
+- `./config/cache.ts` is where the cache configuration is defined
+- `./config/database.ts` is where the database configuration is defined
+- `./config/dns.ts` is where the DNS configuration is defined
+- `./config/email.ts` is where the email configuration is defined
+- `./config/git.ts` is where the git configuration is defined
+- `./config/hashing.ts` is where the hashing configuration is defined
+- `./config/logging.ts` is where the logging configuration is defined
+- `./config/mail.ts` is where the mail configuration is defined
+- `./config/notification.ts` is where the notification configuration is defined
+- `./config/payment.ts` is where the payment configuration is defined
+- `./config/security.ts` is where the security configuration is defined
+- `./config/services.ts` is where the services configuration is defined
+- `./config/storage.ts` is where the storage configuration is defined
+- `./config/team.ts` is where the team configuration is defined
+- `./config/ui.ts` is where the UI configuration is defined
+
+### Database Directory
+
+`./database` directory is where the database logic resides.
+
+- `./database/migrations` directory is where the migrations are defined which likely are auto generated by the ORM, unless the user adds custom migrations (buddy migrate)
+- `./database/seeder.ts` is where the seeder is defined which is used to seed the database (buddy seed)
+
+### Docs Directory
+
+`./docs` is where the BunPress documentation resides.
+
+### Public Directory
+
+`./public` directory is where the public assets reside.
+
+You would place your static assets in this directory. Anything in this directory will be available on the web, exposed behind your domain name, the APP_URL in the .env file.
+
+### Resources Directory
+
+The `./resources` directory is where the resources reside.
+
+- `./resources/assets` _directory where the assets reside_
+- `./resources/assets/fonts` _directory where the fonts reside_
+- `./resources/assets/styles` _directory where the CSS resides_
+- `./resources/assets/styles/docs/` _directory where the Documentation CSS resides_
+- `./resources/components` _directory where the user components reside. These are auto imported into the frontend_
+- `./resources/components/Dashboard` _directory where the dashboard User components reside. If they clashed with default components, these will take precedence_
+- `./resources/components/Docs` _directory where the documentation components reside, which will be auto imported into the documentation_
+- `./resources/emails` _directory where the emails reside_
+- `./resources/functions` _directory where the functions/composables reside_
+- `./resources/lang` _directory where the language files reside_
+- `./resources/layouts` _directory where the layouts reside_
+- `./resources/modules` _directory where the modules reside_
+- `./resources/plugins` _directory where the plugins reside_
+- `./resources/stores` _directory where the stores reside_
+- `./resources/types` _directory where the types reside_
+- `./resources/views` _directory where the views reside_
+
+## Routes Directory
+
+The `./routes` directory is where the routes reside.
+
+- `./routes/api.ts` _the API routes file_
+- `./routes/web.ts` _the web routes file_
+- `./routes/buddy.ts` _the buddy routes file (/buddy/...)_
+- `./routes/users.ts` _the users routes file (/users/...)_
+
+## Storage Directory
+
+The `./storage` directory is where the storage resides, and the core logic of the framework.
+
+- `./storage/framework` _the framework storage directory_
+- `./storage/framework/api` _the API storage directory_
+- `./storage/framework/actions` _the actions storage directory_
+- `./storage/framework/browser-auto-imports.json` _the browser auto imports file_
+- `./storage/framework/server-auto-imports.json` _the server auto imports file_
+- `./storage/framework/cache` _the cache storage directory_
+- `./storage/framework/cloud` _the cloud storage directory_
+- `./storage/framework/config` _the config storage directory_
+- `./storage/framework/core` _the core storage directory is where the core logic of the framework resides_
+- `./storage/framework/core/actions` _the core actions package_
+- `./storage/framework/core/analytics` _the core analytics package_
+- `./storage/framework/core/alias` _the core alias package_
+- `./storage/framework/core/api` _the core api package_
+- `./storage/framework/core/arrays` _the core arrays package_
+- `./storage/framework/core/auth` _the core auth package_
+- `./storage/framework/core/browser` _the core browser package_
+- `./storage/framework/core/build` _the core build package_
+- `./storage/framework/core/bun-create` _the core bun-create package_
+- `./storage/framework/core/calendar` _the core calendar package_
+- `./storage/framework/core/chat` _the core chat package_
+- `./storage/framework/core/cli` _the core cli package_
+- `./storage/framework/core/config` _the core config package_
+- `./storage/framework/core/cron` _the core cron package_
+- `./storage/framework/core/database` _the core database package_
+- `./storage/framework/core/datetime` _the core datetime package_
+- `./storage/framework/core/dns` _the core dns package_
+- `./storage/framework/core/docs` _the core docs package_
+- `./storage/framework/core/events` _the core events package_
+- `./storage/framework/core/faker` _the core faker package_
+- `./storage/framework/core/git` _the core git package_
+- `./storage/framework/core/health` _the core health package_
+- `./storage/framework/core/http` _the core http package_
+- `./storage/framework/core/lint` _the core lint package_
+- `./storage/framework/core/logging` _the core logging package_
+- `./storage/framework/core/mail` _the core mail package_
+- `./storage/framework/core/notifications` _the core notifications package_
+- `./storage/framework/core/objects` _the core objects package_
+- `./storage/framework/core/payments` _the core payments package_
+- `./storage/framework/core/query-builder` _the core query-builder package_
+- `./storage/framework/core/real-time` _the core real-time package_
+- `./storage/framework/core/realtime` _the core realtime package_
+- `./storage/framework/core/registry` _the core registry package_
+- `./storage/framework/core/router` _the core router package_
+- `./storage/framework/core/scheduler` _the core scheduler package_
+- `./storage/framework/core/security` _the core security package_
+- `./storage/framework/core/strings` _the core strings package_
+- `./storage/framework/core/testing` _the core testing package_
+- `./storage/framework/core/tunnel` _the core tunnel package_
+- `./storage/framework/core/ui` _the core ui package_
+- `./storage/framework/core/validation` _the core validation package_
+- `./storage/framework/core/vite-config` _the core vite-config package_
+- `./storage/framework/core/vite-plugin` _the core vite-plugin package_
+- `./storage/framework/core/whois` _the core whois package_
+- `./storage/framework/docs` _the docs storage directory_
+- `./storage/framework/libs` _the libs storage directory_
+- `./storage/framework/requests` _the requests storage directory_
+- `./storage/framework/types` _the types storage directory_
+- `./storage/framework/views` _the views storage directory_
+- `./storage/keys` _the keys storage directory_
+- `./storage/private` _the private storage directory—files that get uploaded to the server, but not exposed to the web_
+- `./storage/public` _the public storage directory—files that get exposed to the web_
+
+### Tests Directory
+
+The `./tests` directory is where the Bun tests reside.
+
+- `./tests/unit` _directory where the unit tests reside_
+- `./tests/features` _directory where the features tests reside_
+- `./tests/setup.ts` _setup script for the tests_

package/ide/cursor/rules/readme.mdc

@@ -0,0 +1,318 @@
+---
+description: General information based on the latest ./README.md content
+globs:
+---
+# Rapid App & Library Development
+
+Stacks is a rapid development framework, where the goal is to _help you_ create & maintain frontends, backends, and clouds—without having to worry about the boilerplate. _An all-in-one toolkit that meets all your full stack needs._
+
+- Web & Desktop Applications _(including system tray apps)_
+- Serverless & Traditional APIs
+- Cloud Infrastructure Creation & Maintenance
+- Interactive CLIs
+- Framework-agnostic Component & Function Libraries
+- Deployment & Release Manager _(CI & CD)_
+
+## Convention Over Configuration
+
+As a developer, Stacks helps you every step along the way—in beginner & expert-friendly ways, allowing you to focus on the _what & why_ of your project, all while enabling you to stay in control & ownership of your _(& your users’)_ data.
+
+> “It is the framework’s responsibility to remove patterns that lead to boilerplate code. And Stacks is really good at that.” _- Chris_
+
+<!-- ![Atomic UI & FX Design](./docs/assets/diagram.png) -->
+
+## Get Started
+
+It’s incredibly easy to get started with this framework. Simply run the following command in your terminal:
+
+```bash
+curl -Ssf stacksjs.com/install | sh # wip
+
+# alternatively, if Bun >= v1.2.0 is installed already,
+# you may also get started via:
+bunx buddy new my-project
+```
+
+## Usage
+
+The following list includes some of the most common ways to interact with the Stacks API.
+
+_Meet the toolkit, Buddy:_
+
+```bash
+buddy install # installs all dependencies
+buddy dev # starts one of the dev servers (frontend, API, components, docs, desktop, etc.)
+buddy share # creates a sharable link of your local project
+buddy build # follow CLI prompts to select which library (or server) to build
+buddy commit # follow CLI prompts for committing changes
+buddy release # creates the releases for the stack & consequently, publishes them to npm
+buddy upgrade # auto-update all deps & the Stacks framework
+
+buddy make:component HelloWorld # scaffolds a Component
+buddy make:function HelloWorld # scaffolds a Function
+buddy make:model Car # scaffolds a Model
+buddy make:action UpdateCar # scaffolds an Action
+buddy make:migration create_cars_table # scaffolds a Migration
+buddy make:view Car # scaffolds a Page (https://my-project.test/car)
+buddy make:command Inspire # scaffolds a Command
+buddy make:job SendEmail # scaffolds a Job
+buddy make:middleware Logger # scaffolds a new Middleware
+buddy make:notification WelcomeEmail # scaffolds a Notification
+buddy make:lang de # scaffolds a language file
+
+buddy list # lists all available commands
+buddy --help
+```
+
+<details>
+<summary>View the complete Buddy Toolkit</summary>
+
+```bash
+buddy --version # get the Stacks version
+buddy --help # view help menu
+# please note: you may suffix any command with the
+# `command --help` flag to review the help menu
+
+buddy install # installs dependencies
+buddy add # adds a stack or dependency
+buddy fresh # fresh reinstall of all deps
+buddy clean # removes all deps
+buddy setup # sets up the project initially
+buddy setup:oh-my-zsh # optional: sets up Oh My Zsh with auto-completions & "aliases"
+
+buddy upgrade # upgrades all dependencies
+buddy upgrade -i # prompts you to select which updates to apply (wip)
+buddy upgrade:dependencies # auto-upgrades package.json deps
+buddy upgrade:framework # auto-upgrades deps & the Stacks framework
+buddy upgrade:search-engine # auto-upgrades configured search engine
+buddy upgrade:shell # upgrades the shell integration
+buddy upgrade:binary # upgrades the `stacks` binary
+buddy upgrade:bun # upgrades to latest project-defined Bun version
+buddy upgrade:all # auto-upgrades all of the above
+
+# if you need any more info on any command listed here, you may suffix
+# any of them via the "help option", i.e. `buddy ... --help`
+
+buddy dev # starts the frontend dev server
+buddy dev -i # prompts any of the dev servers (components, functions, views, docs, or api)
+buddy dev:api # starts the API dev server
+buddy dev:dashboard # starts the Admin/Dashboard dev server
+buddy dev:desktop # starts the Desktop dev server
+buddy dev:views # starts frontend dev server
+buddy dev:components # starts component dev server
+buddy dev:functions # stubs functions
+buddy dev:docs # starts local docs dev server
+buddy dev docs # also starts the local docs dev server (colon is optional for all commands)
+buddy development # `buddy dev` alias
+
+buddy share # creates a sharable link to your local project
+
+# for Laravel folks, `serve` may ring more familiar than the `dev` name. Hence, we aliased it:
+buddy serve
+buddy serve:components
+buddy serve:desktop
+buddy serve:views
+buddy serve:functions
+buddy serve:docs
+
+# building for production (e.g. AWS, Google Cloud, npm, Vercel, Netlify, et al.)
+buddy build # select a specific build (follow CLI prompts)
+buddy build:views # builds SSG views
+buddy build:desktop # builds Desktop application
+buddy build:library # builds any or all libraries
+buddy build:functions # builds function library
+buddy build:components # builds the STX component library and Web Component library
+buddy build:web-components # builds framework agnostic Web Component library (i.e. Custom Elements)
+buddy build:all # builds all your code
+
+# `buddy build` aliases
+buddy prod
+buddy prod:components
+buddy prod:desktop
+buddy prod:library
+buddy prod:views
+buddy prod:functions
+buddy prod:web-components
+buddy prod:all
+buddy production # `buddy prod` alias
+
+# sets your application key
+buddy key:generate
+
+buddy make:component HelloWorld # bootstraps a HelloWorld component
+buddy make:function hello-world # bootstraps a hello-world function
+buddy make:view hello-world # bootstraps a hello-word page
+buddy make:model Car # bootstraps a Car model
+buddy make:database cars # creates a cars database
+buddy make:migration create_cars_table # creates a cars migration file
+buddy make:factory cars # creates a Car factory file
+buddy make:table cars # bootstraps a cars data table
+buddy make:notification welcome-email # bootstraps a welcome-email notification
+buddy make:lang de # bootstraps a lang/de.yml language file
+buddy make:stack my-project # shares logic with `bunx --bun stacks new my-project`
+
+buddy migrate # runs database migrations
+buddy migrate:dns # sets the ./config/dns.ts file
+
+buddy dns example.com # list all DNS records for example.com
+buddy dns example.com --type MX # list MX records for example.com
+
+buddy https example.com/api/hello
+# http [flags] [METHOD] URL [ITEM [ITEM]]
+buddy http --help
+buddy http PUT example.com/api/put X-API-Token:123 name=John # Custom HTTP method, HTTP headers and JSON data
+buddy http -v example.com/api/get # See the request that is being sent using one of the output options
+buddy http POST example.com/api/post hello=World # submitting forms
+buddy http -a USERNAME POST https://api.github.com/repos/user/repo/issues/83/comments body='Great feature! :heart:'
+buddy http localhost:8000 Host:example.com
+
+buddy lint # runs linter
+buddy lint:fix # runs linter and fixes issues
+
+buddy commit # follow CLI prompts for committing staged changes
+buddy release # creates the releases for the stack & triggers the Release Action (workflow)
+buddy changelog # generates CHANGELOG.md
+
+# when deploying your app/s to a remote server or cloud provider
+buddy deploy # select a specific deployment (follow CLI prompts)
+# buddy deploy:docs # deploys docs to AWS (or other configured provider)
+# buddy deploy:functions # deploys functions to AWS (or other configured provider)
+# buddy deploy:views # deploys views to AWS (or other configured provider)
+# buddy deploy:all # deploys all your code
+buddy undeploy # be careful: "undeploys" removes/deletes your deployed resources
+
+buddy cloud:remove # removes cloud setup
+buddy cloud:cleanup # removes cloud setup & cleans up all potentially leftover resources
+buddy cloud:add --jump-box # adds a jump box to your cloud setup
+
+# select the example to run (follow CLI prompts)
+buddy example # prompts you to select which example to run
+buddy example:web-components # runs the Web Component example
+
+# you likely won’t need to run these commands as they are auto-triggered, but they are available
+buddy generate  # prompts you to select which generator to run
+buddy generate:types # generates types for your components, functions, & views
+buddy generate:entries # generates entry files for components, functions, & views
+buddy generate:web-types # generates Web Component types
+buddy generate:vscode-custom-data # generates VSCode custom data
+buddy generate:ide-helpers # generates IDE helpers
+buddy generate:component-meta # generates component meta
+buddy generate:all # runs all generators
+
+# generates your application key
+buddy key:generate # generates your application key
+
+# generate your TypeScript declarations
+buddy types:generate # generates types for your components, functions, & views
+buddy types:fix # auto-fixes types for your components, functions, & views
+
+buddy domains # alias for `buddy domains:list`
+buddy domains:add stacksjs.com # adds a domain
+buddy domains:remove stacksjs.com # removes a domain
+buddy domains:list # lists all domains
+buddy domains:update # apply ./config/dns.ts updates
+buddy domains:purchase stacksjs.com # purchase a new domain
+
+# test your stack
+buddy test # runs test suite (unit & e2e)
+buddy test:coverage # runs test coverage
+buddy test:types # runs typecheck
+
+# the CLI may be triggered in any
+# of the following syntax:
+stx fresh
+buddy fresh
+bud fresh
+```
+
+</details>
+
+Read more here about the Stacks CLI in the documentation.
+
+## Features
+
+The Stacks framework is a harmony of several “engines” to build any web and/or desktop application, in highly scalable & privacy-friendly ways. It consists of the following engines:
+
+### Frontend Development
+
+_Develop dynamic UIs with helpers for atomic design, and much more._
+
+- 🧩 **Components** _primitive to develop user interfaces_
+- 🤖 **Functions** _primitive to develop business logic (and grant your UI superpowers)_
+- 🎨 **UI Kit** _modern & deeply-integrated components_
+- 🌐 **Web** _“a routing & templating engine that makes sense”_
+- 🖥️ **Desktop** _transforms your web app into a desktop app, plus more_
+- 📝 **Documentation** _markdown-based documentation, auto-generated_
+- 📚 **Library** _auto-builds & manages component & function libraries_
+- ⚡️ Powered by Bun, STX, Tauri, Crosswind, and BunPress
+
+### Backend Development
+
+_Develop serverless (or server) functions with countless helpers to build scalable & fast APIs._
+
+- 🪄 **AI** _deep AI integrations & foundational model access_
+- 🤖 **APIs** _scalability & maintainability built-in_
+- 🏎️ **Cache** _unified caching for DynamoDB, Redis and more_
+- ⚙️ **CLIs** _create beautiful CLIs for Linux, Windows, and Mac (dependency-free binaries)_
+- 📀 **Database** _DynamoDB, SQLite, MySQL, Postgres, and more_
+- 👾 **Errors** _native type-safe error handling_
+- 🗓️ **Events** _functional event (front & backend) communication_
+- 📢 **Notifications** _emails, SMSs, direct, and push notifications & webhooks_
+- 🗺️ **ORM** _automated schemas for scale & a pretty API_
+- 💳 **Payments** _unified API for one-off & subscription billing methods for Stripe_
+- ⚙️ **Queues** _run any heavy workload in the background_
+- 🛠️ **Query Builder** _powerful, type-safe SQL query builder_
+- 💬 **Realtime** _“everything you need to build dynamic real-time apps”_
+- 🧭 **Router** _smart routing, file-based or Laravel-like_
+- 🔎 **Search Engine** _smart searching, advanced filtering & sorting, pagination, headless UI_
+- 💾 **Storage** _a secure-by-default File API that feels right_
+- 🧪 **Tinker** _a powerful TypeScript REPL_
+- 🌪️ **Validation** _e2e type-safety (true frontend & backend harmony)_
+
+### Cloud Development
+
+_Develop & maintain cloud infrastructure with ease. “Imagine Vercel, Vapor and Forge having been unified.”_
+
+- ☁️ **Server** _local development server & production-ready servers out-of-the-box_
+- ⛅️ **Serverless** _on-demand, auto-scaling, zero maintenance_
+- ⏰ **Alarms** _built-in cloud infrastructure monitoring to avoid surprises_
+- 🚏 **CDN** _zero-config, low-latency, request life-cycle hooks, optimized request compressions (Brotli & gzip)_
+- 🔀 **Domain** _version-controlled & zero-config domain management (e.g. DNS management)_
+- 🤖 **AI** _fine-tune a foundational model using your application data_
+- 📧 **Email** _secure & zero-setup <easy-peasy@custom-domains.com> mailboxes_
+- 🔐 **Firewall** _native web application firewall support_
+- 📦 **Storage** _unlimited cloud storage & automatic backups_
+- 🚜 **Maintenance** _maintain your cloud infrastructure with ease using Buddy & Stacks_
+- 🚦 **Infrastructure as Code** _version-controlled cloud infrastructure (AWS, Google next?)_
+
+### CI/CD
+
+_Focus on coding, not publishing._
+
+- 🚀 **Deployment Manager** _takes the sweat out of production deployments—zero-setup push-to-deploy_
+- 0️⃣ **Zero Downtime** _deploy with confidence using a zero-downtime deployment strategy_
+- 📫 **Release Manager** _libraries (component & function) auto-published to npm, git helpers, and more_
+
+### Developer Experience (DX)
+
+Convention over configuration, while staying wholly configurable. _No more boilerplate._
+
+- 💎 **Automated Upgrades** _no need to worry about upgrading to the latest versions, Stacks upgrades you_
+- 🦋 **Pretty Dev URLs** _your-project.localhost instead of localhost:3000_
+- 💡 **IDE Integration** _auto-completions, inline docs & a powerful VS Code setup_
+- 🪄 **Zero-Config** _yet highly configurable—convention over configuration_
+- 💅 **Linter & Formatter** _auto-configured & built into your IDE_
+- 💪🏼 **Type Strong** _built-in e2e type-safety_
+- ✨ **Git Workflows** _committing with ease_
+- 🚗 **Auto Imports** _your components & functions, including date, string, array, & object helpers_
+- ⏩ **Code Snippets** _goodbye to the boilerplate code—thank you Sarah Drasner_
+- 🔤 **Spell Checker** _be notified once there are typos_
+- 🛠️ **Essential Utilities** _powers at your fingertips. Collections, STX composables, and more_
+- 👥 **Team Management** _manage your team & their permissions_
+- 🧪 **Streamlined Testing** _unit & e2e tests powered by Bun, Vitest & Playwright_
+
+No matter whether you are a beginner or an expert, the approachable Stacks design allows you to learn at your own pace, using our thorough documentation covering every aspect of the framework. Stacks is extremely beginner & expert-friendly.
+
+Develop beautiful, reactive, composable UIs without learning a new set of languages. HTML, CSS, and minimal JavaScript—that’s all you need to dive in now! _Or TypeScript ✌🏼_
+
+> _An actual rapid application development framework for all Full Stack needs. Next-level simplicity & DX._

package/ide/cursor/rules/syntax-formatting.mdc

@@ -0,0 +1,9 @@
+---
+description: Syntax and Formatting specifics
+globs: 
+---
+## Syntax and Formatting
+
+- Use the "function" keyword for pure functions
+- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements
+- Make sure everything is properly commented

package/ide/cursor/rules/testing.mdc

@@ -0,0 +1,10 @@
+---
+description: Testing specifics
+globs: 
+---
+## Testing
+
+- Write tests for all functions, types, interfaces, and ensure examples are accurate
+- The `./test` directory is where the tests are stored
+- Use `bun test` to run the tests
+- Use bun native modules for testing from `import { x, y, z } from 'bun:test'`

package/ide/cursor/rules/typescript.mdc

@@ -0,0 +1,9 @@
+---
+description: TypeScript Usage specifics
+globs: docs/**/*.md
+---
+## TypeScript Usage
+
+- Use TypeScript for all code; prefer interfaces over types
+- Avoid enums; use `maps` instead, or `as const`
+- Use functional components with TypeScript interfaces