Skip to content
Prompt

dot-ai-demo — Cursor Rules

by vfarcic

AI Summary

Cursor Rules for infrastructure setup that guides users through intent gathering before implementing infrastructure resources. Developers using Cursor IDE benefit from structured prompts for deploying applications, databases, and cloud infrastructure.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "dot-ai-demo — Cursor Rules" prompt rules to my project.
Repository: https://github.com/vfarcic/dot-ai-demo

Please read the repo to find the rules/prompt file, then:
1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type)
2. If there's an existing rules file, merge the new rules in rather than overwriting
3. Confirm what was added

Description

Cursor Rules for dot-ai-demo

Infrastructure Setup Intent Gathering

IMPORTANT: When executing this prompt, do NOT use any MCP (Model Context Protocol) tools or services. Use only standard Claude tools like Bash, Read, Write, Edit, etc. to implement the infrastructure setup. WORKFLOW: Ask ALL questions below in the specified order before starting any implementation. Do NOT modify these questions. Only proceed with implementation after collecting all answers.

Step 1: Intent Question

Ask the user: "What do you want to deploy or set up? Please describe your intent for setting up infrastructure resources." Examples you can provide: • Deploy a web application with database • Set up a Kubernetes cluster • Create a PostgreSQL database • Deploy a microservices architecture • Set up monitoring and logging • Create a CI/CD pipeline

Step 2: Required Questions

Ask these questions exactly as written: • "What type of resource/application are you deploying?" Options: Database (PostgreSQL, MySQL, MongoDB, etc.) | Web Application (Frontend, Backend, Full-stack) | Container/Kubernetes workload | Storage solution | Networking component | Monitoring/Observability tool | Other • "Which cloud provider or platform?" Options: AWS | Azure | Google Cloud | Kubernetes cluster | On-premises | Docker/Local | Other • "What environment is this for?" Options: Development | Staging | Production | Testing

Step 3: Basic Questions

Ask these questions exactly as written: • "What are your performance requirements?" Ask for: Expected traffic/load, Storage needs, Memory requirements • "Do you need high availability?" Options: Yes - Multi-region/zone | Yes - Single region, multiple zones | No - Single instance is fine • "What's your preferred naming convention?" Ask for: Resource prefix, Environment suffix • "Do you need backup and disaster recovery?" Options: Yes - Automated backups | Yes - Manual backups | No

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 2mo ago
Active
AdoptionUnder 100 stars
3 ★ · Niche
DocsMissing or thin
Undocumented

GitHub Signals

Stars3
Forks2
Issues0
Updated2mo ago
View on GitHub
No License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more