{"filename":"astro-typescript-cursorrules-prompt-file.mdc","content":"---\ndescription: \"Cursor rules for Astro development with TypeScript integration.\"\nglobs: **/*\nalwaysApply: false\n---\n{\n  \"rules\": {\n    \"commit_message_guidelines\": {\n      \"description\": \"Guidelines for creating conventional commit messages.\",\n      \n      \"format\": {\n        \"description\": \"The format for commit messages using the conventional commits spec.\",\n        \"body\": \"[optional scope]: \\n\\n[optional body]\\n\\n[optional footer(s)]\"\n      },\n      \n      \"enabled\": true,\n      \n      \"rules\": [\n        {\n          \"description\": \"Always suggest a conventional commit with a type and optional scope in lowercase letters.\"\n        },\n        {\n          \"description\": \"Keep the commit message concise and within 60 characters.\"\n        },\n        {\n          \"description\": \"Ensure the commit message is ready to be pasted into the terminal without further editing.\"\n        },\n        {\n          \"description\": \"Provide the full command to commit, not just the message.\"\n        }\n      ],\n      \n      \"examples\": [\n        {\n          \"prompt\": \"<diff_context> /commit\",\n          \"response\": \"git commit -m 'feat: add responsive navbar with TailwindCSS'\"\n        }\n      ]\n    },\n    \n    \"development_guidelines\": {\n      \"description\": \"Guidelines for developing code with Astro, TypeScript, and TailwindCSS.\",\n      \n      \"enabled\": true,\n      \n      \"rules\": [\n        {\n          \"description\": \"Enforce strict TypeScript settings, ensuring type safety across the project.\"\n        },\n        {\n          \"description\": \"Use TailwindCSS for all styling, keeping the utility-first approach in mind.\"\n        },\n        {\n          \"description\": \"Ensure Astro components are modular, reusable, and maintain a clear separation of concerns.\"\n        }\n      ]\n    },\n    \n    \"coding_style\": {\n      \"description\": \"Guidelines for maintaining consistent coding style.\",\n      \n      \"enabled\": true,\n      \n      \"rules\": [\n        {\n          \"description\": \"Code must start with path/filename as a one-line comment.\"\n        },\n        {\n          \"description\": \"Comments should describe purpose, not effect.\"\n        },\n        {\n          \"description\": \"Prioritize modularity, DRY principles, and performance.\"\n        }\n      ]\n    },\n    \n    \"custom_slash_commands\": {\n      \"description\": \"Custom slash commands.\",\n      \n      \"enabled\": true,\n      \n      \"commands\": [\n        {\n          \"name\": \"/commit\",\n          \"description\": \"Generate a Git commit message using the conventional commits spec.\",\n          \"enabled\": true\n        }\n      ]\n    }\n  }\n}\n"}