25 lines
1.4 KiB
Markdown
25 lines
1.4 KiB
Markdown
# Cursor Rules for BSC Score (Astro Web App)
|
|
|
|
## Summary of Rule Adaptations
|
|
|
|
This project uses the Cursor rules system to enforce best practices and workflow discipline. The following summarizes the rule adaptations, removals, and additions for this project:
|
|
|
|
### Enforced Rules
|
|
- All general development, git workflow, Gitea usage, discipline, and best practices rules are enforced.
|
|
- **best-practices-astro.mdc** is enforced, as the project is built with Astro.
|
|
- Type safety and code quality rules are relevant due to the use of TypeScript (via Astro's strict config).
|
|
|
|
### Not Relevant / Not Present
|
|
- No CLI, API, or data science rules are present or required, as this is a web application only.
|
|
- No rules were removed, as all present rules are applicable to the project domain.
|
|
|
|
### Project-Specific Adaptations
|
|
- See `.cursor/rules/project-adaptations.mdc` for a detailed rationale and documentation of all rule adaptations and exceptions.
|
|
|
|
### Maintenance
|
|
- When central rules are updated, all `.mdc` files in `.cursor/rules` should be re-reviewed and project-specific adaptations re-applied.
|
|
- If any conflicts or ambiguities arise, manual review will be requested.
|
|
|
|
---
|
|
|
|
This README documents the current state of rule enforcement and adaptation for the BSC Score project. For further details, consult the individual rule files in `.cursor/rules/` and the project adaptation summary. |