clean out the security instructions so that others don't generate code that breaks our challenges

commjoen · commjoen · commit 731d4bb500df · 2025-07-09T09:26:49.000+02:00
diff --git a/cursor/rules/project-specification.mdc b/cursor/rules/project-specification.mdc
@@ -173,7 +173,7 @@ To speed up challenge creation, follow these steps:
 
 ---
 
-## Security Requirements and Best Practices (for Real Projects)
+<!-- ## Security Requirements and Best Practices (for Real Projects)
 
 In real projects, always include explicit security requirements in your project specification or agentic plan. This should cover:
 - How secrets are managed, stored, and rotated
@@ -192,4 +192,4 @@ Always include security instructions on:
 - Logging and monitoring for suspicious activity
 
 These practices are essential for protecting your application and its data.
-====
+==== -->
