Document and automate Cursor rules adaptation for Astro web app

.cursor/rules/dev-folder.mdc

@@ -0,0 +1,40 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+# /dev Folder Rules
+
+## Resource Management Protocol
+- Resources in `/dev` are staging materials that require processing before production use
+- NEVER automatically copy resources from `/dev` to production locations
+- ONLY move or process `/dev` resources when explicitly instructed by user
+- Maintain original files in `/dev` unless specifically told to remove them
+
+## Quick and Dirty (QnD) Scripts Protocol
+- `/dev` is the designated location for quick prototyping scripts
+- QnD scripts in `/dev` don't need to follow full production code standards
+- Focus on functionality over code quality for QnD scripts
+- Document script purpose with minimal comments
+- Use descriptive filenames that indicate script function
+- QnD scripts should be marked clearly (e.g., `qnd_` prefix or `.qnd.` in filename)
+
+## Proof of Concept (POC) Protocol
+- All POC development happens exclusively in `/dev`
+- POC code should be isolated from production codebase
+- POC code can be experimental and doesn't require full error handling
+- When POC is approved for production, create separate implementation outside `/dev`
+
+## Temporary Files Management
+- Use `/dev` for all temporary files created during development process
+- User-created temporary files can be placed directly in `/dev`
+
+## Safety and Cleanup Rules
+- NEVER delete files from `/dev` without explicit user permission
+- Ask before moving files out of `/dev` to production locations
+- Maintain clear separation between `/dev` content and production code
+
+## Exclusions and Restrictions
+- Production builds should NEVER reference files directly from `/dev`
+- `/dev` paths should not be hardcoded in production configuration
+- `/dev` is not for production dependencies or critical system files