├── .cursorrules ├── LICENSE ├── README.md ├── cursor-ai-logo.png ├── rules-new ├── clean-code.mdc ├── codequality.mdc ├── cpp.mdc ├── database.mdc ├── fastapi.mdc ├── gitflow.mdc ├── nextjs.mdc ├── node-express.mdc ├── python.mdc ├── react.mdc ├── svelte.mdc ├── tailwind.mdc ├── typescript.mdc └── vue.mdc └── rules ├── android-jetpack-compose-cursorrules-prompt-file ├── .cursorrules ├── android---project-structure.mdc ├── android-jetpack-compose---general-best-practices.mdc ├── android-jetpack-compose---performance-guidelines.mdc ├── android-jetpack-compose---testing-guidelines.mdc └── android-jetpack-compose---ui-guidelines.mdc ├── angular-novo-elements-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── angular-standalone-component-rules.mdc ├── code-style-and-formatting-rules.mdc ├── debugging-and-testing-rules.mdc ├── development-process-rules.mdc ├── general-behavior-rules.mdc ├── general-coding-principles.mdc ├── novo-elements-integration-rules.mdc └── project-structure-rules.mdc ├── angular-typescript-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── angular-general.mdc ├── angular-template-hints.mdc ├── general-reasoning.mdc ├── refactoring-existing-code.mdc └── typescript-coding-style.mdc ├── ascii-simulation-game-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── army-and-battle-mechanics-rule.mdc ├── core-game-mechanics-rule.mdc ├── data-tracking-and-charts-rule.mdc ├── general-game-design-and-programming-rules.mdc └── visual-and-observational-rules.mdc ├── aspnet-abp-cursorrules-prompt-file ├── .cursorrules └── README.md ├── astro-typescript-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── astro-development-guidelines.mdc ├── commit-message-guidelines.mdc ├── custom-slash-commands.mdc ├── general-coding-style.mdc ├── tailwindcss-styling-guidelines.mdc └── typescript-development-guidelines.mdc ├── chrome-extension-dev-js-typescript-cursorrules-pro ├── .cursorrules ├── README.md ├── browser-api-usage-rules.mdc ├── chrome-extension-general-rules.mdc ├── code-output-rules.mdc ├── extension-architecture-rules.mdc ├── javascript-typescript-code-style.mdc ├── manifest-and-permissions-rules.mdc ├── performance-optimization-rules.mdc ├── security-and-privacy-rules.mdc ├── typescript-usage-rules.mdc └── ui-and-styling-rules.mdc ├── code-guidelines-cursorrules-prompt-file ├── .cursorrules ├── README.md └── general-coding-rules.mdc ├── convex-cursorrules-prompt-file ├── .cursorrules ├── convex-development---general.mdc ├── convex-schema-design---built-in-types.mdc ├── convex-schema-design---example-schema.mdc └── convex-schema-design---system-fields.mdc ├── cpp-programming-guidelines-cursorrules-prompt-file ├── .cursorrules └── README.md ├── cursor-ai-react-typescript-shadcn-ui-cursorrules-p ├── .cursorrules ├── README.md ├── naming-conventions-rule.mdc ├── performance-optimization-rule.mdc ├── react-and-typescript-general-rules.mdc ├── typescript-usage-rule.mdc └── ui-and-styling-rule.mdc ├── cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup ├── .cursorrules ├── README.md ├── data-fetching-rules-for-server-components.mdc ├── error-handling-rules.mdc ├── general-guidelines.mdc ├── metadata-rules.mdc ├── next-js-14-general-rules.mdc ├── tailwind-css-styling-rules.mdc └── typescript-code-generation-rules.mdc ├── cursorrules-cursor-ai-wordpress-draft-macos-prompt ├── .cursorrules ├── README.md ├── application-password-rule.mdc ├── initial-configuration-rule.mdc ├── new-user-experience-nux-flow-rule.mdc └── project-overview-rule.mdc ├── cursorrules-file-cursor-ai-python-fastapi-api ├── .cursorrules ├── README.md ├── error-handling-priorities.mdc ├── fastapi-blocking-operations.mdc ├── fastapi-components-and-validation.mdc ├── fastapi-conditional-statements.mdc ├── fastapi-dependencies.mdc ├── fastapi-dependency-injection.mdc ├── fastapi-file-structure.mdc ├── fastapi-function-definitions.mdc ├── fastapi-middleware.mdc ├── fastapi-performance-metrics.mdc ├── fastapi-performance-optimization.mdc ├── fastapi-startup-and-shutdown-events.mdc └── python-general-style.mdc ├── deno-integration-techniques-cursorrules-prompt-fil ├── .cursorrules ├── README.md ├── automation-script-rule.mdc ├── documentation-rule.mdc ├── general-development-rule.mdc └── project-overview-rule.mdc ├── dragonruby-best-practices-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── dragonruby-error-handling.mdc ├── dragonruby-general-ruby-rules.mdc ├── dragonruby-naming-conventions.mdc └── dragonruby-syntax-and-formatting.mdc ├── drupal-11-cursorrules-prompt-file ├── .cursorrules └── README.md ├── elixir-engineer-guidelines-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── commit-message-format.mdc └── elixir-general-engineering-rule.mdc ├── elixir-phoenix-docker-setup-cursorrules-prompt-fil ├── .cursorrules ├── README.md ├── commit-message-generation-rule.mdc └── elixir-general-engineering-rule.mdc ├── es-module-nodejs-guidelines-cursorrules-prompt-fil ├── .cursorrules ├── README.md ├── code-commenting-standards.mdc ├── code-style-and-improvements.mdc └── general-project-practices.mdc ├── flutter-app-expert-cursorrules-prompt-file ├── .cursorrules ├── flutter-core-rules.mdc ├── flutter-feature-rules.mdc ├── flutter-general-best-practices.mdc ├── flutter-performance-rules.mdc ├── flutter-presentation-rules.mdc └── flutter-testing-rules.mdc ├── flutter-development-guidelines-cursorrules-prompt-file ├── flutter-riverpod-cursorrules-prompt-file ├── .cursorrules ├── flutter-project-rules.mdc ├── general-ai-assistant-instructions.mdc └── tech-stack-configuration.mdc ├── git-conventional-commit-messages ├── .cursorrules └── README.md ├── github-code-quality-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── check-x-md-content-rule.mdc ├── file-by-file-changes-rule.mdc ├── no-apologies-rule.mdc ├── no-current-implementation-rule.mdc ├── no-implementation-checks-rule.mdc ├── no-inventions-rule.mdc ├── no-previous-x-md-consideration-rule.mdc ├── no-summaries-rule.mdc ├── no-understanding-feedback-rule.mdc ├── no-unnecessary-confirmations-rule.mdc ├── no-unnecessary-updates-rule.mdc ├── no-whitespace-suggestions-rule.mdc ├── preserve-existing-code-rule.mdc ├── provide-real-file-links-rule.mdc ├── single-chunk-edits-rule.mdc └── verify-information-rule.mdc ├── github-cursorrules-prompt-file-instructions ├── .cursorrules ├── README.md ├── code-writing-standards.mdc ├── comment-usage.mdc ├── conditional-encapsulation.mdc ├── dry-principle.mdc ├── function-length-and-responsibility.mdc ├── general-code-style-and-readability.mdc └── naming-conventions.mdc ├── go-backend-scalability-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── backend-general-expert.mdc ├── database-interaction-best-practices.mdc ├── go-grpc-service-rule.mdc └── protocol-buffer-definitions-rule.mdc ├── go-servemux-rest-api-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── go-api-development-general-rules.mdc ├── go-api-error-handling-and-response-formatting.mdc ├── go-api-security-and-best-practices.mdc ├── go-api-standard-library-usage.mdc └── go-api-step-by-step-planning.mdc ├── graphical-apps-development-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── element-file-structure-rules.mdc ├── general-project-rules.mdc ├── general-python-project-rules.mdc ├── langchain-integration-rules.mdc ├── panel-view-rules.mdc └── param-parameterized-class-rules.mdc ├── html-tailwind-css-javascript-cursorrules-prompt-fi ├── .cursorrules ├── README.md ├── general-ai-programming-assistant-rule.mdc └── html-tailwind-css-and-javascript-expert-rule.mdc ├── htmx-basic-cursorrules-prompt-file ├── .cursorrules ├── htmx-additional-instructions.mdc ├── htmx-best-practices-general.mdc └── htmx-folder-structure.mdc ├── htmx-django-cursorrules-prompt-file ├── .cursorrules ├── django-class-based-views-for-htmx.mdc ├── django-form-handling.mdc ├── django-middleware-for-request-response.mdc ├── django-orm-for-database-operations.mdc ├── django-static-files-management.mdc ├── django-url-routing.mdc ├── general-django-project-structure.mdc └── htmx-and-django-best-practices---general.mdc ├── htmx-flask-cursorrules-prompt-file ├── .cursorrules ├── additional-htmx-and-flask-instructions.mdc ├── flask-folder-structure.mdc └── htmx-and-flask-best-practices.mdc ├── htmx-go-basic-cursorrules-prompt-file ├── .cursorrules ├── htmx-and-go---best-practices.mdc ├── htmx-with-go---additional-instructions.mdc └── htmx-with-go---folder-structure.mdc ├── htmx-go-fiber-cursorrules-prompt-file ├── .cursorrules ├── fiber-logging-and-project-structure.mdc ├── fiber-routing-and-csrf-protection.mdc ├── htmx-go-and-fiber-best-practices-general.mdc └── recommended-folder-structure.mdc ├── java-general-purpose-cursorrules-prompt-file └── .cursorrules ├── java-springboot-jpa-cursorrules-prompt-file ├── .cursorrules ├── apiresponse-class.mdc ├── dto-conventions.mdc ├── entity-class-conventions.mdc ├── general-java-development-practices.mdc ├── globalexceptionhandler-class.mdc ├── repository-class-conventions.mdc ├── restcontroller-conventions.mdc ├── service-class-conventions.mdc └── spring-boot-configuration.mdc ├── javascript-astro-tailwind-css-cursorrules-prompt-f ├── .cursorrules ├── README.md ├── accessibility.mdc ├── astro-build-and-deployment.mdc ├── astro-component-development.mdc ├── astro-content-management.mdc ├── astro-data-fetching.mdc ├── astro-general.mdc ├── astro-integrations-and-plugins.mdc ├── astro-performance-optimization.mdc ├── astro-project-structure.mdc ├── astro-routing-and-pages.mdc ├── astro-seo-and-meta-tags.mdc ├── astro-styling.mdc ├── key-conventions.mdc ├── performance-metrics.mdc ├── tailwind-css-best-practices.mdc ├── tailwind-css-integration.mdc └── testing.mdc ├── javascript-chrome-apis-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── api-usage-rules.mdc ├── chrome-extension-general-rules.mdc ├── chrome-extension-manifest-rules.mdc ├── development-process-rules.mdc ├── extension-architecture-guidelines.mdc ├── internationalization-rules.mdc ├── javascript-code-style-and-structure.mdc ├── performance-optimization-rules.mdc ├── publishing-rules.mdc ├── security-practices.mdc ├── testing-and-debugging-rules.mdc └── ui-and-styling-rules.mdc ├── javascript-typescript-code-quality-cursorrules-pro ├── .cursorrules ├── README.md ├── bug-handling-with-todo-comments.mdc ├── coding-guidelines---dry-and-functional-style.mdc ├── coding-guidelines---early-returns-and-conditionals.mdc ├── coding-guidelines---naming-and-constants.mdc ├── function-ordering-conventions.mdc ├── general-coding-principles.mdc ├── javascript-documentation-with-jsdoc.mdc ├── minimal-code-changes-rule.mdc ├── persona---senior-full-stack-developer.mdc └── typescript-skip-jsdoc.mdc ├── knative-istio-typesense-gpu-cursorrules-prompt-fil ├── .cursorrules ├── README.md ├── backend-api-development.mdc ├── backend-development-rules.mdc ├── frontend-development-rules.mdc ├── general-knative-istio-typesense-htmx-gpu-applications.mdc ├── htmx-frontend-development.mdc ├── istio-service-mesh-configuration.mdc ├── istio-specific-rules.mdc ├── knative-service-guidance.mdc ├── knative-specific-rules.mdc ├── project-wide-rules.mdc ├── testing-and-monitoring-guidance.mdc ├── testing-and-monitoring-rules.mdc ├── typesense-search-engine-configuration.mdc └── typesense-specific-rules.mdc ├── kubernetes-mkdocs-documentation-cursorrules-prompt ├── .cursorrules ├── README.md ├── cloud-native-and-kubernetes-expertise-rules.mdc ├── collaboration-and-version-control-rules.mdc ├── content-creation-rules.mdc ├── documentation-best-practices-rules.mdc ├── documentation-style-and-structure-rules.mdc ├── general-cloud-native-documentation-rules.mdc ├── metadata-and-seo-rules.mdc ├── mkdocs-specific-rules.mdc └── technical-accuracy-and-usability-rules.mdc ├── laravel-php-83-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── laravel-package-coding-standards.mdc ├── laravel-package-development-guidelines.mdc ├── laravel-package-structure.mdc ├── laravel-package-testing-and-documentation.mdc └── readme-md-guidelines.mdc ├── laravel-tall-stack-best-practices-cursorrules-prom ├── .cursorrules ├── README.md ├── alpine-js-usage-rules.mdc ├── key-conventions-rules.mdc ├── laravel-best-practices-rules.mdc ├── livewire-implementation-rules.mdc ├── php-and-laravel-core-rules.mdc ├── security-best-practices-rules.mdc ├── tailwind-css-styling-rules.mdc ├── tall-stack-general.mdc └── testing-rules.mdc ├── linux-nvidia-cuda-python-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── ai-alignment-rules.mdc ├── continuous-improvement-rules.mdc ├── development-principles-rules.mdc ├── documentation-rules.mdc └── project-overview-rules.mdc ├── netlify-official-cursorrules-prompt-file └── .cursorrules ├── next-type-llm ├── .cursorrules ├── README.md ├── assistant-response-rules.mdc ├── coding-process-rules.mdc ├── coding-style-rules.mdc ├── editing-code-rules.mdc ├── general-project-assistant-rules.mdc ├── llm-integration-rules.mdc ├── technology-stack-backend-rules.mdc └── technology-stack-frontend-rules.mdc ├── nextjs-app-router-cursorrules-prompt-file ├── .cursorrules ├── next-js-additional-instructions.mdc ├── next-js-app-router-best-practices.mdc ├── next-js-env-variables.mdc ├── next-js-error-handling.mdc ├── next-js-folder-structure.mdc ├── next-js-image-optimization.mdc ├── next-js-naming-conventions.mdc ├── next-js-seo-guidelines.mdc ├── next-js-styling-conventions.mdc └── next-js-typescript-usage.mdc ├── nextjs-material-ui-tailwind-css-cursorrules-prompt ├── .cursorrules ├── README.md ├── aceternity-ui-configuration.mdc ├── bcrypt-rules.mdc ├── ckeditor-rules.mdc ├── framer-motion-rules.mdc ├── material-ui-configuration.mdc ├── next-js-project-setup.mdc ├── prisma-orm-rules.mdc ├── shadcn-ui-configuration.mdc └── tailwind-css-configuration.mdc ├── nextjs-react-tailwind-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── component-naming-and-directory-structure.mdc ├── general-typescript-node-js-next-js-rules.mdc ├── next-js-conventions-and-best-practices.mdc ├── performance-optimization-rules.mdc ├── placeholder-images.mdc ├── private-vs-shared-components.mdc └── ui-and-styling-with-shadcn-ui-and-tailwind.mdc ├── nextjs-react-typescript-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── error-handling-and-validation.mdc ├── general-solidity-typescript-node-js-next-js-rule.mdc ├── javascript-typescript-coding-style.mdc ├── next-js-conventions.mdc ├── next-js-server-actions.mdc └── react-next-js-components.mdc ├── nextjs-seo-dev-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── general-code-commenting.mdc ├── next-js-project-rules.mdc └── package-json-modification-protection.mdc ├── nextjs-supabase-shadcn-pwa-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── build-notes-file-rules.mdc ├── build-notes-guidelines.mdc ├── context-files-rules.mdc ├── general-code-quality-and-style.mdc ├── monorepo-and-tooling.mdc ├── next-js-15-conventions.mdc └── project-context-review.mdc ├── nextjs-supabase-todo-app-cursorrules-prompt-file ├── .cursorrules ├── README.md └── todo-app-general-rules.mdc ├── nextjs-tailwind-typescript-apps-cursorrules-prompt ├── .cursorrules ├── README.md ├── langchain-rag-application-development.mdc ├── next-js-tailwind-typescript-expert---general.mdc └── supabase-integration-in-next-js.mdc ├── nextjs-typescript-app-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── next-js-configuration-rule.mdc ├── next-js-project-rule.mdc └── typescript-code-style-rule.mdc ├── nextjs-typescript-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── assistant-response-rules.mdc ├── backend-stack-rules.mdc ├── coding-process-rules.mdc ├── coding-style-rules.mdc ├── editing-code-rules.mdc ├── frontend-stack-rules.mdc ├── general-assistant-rules.mdc ├── history-and-next-task-rules.mdc └── llm-integration-rules.mdc ├── nextjs-typescript-tailwind-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── ai-interaction-guidelines.mdc ├── general-typescript-guidelines.mdc ├── next-js-app-routing-guidelines.mdc ├── react-component-guidelines.mdc └── react-hook-guidelines.mdc ├── nextjs-vercel-supabase-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── devias-template-integration.mdc ├── general-ba-copilot-rules.mdc └── general-project-setup.mdc ├── nextjs-vercel-typescript-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── ai-sdk-rsc-integration-rules.mdc ├── general-project-rules.mdc ├── general-typescript-rules.mdc ├── image-optimization-rules.mdc ├── middleware-implementation-rules.mdc ├── next-js-server-component-rules.mdc ├── performance-optimization-rules.mdc ├── ui-component-styling-rules.mdc └── vercel-kv-database-rules.mdc ├── nextjs15-react19-vercelai-tailwind-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── directory-naming-conventions.mdc ├── general-typescript-and-react-rules.mdc ├── next-js-15-async-request-api-rules.mdc ├── next-js-15-component-architecture-rules.mdc └── next-js-15-state-management-rules.mdc ├── nodejs-mongodb-cursorrules-prompt-file-tutorial ├── .cursorrules ├── README.md ├── admin-interface-rules.mdc ├── api-endpoint-summarization.mdc ├── deployment-rule.mdc ├── entry-management-rules.mdc ├── frontend-react-rule.mdc ├── general-backend-node-js-express-rule.mdc ├── pick-management-rules.mdc ├── pools-user-flow-rules.mdc ├── request-state-transitions.mdc ├── results-and-standings-rules.mdc ├── scoring-and-ranking-rules.mdc ├── strategic-planning-with-pseudocode.mdc └── version-control-rule.mdc ├── nodejs-mongodb-jwt-express-react-cursorrules-promp ├── .cursorrules ├── README.md ├── admin-interface-rule.mdc ├── entry-creation-rule.mdc ├── entry-management-rules.mdc ├── frontend-tech-stack.mdc ├── general-coding-style.mdc ├── payment-tracking-rule.mdc ├── pick-management-rules.mdc ├── request-and-entry-tracking-rule.mdc ├── request-limit-rule.mdc ├── results-and-standings-rules.mdc ├── scoring-and-ranking-rules.mdc ├── state-transition-rule.mdc ├── strategic-planning-with-pseudocode.mdc ├── strict-user-requirements-adherence.mdc ├── submission-process-outline.mdc ├── tech-stack.mdc ├── user-flow-rules.mdc └── weekly-scoring-process-pseudocode.mdc ├── optimize-dry-solid-principles-cursorrules-prompt-f ├── .cursorrules ├── README.md ├── code-quality-and-best-practices.mdc ├── communication-and-problem-solving.mdc ├── general-python-rules.mdc ├── python-dependency-management.mdc └── response-formatting.mdc ├── optimize-rell-blockchain-code-cursorrules-prompt-f ├── .cursorrules ├── README.md ├── general-programming-expert-rules.mdc ├── python-dependency-management-rules.mdc └── rell-general-rules.mdc ├── pandas-scikit-learn-guide-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── data-analysis-initial-exploration.mdc ├── data-visualization-rules.mdc ├── data-visualization-with-matplotlib-and-seaborn.mdc ├── error-handling-and-data-validation-rules.mdc ├── general-data-analysis-and-jupyter-notebook-rules.mdc ├── initial-data-analysis-steps.mdc ├── jupyter-notebook-best-practices.mdc ├── large-data-with-dask.mdc ├── pandas-data-manipulation-rules.mdc ├── performance-optimization-rules.mdc └── python-data-analysis-general.mdc ├── plasticode-telegram-api-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── composer-dependency-management.mdc ├── php-general-rules.mdc ├── plasticode-rules.mdc └── telegram-bot-api-rules.mdc ├── py-fast-api ├── .cursorrules ├── README.md ├── database-interaction-rules.mdc ├── error-handling-rules.mdc ├── fastapi-application-rules.mdc ├── fastapi-route-specific-rules.mdc ├── performance-optimization-rules.mdc ├── pydantic-model-rules.mdc └── python-general-principles.mdc ├── pyqt6-eeg-processing-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── eeg-signal-processing-rules.mdc ├── pyqt6-ui-development-rules.mdc ├── python-general-rules.mdc ├── root-level-project-instructions.mdc └── workflow-and-integration-rules.mdc ├── python--typescript-guide-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── django-framework-rules.mdc ├── general-ai-behavior-rules.mdc ├── python-and-typescript-code-style.mdc ├── react-framework-rules.mdc └── tailwind-and-inertiajs-rules.mdc ├── python-312-fastapi-best-practices-cursorrules-prom ├── .cursorrules ├── README.md ├── alembic-database-migrations.mdc ├── fastapi-framework-rules.mdc ├── python-dependency-management-with-poetry.mdc ├── python-general-best-practices.mdc ├── unit-testing-requirement.mdc └── virtual-environment-usage.mdc ├── python-containerization-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── containerization-rules.mdc ├── database-algorithm-rules.mdc └── python-general-rules.mdc ├── python-cursorrules-prompt-file-best-practices ├── .cursorrules ├── README.md ├── ai-friendly-coding-practices.mdc ├── ci-cd-implementation-rule.mdc ├── configuration-management-rule.mdc ├── error-handling-and-logging-rule.mdc ├── modular-design-rule.mdc ├── project-structure-rule.mdc └── python-general-rules.mdc ├── python-developer-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── dependencies-management-rules.mdc ├── general-python-development.mdc ├── project-technology-stack-context.mdc ├── python-code-style.mdc └── python-version.mdc ├── python-django-best-practices-cursorrules-prompt-fi ├── .cursorrules ├── README.md ├── django-forms.mdc ├── django-middleware.mdc ├── django-models.mdc ├── django-rest-framework.mdc ├── django-settings.mdc ├── django-templates.mdc ├── django-urls.mdc ├── django-views.mdc ├── performance-optimization.mdc ├── python-django-general.mdc └── security.mdc ├── python-fastapi-best-practices-cursorrules-prompt-f ├── .cursorrules ├── README.md ├── fastapi-application-structure.mdc ├── fastapi-database-interaction.mdc ├── fastapi-documentation.mdc ├── fastapi-error-handling.mdc ├── fastapi-performance-optimization.mdc └── python-general-coding-style.mdc ├── python-fastapi-cursorrules-prompt-file ├── .cursorrules ├── fastapi-best-practices.mdc ├── fastapi-folder-structure.mdc ├── fastapi-main-application-file.mdc ├── pydantic-models.mdc └── python-general-coding-standards.mdc ├── python-fastapi-scalable-api-cursorrules-prompt-fil ├── .cursorrules ├── README.md ├── backend-performance-optimization.mdc ├── docker-configuration.mdc ├── fastapi-backend-conventions.mdc ├── frontend-performance-optimization.mdc ├── general-python-backend-rules.mdc ├── general-typescript-frontend-rules.mdc └── react-frontend-conventions.mdc ├── python-flask-json-guide-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── drawscape-factorio-usage.mdc ├── general-python-rules.mdc └── json-data-handling.mdc ├── python-github-setup-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── clarification-requirement.mdc ├── communication-tone.mdc ├── handle-incomplete-tasks.mdc ├── project-specific-build-tool.mdc ├── project-specific-testing-framework.mdc ├── project-verbosity-level.mdc ├── python-architecture.mdc ├── python-code-formatting.mdc ├── python-code-review.mdc ├── python-configuration-management.mdc ├── python-dependency-management.mdc ├── python-documentation.mdc ├── python-error-handling.mdc ├── python-general-coding-style.mdc ├── python-logging.mdc ├── python-monitoring.mdc ├── python-naming-conventions.mdc ├── python-security.mdc ├── python-testing.mdc └── python-version-control.mdc ├── python-llm-ml-workflow-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── asynchronous-programming-preference.mdc ├── code-formatting-with-ruff.mdc ├── comprehensive-type-annotations.mdc ├── comprehensive-unit-testing-with-pytest.mdc ├── data-pipeline-management-with-dvc.mdc ├── data-validation-with-pydantic.mdc ├── detailed-docstrings.mdc ├── experiment-configuration-with-hydra-yaml.mdc ├── fastapi-web-framework.mdc ├── google-style-docstrings.mdc ├── llm-prompt-engineering.mdc ├── logging-module-usage.mdc ├── poetry-rye-dependency-management.mdc ├── prioritize-python-3-10-features.mdc ├── python-general-role-definition.mdc ├── testing-framework-pytest.mdc └── type-hinting-rule.mdc ├── python-projects-guide-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── python-ai-friendly-coding-practices-rule.mdc ├── python-ci-cd-implementation-rule.mdc ├── python-code-style-consistency-rule.mdc ├── python-configuration-management-rule.mdc ├── python-dependency-management-rule.mdc ├── python-documentation-rule.mdc ├── python-error-handling-and-logging-rule.mdc ├── python-modular-design-rule.mdc ├── python-project-structure-rule.mdc └── python-testing-with-pytest-rule.mdc ├── pytorch-scikit-learn-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── chemistry-ml---data-handling-and-preprocessing.mdc ├── chemistry-ml---general-python.mdc ├── chemistry-ml---model-evaluation-and-interpretation.mdc ├── chemistry-ml---pytorch-models.mdc ├── chemistry-ml---rdkit-usage.mdc ├── chemistry-ml---reproducibility-and-version-control.mdc ├── chemistry-ml---scikit-learn-models.mdc ├── chemistry-ml---tauri-integration.mdc └── chemistry-ml---testing-and-validation.mdc ├── qwik-basic-cursorrules-prompt-file ├── .cursorrules ├── qwik-js---best-practices.mdc ├── qwik-js---error-handling-optimization.mdc ├── qwik-js---folder-structure.mdc ├── qwik-js---general-preferences.mdc ├── qwik-js---naming-conventions.mdc └── qwik-js---typescript-usage.mdc ├── qwik-tailwind-cursorrules-prompt-file ├── .cursorrules ├── qwik-and-tailwind-best-practices.mdc ├── qwik-city-routing.mdc ├── qwik-folder-structure.mdc ├── qwik-functional-components-preference.mdc ├── qwik-server-side-code.mdc ├── qwik-tailwind-naming-conventions.mdc ├── qwik-typescript-usage.mdc ├── tailwind-css-purging.mdc ├── tailwind-custom-styles.mdc ├── tailwind-dark-mode.mdc └── vite-plugins-for-qwik.mdc ├── react-chakra-ui-cursorrules-prompt-file ├── .cursorrules ├── chakra-ui---accessibility-features.mdc ├── chakra-ui---component-composition.mdc ├── chakra-ui---dark-mode-implementation.mdc ├── chakra-ui---performance-optimization.mdc ├── chakra-ui---responsive-design.mdc ├── chakra-ui---semantic-html-rendering.mdc ├── chakra-ui---theme-directory-rules.mdc ├── chakra-ui-best-practices.mdc ├── react-chakra-ui---folder-structure.mdc ├── react-chakra-ui---general-preferences.mdc └── react-chakra-ui---typescript-usage.mdc ├── react-components-creation-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── react-component-adaptation---post-generation-spa.mdc ├── react-component-adaptation---post-generation.mdc ├── react-component-creation---general.mdc ├── react-component-creation---spa-app.mdc └── react-component-prompt-example.mdc ├── react-graphql-apollo-client-cursorrules-prompt-file ├── .cursorrules ├── apollo-caching.mdc ├── apollo-custom-hooks.mdc ├── apollo-devtools.mdc ├── apollo-provider-setup.mdc ├── graphql-apollo-client-usage.mdc ├── graphql-error-boundaries.mdc ├── graphql-naming-conventions.mdc ├── graphql-typescript-integration.mdc └── react-functional-components-preference.mdc ├── react-mobx-cursorrules-prompt-file ├── .cursorrules ├── folder-structure.mdc ├── mobx-best-practices.mdc ├── mobx-dependency-injection.mdc ├── mobx-devtools.mdc ├── mobx-react-lite-usage.mdc ├── mobx-reaction-usage.mdc ├── mobx-store-implementation.mdc ├── mobx-strict-mode.mdc ├── observer-hoc-or-useobserver-hook.mdc ├── react-general-preferences.mdc └── typescript-with-mobx.mdc ├── react-native-expo-cursorrules-prompt-file ├── .cursorrules ├── react-native-expo---additional-instructions.mdc ├── react-native-expo---general-best-practices.mdc ├── react-native-expo---project-structure.mdc └── react-native-expo---root-files.mdc ├── react-native-expo-router-typescript-windows-cursorrules-prompt-file ├── .cursorrules ├── babel-configuration-for-nativewind.mdc ├── general-project-instructions.mdc ├── nativewind-and-tailwind-css-compatibility.mdc ├── react-native-expo-best-practices.mdc └── react-native-expo-folder-structure.mdc ├── react-nextjs-ui-development-cursorrules-prompt-fil ├── .cursorrules ├── README.md ├── general-javascript-react-next-js-rule.mdc ├── general-project-behavior-rule.mdc └── next-js-app-router-rule.mdc ├── react-query-cursorrules-prompt-file ├── .cursorrules ├── react-functional-components-preference.mdc ├── react-project-folder-structure.mdc ├── react-query-additional-instructions.mdc ├── react-query-general-best-practices.mdc └── react-query-hooks-directory-guidelines.mdc ├── react-redux-typescript-cursorrules-prompt-file ├── .cursorrules ├── react-functional-components.mdc ├── redux-async-actions.mdc ├── redux-devtools-debugging.mdc ├── redux-folder-structure.mdc ├── redux-toolkit-best-practices.mdc └── typescript-type-safety.mdc ├── react-styled-components-cursorrules-prompt-file ├── .cursorrules ├── react-functional-components-preference.mdc ├── styled-components---attrs-method.mdc ├── styled-components---conditional-styling-css-prop.mdc ├── styled-components---css-in-js.mdc ├── styled-components---documentation.mdc ├── styled-components---naming-conventions.mdc ├── styled-components---theming.mdc ├── styled-components---typescript-support.mdc └── styled-components-best-practices---general.mdc ├── react-typescript-nextjs-nodejs-cursorrules-prompt- ├── .cursorrules ├── README.md ├── general-project-rules.mdc ├── next-js-core-principles.mdc ├── next-js-server-action-rules.mdc ├── react-next-js-component-rules.mdc └── typescript-javascript-rules.mdc ├── react-typescript-symfony-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── full-stack-developer-persona.mdc ├── general-ai-programming-assistant.mdc ├── latest-language-versions-and-best-practices.mdc └── thoughtful-and-accurate-responses.mdc ├── solidity-foundry-cursorrules-prompt-file ├── .cursorrules └── README.md ├── solidity-hardhat-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── hardhat-development-workflow.mdc ├── solidity-best-practices.mdc ├── solidity-documentation.mdc ├── solidity-general-rules.mdc ├── solidity-performance-optimization.mdc └── solidity-testing-and-quality-assurance.mdc ├── solidity-react-blockchain-apps-cursorrules-prompt- ├── .cursorrules ├── README.md └── python-general-rules.mdc ├── solidjs-basic-cursorrules-prompt-file ├── .cursorrules ├── solidjs---complex-state-management.mdc ├── solidjs---conditional-and-list-rendering.mdc ├── solidjs---data-fetching.mdc ├── solidjs---derived-values-management.mdc ├── solidjs---error-boundaries.mdc ├── solidjs---functional-components-preference.mdc ├── solidjs---jsx-templates.mdc ├── solidjs---lazy-loading.mdc ├── solidjs---naming-conventions.mdc ├── solidjs---optimization-features.mdc ├── solidjs---reactive-state-management.mdc ├── solidjs---server-side-rendering.mdc ├── solidjs---side-effects-handling.mdc └── solidjs---solid-router.mdc ├── solidjs-tailwind-cursorrules-prompt-file ├── .cursorrules ├── solidjs-folder-structure.mdc ├── solidjs-functional-components.mdc ├── solidjs-tailwind-additional-instructions.mdc ├── solidjs-tailwind-css-best-practices.mdc ├── tailwind-css-configuration.mdc └── tailwind-css-styling.mdc ├── solidjs-typescript-cursorrules-prompt-file ├── .cursorrules ├── solidjs-functional-components-preference.mdc ├── solidjs-project-folder-structure.mdc ├── solidjs-typescript-best-practices.mdc ├── solidjs-typescript-coding-standards.mdc └── tsconfig-json-rules.mdc ├── svelte-5-vs-svelte-4-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── svelte-5-component-structure---snippets.mdc ├── svelte-5-general-rules.mdc └── svelte-5-reactivity-handling.mdc ├── sveltekit-restful-api-tailwind-css-cursorrules-pro ├── .cursorrules ├── README.md ├── ai-assistant-guidelines.mdc ├── ai-md-reference.mdc ├── best-practices-guidelines.mdc ├── code-quality-standards.mdc ├── continuous-improvement-focus.mdc ├── design-and-user-experience-guidelines.mdc ├── development-workflow-details.mdc ├── documentation-standards.mdc ├── elon-musk-s-algorithm-for-efficiency.mdc ├── file-management-rules.mdc ├── file-path-usage.mdc ├── tech-stack-definition.mdc ├── test-driven-development-tdd.mdc ├── testing-guidelines.mdc ├── truthfulness-and-clarity-for-ai.mdc └── windows-compatibility.mdc ├── sveltekit-tailwindcss-typescript-cursorrules-promp ├── .cursorrules ├── README.md ├── accessibility-guidelines.mdc ├── async-operations.mdc ├── code-quality-tools.mdc ├── documentation-standards.mdc ├── general-code-guidelines.mdc ├── imports-aliasing.mdc ├── performance-optimization.mdc ├── project-file-structure.mdc ├── project-standards---version-numbers.mdc ├── senior-frontend-developer-mindset.mdc ├── svelte-component-design.mdc ├── svelte-component-syntax.mdc ├── svelte-state-management.mdc ├── sveltekit-data-fetching.mdc ├── tailwind-css-styling.mdc ├── testing-practices.mdc └── typescript-typing.mdc ├── sveltekit-typescript-guide-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── class-based-state-management.mdc ├── component-development-rules.mdc ├── drizzle-orm-rules.mdc ├── general-sveltekit-typescript-rules.mdc └── supabase-integration-rules.mdc ├── swiftui-guidelines-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── swiftui-general-rules.mdc ├── swiftui-project-structure-rules.mdc └── swiftui-ui-design-rules.mdc ├── tailwind-css-nextjs-guide-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── biome-rules.mdc ├── cairo-contract-rules.mdc ├── development-process-rules.mdc ├── general-project-structure.mdc ├── general-rules.mdc ├── general-typescript-rules.mdc ├── next-js-page-rules.mdc ├── prompt-generation-rules.mdc ├── react-component-guidelines.mdc ├── starknet-react-rules.mdc └── tailwindcss-and-daisyui-rules.mdc ├── tailwind-react-firebase-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── accessibility-rules.mdc ├── code-organization-rules.mdc ├── firebase-rules.mdc ├── form-handling-rules.mdc ├── general-ui-ux-rules.mdc ├── mobile-first-design-rules.mdc └── pill-management-ai-feature.mdc ├── tailwind-shadcn-ui-integration-cursorrules-prompt- ├── .cursorrules ├── README.md ├── general-typescript-nextjs-rule.mdc └── nextjs-component-rule.mdc ├── tauri-svelte-typescript-guide-cursorrules-prompt-f ├── .cursorrules ├── README.md ├── backend-communication-rules.mdc ├── build-and-deployment-rules.mdc ├── general-project-conventions.mdc ├── tauri-native-api-integration.mdc ├── tauri-security-rules.mdc ├── tauri-svelte-typescript-general.mdc ├── tauri-svelte-ui-components.mdc └── testing-rules.mdc ├── temporal-python-cursorrules └── .cursorrules ├── typescript-axios-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── elite-software-engineer-and-product-manager.mdc └── general-python-rules.mdc ├── typescript-clasp-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── code-style-and-structure-rule.mdc ├── general-typescript-google-apps-script-rule.mdc ├── google-apps-script-specifics-rule.mdc ├── key-conventions-rule.mdc ├── naming-conventions-rule.mdc ├── performance-optimization-rule.mdc ├── syntax-and-formatting-rule.mdc └── typescript-specific-usage-rule.mdc ├── typescript-code-convention-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── expo-mobile-app-rule.mdc ├── general-project-rule.mdc ├── general-typescript-rule.mdc ├── next-js-app-router-rule.mdc ├── node-js-backend-rule.mdc ├── radix-ui-rule.mdc ├── react-component-rule.mdc ├── shadcn-ui-rule.mdc ├── tailwind-css-styling-rule.mdc └── trpc-api-rule.mdc ├── typescript-expo-jest-detox-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── api-documentation-rule.mdc ├── error-handling-and-validation-rule.mdc ├── expo-framework-rule.mdc ├── general-typescript-rule.mdc ├── internationalization-rule.mdc ├── mobile-ui-development-rule.mdc ├── naming-conventions-rule.mdc ├── react-native-core-rule.mdc ├── security-practices-rule.mdc └── testing-conventions-rule.mdc ├── typescript-llm-tech-stack-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── code-style.mdc ├── documentation.mdc ├── file-organization.mdc ├── general-typescript-project-rules.mdc ├── library-usage.mdc └── naming-conventions.mdc ├── typescript-nestjs-best-practices-cursorrules-promp ├── .cursorrules ├── README.md ├── nestjs-core-module-guidelines.mdc ├── nestjs-general-guidelines.mdc ├── nestjs-module-structure-guidelines.mdc ├── nestjs-shared-module-guidelines.mdc ├── nestjs-testing-guidelines.mdc └── typescript-general-guidelines.mdc ├── typescript-nextjs-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── code-style-and-structure-rules.mdc ├── general-typescript-node-js-next-js-rules.mdc ├── key-conventions-rule.mdc ├── naming-conventions-rule.mdc ├── next-js-data-fetching-rendering-routing.mdc ├── performance-optimization-rule.mdc ├── syntax-and-formatting-rule.mdc ├── typescript-usage-rule.mdc └── ui-and-styling-rule.mdc ├── typescript-nextjs-react-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── general-typescript-react-tailwind-rules.mdc ├── next-js-app-router-data-fetching-rendering-and-routing-rules.mdc ├── pre-configured-apis-rules.mdc └── vercel-ai-sdk-rules.mdc ├── typescript-nextjs-react-tailwind-supabase-cursorru ├── .cursorrules ├── README.md ├── agp-router-rules.mdc ├── next-js-general-rules.mdc ├── radix-ui-specific-rules.mdc ├── react-general-rules.mdc ├── shaden-ue-specific-rules.mdc ├── supabase-specific-rules.mdc ├── testing-with-nose-js-and-tastains.mdc └── typescript-general-rules.mdc ├── typescript-nextjs-supabase-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── database-querying-rules.mdc ├── general-typescript-node-js-next-js-project-rules.mdc ├── key-conventions-rules.mdc ├── next-js-app-router-rules.mdc ├── performance-optimization-rules.mdc ├── ui-styling-rules.mdc └── vercel-ai-sdk-integration-rules.mdc ├── typescript-nodejs-nextjs-ai-cursorrules-prompt-fil ├── .cursorrules ├── README.md ├── general-project-instructions.mdc └── python-dependency-management.mdc ├── typescript-nodejs-nextjs-app-cursorrules-prompt-fi ├── .cursorrules ├── README.md ├── component-structure-rules.mdc ├── directory-naming-convention.mdc ├── general-typescript-node-js-next-js-app-router-rules.mdc ├── key-conventions-rules.mdc ├── performance-optimization-rules.mdc ├── syntax-and-formatting-rules.mdc ├── typescript-specific-rules.mdc └── ui-and-styling-rules.mdc ├── typescript-nodejs-nextjs-react-ui-css-cursorrules- ├── .cursorrules ├── README.md ├── general-typescript-node-js-next-js-app-router-react-rule.mdc ├── next-js-app-router-optimization-rule.mdc ├── typescript-usage-rule.mdc └── ui-component-styling-rule.mdc ├── typescript-nodejs-react-vite-cursorrules-prompt-fi ├── .cursorrules ├── README.md ├── general-typescript-node-js-react-rule.mdc └── performance-optimization-rule.mdc ├── typescript-react-cursorrules-prompt-file ├── .cursorrules ├── typescript-react---additional-instructions.mdc ├── typescript-react---best-practices.mdc ├── typescript-react---folder-structure.mdc └── typescript-react---general-preferences.mdc ├── typescript-react-nextjs-cloudflare-cursorrules-pro ├── .cursorrules ├── README.md ├── cloudflare-developer-tools-rule.mdc ├── general-typescript-node-js-next-js-rule.mdc ├── key-conventions-rule.mdc ├── naming-conventions-rule.mdc ├── performance-optimization-rule.mdc ├── terminal-commands-rule.mdc └── ui-and-styling-rule.mdc ├── typescript-react-nextui-supabase-cursorrules-promp ├── .cursorrules ├── README.md ├── authentication-flow-rules.mdc ├── email-confirmation-rule.mdc ├── general-frontend-rule.mdc ├── react-ui-components-rule.mdc └── supabase-backend-rule.mdc ├── typescript-shadcn-ui-nextjs-cursorrules-prompt-fil ├── .cursorrules ├── README.md ├── component-file-structure.mdc ├── form-validation-with-zod.mdc ├── general-typescript-code-style.mdc ├── next-js-specific-conventions.mdc ├── performance-optimization-in-react-components.mdc ├── server-actions-error-modeling.mdc ├── syntax-and-formatting.mdc └── ui-and-styling-with-shadcn-ui-and-tailwind.mdc ├── typescript-vite-tailwind-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── code-style-and-structure-rule.mdc ├── general-typescript-rule.mdc ├── performance-optimization-rule.mdc ├── vite-build-optimization-rule.mdc ├── vue-js-component-rule.mdc └── vueuse-library-rule.mdc ├── typescript-vuejs-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── error-handling-and-validation.mdc ├── general-code-style-and-structure.mdc ├── naming-conventions.mdc ├── performance-optimization.mdc ├── syntax-and-formatting.mdc ├── typescript-usage.mdc ├── ui-and-styling.mdc └── vue-js-conventions.mdc ├── typescript-zod-tailwind-nextjs-cursorrules-prompt- ├── .cursorrules ├── README.md ├── error-handling-and-validation.mdc ├── general-typescript-coding-style.mdc ├── key-conventions.mdc ├── naming-conventions.mdc ├── next-js.mdc ├── performance-optimization.mdc ├── react-remix.mdc ├── react-server-components-rsc.mdc ├── syntax-and-formatting.mdc ├── typescript-specific-rules.mdc └── ui-and-styling.mdc ├── uikit-guidelines-cursorrules-prompt-file ├── .cursorrules └── README.md ├── unity-cursor-ai-c-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── general-c-unity-tower-defense-rules.mdc ├── refactoring-guidance.mdc ├── ringcon-controller-integration-rules.mdc └── turret-mechanics-rules.mdc ├── vue-3-nuxt-3-development-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── css-specific-rules.mdc ├── html-specific-rules.mdc └── vue-nuxt-general-rules.mdc ├── vue-3-nuxt-3-typescript-cursorrules-prompt-file ├── .cursorrules ├── README.md └── python-general-rules---service-1.mdc ├── vue3-composition-api-cursorrules-prompt-file ├── .cursorrules ├── vue-3-additional-instructions.mdc ├── vue-3-composition-api---composables.mdc ├── vue-3-composition-api---general.mdc ├── vue-3-project-structure.mdc └── vue-3-typescript-guidelines.mdc ├── web-app-optimization-cursorrules-prompt-file ├── .cursorrules ├── README.md ├── accessibility-rules.mdc ├── configuration-management.mdc ├── form-and-actions-in-sveltekit.mdc ├── paraglide-js-internationalization-i18n.mdc ├── performance-optimization-techniques.mdc ├── seo-and-meta-tags-in-sveltekit.mdc ├── svelte-and-sveltekit-general-rules.mdc ├── svelte-runes-usage.mdc ├── sveltekit-api-routes.mdc ├── sveltekit-project-structure.mdc ├── sveltekit-routing-and-pages.mdc ├── sveltekit-ssr-and-ssg.mdc ├── tailwind-css-and-shadcn-ui-conventions.mdc └── typescript-rules-for-svelte-components.mdc ├── webassembly-z80-cellular-automata-cursorrules-prom ├── .cursorrules ├── README.md ├── data-synchronization-rules.mdc ├── general-z80-cellular-automata-simulation-rules.mdc ├── main-simulation-loop-modification-rules.mdc ├── parameter-specific-logic-rules.mdc ├── region-grid-creation-rules.mdc ├── region-structure-definition-rules.mdc ├── region-visualization-system-rules.mdc ├── shader-code-update-rules.mdc ├── soup-cell-to-region-mapping-rules.mdc ├── user-interface-development-rules.mdc └── wasm-interface-enhancement-rules.mdc └── wordpress-php-guzzle-gutenberg-cursorrules-prompt- ├── .cursorrules ├── README.md ├── functional-programming-preference.mdc ├── javascript-typescript-coding-standards.mdc ├── php-coding-standards.mdc └── wordpress-plugin-general-rules.mdc /cursor-ai-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/7e4db830d65c8951463863dd25cc39b038d34e02/cursor-ai-logo.png -------------------------------------------------------------------------------- /rules/angular-novo-elements-cursorrules-prompt-file/angular-standalone-component-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for Angular components, tailored for standalone components without modules. 3 | globs: **/*.ts 4 | --- 5 | - This project uses Angular with standalone components, do not assume a module file is present. -------------------------------------------------------------------------------- /rules/angular-novo-elements-cursorrules-prompt-file/code-style-and-formatting-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces coding standards, consistent naming conventions, and discourages the use of deprecated features. 3 | globs: **/*.* 4 | --- 5 | - Follow the project's coding standards. 6 | - Use consistent naming conventions. 7 | - Avoid using deprecated functions or libraries. -------------------------------------------------------------------------------- /rules/angular-novo-elements-cursorrules-prompt-file/debugging-and-testing-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies practices for debugging and testing, including logging, unit tests, and ensuring all tests pass. 3 | globs: **/*.* 4 | --- 5 | - Include debug information in log files. 6 | - Write unit tests for new code. 7 | - Ensure all tests pass before merging. -------------------------------------------------------------------------------- /rules/angular-novo-elements-cursorrules-prompt-file/development-process-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Outlines guidelines for development steps, emphasizing incremental changes, thorough testing, and clear documentation. 3 | globs: **/*.* 4 | --- 5 | - Make changes in small, incremental steps. 6 | - Test changes thoroughly before committing. 7 | - Document changes clearly in commit messages. -------------------------------------------------------------------------------- /rules/angular-novo-elements-cursorrules-prompt-file/project-structure-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Maintains project structure, emphasizes meaningful names for files/directories, and avoids unnecessary clutter. 3 | globs: **/*.* 4 | --- 5 | - Maintain a clear and organized project structure. 6 | - Use meaningful names for files and directories. 7 | - Avoid clutter by removing unnecessary files. -------------------------------------------------------------------------------- /rules/angular-typescript-cursorrules-prompt-file/angular-template-hints.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules specific to Angular templates that ensures code quality standards. 3 | globs: **/*.component.html 4 | --- 5 | - Code should obey the rules defined in the .htmlhintrc, and .editorconfig files. 6 | - Be concise and minimize extraneous prose. -------------------------------------------------------------------------------- /rules/angular-typescript-cursorrules-prompt-file/refactoring-existing-code.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Instructions for refactoring code, focusing on readability, performance, and maintainability. 3 | globs: **/* 4 | --- 5 | - Focus on performance, readability, and maintainability when refactoring existing code. 6 | - When refactoring existing code, keep jsdoc comments intact. -------------------------------------------------------------------------------- /rules/ascii-simulation-game-cursorrules-prompt-file/data-tracking-and-charts-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the requirements for tracking game data and generating charts. This rule ensures that the game provides comprehensive information to the player through data visualization. 3 | globs: charts.py 4 | --- 5 | - There should be a chart page that tracks just about everything that can be tracked in the game. -------------------------------------------------------------------------------- /rules/aspnet-abp-cursorrules-prompt-file/README.md: -------------------------------------------------------------------------------- 1 | # ABP framework .cursorrules prompt file 2 | 3 | Author: Berkan Sasmaz 4 | 5 | Related Article: https://www.berkansasmaz.com/building-my-latest-project-with-asp-net-blazor-and-cursor-a-journey-to-abp 6 | -------------------------------------------------------------------------------- /rules/astro-typescript-cursorrules-prompt-file/custom-slash-commands.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enables custom slash commands, such as /commit, to generate conventional commit messages. 3 | globs: * 4 | --- 5 | - Enable the /commit command to generate a Git commit message using the conventional commits spec. -------------------------------------------------------------------------------- /rules/astro-typescript-cursorrules-prompt-file/general-coding-style.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Maintains a consistent coding style, ensuring that code starts with a file path comment and prioritizes modularity. 3 | globs: * 4 | --- 5 | - Code must start with path/filename as a one-line comment. 6 | - Comments should describe purpose, not effect. 7 | - Prioritize modularity, DRY principles, and performance. -------------------------------------------------------------------------------- /rules/astro-typescript-cursorrules-prompt-file/tailwindcss-styling-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Use TailwindCSS for all styling, keeping the utility-first approach in mind for astro components. 3 | globs: *.astro 4 | --- 5 | - Use TailwindCSS for all styling, keeping the utility-first approach in mind. -------------------------------------------------------------------------------- /rules/astro-typescript-cursorrules-prompt-file/typescript-development-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces strict TypeScript settings, ensuring type safety across the project. 3 | globs: *.ts 4 | --- 5 | - Enforce strict TypeScript settings, ensuring type safety across the project. -------------------------------------------------------------------------------- /rules/chrome-extension-dev-js-typescript-cursorrules-pro/browser-api-usage-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for effectively utilizing Chrome's browser APIs, including error handling and scheduling tasks. 3 | globs: **/*.{js,ts} 4 | --- 5 | - Utilize chrome.* APIs effectively (e.g., chrome.tabs, chrome.storage, chrome.runtime) 6 | - Implement proper error handling for all API calls 7 | - Use chrome.alarms for scheduling tasks instead of setInterval -------------------------------------------------------------------------------- /rules/chrome-extension-dev-js-typescript-cursorrules-pro/manifest-and-permissions-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for configuring the extension manifest and handling permissions securely. 3 | globs: **/manifest.json 4 | --- 5 | - Use the latest manifest version (v3) unless there's a specific need for v2 6 | - Follow the principle of least privilege for permissions 7 | - Implement optional permissions where possible -------------------------------------------------------------------------------- /rules/chrome-extension-dev-js-typescript-cursorrules-pro/security-and-privacy-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules to ensure the security and privacy of the Chrome extension and its users. 3 | globs: **/*.{js,ts,html} 4 | --- 5 | - Implement Content Security Policy (CSP) in manifest.json 6 | - Use HTTPS for all network requests 7 | - Sanitize user inputs and validate data from external sources 8 | - Implement proper error handling and logging -------------------------------------------------------------------------------- /rules/chrome-extension-dev-js-typescript-cursorrules-pro/ui-and-styling-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for creating user interfaces and applying consistent styling across the extension's UI elements. 3 | globs: **/popup.html, **/options.html, **/*.css 4 | --- 5 | - Create responsive designs for popup and options pages 6 | - Use CSS Grid or Flexbox for layouts 7 | - Implement consistent styling across all extension UI elements -------------------------------------------------------------------------------- /rules/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/naming-conventions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces specific naming conventions for React and TypeScript code to maintain consistency. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Follow standard TypeScript and JavaScript naming conventions for variables, functions, and components. 6 | - Component names should be PascalCase. 7 | - Variable and function names should be camelCase. -------------------------------------------------------------------------------- /rules/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/performance-optimization-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules to optimize performance of React and TypeScript components. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Optimize React component rendering using memoization techniques (e.g., React.memo). 6 | - Avoid unnecessary re-renders. 7 | - Lazy load components and images when possible. 8 | - Use efficient data structures and algorithms. -------------------------------------------------------------------------------- /rules/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/ui-and-styling-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for UI and styling, focusing on Tailwind CSS and Shaden UI best practices. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Utilize Tailwind CSS utility classes for styling components. 6 | - Follow Shaden UI component guidelines and best practices. 7 | - Ensure UI is responsive and accessible. -------------------------------------------------------------------------------- /rules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/metadata-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for defining metadata in Next.js 14 components for SEO optimization. 3 | globs: **/app/**/*.tsx 4 | --- 5 | - For metadata (in .tsx files): 6 | tsx 7 | import type { Metadata } from 'next' 8 | export const metadata: Metadata = { 9 | title: 'Page Title', 10 | description: 'Page description', 11 | } -------------------------------------------------------------------------------- /rules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/tailwind-css-styling-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for using Tailwind CSS for styling in Next.js 14 components. 3 | globs: **/*.tsx 4 | --- 5 | - Utilize Tailwind CSS classes exclusively for styling. Avoid inline styles. -------------------------------------------------------------------------------- /rules/cursorrules-cursor-ai-wordpress-draft-macos-prompt/application-password-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Explains how to generate and use an Application Password for WordPress authentication in PressThat. 3 | globs: /* 4 | --- 5 | - Users can generate an Application Password in their WordPress dashboard at the bottom of the "Users -> Profile" page. 6 | - This password is unique and can be easily revoked at any time. -------------------------------------------------------------------------------- /rules/cursorrules-cursor-ai-wordpress-draft-macos-prompt/initial-configuration-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Describes the initial configuration process for the PressThat application, including website details. 3 | globs: /* 4 | --- 5 | - After first installing the app, you need to configure it with your website details. This requires the user to provide their WordPress website URL, username, and a generated Application Password. -------------------------------------------------------------------------------- /rules/cursorrules-cursor-ai-wordpress-draft-macos-prompt/new-user-experience-nux-flow-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Details the new user experience flow, guiding users through the initial setup and configuration. 3 | globs: /* 4 | --- 5 | - Here's a quick flow for how the new user experience (NUX) will work: -------------------------------------------------------------------------------- /rules/cursorrules-cursor-ai-wordpress-draft-macos-prompt/project-overview-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General information about the PressThat project, a system tray app for WordPress draft posts. 3 | globs: /* 4 | --- 5 | - This project is called PressThat. 6 | - PressThat is a system tray app that connects to your WordPress website to create a view draft posts. -------------------------------------------------------------------------------- /rules/cursorrules-file-cursor-ai-python-fastapi-api/fastapi-components-and-validation.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the use of functional components and Pydantic models for input validation in FastAPI routes. 3 | globs: **/routers/*.py 4 | --- 5 | - Use functional components (plain functions) and Pydantic models for input validation and response schemas. 6 | - Use declarative route definitions with clear return type annotations. -------------------------------------------------------------------------------- /rules/cursorrules-file-cursor-ai-python-fastapi-api/fastapi-conditional-statements.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Outlines the preferred style for conditional statements in Python files. 3 | globs: **/*.py 4 | --- 5 | - Avoid unnecessary curly braces in conditional statements. 6 | - For single-line statements in conditionals, omit curly braces. 7 | - Use concise, one-line syntax for simple conditional statements (e.g., if condition: do_something()). -------------------------------------------------------------------------------- /rules/cursorrules-file-cursor-ai-python-fastapi-api/fastapi-dependencies.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Lists essential dependencies for FastAPI projects. 3 | globs: **/requirements.txt 4 | --- 5 | - FastAPI 6 | - Pydantic v2 7 | - Async database libraries like asyncpg or aiomysql 8 | - SQLAlchemy 2.0 (if using ORM features) -------------------------------------------------------------------------------- /rules/cursorrules-file-cursor-ai-python-fastapi-api/fastapi-dependency-injection.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Emphasizes the reliance on FastAPI’s dependency injection system for managing state and shared resources. 3 | globs: **/dependencies/*.py 4 | --- 5 | - Rely on FastAPI’s dependency injection system for managing state and shared resources. -------------------------------------------------------------------------------- /rules/cursorrules-file-cursor-ai-python-fastapi-api/fastapi-file-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the preferred file structure for FastAPI router modules. 3 | globs: **/routers/*.py 4 | --- 5 | - File structure: exported router, sub-routes, utilities, static content, types (models, schemas). -------------------------------------------------------------------------------- /rules/cursorrules-file-cursor-ai-python-fastapi-api/fastapi-function-definitions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the use of 'def' and 'async def' for function definitions within FastAPI routers. 3 | globs: **/routers/*.py 4 | --- 5 | - Use def for pure functions and async def for asynchronous operations. 6 | - Use type hints for all function signatures. Prefer Pydantic models over raw dictionaries for input validation. -------------------------------------------------------------------------------- /rules/cursorrules-file-cursor-ai-python-fastapi-api/fastapi-performance-metrics.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Prioritizes API performance metrics in FastAPI applications, focusing on response time, latency, and throughput. 3 | globs: **/*.py 4 | --- 5 | - Prioritize API performance metrics (response time, latency, throughput). -------------------------------------------------------------------------------- /rules/cursorrules-file-cursor-ai-python-fastapi-api/fastapi-startup-and-shutdown-events.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends minimizing the use of startup and shutdown events in favor of lifespan context managers. 3 | globs: **/main.py 4 | --- 5 | - Minimize @app.on_event("startup") and @app.on_event("shutdown"); prefer lifespan context managers for managing startup and shutdown events. -------------------------------------------------------------------------------- /rules/deno-integration-techniques-cursorrules-prompt-fil/documentation-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the guidelines to be followed when updating documentation. 3 | globs: /docs/**/*.* 4 | --- 5 | When updating documentation: 6 | - Follow the existing style and conventions. 7 | - Ensure all updates are accurate and reflect the current state of the code. 8 | - Provide clear and concise explanations for all concepts. -------------------------------------------------------------------------------- /rules/deno-integration-techniques-cursorrules-prompt-fil/general-development-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the general guidelines to be followed when making changes to automation scripts. 3 | globs: /**/*.ts 4 | --- 5 | When making changes: 6 | - Remember to thoroughly test all modifications to ensure they work correctly with the @findhow ecosystem before merging changes into the main branch. -------------------------------------------------------------------------------- /rules/dragonruby-best-practices-cursorrules-prompt-file/dragonruby-error-handling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines error handling and validation strategies within Ruby code in DragonRuby projects. 3 | globs: **/*.rb 4 | --- 5 | - Use exceptions for exceptional cases, not for control flow. 6 | - Implement proper error logging and user-friendly messages. -------------------------------------------------------------------------------- /rules/dragonruby-best-practices-cursorrules-prompt-file/dragonruby-naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces specific naming conventions for files, methods, variables, classes, and modules in DragonRuby projects. 3 | globs: **/*.rb 4 | --- 5 | - Use snake_case for file names, method names, and variables. 6 | - Use CamelCase for class and module names. 7 | - Follow DragonRuby naming conventions. -------------------------------------------------------------------------------- /rules/dragonruby-best-practices-cursorrules-prompt-file/dragonruby-syntax-and-formatting.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Dictates syntax and formatting guidelines for Ruby code within DragonRuby projects, adhering to the Ruby Style Guide. 3 | globs: **/*.rb 4 | --- 5 | - Follow the Ruby Style Guide (https://rubystyle.guide/) 6 | - Use Ruby's expressive syntax (e.g., unless, ||=, &.) 7 | - Prefer single quotes for strings unless interpolation is needed. -------------------------------------------------------------------------------- /rules/flutter-riverpod-cursorrules-prompt-file/tech-stack-configuration.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the tech stack to be used, including AI Model, Frontend framework (Flutter), State Management (Riverpod), and BaaS (Firebase). 3 | globs: * 4 | --- 5 | - Core Technologies: 6 | - AI Model: GPT-4 7 | - Frontend: 8 | - Flutter: ^3.22.0 9 | - State Management: 10 | - Riverpod: ^2.6.1 11 | - BaaS: 12 | - Firebase -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/check-x-md-content-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule reminds the AI to check the x.md file for the current file contents and implementations. 3 | globs: **/*.* 4 | --- 5 | - Remember to check the x.md file for the current file contents and implementations -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/file-by-file-changes-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule instructs the AI to make changes file by file, allowing the user to review each change individually. 3 | globs: **/*.* 4 | --- 5 | - Make changes file by file and give me a chance to spot mistakes -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-apologies-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule prevents the AI from using apologies in its responses. 3 | globs: **/*.* 4 | --- 5 | - Never use apologies -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-current-implementation-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule instructs the AI not to show or discuss the current implementation unless specifically requested. 3 | globs: **/*.* 4 | --- 5 | - Don't show or discuss the current implementation unless specifically requested -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-implementation-checks-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule prevents the AI from asking the user to verify implementations that are visible in the provided context. 3 | globs: **/*.* 4 | --- 5 | - Don't ask the user to verify implementations that are visible in the provided context -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-inventions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule restricts the AI from inventing changes beyond what is explicitly requested. 3 | globs: **/*.* 4 | --- 5 | - Don't invent changes other than what's explicitly requested -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-previous-x-md-consideration-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule instructs the AI not to consider any previous x.md files in its memory, ensuring it treats each run independently. 3 | globs: **/*.* 4 | --- 5 | - Do not consider any previous x.md files in your memory. Complain if the contents are the same as previous runs. -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-summaries-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule instructs the AI not to summarize changes made. 3 | globs: **/*.* 4 | --- 5 | - Don't summarize changes made -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-understanding-feedback-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule instructs the AI to avoid providing feedback about understanding in comments or documentation. 3 | globs: **/*.* 4 | --- 5 | - Avoid giving feedback about understanding in comments or documentation -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-unnecessary-confirmations-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule prevents the AI from asking for confirmation of information already provided in the context. 3 | globs: **/*.* 4 | --- 5 | - Don't ask for confirmation of information already provided in the context -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-unnecessary-updates-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule instructs the AI not to suggest updates or changes to files when there are no actual modifications needed. 3 | globs: **/*.* 4 | --- 5 | - Don't suggest updates or changes to files when there are no actual modifications needed -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/no-whitespace-suggestions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule prevents the AI from suggesting whitespace changes. 3 | globs: **/*.* 4 | --- 5 | - Don't suggest whitespace changes -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/preserve-existing-code-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule instructs the AI to preserve existing code and functionalities, avoiding unnecessary removal of code. 3 | globs: **/*.* 4 | --- 5 | - Don't remove unrelated code or functionalities. Pay attention to preserving existing structures. -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/provide-real-file-links-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule ensures the AI provides links to the real files instead of placeholder names like x.md. 3 | globs: **/*.* 4 | --- 5 | - Always provide links to the real files, not x.md -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/single-chunk-edits-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule requires the AI to provide all edits in a single chunk, avoiding multiple-step instructions for the same file. 3 | globs: **/*.* 4 | --- 5 | - Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file -------------------------------------------------------------------------------- /rules/github-code-quality-cursorrules-prompt-file/verify-information-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule ensures that the AI always verifies information before presenting it, avoiding assumptions and speculation. 3 | globs: **/*.* 4 | --- 5 | - Always verify information before presenting it. Do not make assumptions or speculate without clear evidence. -------------------------------------------------------------------------------- /rules/go-backend-scalability-cursorrules-prompt-file/protocol-buffer-definitions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rule for handling Protocol Buffer definition files in the project. 3 | globs: **/*.proto 4 | --- 5 | When working with `.proto` files: 6 | - Define clear and concise messages and services. 7 | - Use proper data types and naming conventions. 8 | - Ensure the `go_package` option is set correctly for Go code generation. -------------------------------------------------------------------------------- /rules/go-servemux-rest-api-cursorrules-prompt-file/go-api-error-handling-and-response-formatting.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule ensures proper error handling, status codes, and JSON response formatting in Go API development. 3 | globs: /*/**/*_api.go 4 | --- 5 | - Implement proper error handling, including custom error types when beneficial. 6 | - Use appropriate status codes and format JSON responses correctly. -------------------------------------------------------------------------------- /rules/go-servemux-rest-api-cursorrules-prompt-file/go-api-standard-library-usage.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule enforces the use of Go's standard library for API development, focusing on idiomatic and efficient code. 3 | globs: /*/**/*_api.go 4 | --- 5 | - Use the standard library's net/http package for API development. 6 | - Leverage the power and simplicity of Go's standard library to create efficient and idiomatic APIs. -------------------------------------------------------------------------------- /rules/go-servemux-rest-api-cursorrules-prompt-file/go-api-step-by-step-planning.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule focuses on the initial planning stage for Go API development, emphasizing detailed step-by-step thinking and pseudocode. 3 | globs: /*/**/*_api.go 4 | --- 5 | - First think step-by-step - describe your plan for the API structure, endpoints, and data flow in pseudocode, written out in great detail. 6 | - Confirm the plan, then write code! -------------------------------------------------------------------------------- /rules/graphical-apps-development-cursorrules-prompt-file/element-file-structure-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for maintaining a consistent file structure within individual element directories. 3 | globs: /element_templates/**/* 4 | --- 5 | - Each element should have a directory containing: 6 | - `__init__.py` 7 | - `_element.py` 8 | - `_model.py` 9 | - `css/` directory containing CSS files for styling. -------------------------------------------------------------------------------- /rules/graphical-apps-development-cursorrules-prompt-file/general-python-project-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General Python project rules for all Python files in the project. Enforces specific Python versions and class usage. 3 | globs: /**/*.*.py 4 | --- 5 | - Always use UV when installing dependencies. 6 | - Always use Python 3.12. 7 | - Always use classes instead of functions. 8 | - Docstrings should use a NumPy/SciPy style. -------------------------------------------------------------------------------- /rules/graphical-apps-development-cursorrules-prompt-file/langchain-integration-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules to apply to files relating to Langchain. Langchain is responsible for LLM related workflows. 3 | globs: /llm/**/*.* 4 | --- 5 | - Langchain is responsible for specific functions pertaining to incorporating LLM workflows. -------------------------------------------------------------------------------- /rules/graphical-apps-development-cursorrules-prompt-file/panel-view-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for Panel views, specifying that Panel should be used for the visualization layer. 3 | globs: /**/*_view.py 4 | --- 5 | - Use Panel to create the visualization layer and run the GUI. 6 | - Views should consist of Panel objects. 7 | - Panel objects can be styled with Python and CSS. -------------------------------------------------------------------------------- /rules/htmx-basic-cursorrules-prompt-file/htmx-folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces a specific folder structure within the 'src' directory for HTMX projects, promoting organization and maintainability of templates, static assets, and application logic. 3 | globs: src/**/*.* 4 | --- 5 | - Enforce the following folder structure: 6 | 7 | src/ 8 | templates/ 9 | static/ 10 | css/ 11 | js/ 12 | app.py -------------------------------------------------------------------------------- /rules/htmx-django-cursorrules-prompt-file/django-class-based-views-for-htmx.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Advises using Django's class-based views when constructing HTMX responses in view files. Class-based views provide a structured way to handle different HTTP methods. 3 | globs: **/views.py 4 | --- 5 | - Use Django's class-based views for HTMX responses -------------------------------------------------------------------------------- /rules/htmx-django-cursorrules-prompt-file/django-form-handling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies that Django forms should be used when handling form inputs in Python files named forms.py. This rule ensures consistent form handling practices within the project. 3 | globs: **/forms.py 4 | --- 5 | - Implement Django forms for form handling 6 | - Use Django's form validation for HTMX requests -------------------------------------------------------------------------------- /rules/htmx-django-cursorrules-prompt-file/django-middleware-for-request-response.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends utilizing Django's middleware for handling request and response processing. Middleware allows for global actions to be performed on requests and responses. 3 | globs: **/middleware.py 4 | --- 5 | - Utilize Django's middleware for request/response processing -------------------------------------------------------------------------------- /rules/htmx-django-cursorrules-prompt-file/django-orm-for-database-operations.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies that Django's ORM should be used for interacting with the database when defining models. This encourages a consistent approach to database operations across the project. 3 | globs: **/models.py 4 | --- 5 | - Implement Django ORM for database operations -------------------------------------------------------------------------------- /rules/htmx-django-cursorrules-prompt-file/django-static-files-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the use of Django's staticfiles app for managing static assets within the 'static' directory. This promotes consistent and efficient management of CSS, JavaScript, and other static files. 3 | globs: **/static/**/*.* 4 | --- 5 | - Use Django's staticfiles app for managing static assets -------------------------------------------------------------------------------- /rules/htmx-django-cursorrules-prompt-file/django-url-routing.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures Django's URL routing system is used in URL configuration files. This promotes consistent and maintainable URL management across Django projects. 3 | globs: **/urls.py 4 | --- 5 | - Utilize Django's URL routing system -------------------------------------------------------------------------------- /rules/htmx-django-cursorrules-prompt-file/general-django-project-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Encourages adhering to Django's best practices for project structure, especially in settings files. This promotes maintainability and standardization across Django projects. 3 | globs: **/settings.py 4 | --- 5 | - Follow Django's best practices for project structure -------------------------------------------------------------------------------- /rules/htmx-flask-cursorrules-prompt-file/flask-folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces a standard folder structure for Flask projects with Python files. 3 | globs: *.py 4 | --- 5 | - Define the following folder structure: 6 | 7 | app/ 8 | templates/ 9 | static/ 10 | css/ 11 | js/ 12 | models/ 13 | routes/ 14 | __init__.py 15 | config.py 16 | run.py -------------------------------------------------------------------------------- /rules/htmx-go-fiber-cursorrules-prompt-file/fiber-logging-and-project-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies best practices for logging, project structure, and environment variable usage specifically to the main application file. 3 | globs: cmd/main.go 4 | --- 5 | - Implement proper logging with Fiber's Logger middleware 6 | - Follow Fiber's best practices for project structure 7 | - Use environment variables for configuration -------------------------------------------------------------------------------- /rules/htmx-go-fiber-cursorrules-prompt-file/recommended-folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces specific folder structure at root level. 3 | globs: * 4 | --- 5 | The recommended folder structure is: 6 | 7 | cmd/ 8 | main.go 9 | internal/ 10 | handlers/ 11 | models/ 12 | templates/ 13 | static/ 14 | css/ 15 | js/ 16 | go.mod 17 | go.sum -------------------------------------------------------------------------------- /rules/java-springboot-jpa-cursorrules-prompt-file/apiresponse-class.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Structure of ApiResponse class. 3 | globs: **/src/main/java/com/example/ApiResponse.java 4 | --- 5 | -------------------------------------------------------------------------------- /rules/java-springboot-jpa-cursorrules-prompt-file/globalexceptionhandler-class.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Structure of GlobalExceptionHandler class. 3 | globs: **/src/main/java/com/example/GlobalExceptionHandler.java 4 | --- 5 | -------------------------------------------------------------------------------- /rules/javascript-astro-tailwind-css-cursorrules-prompt-f/accessibility.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for ensuring accessibility in Astro components, including semantic HTML and ARIA attributes. 3 | globs: src/**/*.* 4 | --- 5 | Accessibility 6 | 7 | - Ensure proper semantic HTML structure in Astro components. 8 | - Implement ARIA attributes where necessary. 9 | - Ensure keyboard navigation support for interactive elements. -------------------------------------------------------------------------------- /rules/javascript-astro-tailwind-css-cursorrules-prompt-f/astro-project-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforce the recommended Astro project structure. 3 | globs: astro.config.mjs 4 | --- 5 | Astro Project Structure 6 | 7 | - Use the recommended Astro project structure: 8 | - src/ 9 | - components/ 10 | - layouts/ 11 | - pages/ 12 | - styles/ 13 | - public/ 14 | - astro.config.mjs -------------------------------------------------------------------------------- /rules/javascript-astro-tailwind-css-cursorrules-prompt-f/astro-seo-and-meta-tags.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for SEO and meta tag implementation in Astro using the tag and canonical URLs. 3 | globs: src/**/*.* 4 | --- 5 | SEO and Meta Tags 6 | 7 | - Use Astro's tag for adding meta information. 8 | - Implement canonical URLs for proper SEO. 9 | - Use the component pattern for reusable SEO setups. -------------------------------------------------------------------------------- /rules/javascript-astro-tailwind-css-cursorrules-prompt-f/performance-metrics.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Performance metrics rules including Core Web Vitals, Lighthouse and WebPageTest. 3 | globs: src/**/*.* 4 | --- 5 | Performance Metrics 6 | 7 | - Prioritize Core Web Vitals (LCP, FID, CLS) in development. 8 | - Use Lighthouse and WebPageTest for performance auditing. 9 | - Implement performance budgets and monitoring. -------------------------------------------------------------------------------- /rules/javascript-astro-tailwind-css-cursorrules-prompt-f/tailwind-css-integration.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for integrating Tailwind CSS with Astro using @astrojs/tailwind. 3 | globs: astro.config.mjs 4 | --- 5 | Styling with Tailwind CSS 6 | 7 | - Integrate Tailwind CSS with Astro @astrojs/tailwind -------------------------------------------------------------------------------- /rules/javascript-astro-tailwind-css-cursorrules-prompt-f/testing.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for testing Astro projects, including unit tests and end-to-end testing. 3 | globs: tests/**/*.* 4 | --- 5 | Testing 6 | 7 | - Implement unit tests for utility functions and helpers. 8 | - Use end-to-end testing tools like Cypress for testing the built site. 9 | - Implement visual regression testing if applicable. -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/api-usage-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for proper API usage within Chrome extensions, ensuring compatibility and best practices. 3 | globs: **/*.js 4 | --- 5 | - API Usage -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/chrome-extension-manifest-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules related to the Chrome extension manifest file, ensuring proper structure and content. 3 | globs: manifest.json 4 | --- 5 | - Chrome Extension Manifest -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/development-process-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for the overall development process of Chrome extensions, including testing, debugging, and publishing. 3 | globs: **/*.{js,html,css,json} 4 | --- 5 | - Development Process -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/extension-architecture-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for structuring the architecture of a Chrome extension, focusing on modularity and maintainability. 3 | globs: **/*.{js,html} 4 | --- 5 | - Extension Architecture -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/internationalization-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for internationalizing Chrome extensions to support multiple languages. 3 | globs: **/*.{js,html} 4 | --- 5 | - Internationalization -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/javascript-code-style-and-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for JavaScript code style, naming conventions, and general usage within Chrome extensions. 3 | globs: **/*.js 4 | --- 5 | - Code Style and Structure 6 | - Naming Conventions 7 | - JavaScript Usage -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/performance-optimization-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for optimizing the performance of Chrome extensions, covering aspects like efficient code and resource usage. 3 | globs: **/*.js 4 | --- 5 | - Performance Optimization -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/publishing-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for publishing Chrome extensions to the Chrome Web Store, ensuring proper submission guidelines are followed. 3 | globs: manifest.json 4 | --- 5 | - Publishing -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/security-practices.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for secure coding practices within Chrome extensions to prevent vulnerabilities. 3 | globs: **/*.{js,html} 4 | --- 5 | - Security Practices -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/testing-and-debugging-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for testing and debugging Chrome extensions to ensure quality and stability. 3 | globs: **/*.js 4 | --- 5 | - Testing and Debugging -------------------------------------------------------------------------------- /rules/javascript-chrome-apis-cursorrules-prompt-file/ui-and-styling-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for developing the user interface and styling of Chrome extensions, ensuring a consistent look and feel. 3 | globs: **/*.{html,css} 4 | --- 5 | - User Interface and Styling -------------------------------------------------------------------------------- /rules/javascript-typescript-code-quality-cursorrules-pro/bug-handling-with-todo-comments.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the usage of TODO comments to outline problems or bugs encountered in existing code, regardless of file type. 3 | globs: **/*.* 4 | --- 5 | - TODO Comments: If you encounter a bug in existing code, or the instructions lead to suboptimal or buggy code, add comments starting with "TODO:" outlining the problems. -------------------------------------------------------------------------------- /rules/javascript-typescript-code-quality-cursorrules-pro/coding-guidelines---dry-and-functional-style.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies guidelines emphasizing DRY code and functional programming style across all files. 3 | globs: **/*.* 4 | --- 5 | - Correct and DRY Code: Focus on writing correct, best practice, DRY (Don't Repeat Yourself) code. 6 | - Functional and Immutable Style: Prefer a functional, immutable style unless it becomes much more verbose. -------------------------------------------------------------------------------- /rules/javascript-typescript-code-quality-cursorrules-pro/coding-guidelines---early-returns-and-conditionals.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies coding guidelines related to using early returns and conditional classes in all files. 3 | globs: **/*.* 4 | --- 5 | - Utilize Early Returns: Use early returns to avoid nested conditions and improve readability. 6 | - Conditional Classes: Prefer conditional classes over ternary operators for class attributes. -------------------------------------------------------------------------------- /rules/javascript-typescript-code-quality-cursorrules-pro/general-coding-principles.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies general coding principles like simplicity, readability, performance, maintainability, testability, and reusability to all files. 3 | globs: **/*.* 4 | --- 5 | - Focus on simplicity, readability, performance, maintainability, testability, and reusability. 6 | - Remember less code is better. 7 | - Lines of code = Debt. -------------------------------------------------------------------------------- /rules/javascript-typescript-code-quality-cursorrules-pro/javascript-documentation-with-jsdoc.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the use of JSDoc comments for documenting JavaScript files, especially with modern ES6 syntax. 3 | globs: **/*.js 4 | --- 5 | - JSDoc Comments: Use JSDoc comments for JavaScript and modern ES6 syntax. -------------------------------------------------------------------------------- /rules/javascript-typescript-code-quality-cursorrules-pro/minimal-code-changes-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the principle of making minimal code changes to avoid introducing bugs or technical debt in any file. 3 | globs: **/*.* 4 | --- 5 | - Only modify sections of the code related to the task at hand. 6 | - Avoid modifying unrelated pieces of code. 7 | - Accomplish goals with minimal code changes. -------------------------------------------------------------------------------- /rules/javascript-typescript-code-quality-cursorrules-pro/persona---senior-full-stack-developer.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the persona as a senior full-stack developer with extensive knowledge applicable to all files. 3 | globs: **/*.* 4 | --- 5 | - You are a senior full-stack developer. One of those rare 10x developers that has incredible knowledge. -------------------------------------------------------------------------------- /rules/javascript-typescript-code-quality-cursorrules-pro/typescript-skip-jsdoc.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: TypeScript should not use JSDoc comments as TypeScript's type system obviates the need. 3 | globs: **/*.ts 4 | --- 5 | - JSDoc Comments: Do not use JSDoc comments because this is TypeScript and types are defined. -------------------------------------------------------------------------------- /rules/kubernetes-mkdocs-documentation-cursorrules-prompt/metadata-and-seo-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Focuses on optimizing metadata and SEO to improve discoverability of the documentation. 3 | globs: **/*.md 4 | --- 5 | - Use relevant keywords in titles, headings, and descriptions. 6 | - Add appropriate metadata to all pages. 7 | - Optimize images and other media for search engines. 8 | - Use internal and external links to improve navigation and SEO. -------------------------------------------------------------------------------- /rules/laravel-php-83-cursorrules-prompt-file/laravel-package-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidance on package structure and file organization within the Laravel package. 3 | globs: */src/**/*.* 4 | --- 5 | - Outline the directory structure for the package 6 | - Describe the purpose of each main directory and key files 7 | - Explain how the package will be integrated into a Laravel application -------------------------------------------------------------------------------- /rules/laravel-php-83-cursorrules-prompt-file/laravel-package-testing-and-documentation.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Outlines the strategy for testing and documentation within the Laravel Package. 3 | globs: */tests/**/*.* 4 | --- 5 | - Provide an overview of the testing strategy (e.g., unit tests, feature tests) 6 | - Outline the documentation structure, including README.md, usage examples, and API references -------------------------------------------------------------------------------- /rules/laravel-php-83-cursorrules-prompt-file/readme-md-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for README.md file. 3 | globs: */README.md 4 | --- 5 | - The README.md file should include usage examples and API references -------------------------------------------------------------------------------- /rules/laravel-tall-stack-best-practices-cursorrules-prom/testing-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for writing unit and feature tests. 3 | globs: /tests/**/*.php 4 | --- 5 | - Write unit tests for Laravel controllers and models. 6 | - Implement feature tests for Livewire components using Laravel's testing tools. 7 | - Use Laravel Dusk for end-to-end testing when necessary. -------------------------------------------------------------------------------- /rules/linux-nvidia-cuda-python-cursorrules-prompt-file/continuous-improvement-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guides continuous improvement by seeking feedback, suggesting enhancements, and documenting changes. 3 | globs: **/* 4 | --- 5 | - Actively seek feedback on the app's functionality and user experience. 6 | - Suggest improvements that could make the app more efficient or user-friendly, ensuring any changes maintain the app's core principles. -------------------------------------------------------------------------------- /rules/linux-nvidia-cuda-python-cursorrules-prompt-file/development-principles-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Governs development principles for python code. 3 | globs: **/*.py 4 | --- 5 | - Ensure the quantization process is streamlined, efficient, and free of errors. 6 | - Handle edge cases, such as incompatible models or quantization failures, with clear and informative error messages, along with suggested resolutions. -------------------------------------------------------------------------------- /rules/next-type-llm/coding-process-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the coding process guidelines, applicable to all coding tasks. 3 | globs: * 4 | --- 5 | - Show concise step-by-step reasoning 6 | - Prioritize tasks/steps you’ll address in each response 7 | - Finish one file before the next 8 | - If you can’t finish code, add TODO: comments 9 | - If needed, interrupt yourself and ask to continue -------------------------------------------------------------------------------- /rules/next-type-llm/coding-style-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the general coding style guidelines, applicable to all project files. 3 | globs: * 4 | --- 5 | - Code must start with path/filename as a one-line comment 6 | - Comments MUST describe mainly purpose, but also effect when necessary 7 | - Prioritize modularity, DRY, performance, and security -------------------------------------------------------------------------------- /rules/next-type-llm/editing-code-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Prioritizes the method for editing code and defines verbosity levels. 3 | globs: * 4 | --- 5 | - Editing Code (prioritized choices): 6 | - Return completely edited file 7 | - Verbosity: I may use V=[0-3] to define code detail: 8 | - V=0 code golf 9 | - V=1 concise 10 | - V=2 simple 11 | - V=3 verbose, DRY with extracted functions -------------------------------------------------------------------------------- /rules/next-type-llm/general-project-assistant-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines holistic requirements for understanding the project and general assistant behavior, applicable project-wide. 3 | globs: * 4 | --- 5 | - Don’t apologize for errors: fix them 6 | - You may ask about stack assumptions if writing code -------------------------------------------------------------------------------- /rules/next-type-llm/llm-integration-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies rules for LLM integration, including language and API endpoint details, specific to LLM integration related files. 3 | globs: llm/**/*.* 4 | --- 5 | - Python wrapper for LLM interaction 6 | - API endpoint to connect frontend with Python backend -------------------------------------------------------------------------------- /rules/next-type-llm/technology-stack-backend-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the backend technology stack and coding style, applicable to backend directories. 3 | globs: backend/**/*.* 4 | --- 5 | - Framework: Next.js API Routes (for serverless functions) 6 | - Language: TypeScript (for API routes) -------------------------------------------------------------------------------- /rules/next-type-llm/technology-stack-frontend-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the frontend technology stack and coding style, applicable to frontend directories. 3 | globs: frontend/**/*.* 4 | --- 5 | - Framework: Next.js (React) 6 | - Language: TypeScript 7 | - UI Components: shadcn/ui (based on Radix UI primitives) 8 | - Styling: Tailwind CSS 9 | - Icons: Lucide React -------------------------------------------------------------------------------- /rules/nextjs-app-router-cursorrules-prompt-file/next-js-env-variables.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule advises using environment variables for configuration in a Next.js project. 3 | globs: **/*.{js,jsx,ts,tsx} 4 | --- 5 | - Use environment variables for configuration -------------------------------------------------------------------------------- /rules/nextjs-app-router-cursorrules-prompt-file/next-js-error-handling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule mandates proper error boundaries for effective error handling in Next.js applications. 3 | globs: **/*.{js,jsx,ts,tsx} 4 | --- 5 | - Implement proper error boundaries -------------------------------------------------------------------------------- /rules/nextjs-app-router-cursorrules-prompt-file/next-js-folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule defines the recommended folder structure for Next.js projects. 3 | globs: app/**/*.* 4 | --- 5 | - Adhere to the following folder structure: 6 | 7 | app/ 8 | layout.js 9 | page.js 10 | components/ 11 | lib/ 12 | styles/ 13 | public/ -------------------------------------------------------------------------------- /rules/nextjs-app-router-cursorrules-prompt-file/next-js-image-optimization.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule promotes the optimization of images using the Next.js Image component for better performance. 3 | globs: **/*.{js,jsx,ts,tsx} 4 | --- 5 | - Utilize Next.js Image component for optimized images -------------------------------------------------------------------------------- /rules/nextjs-app-router-cursorrules-prompt-file/next-js-naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule helps in following Next.js file naming conventions for special files within the 'app' directory. 3 | globs: app/**/*.* 4 | --- 5 | - Follow Next.js naming conventions for special files -------------------------------------------------------------------------------- /rules/nextjs-app-router-cursorrules-prompt-file/next-js-seo-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule ensures that SEO best practices are followed through proper metadata implementation in Next.js. 3 | globs: **/*.{js,jsx,ts,tsx} 4 | --- 5 | - Implement proper metadata for SEO -------------------------------------------------------------------------------- /rules/nextjs-app-router-cursorrules-prompt-file/next-js-styling-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule recommends using CSS Modules or Tailwind CSS for styling components in a Next.js project. 3 | globs: **/*.{js,jsx,ts,tsx,css,scss} 4 | --- 5 | - Use CSS Modules or Tailwind CSS for styling -------------------------------------------------------------------------------- /rules/nextjs-app-router-cursorrules-prompt-file/next-js-typescript-usage.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule encourages the usage of Typescript for type safety across a Next.js project. 3 | globs: **/*.{ts,tsx} 4 | --- 5 | - Use TypeScript for type safety -------------------------------------------------------------------------------- /rules/nextjs-material-ui-tailwind-css-cursorrules-prompt/aceternity-ui-configuration.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies that Aceternity UI dependencies should be considered during code generation or modification. 3 | globs: **/aceternityui/**/*.* 4 | --- 5 | - The project uses Aceternity UI. -------------------------------------------------------------------------------- /rules/nextjs-material-ui-tailwind-css-cursorrules-prompt/bcrypt-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines to use bcryptjs for hash functions. 3 | globs: **/*bcryptjs*.* 4 | --- 5 | - Use bcryptjs when you need hash functions. -------------------------------------------------------------------------------- /rules/nextjs-material-ui-tailwind-css-cursorrules-prompt/ckeditor-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines CKEditor is being used for text editing 3 | globs: **/ckeditor5/**/*.* 4 | --- 5 | - The project uses CKEditor for text editing -------------------------------------------------------------------------------- /rules/nextjs-material-ui-tailwind-css-cursorrules-prompt/framer-motion-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines framer motion is being used for animations 3 | globs: **/framer-motion/**/*.* 4 | --- 5 | - The project uses framer motion for animations -------------------------------------------------------------------------------- /rules/nextjs-material-ui-tailwind-css-cursorrules-prompt/material-ui-configuration.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies that Material UI dependencies should be considered during code generation or modification. 3 | globs: **/@mui/**/*.* 4 | --- 5 | - The project uses Material UI. -------------------------------------------------------------------------------- /rules/nextjs-material-ui-tailwind-css-cursorrules-prompt/prisma-orm-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines that prisma should be considered as ORM. 3 | globs: prisma/schema.prisma 4 | --- 5 | - Prisma is being used as an ORM. -------------------------------------------------------------------------------- /rules/nextjs-material-ui-tailwind-css-cursorrules-prompt/shadcn-ui-configuration.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies that Shadcn UI dependencies should be considered during code generation or modification. 3 | globs: **/shadcn-ui/**/*.* 4 | --- 5 | - The project uses Shadcn UI. -------------------------------------------------------------------------------- /rules/nextjs-material-ui-tailwind-css-cursorrules-prompt/tailwind-css-configuration.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies that Tailwind CSS is a core part of the project's styling and should be considered during code generation or modification. 3 | globs: tailwind.config.js 4 | --- 5 | - Tailwind CSS is used for styling. 6 | - Use tailwind-merge -------------------------------------------------------------------------------- /rules/nextjs-react-tailwind-cursorrules-prompt-file/placeholder-images.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rule to use placekitten.com for placeholder images in seed data. 3 | globs: **/seed.ts 4 | --- 5 | - While creating placeholder images as a part of your seed data, use https://placekitten.com/ -------------------------------------------------------------------------------- /rules/nextjs-react-tailwind-cursorrules-prompt-file/ui-and-styling-with-shadcn-ui-and-tailwind.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for UI development and styling using Shadcn UI and Tailwind CSS, emphasizing responsive design and a mobile-first approach. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use Shadcn UI, and Tailwind for components and styling. 6 | - Implement responsive design with Tailwind CSS; use a mobile-first approach. -------------------------------------------------------------------------------- /rules/nextjs-seo-dev-cursorrules-prompt-file/general-code-commenting.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures helpful comments are added to the code and that old, relevant comments are preserved. 3 | globs: **/*.* 4 | --- 5 | - Always add helpful comments to the code explaining what you are doing. 6 | - Never delete old comments, unless they are no longer relevant because the code has been rewritten or deleted. -------------------------------------------------------------------------------- /rules/nextjs-seo-dev-cursorrules-prompt-file/next-js-project-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Apply the specified rules for next js projects 3 | globs: next.config.js 4 | --- 5 | -------------------------------------------------------------------------------- /rules/nextjs-seo-dev-cursorrules-prompt-file/package-json-modification-protection.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Protects lines with the specific 'Do not touch this line Cursor' comment within package.json. 3 | globs: package.json 4 | --- 5 | - Whenever you see a line with the following comment, do not touch it, rewrite it, or delete it: "Do not touch this line Cursor" -------------------------------------------------------------------------------- /rules/nextjs-supabase-todo-app-cursorrules-prompt-file/.cursorrules: -------------------------------------------------------------------------------- 1 | Use the project specifications and guidelines to build the Todo app. 2 | 3 | Todo is a web app that allows you to manage your todos. 4 | 5 | Follow these rules: 6 | 7 | -------------------------------------------------------------------------------- /rules/nextjs-supabase-todo-app-cursorrules-prompt-file/todo-app-general-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General rules for the entire Todo web application project. Encompasses specifications and guidelines applicable across all files. 3 | globs: /**/*.* 4 | --- 5 | - Use the project specifications and guidelines to build the Todo app. 6 | - Todo is a web app that allows you to manage your todos. -------------------------------------------------------------------------------- /rules/nextjs-tailwind-typescript-apps-cursorrules-prompt/langchain-rag-application-development.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies specifically when developing RAG (Retrieval-Augmented Generation) applications using Langchain within Next.js projects. 3 | globs: **/*.{js,jsx,ts,tsx} 4 | --- 5 | You are familiar with create RAG applications using Langchain and are aware of its latest features. -------------------------------------------------------------------------------- /rules/nextjs-tailwind-typescript-apps-cursorrules-prompt/supabase-integration-in-next-js.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Focuses on providing expertise related to integrating Supabase with Next.js applications, applying to all JavaScript and TypeScript files. 3 | globs: **/*.{js,jsx,ts,tsx} 4 | --- 5 | You are familiar with latest features of supabase and how to integrate with Next.js application. -------------------------------------------------------------------------------- /rules/nextjs-typescript-app-cursorrules-prompt-file/.cursorrules: -------------------------------------------------------------------------------- 1 | This project, named Astral, the Block Explorer of Autonomys network, is built using Next.js and TypeScript. 2 | 3 | It integrates various libraries for state management, UI components, and data fetching. 4 | 5 | -------------------------------------------------------------------------------- /rules/nextjs-typescript-app-cursorrules-prompt-file/next-js-configuration-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules specifically for the Next.js configuration file. 3 | globs: /next.config.js 4 | --- 5 | - Ensure the Next.js configuration is optimized for performance. 6 | - Review and update the configuration regularly based on project needs. -------------------------------------------------------------------------------- /rules/nextjs-typescript-app-cursorrules-prompt-file/next-js-project-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General rules for the entire Next.js project, covering technology stack and core libraries. 3 | globs: /**/*.* 4 | --- 5 | - The project is named Astral, the Block Explorer of Autonomys network. 6 | - The project is built using Next.js and TypeScript. 7 | - The project integrates various libraries for state management, UI components, and data fetching. -------------------------------------------------------------------------------- /rules/nextjs-typescript-app-cursorrules-prompt-file/typescript-code-style-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules specific to TypeScript files in the project, ensuring consistent code style. 3 | globs: /**/*.ts 4 | --- 5 | - Use TypeScript for all new code. 6 | - Maintain consistent code style across all TypeScript files. -------------------------------------------------------------------------------- /rules/nextjs-typescript-cursorrules-prompt-file/backend-stack-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the backend technology stack including Next.js API Routes and TypeScript, applying to all backend files. 3 | globs: backend/**/*.* 4 | --- 5 | - Framework: Next.js API Routes (for serverless functions) 6 | - Language: TypeScript (for API routes) -------------------------------------------------------------------------------- /rules/nextjs-typescript-cursorrules-prompt-file/coding-style-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the coding style guidelines, including comments, modularity, DRY principle, performance, and security, applying to all files. 3 | globs: * 4 | --- 5 | - Code must start with path/filename as a one-line comment 6 | - Comments MUST describe mainly purpose, but also effect when necessary 7 | - Prioritize modularity, DRY, performance, and security -------------------------------------------------------------------------------- /rules/nextjs-typescript-cursorrules-prompt-file/editing-code-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Prioritizes returning completely edited files and defines verbosity levels for code detail, applying to all files. 3 | globs: * 4 | --- 5 | - Return completely edited file -------------------------------------------------------------------------------- /rules/nextjs-typescript-cursorrules-prompt-file/frontend-stack-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the frontend technology stack including React, TypeScript, Shadcn/UI, Tailwind CSS, and Lucide React, applying to all frontend files. 3 | globs: frontend/**/*.* 4 | --- 5 | - Framework: Next.js (React) 6 | - Language: TypeScript 7 | - UI Components: shadcn/ui (based on Radix UI primitives) 8 | - Styling: Tailwind CSS 9 | - Icons: Lucide React -------------------------------------------------------------------------------- /rules/nextjs-typescript-cursorrules-prompt-file/general-assistant-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines general assistant behavior for all files, including how to handle errors, ask questions, and understand project stack. 3 | globs: * 4 | --- 5 | - Holistic understanding of requirements & stack 6 | - Don’t apologize for errors: fix them 7 | - You may ask about stack assumptions if writing code -------------------------------------------------------------------------------- /rules/nextjs-typescript-cursorrules-prompt-file/llm-integration-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies rules for LLM integration, including the use of a Python wrapper and an API endpoint, applying to all LLM-related files. 3 | globs: llm/**/*.* 4 | --- 5 | - Python wrapper for LLM interaction 6 | - API endpoint to connect frontend with Python backend -------------------------------------------------------------------------------- /rules/nextjs-typescript-tailwind-cursorrules-prompt-file/ai-interaction-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Interaction with AI models. Used to minimize AI generated comments and focus on clear code 3 | globs: **/* 4 | --- 5 | - Minimize the use of AI generated comments, instead use clearly named variables and functions. -------------------------------------------------------------------------------- /rules/nextjs-typescript-tailwind-cursorrules-prompt-file/general-typescript-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces TypeScript best practices and coding standards for all TypeScript files in the project. 3 | globs: **/*.ts 4 | --- 5 | - When generating code, prioritize TypeScript and React best practices. 6 | - Follow the coding standards defined in the ESLint configuration. 7 | - Always validate user inputs and handle errors gracefully. -------------------------------------------------------------------------------- /rules/nextjs-typescript-tailwind-cursorrules-prompt-file/react-hook-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for custom React hooks, emphasizing state management best practices. 3 | globs: src/hooks/**/*.ts 4 | --- 5 | - When generating code, prioritize TypeScript and React best practices. 6 | - Always validate user inputs and handle errors gracefully. -------------------------------------------------------------------------------- /rules/nextjs-vercel-typescript-cursorrules-prompt-file/ai-sdk-rsc-integration-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guides the integration of `ai-sdk-rsc` into React Server Components for managing state and streaming generative content. 3 | globs: **/*.tsx 4 | --- 5 | - Integrate `ai-sdk-rsc` into your Next.js project. 6 | - Use `ai-sdk-rsc` hooks to manage state and stream generative content. -------------------------------------------------------------------------------- /rules/nextjs-vercel-typescript-cursorrules-prompt-file/image-optimization-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for optimizing images within React components to improve performance. 3 | globs: components/**/*.{js,jsx,ts,tsx} 4 | --- 5 | - Optimize images: use WebP format, include size data, implement lazy loading. -------------------------------------------------------------------------------- /rules/nextjs-vercel-typescript-cursorrules-prompt-file/middleware-implementation-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies specifically to the `middleware.ts` file to manage requests and sessions using Vercel's KV database. 3 | globs: middleware.ts 4 | --- 5 | - Use Vercel middleware to handle incoming requests. 6 | - Use middleware to parse user input and manage sessions with the KV database. 7 | - Use Vercel's KV database for managing stateful data. -------------------------------------------------------------------------------- /rules/nextjs-vercel-typescript-cursorrules-prompt-file/performance-optimization-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for optimizing performance by minimizing client-side operations and using server-side rendering. 3 | globs: **/*.{js,jsx,ts,tsx} 4 | --- 5 | - Optimize Web Vitals (LCP, CLS, FID). 6 | - Use dynamic loading for non-critical components. -------------------------------------------------------------------------------- /rules/nextjs-vercel-typescript-cursorrules-prompt-file/ui-component-styling-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces UI and styling conventions using Shadcn UI, Radix UI, and Tailwind CSS for all components. 3 | globs: components/**/*.{js,jsx,ts,tsx} 4 | --- 5 | - Use Shadcn UI, Radix UI, and Tailwind for components and styling. 6 | - Implement responsive design with Tailwind CSS; use a mobile-first approach. 7 | - Use declarative JSX. -------------------------------------------------------------------------------- /rules/nextjs15-react19-vercelai-tailwind-cursorrules-prompt-file/directory-naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces a consistent naming convention for directories across the project. 3 | globs: **/* 4 | --- 5 | - Use lowercase with dashes for directories (components/auth-wizard) -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/admin-interface-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for the Admin interface functionalities 3 | globs: /admin/**/*.* 4 | --- 5 | - Admin interface for managing and approving Requests -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/api-endpoint-summarization.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules that enforce to describe API endpoints before implementation 3 | globs: /api/**/*.* 4 | --- 5 | - Summarize the pick submission process and outline the API endpoint and business logic in pseudocode before coding. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/deployment-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies to deployment files, mentions the use of Docker for deployment (optional). 3 | globs: /deploy/**/*.* 4 | --- 5 | - Deployment: Docker (optional) -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/entry-management-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies to the entries related files. Details entry management related requirements. 3 | globs: /entries/**/*.* 4 | --- 5 | - Each user can have up to 3 Entries per Pool 6 | - Entries are numbered 1, 2, 3 7 | - Picks are made and tracked separately for each Entry -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/frontend-react-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies to all frontend files and uses React.js for the admin panel. 3 | globs: /frontend/**/*.* 4 | --- 5 | - Frontend: React.js (for admin panel, if required) -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/pick-management-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies to pick management files, describes how to manage picks. 3 | globs: /picks/**/*.* 4 | --- 5 | - Users make Picks for each Entry separately 6 | - Picks can be updated until deadline (game start or 1PM Sunday of the current week of the pick) -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/results-and-standings-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies to results related files, includes all the logic that involves presenting the result to the user. 3 | globs: /results/**/*.* 4 | --- 5 | - Users view Picks/scores for each Entry separately 6 | - Pool standings show all Entries (multiple per User possible) 7 | - Pool members can view all Picks after scoring -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/scoring-and-ranking-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies to scoring logic. Describes the scoring system and ranking process. 3 | globs: /scoring/**/*.* 4 | --- 5 | - Picks scored after games complete 6 | - Win: Entry moves to next week 7 | - Loss: Entry eliminated from Pool 8 | - Each Entry ranked separately in Pool standings -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/strategic-planning-with-pseudocode.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules that enforce to use pseudocode before implementation 3 | globs: /*.* 4 | --- 5 | - Begin each feature with detailed pseudocode. 6 | - Example: Provide pseudocode for the weekly scoring process, detailing steps from game result input to entry status updates. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-cursorrules-prompt-file-tutorial/version-control-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies to git related files, specifies to always use git for version control. 3 | globs: /*/.git/**/*.* 4 | --- 5 | - Version Control: Git -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/admin-interface-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the creation of an admin interface for managing and approving requests. 3 | globs: */admin-interface/**/*.* 4 | --- 5 | - Admin interface for managing and approving Requests. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/entry-creation-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures that an entry is created only after admin approval and payment completion. 3 | globs: */entry-creation/**/*.* 4 | --- 5 | - Create Entry only after admin approval and payment completion. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/entry-management-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Outlines the rules for entry management, including the number of entries per user, entry numbering, and pick management. 3 | globs: */entry-management/**/*.* 4 | --- 5 | - Each user can have up to 3 Entries per Pool. 6 | - Entries are numbered 1, 2, 3. 7 | - Picks are made and tracked separately for each Entry. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/frontend-tech-stack.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the technology for frontend development, React.js, and focuses on the admin panel if required. 3 | globs: */frontend/**/*.* 4 | --- 5 | - Use React.js for the admin panel (if required). -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/general-coding-style.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures secure, efficient code following RESTful API best practices with error handling and input validation. 3 | globs: **/*.* 4 | --- 5 | - Ensure secure, efficient code following RESTful API best practices. 6 | - Implement proper error handling and input validation. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/payment-tracking-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Implements payment status tracking in the Request model. 3 | globs: */payment-tracking/**/*.* 4 | --- 5 | - Implement payment status tracking in the Request model. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/pick-management-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines how users manage their picks for each entry, including update deadlines. 3 | globs: */pick-management/**/*.* 4 | --- 5 | - Users make Picks for each Entry separately. 6 | - Picks can be updated until the deadline (game start or 1PM Sunday of the current week of the pick). -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/request-and-entry-tracking-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies that requests and entries should be tracked separately and numbered 1, 2, 3. 3 | globs: */request-entry-tracking/**/*.* 4 | --- 5 | - Track Requests and Entries separately (numbered 1, 2, 3). -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/request-limit-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Limits the number of requests a user can make per pool to 3. 3 | globs: */request-handling/**/*.* 4 | --- 5 | - Limit Requests to 3 per User per Pool. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/results-and-standings-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines how results and standings are displayed to users, including pick visibility and pool standings. 3 | globs: */results-standings/**/*.* 4 | --- 5 | - Users view Picks/scores for each Entry separately. 6 | - Pool standings show all Entries (multiple per User possible). 7 | - Pool members can view all Picks after scoring. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/scoring-and-ranking-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies how picks are scored, how entries advance or are eliminated, and how entries are ranked. 3 | globs: */scoring-ranking/**/*.* 4 | --- 5 | - Picks scored after games complete. 6 | - Win: Entry moves to the next week. 7 | - Loss: Entry eliminated from Pool. 8 | - Each Entry ranked separately in Pool standings. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/state-transition-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Implements state transitions for requests, such as pending to approved to entry created. 3 | globs: */state-transitions/**/*.* 4 | --- 5 | - Implement state transitions (Request: pending -> approved -> Entry created). -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/strategic-planning-with-pseudocode.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Begins each feature with detailed pseudocode before implementing the actual code. 3 | globs: **/*.* 4 | --- 5 | - Begin each feature with detailed pseudocode. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/strict-user-requirements-adherence.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Strictly adheres to specified user flow and game rules, making sure to follow documented features. 3 | globs: **/*.* 4 | --- 5 | - Strictly adhere to specified user flow and game rules. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/submission-process-outline.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Summarize the pick submission process and outline the API endpoint and business logic in pseudocode before coding. 3 | globs: */pick-submission/**/*.* 4 | --- 5 | - Summarize the pick submission process and outline the API endpoint and business logic in pseudocode before coding. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/user-flow-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the user flow for browsing pools, submitting requests, completing payments, and admin approval. 3 | globs: */user-flow/**/*.* 4 | --- 5 | - Users browse available Pools. 6 | - Users submit up to 3 Requests per Pool. 7 | - Users complete payment for Requests. 8 | - Admin approves/rejects Requests. 9 | - Approved Requests become Entries. -------------------------------------------------------------------------------- /rules/nodejs-mongodb-jwt-express-react-cursorrules-promp/weekly-scoring-process-pseudocode.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Provide pseudocode for the weekly scoring process, detailing steps from game result input to entry status updates. 3 | globs: */weekly-scoring/**/*.* 4 | --- 5 | - Provide pseudocode for the weekly scoring process, detailing steps from game result input to entry status updates. -------------------------------------------------------------------------------- /rules/optimize-dry-solid-principles-cursorrules-prompt-f/code-quality-and-best-practices.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for code quality, best practices, relevant paradigms and semantic naming applying to all files. 3 | globs: /**/*.* 4 | --- 5 | - Adhere to code quality and best practices. 6 | - Apply relevant paradigms and principles. 7 | - Use semantic naming and abstractions. -------------------------------------------------------------------------------- /rules/optimize-dry-solid-principles-cursorrules-prompt-f/communication-and-problem-solving.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for communication, problem-solving and platform thinking applying to all files. 3 | globs: /**/*.* 4 | --- 5 | - Follow communication and problem-solving guidelines. 6 | - Consider platform thinking. 7 | - Handle uncertainty and limitations responsibly. -------------------------------------------------------------------------------- /rules/optimize-dry-solid-principles-cursorrules-prompt-f/python-dependency-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of UV for dependency installation and Python 3.12 within the service-1 directory. 3 | globs: /service-1/**/*.* 4 | --- 5 | - Always use UV when installing dependencies. 6 | - Always use Python 3.12. 7 | - Always use classes instead of functions. -------------------------------------------------------------------------------- /rules/optimize-dry-solid-principles-cursorrules-prompt-f/response-formatting.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for code quality, best practices, relevant paradigms and semantic naming applying to all files. 3 | globs: /**/*.* 4 | --- 5 | - Format responses according to guidelines. -------------------------------------------------------------------------------- /rules/optimize-rell-blockchain-code-cursorrules-prompt-f/python-dependency-management-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for Python dependency management and version control in the service-1 directory. 3 | globs: /service-1/**/*.* 4 | --- 5 | - Always use UV when installing depdendencies 6 | - Always use python 3.12 7 | - Always use classes instead of function -------------------------------------------------------------------------------- /rules/pandas-scikit-learn-guide-cursorrules-prompt-file/initial-data-analysis-steps.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Sets the convention to begin any analysis with data exploration and summary statistics, providing a consistent starting point. 3 | globs: **/*.py 4 | --- 5 | - Begin analysis with data exploration and summary statistics. -------------------------------------------------------------------------------- /rules/pandas-scikit-learn-guide-cursorrules-prompt-file/large-data-with-dask.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific optimization strategies for Python scripts working with larger-than-memory datasets via Dask. 3 | globs: **/dask_analysis/*.py 4 | --- 5 | - Consider using dask for larger-than-memory datasets. -------------------------------------------------------------------------------- /rules/plasticode-telegram-api-cursorrules-prompt-file/composer-dependency-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules pertaining to Composer dependency management, promoting best practices for declaring and updating dependencies. 3 | globs: **/composer.json 4 | --- 5 | - Use Composer for dependency management. 6 | - Ensure dependencies are properly declared in composer.json. 7 | - Update dependencies regularly. -------------------------------------------------------------------------------- /rules/plasticode-telegram-api-cursorrules-prompt-file/plasticode-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for files within the Plasticode framework directory, focusing on dependency management and Plasticode conventions. 3 | globs: **/plasticode/**/*.* 4 | --- 5 | - When working with Plasticode, follow Plasticode conventions. 6 | - Use Composer for dependency management. -------------------------------------------------------------------------------- /rules/plasticode-telegram-api-cursorrules-prompt-file/telegram-bot-api-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for files related to the Telegram Bot API integration, emphasizing API-specific best practices. 3 | globs: **/telegram_bot/**/*.* 4 | --- 5 | - When working with Telegram Bot API, use relevant API best practices. -------------------------------------------------------------------------------- /rules/py-fast-api/database-interaction-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for interacting with databases using async libraries within the db directory. 3 | globs: **/db/*.py 4 | --- 5 | - Async database libraries like asyncpg or aiomysql 6 | - SQLAlchemy 2.0 (if using ORM features) 7 | - Use dedicated async functions for database and external API operations. -------------------------------------------------------------------------------- /rules/py-fast-api/pydantic-model-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for creating Pydantic models, focusing on versioning and usage within the project. 3 | globs: **/models/*.py 4 | --- 5 | - Use type hints for all function signatures. Prefer Pydantic models over raw dictionaries for input validation. 6 | - Use Pydantic v2. 7 | - Use Pydantic's BaseModel for consistent input/output validation and response schemas. -------------------------------------------------------------------------------- /rules/pyqt6-eeg-processing-cursorrules-prompt-file/python-general-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General Python coding style and best practices for all Python files in the project. 3 | globs: /**/*.*.py 4 | --- 5 | - Write clean, well-documented, and easily maintainable code. 6 | - Implement comprehensive error handling and logging. 7 | - Utilize version control and follow collaborative development practices. -------------------------------------------------------------------------------- /rules/python--typescript-guide-cursorrules-prompt-file/django-framework-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific guidelines for Django projects, enforcing the use of the latest stable version and best practices. 3 | globs: **/django/**/*.* 4 | --- 5 | - You always use the latest stable version of Django, and you are familiar with the latest features and best practices. -------------------------------------------------------------------------------- /rules/python--typescript-guide-cursorrules-prompt-file/general-ai-behavior-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General rules for the AI's behavior, focusing on providing accurate and thoughtful answers. 3 | globs: **/*.* 4 | --- 5 | - You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning. -------------------------------------------------------------------------------- /rules/python--typescript-guide-cursorrules-prompt-file/react-framework-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for React projects, enforcing the use of the latest stable version and best practices. 3 | globs: **/react/**/*.* 4 | --- 5 | - You always use the latest stable version of React, and you are familiar with the latest features and best practices. -------------------------------------------------------------------------------- /rules/python--typescript-guide-cursorrules-prompt-file/tailwind-and-inertiajs-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for using Tailwind CSS and InertiaJS, including the use of Catalyst components. 3 | globs: **/*.jsx, **/*.tsx, **/*.html 4 | --- 5 | - You also use the latest version of Tailwind and InertiaJS. You use Catalyst components where possible and you avoid changing the Catalyst components themselves. -------------------------------------------------------------------------------- /rules/python-312-fastapi-best-practices-cursorrules-prom/alembic-database-migrations.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies that Alembic should be used for managing database migrations, ensuring controlled schema evolution. 3 | globs: **/migrations/**/*.* 4 | --- 5 | - Use alembic for database migrations. -------------------------------------------------------------------------------- /rules/python-312-fastapi-best-practices-cursorrules-prom/python-dependency-management-with-poetry.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures the project uses Poetry for managing dependencies, promoting consistent and reproducible builds. 3 | globs: **/pyproject.toml 4 | --- 5 | - Use poetry for dependency management. 6 | - Use UV when installing depdendencies. -------------------------------------------------------------------------------- /rules/python-312-fastapi-best-practices-cursorrules-prom/unit-testing-requirement.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the implementation of unit tests to guarantee code reliability and maintainability, especially within the 'tests' directory. 3 | globs: **/tests/**/*.* 4 | --- 5 | - Implement unit tests to ensure code reliability. -------------------------------------------------------------------------------- /rules/python-312-fastapi-best-practices-cursorrules-prom/virtual-environment-usage.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Mandates the use of virtual environments for isolating project dependencies and ensuring reproducibility. 3 | globs: **/* 4 | --- 5 | - Isolate project dependencies using virtual environments (e.g., `venv`). -------------------------------------------------------------------------------- /rules/python-containerization-cursorrules-prompt-file/.cursorrules: -------------------------------------------------------------------------------- 1 | You are an expert in Python, database algorithms, and containerization technologies. 2 | 3 | Follow Python's official documentation and PEPs for best practices in Python development. 4 | 5 | -------------------------------------------------------------------------------- /rules/python-containerization-cursorrules-prompt-file/containerization-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for creating and maintaining Dockerfiles. 3 | globs: **/Dockerfile 4 | --- 5 | - You are an expert in containerization technologies. 6 | - Follow best practices for creating efficient and secure Dockerfiles. -------------------------------------------------------------------------------- /rules/python-containerization-cursorrules-prompt-file/database-algorithm-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for writing and optimizing database algorithms. 3 | globs: **/database/**/*.* 4 | --- 5 | - You are an expert in database algorithms. 6 | - Optimize algorithms for performance and scalability. 7 | - Use appropriate data structures and indexing strategies. -------------------------------------------------------------------------------- /rules/python-containerization-cursorrules-prompt-file/python-general-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General Python development rules applicable to all Python files in the project. 3 | globs: **/*.py 4 | --- 5 | - Follow Python's official documentation and PEPs for best practices in Python development. 6 | - You are an expert in Python, database algorithms, and containerization technologies. -------------------------------------------------------------------------------- /rules/python-cursorrules-prompt-file-best-practices/ai-friendly-coding-practices.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Optimize code snippets and explanations for clarity and AI-assisted development. 3 | globs: * 4 | --- 5 | - Provide code snippets and explanations tailored to these principles, optimizing for clarity and AI-assisted development. -------------------------------------------------------------------------------- /rules/python-cursorrules-prompt-file-best-practices/ci-cd-implementation-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Uses GitHub Actions or GitLab CI for CI/CD implementation. 3 | globs: * 4 | --- 5 | - CI/CD implementation with GitHub Actions or GitLab CI. -------------------------------------------------------------------------------- /rules/python-cursorrules-prompt-file-best-practices/configuration-management-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Uses environment variables for managing configurations. 3 | globs: * 4 | --- 5 | - Configuration management using environment variables. -------------------------------------------------------------------------------- /rules/python-cursorrules-prompt-file-best-practices/error-handling-and-logging-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Implements robust error handling and logging, including context capture. 3 | globs: * 4 | --- 5 | - Robust error handling and logging, including context capture. -------------------------------------------------------------------------------- /rules/python-cursorrules-prompt-file-best-practices/modular-design-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Promotes modular design with distinct files for models, services, controllers, and utilities. 3 | globs: * 4 | --- 5 | - Modular design with distinct files for models, services, controllers, and utilities. -------------------------------------------------------------------------------- /rules/python-cursorrules-prompt-file-best-practices/project-structure-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces a clear project structure with separated directories for source code, tests, docs, and config. 3 | globs: * 4 | --- 5 | - Approach emphasizes a clear project structure with separate directories for source code, tests, docs, and config. -------------------------------------------------------------------------------- /rules/python-developer-cursorrules-prompt-file/.cursorrules: -------------------------------------------------------------------------------- 1 | You are an elite software developer with extensive expertise in Python, command-line tools, and file system operations. 2 | 3 | Your strong background in debugging complex issues and optimizing code performance makes you an invaluable asset to this project. 4 | 5 | This project utilizes the following technologies: 6 | 7 | -------------------------------------------------------------------------------- /rules/python-developer-cursorrules-prompt-file/dependencies-management-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Mandates the usage of UV when installing dependencies to ensure consistency and efficiency across all environments. 3 | globs: **/requirements.txt 4 | --- 5 | - Always use UV when installing dependencies -------------------------------------------------------------------------------- /rules/python-developer-cursorrules-prompt-file/project-technology-stack-context.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Provides a comprehensive overview of the technologies used in the project to help with understanding the environment. 3 | globs: **/* 4 | --- 5 | This project utilizes the following technologies: -------------------------------------------------------------------------------- /rules/python-developer-cursorrules-prompt-file/python-code-style.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures that all Python code is written using classes instead of functions. 3 | globs: **/*.py 4 | --- 5 | - Always use classes instead of function -------------------------------------------------------------------------------- /rules/python-developer-cursorrules-prompt-file/python-version.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies that the project must always utilize Python version 3.12 for all Python code. 3 | globs: **/*.py 4 | --- 5 | - Always use python 3.12 -------------------------------------------------------------------------------- /rules/python-django-best-practices-cursorrules-prompt-fi/django-middleware.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidance on using Django middleware for cross-cutting concerns like authentication, logging, and caching. 3 | globs: **/middleware.py 4 | --- 5 | - Use middleware judiciously to handle cross-cutting concerns like authentication, logging, and caching. 6 | - Use Django’s middleware for common tasks such as authentication, logging, and security. -------------------------------------------------------------------------------- /rules/python-django-best-practices-cursorrules-prompt-fi/django-models.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for Django models, emphasizing ORM usage, database interactions, and data validation. 3 | globs: **/models.py 4 | --- 5 | - Leverage Django’s ORM for database interactions; avoid raw SQL queries unless necessary for performance. 6 | - Keep business logic in models and forms; keep views light and focused on request handling. -------------------------------------------------------------------------------- /rules/python-django-best-practices-cursorrules-prompt-fi/django-rest-framework.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for Django REST Framework serializers, focusing on JSON responses. 3 | globs: **/serializers.py 4 | --- 5 | - Use Django templates for rendering HTML and DRF serializers for JSON responses. -------------------------------------------------------------------------------- /rules/python-django-best-practices-cursorrules-prompt-fi/django-settings.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Configurations for Django settings file with the list of dependencies and conventions. 3 | globs: **/settings.py 4 | --- 5 | - Django 6 | - Django REST Framework (for API development) 7 | - Celery (for background tasks) 8 | - Redis (for caching and task queues) 9 | - PostgreSQL or MySQL (preferred databases for production) -------------------------------------------------------------------------------- /rules/python-django-best-practices-cursorrules-prompt-fi/django-templates.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for Django templates, focusing on rendering HTML and following best practices. 3 | globs: **/templates/**/*.html 4 | --- 5 | - Use Django templates for rendering HTML and DRF serializers for JSON responses. -------------------------------------------------------------------------------- /rules/python-django-best-practices-cursorrules-prompt-fi/django-urls.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for Django URL configurations, focusing on clear and RESTful URL patterns. 3 | globs: **/urls.py 4 | --- 5 | - Use Django’s URL dispatcher (urls.py) to define clear and RESTful URL patterns. -------------------------------------------------------------------------------- /rules/python-django-best-practices-cursorrules-prompt-fi/security.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Apply security best practices across all files in the Django project. 3 | globs: **/*.* 4 | --- 5 | - Apply Django's security best practices (e.g., CSRF protection, SQL injection protection, XSS prevention). 6 | - Prioritize security and performance optimization in every stage of development. -------------------------------------------------------------------------------- /rules/python-fastapi-best-practices-cursorrules-prompt-f/fastapi-database-interaction.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the preferred asynchronous database libraries and interaction patterns for FastAPI applications. 3 | globs: **/db/**/*.py 4 | --- 5 | - Async database libraries like asyncpg or aiomysql. 6 | - SQLAlchemy 2.0 (if using ORM features). 7 | - Minimize blocking I/O operations; use asynchronous operations for all database calls. -------------------------------------------------------------------------------- /rules/python-fastapi-best-practices-cursorrules-prompt-f/fastapi-documentation.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Provides a reminder to refer to the FastAPI documentation for guidance on best practices for data models, path operations, and middleware. 3 | globs: **/routers/**/*.py 4 | --- 5 | - Refer to FastAPI documentation for Data Models, Path Operations, and Middleware for best practices. -------------------------------------------------------------------------------- /rules/python-fastapi-best-practices-cursorrules-prompt-f/fastapi-error-handling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines how errors should be handled within FastAPI applications using middleware. 3 | globs: **/middleware.py 4 | --- 5 | - Use middleware for handling unexpected errors, logging, and error monitoring. 6 | - Prioritize error handling and edge cases. 7 | - Use Pydantic's BaseModel for consistent input/output validation and response schemas. -------------------------------------------------------------------------------- /rules/python-fastapi-cursorrules-prompt-file/fastapi-folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the recommended folder structure for FastAPI projects to maintain organization and separation of concerns within the 'app' directory. 3 | globs: app/**/*.* 4 | --- 5 | - Follow this folder structure: 6 | 7 | app/ 8 | main.py 9 | models/ 10 | schemas/ 11 | routers/ 12 | dependencies/ 13 | services/ 14 | tests/ -------------------------------------------------------------------------------- /rules/python-fastapi-cursorrules-prompt-file/fastapi-main-application-file.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies guidelines for the main application file in FastAPI projects, focusing on application initialization and configuration. 3 | globs: app/main.py 4 | --- 5 | - Ensure proper application initialization with FastAPI() 6 | - Configure middleware and exception handlers 7 | - Define API routes using path operation decorators -------------------------------------------------------------------------------- /rules/python-fastapi-cursorrules-prompt-file/pydantic-models.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for defining Pydantic models within the models directory of a FastAPI project to ensure data validation and serialization. 3 | globs: app/models/*.py 4 | --- 5 | - Use Pydantic models for request and response schemas 6 | - Define data types using Pydantic fields 7 | - Implement validation logic using Pydantic validators -------------------------------------------------------------------------------- /rules/python-fastapi-scalable-api-cursorrules-prompt-fil/backend-performance-optimization.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Focuses on performance optimization techniques for the Python backend. 3 | globs: backend/src/**/*.py 4 | --- 5 | - Minimize blocking I/O operations using async functions. 6 | - Implement caching strategies for frequently accessed data using Redis or in-memory stores. 7 | - Use lazy loading techniques for large datasets and API responses. -------------------------------------------------------------------------------- /rules/python-fastapi-scalable-api-cursorrules-prompt-fil/docker-configuration.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules regarding docker usage in the project. 3 | globs: Dockerfile* 4 | --- 5 | - Use Docker for containerization and ensure easy deployment. 6 | - Use Docker and docker compose for orchestration in both development and production environments. Avoid using the obsolete `docker-compose` command. -------------------------------------------------------------------------------- /rules/python-fastapi-scalable-api-cursorrules-prompt-fil/frontend-performance-optimization.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Focuses on performance optimization techniques for the TypeScript frontend. 3 | globs: frontend/src/**/*.ts* 4 | --- 5 | - Favor server-side rendering and avoid heavy client-side rendering where possible. 6 | - Implement dynamic loading for non-critical components and optimize image loading using WebP format with lazy loading. -------------------------------------------------------------------------------- /rules/python-fastapi-scalable-api-cursorrules-prompt-fil/react-frontend-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines conventions and optimizations for React frontend development. 3 | globs: frontend/src/**/*.ts* 4 | --- 5 | - Optimize Web Vitals (LCP, CLS, FID). 6 | - Limit `use client` hooks to small, specific components for Web API access. -------------------------------------------------------------------------------- /rules/python-flask-json-guide-cursorrules-prompt-file/general-python-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines general Python version and dependency management rules for the project. 3 | globs: **/*.py 4 | --- 5 | - Always use UV when installing dependencies. 6 | - Always use Python 3.12. 7 | - Always use classes instead of functions when appropriate. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/clarification-requirement.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Sets the project for asking for clarification when tasks are unclear. 3 | globs: **/*.py 4 | --- 5 | - Ask for clarification on unclear tasks. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/communication-tone.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Establish a professional and concise style for all AI communication and output. 3 | globs: **/*.py 4 | --- 5 | - Maintain a professional and concise communication tone. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/handle-incomplete-tasks.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Configure the behaviour for the handler of incomplete tasks. 3 | globs: **/*.py 4 | --- 5 | - Provide partial solution and explain limitations. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/project-specific-build-tool.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the setuptools build tool for the project 3 | globs: **/setup.py 4 | --- 5 | - Use setuptools build tool. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/project-specific-testing-framework.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the pytest framework for all tests under the tests directory 3 | globs: **/tests/**/* 4 | --- 5 | - Use pytest testing framework. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/project-verbosity-level.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the desired verbosity level for the project's applications. 3 | globs: **/*.py 4 | --- 5 | - Set verbosity level to 2 (range: 0-3). -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-architecture.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines architectural patterns and principles for Python projects, including modular design, Single Responsibility, and DRY. 3 | globs: **/*.py 4 | --- 5 | - Use modular design. 6 | - Follow Single Responsibility Principle. 7 | - Follow DRY (Don't Repeat Yourself) Principle. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-code-formatting.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Sets code formatting rules for Python projects using Black and Pylint and following PEP 8. 3 | globs: **/*.py 4 | --- 5 | - Use Black for code formatting. 6 | - Use Pylint for linting. 7 | - Follow PEP 8 and project-specific rules. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-code-review.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies code review requirements for Python projects, including requiring reviews and using GitHub Pull Requests. 3 | globs: **/*.py 4 | --- 5 | - Require code reviews. 6 | - Use GitHub Pull Requests for code reviews. 7 | - Review for functionality, code quality, and security. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-configuration-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines configuration management practices for Python projects, including using .env files and python-dotenv. 3 | globs: **/*.py 4 | --- 5 | - Use .env files for configuration. 6 | - Use python-dotenv for environment variable management. 7 | - Manage secrets using environment variables. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-dependency-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines dependency management practices for Python projects, including using pip and Semantic Versioning. 3 | globs: **/requirements.txt 4 | --- 5 | - Use pip for package management. 6 | - Use Semantic Versioning for dependency versioning. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-documentation.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Sets documentation requirements for Python code, including requiring docstrings and following the Google Python Style Guide. 3 | globs: **/*.py 4 | --- 5 | - Require documentation for all code. 6 | - Use docstrings for documentation. 7 | - Follow the Google Python Style Guide for documentation. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-error-handling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines Python error handling preferences, including using try-except blocks and logging errors. 3 | globs: **/*.py 4 | --- 5 | - Prefer using try-except blocks for error handling. 6 | - Log errors appropriately. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-general-coding-style.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces general Python coding style guidelines including indentation, line length, and commenting style. 3 | globs: **/*.py 4 | --- 5 | - Use strict mode. 6 | - Indent using 4 spaces. 7 | - Limit line length to 120 characters. 8 | - Use # for single-line comments and ''' for multi-line comments. 9 | - Require comments in the code. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-logging.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Configures logging practices for Python applications, including using the Python logging module and defining log levels. 3 | globs: **/*.py 4 | --- 5 | - Use the Python logging module for logging. 6 | - Use log levels: debug, info, warn, error. 7 | - Set a log retention policy of 7 days. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-monitoring.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies monitoring practices for Python applications, including monitoring file processing time, classification accuracy, and error rate. 3 | globs: **/*.py 4 | --- 5 | - Monitor file processing time. 6 | - Monitor classification accuracy. 7 | - Monitor error rate. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies Python naming conventions for variables, functions, classes, interfaces, and files. 3 | globs: **/*.py 4 | --- 5 | - Use snake_case for variables. 6 | - Use snake_case for functions. 7 | - Use PascalCase for classes. 8 | - Use PascalCase for interfaces. 9 | - Use snake_case for files. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-security.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces security best practices for Python code, including requiring HTTPS, input sanitization, and using environment variables. 3 | globs: **/*.py 4 | --- 5 | - Require HTTPS for secure connections. 6 | - Sanitize all inputs. 7 | - Validate all inputs. 8 | - Use environment variables for sensitive configuration. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-testing.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies requirements for testing Python code, including requiring tests, coverage targets, and test types. 3 | globs: **/test_*.py 4 | --- 5 | - Require tests for all code. 6 | - Aim for 80% test coverage. 7 | - Include unit and integration tests. -------------------------------------------------------------------------------- /rules/python-github-setup-cursorrules-prompt-file/python-version-control.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Outlines version control practices for Python projects, including using Git, GitHub Flow, and Conventional Commits. 3 | globs: **/.git/**/* 4 | --- 5 | - Use Git for version control. 6 | - Follow the GitHub Flow branching strategy. 7 | - Use Conventional Commits for commit messages. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/asynchronous-programming-preference.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Favors the use of async and await for asynchronous programming in Python. 3 | globs: **/*.py 4 | --- 5 | - **Asynchronous Programming:** Prefer `async` and `await` -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/code-formatting-with-ruff.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces code formatting using Ruff, replacing Black, isort, and flake8 for consistent style. 3 | globs: **/*.py 4 | --- 5 | - **Code Formatting:** Ruff (replaces `black`, `isort`, `flake8`) -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/comprehensive-type-annotations.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Requires detailed type annotations for all Python functions, methods, and class members. 3 | globs: **/*.py 4 | --- 5 | - **Comprehensive Type Annotations:** All functions, methods, and class members must have type annotations, using the most specific types possible. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/comprehensive-unit-testing-with-pytest.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Aims for high test coverage using pytest, testing both common and edge cases. 3 | globs: **/tests/*.py 4 | --- 5 | - **Thorough Unit Testing:** Aim for high test coverage (90% or higher) using `pytest`. Test both common cases and edge cases. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/data-pipeline-management-with-dvc.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Employs scripts or tools like dvc to manage data preprocessing and ensure reproducibility. 3 | globs: **/data_pipeline/*.py 4 | --- 5 | - **Data Pipeline Management:** Employ scripts or tools like `dvc` to manage data preprocessing and ensure reproducibility. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/data-validation-with-pydantic.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Use Pydantic models for rigorous request and response data validation in FastAPI applications. 3 | globs: **/app/*.py 4 | --- 5 | - **Data Validation:** Use Pydantic models for rigorous request and response data validation. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/detailed-docstrings.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Requires detailed Google-style docstrings for all functions, methods, and classes. 3 | globs: **/*.py 4 | --- 5 | - **Detailed Docstrings:** All functions, methods, and classes must have Google-style docstrings, thoroughly explaining their purpose, parameters, return values, and any exceptions raised. Include usage examples where helpful. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/experiment-configuration-with-hydra-yaml.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends using Hydra or YAML for experiment configuration to ensure clarity and reproducibility. 3 | globs: **/configs/*.yaml 4 | --- 5 | - **Experiment Configuration:** Use `hydra` or `yaml` for clear and reproducible experiment configurations. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/fastapi-web-framework.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies FastAPI as the web framework for API development. 3 | globs: **/app/*.py 4 | --- 5 | - **Web Framework:** `fastapi` -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/google-style-docstrings.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Requires Google-style docstrings for all Python functions, methods, and classes. 3 | globs: **/*.py 4 | --- 5 | - **Documentation:** Google style docstring -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/llm-prompt-engineering.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Dedicates a module or files for managing Prompt templates with version control for LLM applications. 3 | globs: **/prompts/*.py 4 | --- 5 | - **LLM Prompt Engineering:** Dedicate a module or files for managing Prompt templates with version control. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/logging-module-usage.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Employs the logging module judiciously to log important events, warnings, and errors. 3 | globs: **/*.py 4 | --- 5 | - **Logging:** Employ the `logging` module judiciously to log important events, warnings, and errors. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/poetry-rye-dependency-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies Poetry or Rye for dependency management in Python projects. 3 | globs: **/pyproject.toml 4 | --- 5 | - **Dependency Management:** Poetry / Rye -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/prioritize-python-3-10-features.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Prioritizes the use of new features available in Python 3.10 and later versions. 3 | globs: **/*.py 4 | --- 5 | - **Prioritize new features in Python 3.10+**. -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/testing-framework-pytest.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies pytest as the testing framework for Python projects. 3 | globs: **/tests/*.py 4 | --- 5 | - **Testing Framework:** `pytest` -------------------------------------------------------------------------------- /rules/python-llm-ml-workflow-cursorrules-prompt-file/type-hinting-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Mandates strict type hinting using the typing module for all Python functions, methods, and class members. 3 | globs: **/*.py 4 | --- 5 | - **Type Hinting:** Strictly use the `typing` module. All functions, methods, and class members must have type annotations. -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-ai-friendly-coding-practices-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Promotes AI-friendly coding practices in Python files, including descriptive names, type hints, detailed comments, and rich error context. 3 | globs: /**/*.py 4 | --- 5 | - Use descriptive variable and function names 6 | - Use type hints 7 | - Provide detailed comments for complex logic 8 | - Provide rich error context for debugging -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-ci-cd-implementation-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Implements CI/CD pipelines using GitHub Actions or GitLab CI for automated building, testing, and deployment processes. 3 | globs: /.github/workflows/**/*.* 4 | --- 5 | - Implement CI/CD with GitHub Actions or GitLab CI. -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-code-style-consistency-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures code style consistency using Ruff for Python files to maintain a clean and uniform codebase. 3 | globs: /**/*.py 4 | --- 5 | - Enforce code style consistency using Ruff. -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-configuration-management-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Handles configuration management using environment variables within the 'config' directory for flexible and maintainable application settings. 3 | globs: /config/**/*.* 4 | --- 5 | - Manage configuration using environment variables. -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-dependency-management-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies dependency management using Rye and virtual environments for consistent and isolated project dependencies. 3 | globs: /**/pyproject.toml 4 | --- 5 | - Manage dependencies via https://github.com/astral-sh/rye and virtual environments. -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-documentation-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Promotes detailed documentation within Python files using docstrings and README files to enhance code understanding and maintainability. 3 | globs: /**/*.py 4 | --- 5 | - Provide detailed documentation using docstrings and README files. -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-error-handling-and-logging-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Emphasizes robust error handling and logging practices in Python files, including context capture for detailed debugging information. 3 | globs: /**/*.py 4 | --- 5 | - Implement robust error handling and logging, including context capture. -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-modular-design-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Promotes modular design within the 'src' directory by organizing code into distinct files for models, services, controllers, and utilities. 3 | globs: /src/**/*.* 4 | --- 5 | - Implement modular design with distinct files for models, services, controllers, and utilities. -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-project-structure-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces a clear project structure for all Python projects, advocating for separate directories for source code, tests, docs, and configuration. 3 | globs: /**/*.* 4 | --- 5 | - Ensure a clear project structure with separate directories for source code (src), tests (tests), documentation (docs), and configuration (config). -------------------------------------------------------------------------------- /rules/python-projects-guide-cursorrules-prompt-file/python-testing-with-pytest-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies comprehensive testing practices using pytest within the 'tests' directory to ensure code reliability and quality. 3 | globs: /tests/**/*.* 4 | --- 5 | - Use pytest for comprehensive testing. -------------------------------------------------------------------------------- /rules/qwik-basic-cursorrules-prompt-file/qwik-js---error-handling-optimization.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Focuses on error handling, routing with Qwik City, Qwik's optimization features, and lazy-loading for improved performance. 3 | globs: src/**/*.* 4 | --- 5 | - Implement proper error boundaries 6 | - Utilize Qwik City for routing when applicable 7 | - Use Qwik's built-in optimization features 8 | - Implement lazy-loading for improved performance -------------------------------------------------------------------------------- /rules/qwik-basic-cursorrules-prompt-file/qwik-js---folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Provides guidelines and the expected folder structure for a Qwik.js project. 3 | globs: * 4 | --- 5 | - Use the following folder structure: 6 | 7 | src/ 8 | components/ 9 | routes/ 10 | global.css 11 | root.tsx 12 | entry.ssr.tsx 13 | public/ 14 | vite.config.ts 15 | tsconfig.json -------------------------------------------------------------------------------- /rules/qwik-basic-cursorrules-prompt-file/qwik-js---general-preferences.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces general preferences for Qwik.js components in TypeScript files, promoting functional components. 3 | globs: **/*.tsx 4 | --- 5 | - Prefer functional components -------------------------------------------------------------------------------- /rules/qwik-basic-cursorrules-prompt-file/qwik-js---naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Adheres to Qwik's naming conventions, server-side code execution, and leveraging Vite plugins for optimized builds. 3 | globs: src/**/*.* 4 | --- 5 | - Follow Qwik's naming conventions and best practices 6 | - Use server$ for server-side code execution 7 | - Leverage Vite plugins for optimized builds -------------------------------------------------------------------------------- /rules/qwik-basic-cursorrules-prompt-file/qwik-js---typescript-usage.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures TypeScript is used for all .ts and .tsx files, enhancing type safety in Qwik.js projects. 3 | globs: **/*.ts, **/*.tsx 4 | --- 5 | - Use TypeScript for all .ts and .tsx files -------------------------------------------------------------------------------- /rules/qwik-tailwind-cursorrules-prompt-file/qwik-city-routing.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Encourages the use of Qwik City for routing within Qwik applications when applicable. 3 | globs: src/routes/**/*.{ts,tsx} 4 | --- 5 | - Utilize Qwik City for routing when applicable -------------------------------------------------------------------------------- /rules/qwik-tailwind-cursorrules-prompt-file/qwik-functional-components-preference.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of functional components within Qwik projects, promoting a consistent and modern coding style. 3 | globs: **/*.{ts,tsx} 4 | --- 5 | - Always prefer functional components in Qwik files. -------------------------------------------------------------------------------- /rules/qwik-tailwind-cursorrules-prompt-file/qwik-server-side-code.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Instructs using server$ for server-side code execution within Qwik components. 3 | globs: src/**/*.{ts,tsx} 4 | --- 5 | - Use server$ for server-side code execution -------------------------------------------------------------------------------- /rules/qwik-tailwind-cursorrules-prompt-file/qwik-tailwind-naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Stresses following both Qwik and Tailwind naming conventions for consistency and readability. 3 | globs: **/*.{ts,tsx,css} 4 | --- 5 | - Follow both Qwik and Tailwind naming conventions -------------------------------------------------------------------------------- /rules/qwik-tailwind-cursorrules-prompt-file/qwik-typescript-usage.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Mandates the use of TypeScript for all .ts and .tsx files in Qwik projects to ensure type safety and improved code maintainability. 3 | globs: **/*.{ts,tsx} 4 | --- 5 | - Use TypeScript for all .ts and .tsx files -------------------------------------------------------------------------------- /rules/qwik-tailwind-cursorrules-prompt-file/tailwind-css-purging.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Instructs the implementation of proper Tailwind CSS purging for production builds to reduce the final CSS bundle size. 3 | globs: tailwind.config.js 4 | --- 5 | - Implement proper Tailwind CSS purging for production builds -------------------------------------------------------------------------------- /rules/qwik-tailwind-cursorrules-prompt-file/tailwind-custom-styles.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Suggests using Tailwind's @layer directive for custom styles to maintain organization and prevent conflicts. 3 | globs: src/**/*.css 4 | --- 5 | - Use Tailwind's @layer directive for custom styles -------------------------------------------------------------------------------- /rules/qwik-tailwind-cursorrules-prompt-file/tailwind-dark-mode.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends implementing dark mode using Tailwind's dark variant to provide a user-friendly experience. 3 | globs: tailwind.config.js 4 | --- 5 | - Implement dark mode using Tailwind's dark variant -------------------------------------------------------------------------------- /rules/qwik-tailwind-cursorrules-prompt-file/vite-plugins-for-qwik.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Encourages leveraging Vite plugins for optimized Qwik builds to improve performance and efficiency. 3 | globs: vite.config.ts 4 | --- 5 | - Leverage Vite plugins for optimized builds -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/chakra-ui---accessibility-features.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Accessibility features for React components built with Chakra UI. 3 | globs: src/**/*.* 4 | --- 5 | - Utilize Chakra UI's built-in accessibility features -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/chakra-ui---component-composition.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensuring that React components are built composably using Chakra UI components. 3 | globs: src/components/**/*.* 4 | --- 5 | - Implement proper component composition using Chakra UI -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/chakra-ui---dark-mode-implementation.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Implement dark mode using Chakra UI's color mode when building React components. 3 | globs: src/**/*.* 4 | --- 5 | - Implement dark mode using Chakra UI's color mode -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/chakra-ui---performance-optimization.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Following Chakra UI best practices for optimizing React components for performance. 3 | globs: src/**/*.* 4 | --- 5 | - Follow Chakra UI best practices for performance optimization -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/chakra-ui---responsive-design.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Utilize Chakra UI's layout components for creating responsive designs in React applications. 3 | globs: src/**/*.* 4 | --- 5 | - Use Chakra UI's layout components for responsive design -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/chakra-ui---semantic-html-rendering.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Use the 'as' prop for semantic HTML rendering when working with Chakra UI components. 3 | globs: src/components/**/*.* 4 | --- 5 | - Use the 'as' prop for semantic HTML rendering -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/chakra-ui---theme-directory-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules specific to the theme directory for managing and customizing the Chakra UI theme. 3 | globs: src/theme/**/*.* 4 | --- 5 | - Create theme/index.js to export theme 6 | - Place theme foundations in theme/foundations/ 7 | - Place component-specific theme overrides in theme/components/ -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/react-chakra-ui---folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Maintain the defined folder structure for React and Chakra UI projects to ensure organized code. 3 | globs: src/**/*.* 4 | --- 5 | - Follow the following folder structure: 6 | 7 | src/ 8 | components/ 9 | pages/ 10 | theme/ 11 | index.js 12 | foundations/ 13 | components/ 14 | hooks/ 15 | utils/ -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/react-chakra-ui---general-preferences.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General preferences for React components using Chakra UI, including the use of functional components with hooks. 3 | globs: src/**/*.* 4 | --- 5 | - Prefer functional components with hooks -------------------------------------------------------------------------------- /rules/react-chakra-ui-cursorrules-prompt-file/react-chakra-ui---typescript-usage.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Utilize Typescript for type safety when using React components with Chakra UI. 3 | globs: src/**/*.tsx 4 | --- 5 | - Use TypeScript for type safety with Chakra UI components -------------------------------------------------------------------------------- /rules/react-graphql-apollo-client-cursorrules-prompt-file/apollo-caching.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Utilize Apollo Client's caching capabilities to improve performance. 3 | globs: src/**/*.js 4 | --- 5 | - Utilize Apollo Client's caching capabilities -------------------------------------------------------------------------------- /rules/react-graphql-apollo-client-cursorrules-prompt-file/apollo-custom-hooks.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Instructs to implement custom hooks for Apollo operations. 3 | globs: src/hooks/**/*.js 4 | --- 5 | - Implement custom hooks for Apollo operations -------------------------------------------------------------------------------- /rules/react-graphql-apollo-client-cursorrules-prompt-file/apollo-devtools.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Suggests the use of Apollo Client DevTools for debugging. 3 | globs: src/**/*.js 4 | --- 5 | - Use Apollo Client DevTools for debugging -------------------------------------------------------------------------------- /rules/react-graphql-apollo-client-cursorrules-prompt-file/apollo-provider-setup.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Requires the use of Apollo Provider at the root of the application. 3 | globs: src/App.jsx 4 | --- 5 | - Use Apollo Provider at the root of your app -------------------------------------------------------------------------------- /rules/react-graphql-apollo-client-cursorrules-prompt-file/graphql-error-boundaries.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Requires the implementation of proper error boundaries for GraphQL errors. 3 | globs: src/**/*.jsx 4 | --- 5 | - Implement proper error boundaries for GraphQL errors -------------------------------------------------------------------------------- /rules/react-graphql-apollo-client-cursorrules-prompt-file/graphql-naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Requires following naming conventions for queries, mutations, and fragments. 3 | globs: src/graphql/**/*.js 4 | --- 5 | - Follow naming conventions for queries, mutations, and fragments -------------------------------------------------------------------------------- /rules/react-graphql-apollo-client-cursorrules-prompt-file/graphql-typescript-integration.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of TypeScript for type safety with GraphQL operations. 3 | globs: src/graphql/**/*.ts 4 | --- 5 | - Use TypeScript for type safety with GraphQL operations -------------------------------------------------------------------------------- /rules/react-graphql-apollo-client-cursorrules-prompt-file/react-functional-components-preference.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of functional components with hooks in React components. 3 | globs: src/components/**/*.jsx 4 | --- 5 | - Always use functional components with hooks instead of class components. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforce specific directory structure for React and MobX Projects. 3 | globs: src/** 4 | --- 5 | - Maintain following folder structure: 6 | src/ 7 | components/ 8 | stores/ 9 | hooks/ 10 | pages/ 11 | utils/ -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/mobx-best-practices.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Adhere to MobX best practices for scalable state management. 3 | globs: src/**/*.ts 4 | --- 5 | - Follow MobX best practices for scalable state management. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/mobx-dependency-injection.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Implement proper dependency injection for stores. 3 | globs: src/**/*.ts 4 | --- 5 | - Implement proper dependency injection for stores. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/mobx-devtools.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Utilize MobX DevTools for debugging MobX applications. 3 | globs: src/**/*.ts 4 | --- 5 | - Utilize MobX DevTools for debugging. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/mobx-react-lite-usage.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforce best practices when using MobX with React Lite. 3 | globs: src/components/**/*.tsx 4 | --- 5 | - Use MobX-react-lite for optimal performance with functional components. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/mobx-reaction-usage.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Use reaction for side-effects based on observable changes. 3 | globs: src/**/*.ts 4 | --- 5 | - Use reaction for side-effects based on observable changes. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/mobx-store-implementation.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for implementing MobX stores for application state management. 3 | globs: src/stores/**/*.ts 4 | --- 5 | - Implement stores for managing application state. 6 | - Utilize computed values for derived state. 7 | - Use actions for modifying observable state. 8 | - Implement proper error handling in asynchronous actions. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/mobx-strict-mode.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforce strict mode for MobX for better debugging. 3 | globs: src/stores/**/*.ts 4 | --- 5 | - Implement strict mode for MobX for better debugging. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/observer-hoc-or-useobserver-hook.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Use Observer HOC or the useObserver hook for reactive components. 3 | globs: src/components/**/*.tsx 4 | --- 5 | - Use observer HOC or useObserver hook for reactive components. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/react-general-preferences.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General React preferences to prefer functional components with hooks. 3 | globs: src/**/*.tsx 4 | --- 5 | - Prefer functional components with hooks. -------------------------------------------------------------------------------- /rules/react-mobx-cursorrules-prompt-file/typescript-with-mobx.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Instructions on how to use Typescript with MobX. 3 | globs: src/**/*.ts 4 | --- 5 | - Use TypeScript for type safety with MobX. -------------------------------------------------------------------------------- /rules/react-native-expo-cursorrules-prompt-file/react-native-expo---root-files.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific configuration guidelines for the root level files App.js and app.json 3 | globs: App.js, app.json 4 | --- 5 | - Always keep App.js clean and delegate work to other components. 6 | - Always configure app.json based on the documentation -------------------------------------------------------------------------------- /rules/react-nextjs-ui-development-cursorrules-prompt-fil/next-js-app-router-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for the Next.js App Router directory, ensuring the AI avoids the Pages Router. 3 | globs: app/**/*.* 4 | --- 5 | - This project uses Next.js App Router never suggest using the pages router or provide code using the pages router. -------------------------------------------------------------------------------- /rules/react-query-cursorrules-prompt-file/react-functional-components-preference.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule enforces the use of functional components with hooks in React components within the src/components directory. 3 | globs: src/components/**/*.tsx 4 | --- 5 | - Always use functional components with hooks instead of class components. -------------------------------------------------------------------------------- /rules/react-query-cursorrules-prompt-file/react-project-folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule enforces the defined folder structure for a React project, improving organization and maintainability. 3 | globs: src/**/* 4 | --- 5 | - Enforce the following folder structure: 6 | - src/ 7 | - components/ 8 | - hooks/ 9 | - useQueries/ 10 | - useMutations/ 11 | - pages/ 12 | - utils/ 13 | - api/ -------------------------------------------------------------------------------- /rules/react-query-cursorrules-prompt-file/react-query-hooks-directory-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: This rule specifies the folder structure and purpose for placing React Query custom hooks in dedicated subdirectories. 3 | globs: src/hooks/**/*.ts 4 | --- 5 | - Place query hooks in src/hooks/useQueries/ 6 | - Place mutation hooks in src/hooks/useMutations/ -------------------------------------------------------------------------------- /rules/react-redux-typescript-cursorrules-prompt-file/react-functional-components.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of functional components with hooks in React components. 3 | globs: src/components/**/*.tsx 4 | --- 5 | - Always use React functional components with hooks. 6 | - Use React.FC for functional components with props. -------------------------------------------------------------------------------- /rules/react-redux-typescript-cursorrules-prompt-file/redux-async-actions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific instructions when handling Redux async actions 3 | globs: src/features/**/*.ts 4 | --- 5 | - Utilize createAsyncThunk for handling async actions. 6 | - Implement proper error handling in async operations. -------------------------------------------------------------------------------- /rules/react-redux-typescript-cursorrules-prompt-file/redux-devtools-debugging.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends Redux DevTools for debugging Redux applications. 3 | globs: src/store/store.ts 4 | --- 5 | - Use Redux DevTools for debugging. -------------------------------------------------------------------------------- /rules/react-redux-typescript-cursorrules-prompt-file/redux-folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces specific folder structure conventions within the Redux store directory. 3 | globs: src/store/**/* 4 | --- 5 | - Follow this folder structure: 6 | src/ 7 | components/ 8 | features/ 9 | store/ 10 | slices/ 11 | hooks.ts 12 | store.ts 13 | types/ 14 | utils/ -------------------------------------------------------------------------------- /rules/react-redux-typescript-cursorrules-prompt-file/typescript-type-safety.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures TypeScript is used for type safety throughout the project. 3 | globs: src/**/*.ts* 4 | --- 5 | - Use TypeScript for type safety. 6 | - Implement strict TypeScript checks. 7 | - Create reusable typed hooks for Redux operations, if applicable. -------------------------------------------------------------------------------- /rules/react-styled-components-cursorrules-prompt-file/react-functional-components-preference.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of functional components with hooks in React files. 3 | globs: src/**/*.jsx 4 | --- 5 | - Always use functional components with hooks in React development. -------------------------------------------------------------------------------- /rules/react-styled-components-cursorrules-prompt-file/styled-components---attrs-method.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends utilizing styled-components' attrs method for frequently used props. 3 | globs: src/components/styled/**/*.js 4 | --- 5 | - Utilize styled-components' attrs method for frequently used props. -------------------------------------------------------------------------------- /rules/react-styled-components-cursorrules-prompt-file/styled-components---conditional-styling-css-prop.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends using the css prop for conditional styling in Styled Components when appropriate. 3 | globs: src/components/styled/**/*.js 4 | --- 5 | - Use the css prop for conditional styling when appropriate. -------------------------------------------------------------------------------- /rules/react-styled-components-cursorrules-prompt-file/styled-components---css-in-js.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures all styling is done using CSS-in-JS with Styled Components. 3 | globs: src/**/*.js 4 | --- 5 | - Use CSS-in-JS for all styling needs. -------------------------------------------------------------------------------- /rules/react-styled-components-cursorrules-prompt-file/styled-components---documentation.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends following the styled-components documentation for best practices. 3 | globs: src/components/styled/**/*.js 4 | --- 5 | - Follow the styled-components documentation for best practices. -------------------------------------------------------------------------------- /rules/react-styled-components-cursorrules-prompt-file/styled-components---naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces proper naming conventions for Styled Components. 3 | globs: src/components/styled/**/*.js 4 | --- 5 | - Use proper naming conventions for styled components (e.g., StyledButton). -------------------------------------------------------------------------------- /rules/react-styled-components-cursorrules-prompt-file/styled-components---theming.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the use of a consistent theming system with Styled Components. 3 | globs: src/styles/theme.js 4 | --- 5 | - Implement a consistent theming system. -------------------------------------------------------------------------------- /rules/react-styled-components-cursorrules-prompt-file/styled-components---typescript-support.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures proper TypeScript support for styled-components. 3 | globs: src/components/styled/**/*.tsx 4 | --- 5 | - Implement proper TypeScript support for styled-components. -------------------------------------------------------------------------------- /rules/react-typescript-symfony-cursorrules-prompt-file/full-stack-developer-persona.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Configures the AI to act as a full-stack developer with expertise in React, TypeScript, PHP, Symfony, and Docker. 3 | globs: **/*.* 4 | --- 5 | You are a full stack developer with expert knowledge in React, TypeScript, PHP, Symfony and Docker. -------------------------------------------------------------------------------- /rules/react-typescript-symfony-cursorrules-prompt-file/general-ai-programming-assistant.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Sets the AI's persona as an expert programming assistant focused on producing clean and readable code across the project. 3 | globs: **/*.* 4 | --- 5 | You are an AI programming assistant that primarily focuses on producing clean and readable code. -------------------------------------------------------------------------------- /rules/react-typescript-symfony-cursorrules-prompt-file/latest-language-versions-and-best-practices.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ensures the AI uses the latest stable versions of programming languages and adheres to current best practices in all files. 3 | globs: **/*.* 4 | --- 5 | You always use the latest stable version of the programming language you are working with and you are familiar with the latest features and best practices. -------------------------------------------------------------------------------- /rules/react-typescript-symfony-cursorrules-prompt-file/thoughtful-and-accurate-responses.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Instructs the AI to provide accurate, factual, and thoughtful answers, emphasizing reasoning and accuracy in all contexts. 3 | globs: **/*.* 4 | --- 5 | You carefully provide accurate, factual thoughtfull answers and are a genius at reasoning. -------------------------------------------------------------------------------- /rules/solidity-hardhat-cursorrules-prompt-file/hardhat-development-workflow.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific to Hardhat projects, guiding on using Hardhat's features and implementing a CI/CD pipeline. 3 | globs: hardhat.config.js 4 | --- 5 | - Utilize Hardhat's testing and debugging features. 6 | - Implement a robust CI/CD pipeline for smart contract deployments. 7 | - Use static type checking and linting tools in pre-commit hooks. -------------------------------------------------------------------------------- /rules/solidity-hardhat-cursorrules-prompt-file/solidity-performance-optimization.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies to smart contracts, guiding on optimizing contracts for gas efficiency, considering storage layout and function optimization. 3 | globs: **/*.sol 4 | --- 5 | - Optimize contracts for gas efficiency, considering storage layout and function optimization. 6 | - Implement efficient indexing and querying strategies for off-chain data. -------------------------------------------------------------------------------- /rules/solidity-react-blockchain-apps-cursorrules-prompt-/.cursorrules: -------------------------------------------------------------------------------- 1 | I'm sorry, but it seems like you haven't provided the content of the corrupted file. Could you please provide the text that needs formatting? 2 | -------------------------------------------------------------------------------- /rules/solidity-react-blockchain-apps-cursorrules-prompt-/python-general-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General Python rules for the service-1 directory, ensuring consistent dependency management and Python version. 3 | globs: /service-1/**/*.* 4 | --- 5 | - Always use UV when installing dependencies 6 | - Always use python 3.12 7 | - Always use classes instead of functions -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---complex-state-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Suggests utilizing createStore for complex state management within SolidJS components. 3 | globs: src/components/**/*.jsx 4 | --- 5 | - Utilize createStore() for complex state management. -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---conditional-and-list-rendering.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Advises the implementation of Show and For components for conditional and list rendering in SolidJS. 3 | globs: src/components/**/*.jsx 4 | --- 5 | - Implement Show and For components for conditional and list rendering. -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---data-fetching.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends using createResource for data fetching within SolidJS components. 3 | globs: src/components/**/*.jsx 4 | --- 5 | - Use createResource() for data fetching. -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---derived-values-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guides the implementation of createMemo for managing derived values in SolidJS components. 3 | globs: src/components/**/*.jsx 4 | --- 5 | - Implement createMemo() for derived values. -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---error-boundaries.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends implementing proper error boundaries within the SolidJS project. 3 | globs: src/**/*.jsx 4 | --- 5 | - Implement proper error boundaries -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---functional-components-preference.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the preference for functional components in SolidJS projects within the components directory. 3 | globs: src/components/**/*.jsx 4 | --- 5 | - Always use functional components instead of class components. -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---jsx-templates.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the use of JSX for component templates throughout the SolidJS project. 3 | globs: src/**/*.jsx 4 | --- 5 | - Use JSX for component templates -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---lazy-loading.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Recommends implementing lazy-loading for improved performance within SolidJS. 3 | globs: src/**/*.jsx 4 | --- 5 | - Implement lazy-loading for improved performance -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Requires adherence to Solid.js naming conventions and best practices throughout the project. 3 | globs: src/**/*.jsx 4 | --- 5 | - Follow Solid.js naming conventions and best practices -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---optimization-features.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Suggests utilizing Solid's built-in optimization features for enhanced performance. 3 | globs: src/**/*.jsx 4 | --- 5 | - Use Solid's built-in optimization features -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---reactive-state-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Provides guidelines for managing reactive state using createSignal in SolidJS components. 3 | globs: src/components/**/*.jsx 4 | --- 5 | - Use createSignal() for reactive state. -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---server-side-rendering.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Suggests the implementation of server-side rendering (SSR) when needed in SolidJS projects. 3 | globs: src/**/*.jsx 4 | --- 5 | - Use server-side rendering (SSR) when needed -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---side-effects-handling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the use of createEffect for handling side effects in SolidJS components. 3 | globs: src/components/**/*.jsx 4 | --- 5 | - Utilize createEffect() for side effects. -------------------------------------------------------------------------------- /rules/solidjs-basic-cursorrules-prompt-file/solidjs---solid-router.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Encourages the use of Solid Router for routing when applicable in SolidJS projects. 3 | globs: src/**/*.jsx 4 | --- 5 | - Utilize Solid Router for routing when applicable -------------------------------------------------------------------------------- /rules/solidjs-tailwind-cursorrules-prompt-file/solidjs-folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Describes and enforces the preferred folder structure for SolidJS projects, including components, pages, and styles. 3 | globs: src/**/* 4 | --- 5 | - Use the following folder structure: 6 | src/ 7 | components/ 8 | pages/ 9 | styles/ 10 | App.jsx 11 | index.jsx -------------------------------------------------------------------------------- /rules/solidjs-tailwind-cursorrules-prompt-file/solidjs-functional-components.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of functional components in SolidJS projects. 3 | globs: **/*.jsx 4 | --- 5 | - Always use functional components in SolidJS. -------------------------------------------------------------------------------- /rules/solidjs-tailwind-cursorrules-prompt-file/tailwind-css-configuration.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Provides rules related to the configuration file for Tailwind CSS, focusing on customization. 3 | globs: tailwind.config.js 4 | --- 5 | - Use Tailwind's configuration file for customization. 6 | - Implement Tailwind CSS purging for production builds. 7 | - Use JIT (Just-In-Time) mode for faster development. -------------------------------------------------------------------------------- /rules/solidjs-typescript-cursorrules-prompt-file/solidjs-functional-components-preference.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of functional components in SolidJS TypeScript files. This rule promotes a consistent and modern approach to component design in SolidJS projects. 3 | globs: **/*.tsx 4 | --- 5 | - Prefer functional components in SolidJS development. -------------------------------------------------------------------------------- /rules/solidjs-typescript-cursorrules-prompt-file/tsconfig-json-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines general rules for tsconfig.json. It suggest using strict TypeScript checks 3 | globs: tsconfig.json 4 | --- 5 | - Implement strict TypeScript checks -------------------------------------------------------------------------------- /rules/svelte-5-vs-svelte-4-cursorrules-prompt-file/svelte-5-component-structure---snippets.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Instructions for using snippets in Svelte 5 components to create reusable markup. 3 | globs: **/*.svelte 4 | --- 5 | - Use snippets and render tags to create reusable chunks of markup inside components. 6 | - Snippets help reduce duplication and enhance maintainability. -------------------------------------------------------------------------------- /rules/svelte-5-vs-svelte-4-cursorrules-prompt-file/svelte-5-reactivity-handling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for handling reactivity and reactive statements in Svelte 5. 3 | globs: **/*.svelte 4 | --- 5 | - Prefer runes over reactive declarations ( `$:`) for reactivity, e.g. `bind:value` 6 | - Treat event handlers as properties, simplifying their use. -------------------------------------------------------------------------------- /rules/sveltekit-restful-api-tailwind-css-cursorrules-pro/testing-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines testing guidelines, including using Vitest for unit and integration tests and aiming for high test coverage. This rule emphasizes the importance of thorough testing for code quality. 3 | globs: **/* 4 | --- 5 | - |- 6 | 5. Testing: 7 | - Use Vitest for unit and integration tests 8 | - Aim for high test coverage (80% or higher) -------------------------------------------------------------------------------- /rules/sveltekit-tailwindcss-typescript-cursorrules-promp/project-standards---version-numbers.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the required version numbers for Node.js, SvelteKit, TypeScript, Vite, and PNPM within the project. This rule ensures consistency across the project dependencies. 3 | globs: **/package.json 4 | --- 5 | - Node.js: 18.x or later 6 | - SvelteKit: 2.x (Svelte 4.x) 7 | - TypeScript: 5.x 8 | - Vite: 5.x 9 | - PNPM: 8.x or later -------------------------------------------------------------------------------- /rules/sveltekit-typescript-guide-cursorrules-prompt-file/drizzle-orm-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for using Drizzle ORM within the `src/lib/db` directory. Ensures consistent data modeling and database interactions. 3 | globs: src/lib/db/**/*.ts 4 | --- 5 | - Follow best practices for Drizzle ORM usage, including schema definition and query building. 6 | - Ensure proper data validation and error handling when interacting with the database. -------------------------------------------------------------------------------- /rules/sveltekit-typescript-guide-cursorrules-prompt-file/supabase-integration-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for interacting with Supabase in the `src/lib/supabase` directory. This ensures consistent and correct Supabase integration. 3 | globs: src/lib/supabase/**/*.ts 4 | --- 5 | - Follow best practices for Supabase integration, including data fetching and authentication. 6 | - Use TypeScript for type safety when interacting with Supabase. -------------------------------------------------------------------------------- /rules/tailwind-css-nextjs-guide-cursorrules-prompt-file/general-project-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules to organize Project Structure. 3 | globs: **/* 4 | --- 5 | - Organize project structure: components, pages, hooks, utils, styles, contracts, services 6 | - Separate concerns: presentational components, business logic, side effects -------------------------------------------------------------------------------- /rules/tailwind-css-nextjs-guide-cursorrules-prompt-file/general-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General Rules to set up Typescript. 3 | globs: tsconfig.json 4 | --- 5 | - Enable strict TypeScript (strict: true in tsconfig.json) 6 | - Avoid 'any', prefer 'unknown' with runtime checks 7 | - Explicitly type function inputs and outputs 8 | - Use advanced TypeScript features (type guards, mapped types, conditional types) -------------------------------------------------------------------------------- /rules/tailwind-react-firebase-cursorrules-prompt-file/accessibility-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for ensuring accessibility in React components using tailwind. 3 | globs: **/*.{tsx,jsx} 4 | --- 5 | - Ensure proper color contrast ratios using Tailwind's text-* and bg-* classes. 6 | - Use semantic HTML elements and ARIA attributes where necessary. 7 | - Implement keyboard navigation support. -------------------------------------------------------------------------------- /rules/tailwind-react-firebase-cursorrules-prompt-file/code-organization-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for organizing code structure and utilizing custom hooks. 3 | globs: **/src/**/*.* 4 | --- 5 | - Follow a consistent folder structure (e.g., components, hooks, pages, services). 6 | - Use custom hooks to encapsulate and reuse logic. -------------------------------------------------------------------------------- /rules/tailwind-react-firebase-cursorrules-prompt-file/firebase-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Best practices for interacting with Firebase services, including security and optimization. 3 | globs: **/firebase/**/*.js 4 | --- 5 | - Implement proper security rules in Firebase. 6 | - Use Firebase SDK's offline persistence for better performance and offline support. 7 | - Optimize queries to minimize read/write operations. -------------------------------------------------------------------------------- /rules/tailwind-react-firebase-cursorrules-prompt-file/form-handling-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for handling forms in React components. 3 | globs: **/components/forms/**/*.tsx 4 | --- 5 | - Use libraries like Formik or react-hook-form for efficient form management. 6 | - Implement proper form validation with clear error messages. -------------------------------------------------------------------------------- /rules/typescript-axios-cursorrules-prompt-file/.cursorrules: -------------------------------------------------------------------------------- 1 | You are an elite software engineer and product manager with the following expertise: 2 | 3 | Utilize the following libraries effectively: 4 | 5 | -------------------------------------------------------------------------------- /rules/typescript-axios-cursorrules-prompt-file/elite-software-engineer-and-product-manager.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the persona of an elite software engineer and product manager to be used across all files, emphasizing the use of expertise and libraries effectively. 3 | globs: **/*.* 4 | --- 5 | You are an elite software engineer and product manager with the following expertise: 6 | 7 | Utilize the following libraries effectively: -------------------------------------------------------------------------------- /rules/typescript-axios-cursorrules-prompt-file/general-python-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines general rules for Python development within the service-1 directory, focusing on dependency management, Python version, and code structure. 3 | globs: /service-1/**/*.* 4 | --- 5 | - Always use UV when installing dependencies 6 | - Always use python 3.12 7 | - Always use classes instead of functions -------------------------------------------------------------------------------- /rules/typescript-clasp-cursorrules-prompt-file/naming-conventions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies naming conventions for classes, functions, and variables in TypeScript/Google Apps Script projects. 3 | globs: **/*.ts 4 | --- 5 | - Use PascalCase for class names and camelCase for functions and variables. 6 | - Follow Google Apps Script naming conventions for built-in services and methods. -------------------------------------------------------------------------------- /rules/typescript-clasp-cursorrules-prompt-file/performance-optimization-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Offers strategies for optimizing Google Apps Script performance and resource usage. 3 | globs: **/*.gs 4 | --- 5 | - Minimize API calls and use batch operations when possible. 6 | - Implement caching strategies for frequently accessed data. 7 | - Use efficient data structures and algorithms suitable for script limitations. -------------------------------------------------------------------------------- /rules/typescript-clasp-cursorrules-prompt-file/typescript-specific-usage-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guides the correct usage of TypeScript features like interfaces, types, and enums within Google Apps Script. 3 | globs: **/*.ts 4 | --- 5 | - Use TypeScript for all code; prefer interfaces over types. 6 | - Use enums when appropriate for Google Apps Script constants. 7 | - Implement custom types for Google Apps Script objects and return types. -------------------------------------------------------------------------------- /rules/typescript-code-convention-cursorrules-prompt-file/expo-mobile-app-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies best practices and conventions for Expo-based mobile app development. 3 | globs: mobile/**/*.tsx 4 | --- 5 | - You are an expert in Expo. 6 | - Follow Expo documentation for best practices. -------------------------------------------------------------------------------- /rules/typescript-code-convention-cursorrules-prompt-file/next-js-app-router-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies Next.js App Router specific guidelines to components and pages within the 'app' directory. 3 | globs: app/**/*.tsx 4 | --- 5 | - You are an expert in Next.js App Router. 6 | - Follow Next.js documentation for best practices in data fetching, rendering, and routing. -------------------------------------------------------------------------------- /rules/typescript-code-convention-cursorrules-prompt-file/node-js-backend-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces Node.js specific conventions and practices in the backend server directory. 3 | globs: server/**/*.js 4 | --- 5 | - You are an expert in Node.js. 6 | - Code Style and Structure: Follow Node.js conventions for structuring backend code. 7 | - Error Handling and Validation: Implement robust error handling and validation in Node.js. -------------------------------------------------------------------------------- /rules/typescript-code-convention-cursorrules-prompt-file/radix-ui-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific styles and conventions for Radix UI components 3 | globs: components/radix/**/*.tsx 4 | --- 5 | - You are an expert in Radix UI. -------------------------------------------------------------------------------- /rules/typescript-code-convention-cursorrules-prompt-file/react-component-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines code style and best practices for React components across the project. 3 | globs: components/**/*.tsx 4 | --- 5 | - You are an expert in React. 6 | - Code Style and Structure: Maintain a consistent structure for React components. 7 | - Syntax and Formatting: Adhere to consistent coding style and formatting guidelines for React. -------------------------------------------------------------------------------- /rules/typescript-code-convention-cursorrules-prompt-file/shadcn-ui-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies specific styles and conventions related to Shadcn UI components. 3 | globs: components/ui/**/*.tsx 4 | --- 5 | - You are an expert in Shadcn UI. -------------------------------------------------------------------------------- /rules/typescript-code-convention-cursorrules-prompt-file/tailwind-css-styling-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Apply Tailwind CSS styling conventions in all relevant files. 3 | globs: **/*.tsx 4 | --- 5 | - You are an expert in Tailwind. 6 | - UI and Styling: Use Tailwind CSS for consistent UI styling. -------------------------------------------------------------------------------- /rules/typescript-code-convention-cursorrules-prompt-file/trpc-api-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces conventions and practices for tRPC API endpoints and procedures. 3 | globs: trpc/**/*.ts 4 | --- 5 | - You are an expert in tRPC. -------------------------------------------------------------------------------- /rules/typescript-expo-jest-detox-cursorrules-prompt-file/api-documentation-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Documentation of the API's and how to use it. 3 | globs: **/api/**/*.* 4 | --- 5 | - Provide clear and concise API documentation for all endpoints and methods. 6 | - Include usage examples and parameter descriptions. 7 | - Keep the documentation up-to-date with the latest changes. -------------------------------------------------------------------------------- /rules/typescript-expo-jest-detox-cursorrules-prompt-file/error-handling-and-validation-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Deals with Error handling and validation in all files matching '*Error*'. 3 | globs: **/*Error*.* 4 | --- 5 | - Implement robust error handling and validation techniques. 6 | - Ensure proper validation of user inputs and data. 7 | - Handle edge cases and unexpected scenarios gracefully. -------------------------------------------------------------------------------- /rules/typescript-expo-jest-detox-cursorrules-prompt-file/expo-framework-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Expo Framework-specific guidelines. Includes best practices for Views, Blueprints, and Extensions. 3 | globs: **/expo/**/*.* 4 | --- 5 | - You are an expert in Expo. 6 | - Refer to Expo's documentation for Views, Blueprints, and Extensions. 7 | - Adhere to Expo's best practices for mobile development. -------------------------------------------------------------------------------- /rules/typescript-expo-jest-detox-cursorrules-prompt-file/general-typescript-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General TypeScript rules and guidelines. Applies to all TypeScript files. 3 | globs: **/*.ts 4 | --- 5 | - You are an expert in TypeScript. 6 | - Follow the prescribed naming conventions. 7 | - Enforce strong typing. 8 | - Adhere to the defined syntax and formatting standards. -------------------------------------------------------------------------------- /rules/typescript-expo-jest-detox-cursorrules-prompt-file/internationalization-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Deals with i18n in your project. 3 | globs: **/*i18n*.* 4 | --- 5 | - Implement internationalization (i18n) to support multiple languages. 6 | - Ensure text and UI elements are adaptable to different locales. 7 | - Provide translations for all user-facing content. -------------------------------------------------------------------------------- /rules/typescript-expo-jest-detox-cursorrules-prompt-file/mobile-ui-development-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General rules pertaining to Mobile UI development. Covers UI/UX best practices, state management, and navigation patterns. 3 | globs: **/mobile/**/*.* 4 | --- 5 | - You are an expert in Mobile UI development. 6 | - Focus on UI and styling best practices. 7 | - Implement Navigation patterns effectively. 8 | - Manage State efficiently. -------------------------------------------------------------------------------- /rules/typescript-expo-jest-detox-cursorrules-prompt-file/naming-conventions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines how to name functions, variables and components. 3 | globs: **/*Name*.* 4 | --- 5 | - Follow strict naming conventions for variables, functions, and components. 6 | - Use descriptive names that accurately reflect the purpose of the code. 7 | - Maintain consistency in naming throughout the project. -------------------------------------------------------------------------------- /rules/typescript-expo-jest-detox-cursorrules-prompt-file/security-practices-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies to all files containing Security to ensure proper security practices. 3 | globs: **/*Security*.* 4 | --- 5 | - Implement security best practices to protect against vulnerabilities. 6 | - Follow secure coding guidelines and prevent common security flaws. 7 | - Ensure data is encrypted and access is properly controlled. -------------------------------------------------------------------------------- /rules/typescript-expo-jest-detox-cursorrules-prompt-file/testing-conventions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules concerning testing, applies only to __tests__ folder. 3 | globs: **/__tests__/**/*.* 4 | --- 5 | - Write comprehensive tests for all components and functionalities. 6 | - Utilize appropriate testing frameworks and methodologies. 7 | - Ensure code coverage is adequate and tests are reliable. -------------------------------------------------------------------------------- /rules/typescript-llm-tech-stack-cursorrules-prompt-file/file-organization.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the file organization structure for TypeScript projects, emphasizing modularity and separation of concerns. 3 | globs: **/*.ts 4 | --- 5 | - Group related functionality into modules 6 | - Use index files to simplify imports 7 | - Separate concerns: keep business logic, UI components, and utilities in different directories -------------------------------------------------------------------------------- /rules/typescript-nestjs-best-practices-cursorrules-promp/nestjs-core-module-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces specific guidelines for the core module in NestJS, focusing on global filters, middleware, guards, and interceptors. 3 | globs: src/core/**/*.* 4 | --- 5 | - Global filters for exception handling. 6 | - Global middlewares for request management. 7 | - Guards for permission management. 8 | - Interceptors for request management. -------------------------------------------------------------------------------- /rules/typescript-nestjs-best-practices-cursorrules-promp/nestjs-shared-module-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines standards for the shared module in NestJS, emphasizing utilities and shared business logic accessible across modules. 3 | globs: src/shared/**/*.* 4 | --- 5 | - Utilities 6 | - Shared business logic -------------------------------------------------------------------------------- /rules/typescript-nextjs-cursorrules-prompt-file/naming-conventions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for naming conventions in TypeScript, Node.js, and Next.js projects. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use lowercase with dashes for directories (e.g., components/auth-wizard). 6 | - Favor named exports for components. -------------------------------------------------------------------------------- /rules/typescript-nextjs-cursorrules-prompt-file/next-js-data-fetching-rendering-routing.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Follow Next.js documentation regarding Data Fetching, Rendering and Routing when working in the /app directory 3 | globs: app/**/*.* 4 | --- 5 | - Follow Next.js docs for Data Fetching, Rendering, and Routing. -------------------------------------------------------------------------------- /rules/typescript-nextjs-cursorrules-prompt-file/syntax-and-formatting-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for syntax and formatting in TypeScript, Node.js, and Next.js projects. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use the "function" keyword for pure functions. 6 | - Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements. 7 | - Use declarative JSX. -------------------------------------------------------------------------------- /rules/typescript-nextjs-cursorrules-prompt-file/typescript-usage-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules specific to TypeScript usage including interfaces, types, and functional components. 3 | globs: **/*.{ts,tsx} 4 | --- 5 | - Use TypeScript for all code; prefer interfaces over types. 6 | - Avoid enums; use maps instead. 7 | - Use functional components with TypeScript interfaces. -------------------------------------------------------------------------------- /rules/typescript-nextjs-cursorrules-prompt-file/ui-and-styling-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for UI and styling using Daisy UI and Tailwind in React components. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use Daisy UI and Tailwind for components and styling. 6 | - Implement responsive design with Tailwind CSS; use a mobile-first approach. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-cursorrules-prompt-file/general-typescript-react-tailwind-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General rules for TypeScript, React, and Tailwind projects. This rule applies to all JavaScript/TypeScript files. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | You are an expert in TypeScript, Next.js App Router, React, and Tailwind. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-cursorrules-prompt-file/next-js-app-router-data-fetching-rendering-and-routing-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for Next.js 14 App Router projects. This rule applies to all files within the 'app' directory. 3 | globs: app/**/*.* 4 | --- 5 | Follow @Next.js 14 App Router docs for Data Fetching, Rendering, and Routing. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-cursorrules-prompt-file/pre-configured-apis-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for using pre-configured APIs in the project, using them only if they are required by the project. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | There are some pre-configured APIs in this template that can be used but only if required by the current project. These have already been created: -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-cursorrules-prompt-file/vercel-ai-sdk-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for using the Vercel AI SDK in the project. This rule applies to all JavaScript/TypeScript files. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | Use Vercel AI SDK for handling AI interactions and streaming responses. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-tailwind-supabase-cursorru/.cursorrules: -------------------------------------------------------------------------------- 1 | You are an expert in TypeScript, Nose-Js, Next.Js, Agp Rauter, React, Shaden UE, Radix UI, Supabase, and Tastains. 2 | 3 | Code Style and Structure 4 | 5 | -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-tailwind-supabase-cursorru/agp-router-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for using the Agp Router. 3 | globs: **/agp-router/**/*.* 4 | --- 5 | - You are an expert in Agp Router. 6 | - Use the Agp Router to create routes for your application. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-tailwind-supabase-cursorru/next-js-general-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules specific to Next.js components and pages. 3 | globs: **/pages/**/*.* 4 | --- 5 | - You are an expert in Next.js. 6 | - Use best practices for Next.js development, including server-side rendering and static site generation where appropriate. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-tailwind-supabase-cursorru/radix-ui-specific-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for Radix UI components. 3 | globs: **/radix-ui/**/*.* 4 | --- 5 | - You are an expert in Radix UI. 6 | - Implement Radix UI components according to their documentation and accessibility guidelines. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-tailwind-supabase-cursorru/react-general-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General React component rules. 3 | globs: **/components/**/*.* 4 | --- 5 | - You are an expert in React. 6 | - Follow React best practices, including using functional components and hooks. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-tailwind-supabase-cursorru/shaden-ue-specific-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for Shaden UE. 3 | globs: **/shaden-ue/**/*.* 4 | --- 5 | - You are an expert in Shaden UE. 6 | - Adhere to Shaden UE conventions and best practices. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-tailwind-supabase-cursorru/supabase-specific-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for Supabase. 3 | globs: **/supabase/**/*.* 4 | --- 5 | - You are an expert in Supabase. 6 | - Follow best practices for Supabase authentication, data storage, and real-time functionality. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-tailwind-supabase-cursorru/testing-with-nose-js-and-tastains.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules relating to testing using Nose-Js and Tastains. 3 | globs: **/tests/**/*.* 4 | --- 5 | - You are an expert in Nose-Js and Tastains. 6 | - Write comprehensive unit and integration tests using Nose-Js and Tastains. -------------------------------------------------------------------------------- /rules/typescript-nextjs-react-tailwind-supabase-cursorru/typescript-general-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General TypeScript rules for the project, ensuring consistent coding practices. 3 | globs: **/*.ts 4 | --- 5 | - You are an expert in TypeScript. 6 | - Follow best practices for TypeScript development. -------------------------------------------------------------------------------- /rules/typescript-nextjs-supabase-cursorrules-prompt-file/database-querying-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for database querying and data model creation using Supabase SDK and schema builder, focusing on the API routes directory. 3 | globs: /(app|pages)/api/**/*.(ts|js) 4 | --- 5 | - Use Supabase SDK for data fetching and querying. 6 | - For data model creation, use Supabase's schema builder. -------------------------------------------------------------------------------- /rules/typescript-nextjs-supabase-cursorrules-prompt-file/ui-styling-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for UI styling, specifically targeting the components directory and using Shadcn UI, Radix, and Tailwind CSS. 3 | globs: /components/**/*.(ts|tsx) 4 | --- 5 | - Use Shadcn UI, Radix, and Tailwind for components and styling. 6 | - Implement responsive design with Tailwind CSS; use a mobile-first approach. -------------------------------------------------------------------------------- /rules/typescript-nodejs-nextjs-ai-cursorrules-prompt-fil/python-dependency-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rule to ensure specific dependency management and Python version are used for a service. 3 | globs: /service-1/**/*.* 4 | --- 5 | - Always use UV when installing depdendencies 6 | - Always use python 3.12 7 | - Always use classes instead of function -------------------------------------------------------------------------------- /rules/typescript-nodejs-nextjs-app-cursorrules-prompt-fi/component-structure-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines how React components should be structured within the components directory. 3 | globs: components/**/*.* 4 | --- 5 | - Structure files: exported component, subcomponents, helpers, static content, types. 6 | - Favor named exports for components. -------------------------------------------------------------------------------- /rules/typescript-nodejs-nextjs-app-cursorrules-prompt-fi/directory-naming-convention.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the directory naming convention. 3 | globs: components/**/* 4 | --- 5 | - Use lowercase with dashes for directories (e.g., components/auth-wizard). -------------------------------------------------------------------------------- /rules/typescript-nodejs-nextjs-app-cursorrules-prompt-fi/key-conventions-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for key conventions, including nuqs for URL state management and Web Vitals optimization. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use 'nuqs' for URL search parameter state management. 6 | - Optimize Web Vitals (LCP, CLS, FID). 7 | - Limit 'use client': Follow Next.js docs for Data Fetching, Rendering, and Routing. -------------------------------------------------------------------------------- /rules/typescript-nodejs-nextjs-app-cursorrules-prompt-fi/syntax-and-formatting-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for code syntax and formatting, emphasizing concise and declarative styles. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use the "function" keyword for pure functions. 6 | - Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements. 7 | - Use declarative JSX. -------------------------------------------------------------------------------- /rules/typescript-nodejs-nextjs-app-cursorrules-prompt-fi/typescript-specific-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for TypeScript usage within the project. 3 | globs: **/*.{ts,tsx} 4 | --- 5 | - Use TypeScript for all code; prefer interfaces over types. 6 | - Avoid enums; use maps instead. 7 | - Use functional components with TypeScript interfaces. -------------------------------------------------------------------------------- /rules/typescript-nodejs-nextjs-app-cursorrules-prompt-fi/ui-and-styling-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for UI and styling, specifying the use of Shadcn UI, Radix UI, and Tailwind CSS. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use Shadcn UI, Radix, and Tailwind for components and styling. 6 | - Implement responsive design with Tailwind CSS; use a mobile-first approach. -------------------------------------------------------------------------------- /rules/typescript-react-cursorrules-prompt-file/typescript-react---folder-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the preferred folder structure for TypeScript React projects to maintain a consistent organization. 3 | globs: src/**/*.* 4 | --- 5 | - Recommended folder structure: 6 | src/ 7 | components/ 8 | hooks/ 9 | pages/ 10 | types/ 11 | utils/ 12 | App.tsx 13 | index.tsx -------------------------------------------------------------------------------- /rules/typescript-react-cursorrules-prompt-file/typescript-react---general-preferences.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Sets general preferences for TypeScript React development, such as preferring functional components. 3 | globs: **/*.tsx 4 | --- 5 | - Prefer functional components -------------------------------------------------------------------------------- /rules/typescript-react-nextjs-cloudflare-cursorrules-pro/key-conventions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies key conventions like using 'nuqs' for URL search parameter state management and optimizing Web Vitals. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use 'nuqs' for URL search parameter state management. 6 | - Optimize Web Vitals (LCP, CLS, FID). 7 | - Limit 'use client': Follow Next.js docs for Data Fetching, Rendering, and Routing. -------------------------------------------------------------------------------- /rules/typescript-react-nextjs-cloudflare-cursorrules-pro/naming-conventions-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces naming conventions for directories and components. 3 | globs: **/* 4 | --- 5 | - Use lowercase with dashes for directories (e.g., components/auth-wizard). 6 | - Favor named exports for components. -------------------------------------------------------------------------------- /rules/typescript-react-nextjs-cloudflare-cursorrules-pro/terminal-commands-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies expertise in suggesting wrangler commands within the terminal environment. 3 | globs: **/* 4 | --- 5 | - In the terminal, you are also an expert at suggesting wrangler commands. -------------------------------------------------------------------------------- /rules/typescript-react-nextjs-cloudflare-cursorrules-pro/ui-and-styling-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Governs UI and styling practices, including the use of Shadcn UI, Radix, and Tailwind CSS. 3 | globs: **/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use Shadcn UI, Radix, and Tailwind for components and styling. 6 | - Implement responsive design with Tailwind CSS; use a mobile-first approach. -------------------------------------------------------------------------------- /rules/typescript-react-nextui-supabase-cursorrules-promp/general-frontend-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General rules applying to the entire frontend codebase, including TypeScript usage and navigation patterns. 3 | globs: frontend/**/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use TypeScript for type-safe code. 6 | - Implement responsive navigation using Navbar and Sidebar components. 7 | - Handle errors gracefully using a generic error component. -------------------------------------------------------------------------------- /rules/typescript-react-nextui-supabase-cursorrules-promp/react-ui-components-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for React UI components using NextUI library. Focuses on UI development patterns for the frontend. 3 | globs: frontend/**/*.{ts,tsx,js,jsx} 4 | --- 5 | - Use React for building UI components. 6 | - Utilize NextUI components (buttons, modals, inputs, etc.) for consistent UI elements. 7 | - Ensure components are type-safe using TypeScript. -------------------------------------------------------------------------------- /rules/typescript-shadcn-ui-nextjs-cursorrules-prompt-fil/form-validation-with-zod.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of Zod for form validation throughout the project. 3 | globs: **/*.ts 4 | --- 5 | - Use Zod for form validation -------------------------------------------------------------------------------- /rules/typescript-shadcn-ui-nextjs-cursorrules-prompt-fil/server-actions-error-modeling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies how to model expected errors as return values in Server Actions. 3 | globs: app/actions/**/* 4 | --- 5 | - Model expected errors as return values in Server Actions 6 | - Use error boundaries for unexpected errors -------------------------------------------------------------------------------- /rules/typescript-shadcn-ui-nextjs-cursorrules-prompt-fil/syntax-and-formatting.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces specific syntax and formatting rules for JSX files. 3 | globs: **/*.tsx 4 | --- 5 | - Use the "function" keyword for pure functions 6 | - Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements 7 | - Use declarative JSX -------------------------------------------------------------------------------- /rules/typescript-shadcn-ui-nextjs-cursorrules-prompt-fil/ui-and-styling-with-shadcn-ui-and-tailwind.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies the usage of Shadcn UI, Radix, Tailwind Aria for UI components and styling within the project. 3 | globs: **/*.tsx 4 | --- 5 | - Use Shadcn UI, Radix, and Tailwind Aria for components and styling 6 | - Implement responsive design with Tailwind CSS; use a mobile-first approach -------------------------------------------------------------------------------- /rules/typescript-vite-tailwind-cursorrules-prompt-file/vueuse-library-rule.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Encourages leveraging VueUse functions throughout the project to enhance reactivity and performance. 3 | globs: src/**/*.* 4 | --- 5 | - Leverage VueUse functions where applicable to enhance reactivity and performance. -------------------------------------------------------------------------------- /rules/typescript-vuejs-cursorrules-prompt-file/.cursorrules: -------------------------------------------------------------------------------- 1 | Code Style and Structure: 2 | 3 | Naming Conventions: 4 | 5 | TypeScript Usage: 6 | 7 | Syntax and Formatting: 8 | 9 | Error Handling and Validation: 10 | 11 | UI and Styling: 12 | 13 | Performance Optimization: 14 | 15 | Key Conventions: 16 | Follow Vue.js docs for where makes sense 17 | 18 | -------------------------------------------------------------------------------- /rules/typescript-vuejs-cursorrules-prompt-file/error-handling-and-validation.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for handling errors and validating input. 3 | globs: **/*.{js,ts,jsx,tsx,py} 4 | --- 5 | - Implement robust error handling using try-catch blocks. 6 | - Validate user input to prevent unexpected errors or security vulnerabilities. 7 | - Log errors and exceptions to facilitate debugging. 8 | - Provide informative error messages to users. -------------------------------------------------------------------------------- /rules/typescript-vuejs-cursorrules-prompt-file/naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces specific naming conventions across the project. 3 | globs: **/*.{js,ts,jsx,tsx,py} 4 | --- 5 | - Use descriptive and meaningful names. 6 | - Follow camelCase for variables and functions (e.g., `myVariable`, `myFunction`). 7 | - Use PascalCase for class names (e.g., `MyClass`). 8 | - Avoid abbreviations unless they are widely understood. -------------------------------------------------------------------------------- /rules/typescript-vuejs-cursorrules-prompt-file/performance-optimization.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules for optimizing application performance. 3 | globs: **/*.{js,ts,jsx,tsx,vue} 4 | --- 5 | - Optimize images and other assets for faster loading times. 6 | - Use lazy loading to improve initial page load performance. 7 | - Minimize the number of HTTP requests. 8 | - Avoid unnecessary DOM manipulations. -------------------------------------------------------------------------------- /rules/typescript-vuejs-cursorrules-prompt-file/syntax-and-formatting.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines syntax and formatting rules for consistent code appearance. 3 | globs: **/*.{js,ts,jsx,tsx,py} 4 | --- 5 | - Use consistent indentation (e.g., 2 spaces or 4 spaces). 6 | - Keep lines under a reasonable length (e.g., 80-120 characters). 7 | - Use consistent bracing style (e.g., K&R or Allman). 8 | - Avoid unnecessary semicolons where possible. -------------------------------------------------------------------------------- /rules/typescript-vuejs-cursorrules-prompt-file/ui-and-styling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for UI and styling in Vue.js components. 3 | globs: src/components/**/*.{vue,scss,css} 4 | --- 5 | - Maintain a consistent design language across the application. 6 | - Use CSS preprocessors (e.g., Sass, Less) for improved styling capabilities. 7 | - Follow BEM (Block Element Modifier) naming conventions for CSS classes. -------------------------------------------------------------------------------- /rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-/key-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies key conventions for URL search parameter state management and Web Vitals optimization. 3 | globs: **/* 4 | --- 5 | - Use proper URL search parameter state management. 6 | - Optimize Web Vitals (LCP, CLS, FID). 7 | - Limit 'use client'. -------------------------------------------------------------------------------- /rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-/naming-conventions.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines naming conventions for directories and components within the project. 3 | globs: **/* 4 | --- 5 | - Use lowercase with dashes for directories (e.g., components/auth-wizard). 6 | - Favor named exports for components. -------------------------------------------------------------------------------- /rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-/next-js.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Instructs developers to follow Next.js documentation for data fetching, rendering, and routing when using Next.js. 3 | globs: **/nextjs/**/* 4 | --- 5 | - Follow Next.js docs for Data Fetching, Rendering, and Routing when Next JS is used instead of React Remix. -------------------------------------------------------------------------------- /rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-/react-remix.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Directs developers to follow React Remix documentation for data fetching, rendering, and routing when using React Remix. 3 | globs: **/remix/**/* 4 | --- 5 | - Follow React Remix docs for Data Fetching, Rendering, and Routing. -------------------------------------------------------------------------------- /rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-/react-server-components-rsc.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Guidelines for using React Server Components, including favoring server components and limiting their use to Web API access. 3 | globs: **/*.{js,jsx,ts,tsx} 4 | --- 5 | - Favor server components and Next.js SSR. 6 | - Use only for Web API access in small components. 7 | - Avoid for data fetching or state management. -------------------------------------------------------------------------------- /rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-/syntax-and-formatting.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specifies syntax and formatting preferences for TypeScript code, including function keyword usage and JSX syntax. 3 | globs: **/*.ts 4 | --- 5 | - Use the "function" keyword for pure functions. 6 | - Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements. 7 | - Use declarative JSX. -------------------------------------------------------------------------------- /rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-/typescript-specific-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces specific TypeScript usage guidelines, such as preferring interfaces over types and avoiding enums. 3 | globs: **/*.ts 4 | --- 5 | - Use TypeScript for all code; prefer interfaces over types. 6 | - Avoid enums; use maps instead. 7 | - Use functional components with TypeScript interfaces. 8 | - Use Zod for form validation. -------------------------------------------------------------------------------- /rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-/ui-and-styling.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines UI and styling guidelines, recommending the use of Shadcn UI, Radix, and Tailwind Aria, as well as responsive design practices. 3 | globs: **/*.{js,jsx,ts,tsx} 4 | --- 5 | - Use Shadcn UI, Radix, and Tailwind Aria for components and styling. 6 | - Implement responsive design with Tailwind CSS; use a desktop-first approach. -------------------------------------------------------------------------------- /rules/unity-cursor-ai-c-cursorrules-prompt-file/ringcon-controller-integration-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Sets rules for the part of the project which controls the Ringcon. 3 | globs: Assets/Scripts/RingconController/**/*.cs 4 | --- 5 | - This part of the project involves making a tower defense style game that uses a Nintendo Ringcon as the controller. -------------------------------------------------------------------------------- /rules/unity-cursor-ai-c-cursorrules-prompt-file/turret-mechanics-rules.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Rules and constrains regarding the turrets which are part of the tower defense game 3 | globs: Assets/Scripts/Turrets/**/*.cs 4 | --- 5 | - Players place turrets and then use exercise to charge up those turrets. -------------------------------------------------------------------------------- /rules/vue-3-nuxt-3-typescript-cursorrules-prompt-file/.cursorrules: -------------------------------------------------------------------------------- 1 | I'm sorry, but it seems like you forgot to include the content of the corrupted file. Could you please provide the text that needs formatting? 2 | -------------------------------------------------------------------------------- /rules/vue-3-nuxt-3-typescript-cursorrules-prompt-file/python-general-rules---service-1.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: General Python rules to be applied within the 'service-1' directory. Enforces dependency management, Python version, and code structure. 3 | globs: /service-1/**/*.* 4 | --- 5 | - Always use UV when installing depdendencies 6 | - Always use python 3.12 7 | - Always use classes instead of function -------------------------------------------------------------------------------- /rules/vue3-composition-api-cursorrules-prompt-file/vue-3-composition-api---composables.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Specific rules for composables in the Vue 3 Composition API. This focuses on how to structure and implement reusable logic using composables. 3 | globs: src/composables/**/*.js 4 | --- 5 | - Use setup() function for component logic 6 | - Utilize ref and reactive for reactive state -------------------------------------------------------------------------------- /rules/vue3-composition-api-cursorrules-prompt-file/vue-3-project-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Defines the recommended folder structure for a Vue 3 project to maintain consistency and organization. 3 | globs: src/**/* 4 | --- 5 | - Recommended folder structure: 6 | - src/ 7 | - components/ 8 | - composables/ 9 | - views/ 10 | - router/ 11 | - store/ 12 | - assets/ 13 | - App.vue 14 | - main.js -------------------------------------------------------------------------------- /rules/vue3-composition-api-cursorrules-prompt-file/vue-3-typescript-guidelines.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the use of TypeScript for type safety in Vue 3 projects, especially for .ts files. 3 | globs: src/**/*.ts 4 | --- 5 | - Use TypeScript for type safety 6 | - Implement proper props and emits definitions -------------------------------------------------------------------------------- /rules/web-app-optimization-cursorrules-prompt-file/configuration-management.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Configuration management techniques 3 | globs: svelte.config.js 4 | --- 5 | - Use environment variables for configuration management. -------------------------------------------------------------------------------- /rules/web-app-optimization-cursorrules-prompt-file/form-and-actions-in-sveltekit.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Describes Form and Actions implementations. 3 | globs: **/*.svelte 4 | --- 5 | - Utilize SvelteKit's form actions for server-side form handling. 6 | - Implement proper client-side form validation using Svelte's reactive declarations. 7 | - Use progressive enhancement for JavaScript-optional form submissions. -------------------------------------------------------------------------------- /rules/web-app-optimization-cursorrules-prompt-file/seo-and-meta-tags-in-sveltekit.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Provides SEO and Meta Tags guidelines in SvelteKit. 3 | globs: **/*.svelte 4 | --- 5 | - Use Svelte:head component for adding meta information. 6 | - Implement canonical URLs for proper SEO. 7 | - Create reusable SEO components for consistent meta tag management. -------------------------------------------------------------------------------- /rules/web-app-optimization-cursorrules-prompt-file/sveltekit-project-structure.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces the recommended SvelteKit project structure. 3 | globs: src/ 4 | --- 5 | - Use the recommended SvelteKit project structure: 6 | 7 | - src/ 8 | - lib/ 9 | - routes/ 10 | - app.html 11 | - static/ 12 | - svelte.config.js 13 | - vite.config.js -------------------------------------------------------------------------------- /rules/web-app-optimization-cursorrules-prompt-file/sveltekit-ssr-and-ssg.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Applies Server-Side Rendering and Static Site Generation 3 | globs: svelte.config.js 4 | --- 5 | - Leverage SvelteKit's SSR capabilities for dynamic content. 6 | - Implement SSG for static pages using prerender option. 7 | - Use the adapter-auto for automatic deployment configuration. -------------------------------------------------------------------------------- /rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt-/javascript-typescript-coding-standards.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces WordPress coding standards and prefers TypeScript for JavaScript/TypeScript files within the WordPress plugin. 3 | globs: /wp-plugin/**/*.{js,jsx,ts,tsx} 4 | --- 5 | - Always use WordPress coding standards when writing JavaScript and TypeScript. 6 | - Prefer writing TypeScript over JavaScript. -------------------------------------------------------------------------------- /rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt-/php-coding-standards.mdc: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforces WordPress coding standards and type hinting for PHP files within the WordPress plugin. 3 | globs: /wp-plugin/**/*.php 4 | --- 5 | - Always use WordPress coding standards when writing PHP. 6 | - Always type hint PHP code. --------------------------------------------------------------------------------