astro typescript
via PatrickJS/awesome-cursorrules
Astro + TypeScript development rules with conventional commits and TailwindCSS styling guidelines.
What is astro typescript?
This rule enforces development standards for Astro projects using TypeScript, including strict type safety, TailwindCSS utility-first styling, and conventional commit message formatting. Use it to maintain consistent code quality, modularity, and git history across Astro-based applications.
- Enforce strict TypeScript type checking for type safety
- Generate conventional commit messages with the /commit slash command
- Require TailwindCSS for all styling with utility-first approach
- Ensure modular, reusable Astro components with clear separation of concerns
- Enforce coding style with file path comments and purpose-driven documentation
Applies to
File patterns this rule matches.
Rule definition (reference)
Source of truth, from the repository.
{ "rules": { "commit_message_guidelines": { "description": "Guidelines for creating conventional commit messages.",
"format": {
"description": "The format for commit messages using the conventional commits spec.",
"body": "[optional scope]: \n\n[optional body]\n\n[optional footer(s)]"
},
"enabled": true,
"rules": [
{
"description": "Always suggest a conventional commit with a type and optional scope in lowercase letters."
},
{
"description": "Keep the commit message concise and within 60 characters."
},
{
"description": "Ensure the commit message is ready to be pasted into the terminal without further editing."
},
{
"description": "Provide the full command to commit, not just the message."
}
],
"examples": [
{
"prompt": "<diff_context> /commit",
"response": "git commit -m 'feat: add responsive navbar with TailwindCSS'"
}
]
},
"development_guidelines": {
"description": "Guidelines for developing code with Astro, TypeScript, and TailwindCSS.",
"enabled": true,
"rules": [
{
"description": "Enforce strict TypeScript settings, ensuring type safety across the project."
},
{
"description": "Use TailwindCSS for all styling, keeping the utility-first approach in mind."
},
{
"description": "Ensure Astro components are modular, reusable, and maintain a clear separation of concerns."
}
]
},
"coding_style": {
"description": "Guidelines for maintaining consistent coding style.",
"enabled": true,
"rules": [
{
"description": "Code must start with path/filename as a one-line comment."
},
{
"description": "Comments should describe purpose, not effect."
},
{
"description": "Prioritize modularity, DRY principles, and performance."
}
]
},
"custom_slash_commands": {
"description": "Custom slash commands.",
"enabled": true,
"commands": [
{
"name": "/commit",
"description": "Generate a Git commit message using the conventional commits spec.",
"enabled": true
}
]
}
} }
Related rules
AutoML and hyperparameter optimization rules for Python ML projects using Ray Tune, Optuna, PyCaret, and time-series libraries
Guidelines for integrating Beefree SDK email editor into web applications with authentication, configuration, and template management.
Embed Beefree SDK's no-code email, page, and popup editors into web applications.
Structure, register, and safely script Blender Python add-ons with operators, panels, and properties.
Expert guidance for Chrome Extension development with TypeScript, modern JavaScript, and Web APIs.
Guidelines for writing clean, maintainable, and human-readable code.