27 lines
1.4 KiB
Plaintext
27 lines
1.4 KiB
Plaintext
---
|
|
description:
|
|
globs:
|
|
alwaysApply: false
|
|
---
|
|
# Project-Specific Rule Adaptations for BSC Score (Astro Web App)
|
|
|
|
## Overview
|
|
This project is a modern, responsive web application for tracking billiards scores, built with Astro and vanilla JavaScript. The following adaptations and exceptions apply to the default Cursor rules:
|
|
|
|
## Rule Adaptations & Removals
|
|
|
|
- **best-practices-astro.mdc**: Kept and enforced, as the project is built with Astro.
|
|
- **CLI/API/Non-Web Rules**: No CLI, API, or data science rules are needed. No such rules exist in the current ruleset, so no removals are required.
|
|
- **All Other Rules**: All other rules are relevant and retained, as they apply to general development, git workflow, Gitea usage, discipline, and best practices for web projects.
|
|
|
|
## Reasoning
|
|
- The project is a web application using Astro, so Astro-specific best practices are required.
|
|
- There is no CLI, API, or non-web domain logic, so no domain-specific rules for those are needed.
|
|
- TypeScript is supported via Astro's strict config, so type safety rules are relevant.
|
|
|
|
## Overrides/Extensions
|
|
- No overrides or extensions are currently required. If the project scope changes (e.g., adds an API or CLI), new rules will be proposed.
|
|
|
|
## Documentation
|
|
- This file documents the rationale for rule selection and adaptation. All changes are summarized in .cursor/README.md as required.
|