Update role analysis, coding, and documentation rules to always apply. Adjust documentation links for consistency across planning tasks. These changes enhance the reliability of role applications and improve documentation clarity for users.

Author: fr4iser90

.cursor/rules/role_analysis_planning.mdc

@@ -1,7 +1,7 @@
 ---
 description: 
 globs: 
-alwaysApply: false
+alwaysApply: true
 ---
 # role_analysis_planning.mdc
 

.cursor/rules/role_coding_phase.mdc

@@ -1,7 +1,7 @@
 ---
 description: 
 globs: 
-alwaysApply: false
+alwaysApply: true
 ---
 # role_coding_phase.mdc
 

.cursor/rules/role_documentation.mdc

@@ -1,7 +1,7 @@
 ---
 description: 
 globs: 
-alwaysApply: false
+alwaysApply: true
 ---
 # role_documentation.mdc
 
@@ -14,7 +14,7 @@ alwaysApply: false
 - Always active; responsible for all documentation quality and structure.
 
 **Core Principle:**
-Documentation is a first-class citizen. It must be clear, up-to-date, and easy to navigate for all users and contributors.
+Documentation is a first-class citizen. It must be clear, up-to-date, and easy to navigate for all users and contributors. English only.
 
 **Workflow / Key Responsibilities:**
 1. Maintain a central documentation index (INDEX.md)

docs/plan/task_1.md

@@ -1,12 +1,12 @@
 # Task List: Phase 1 – Preparation & Planning
 
 - [x] Write project objectives and scope in README.md
-- [x] List and justify tech stack in doc/plan/detailed_plan.md
-- [x] Draw and describe architecture in doc/plan/detailed_plan.md
-- [x] Specify folder/file structure in doc/plan/detailed_plan.md
-- [x] Draft implementation plan in doc/plan/detailed_plan.md
+- [x] List and justify tech stack in docs/plan/detailed_plan.md
+- [x] Draw and describe architecture in docs/plan/detailed_plan.md
+- [x] Specify folder/file structure in docs/plan/detailed_plan.md
+- [x] Draft implementation plan in docs/plan/detailed_plan.md
 - [x] Draft sequenced, atomic task lists in task_1.md–task_5.md
 - [x] Write initial README.md (overview, features, usage, architecture, roadmap)
 - [x] Write LICENSE (MIT)
-- [x] Write extension/contribution guidelines in doc/EXTENDING.md
+- [x] Write extension/contribution guidelines in docs/EXTENDING.md
 - [x] Review and finalize all planning docs

docs/plan/task_2.md

@@ -4,7 +4,7 @@
 - [x] Create /zap/ directory for ZAP configs
 - [x] Create /trivy/ directory for Trivy configs
 - [x] Create /scripts/ directory for automation scripts
-- [x] Create /doc/plan/ directory for planning docs
+- [x] Create /docs/plan/ directory for planning docs
 - [x] Create .github/workflows/ directory for GitHub Actions
 - [x] Create .vscode/ directory for editor settings (if not present)
 - [x] Place README.md and LICENSE in root

docs/plan/task_4.md

@@ -7,5 +7,5 @@
 - [x] Write trivy/config.yaml (dependency/container scan config)
 - [x] Place all rules/configs in correct folders
 - [x] Test each rule/config with scripts/security-check.sh
-- [x] Document each rule/config in README.md and doc/EXTENDING.md
+- [x] Document each rule/config in README.md and docs/EXTENDING.md
 - [x] Refine based on test results

docs/plan/task_5.md

@@ -5,6 +5,6 @@
 - [x] Test both CI configs on a sample repo
 - [x] Validate that results appear in CI logs and as artifacts
 - [x] Finalize and polish README.md (add CI badges, usage, troubleshooting)
-- [x] Finalize doc/EXTENDING.md (how to add rules, tools, outputs)
+- [x] Finalize docs/EXTENDING.md (how to add rules, tools, outputs)
 - [x] Review and update all planning and documentation files
 - [x] Mark project as ready for coding phase exit

docs/plan/task_6.md

@@ -1,12 +1,12 @@
-# Task List: Phase 6 – Automatisierte Auswertung, Reporting & API-Security
+# Task List: Phase 6 – Automated Analysis, Reporting & API Security
 
-- [x] Script zur Auswertung aller Scan-Resultate (ZAP, Semgrep, Trivy)
-- [x] Findings nach Schweregrad sortieren und zusammenfassen
-- [x] "Alles okay"-Abschnitte explizit ausgeben
-- [ ] To-Do-Liste für Entwickler generieren
-- [ ] Optional: HTML-Report erzeugen
-- [ ] Optional: Slack/Teams/Email-Benachrichtigung bei kritischen Findings
-- [ ] Semgrep-Regeln für API-Absicherung (Auth, CORS, Rate Limiting)
-- [ ] ZAP-Policy für API-Endpoints anpassen
-- [ ] Weitere Semgrep-Regeln für LLM/AI-Security
-- [ ] Doku im README ergänzen 
+- [x] Script to analyze all scan results (ZAP, Semgrep, Trivy)
+- [x] Sort and summarize findings by severity
+- [x] Explicitly output "All OK" sections
+- [ ] Generate to-do list for developers
+- [ ] Optionally: Generate HTML report
+- [ ] Optionally: Slack/Teams/Email notification for critical findings
+- [ ] Semgrep rules for API security (Auth, CORS, Rate Limiting)
+- [ ] Adjust ZAP policy for API endpoints
+- [ ] More Semgrep rules for LLM/AI security
+- [ ] Update documentation!

docs/plan/task_7.md

@@ -1,14 +1,14 @@
 # Task List: Phase 7 – Advanced Automation, Integration & Developer Experience
 
-- [ ] Automatisches Mapping aller Findings auf OWASP Top 10, DSGVO, NIST, etc.
-- [ ] Compliance-Report generieren
-- [ ] Plug-in-System für neue Tools/Checks
-- [ ] Auto-Fix-Vorschläge für triviale Findings
-- [ ] False-Positive-Handling (Whitelist, Suppression)
-- [ ] Historie/Trend-Analyse der Findings
-- [ ] Dashboard für Security-Status und Trends
-- [ ] Automatische Erkennung des Tech-Stacks und Anpassung der Checks
-- [ ] Ticket-Erstellung bei kritischen Findings (Jira, GitHub Issues)
-- [ ] PDF-Export des Reports
-- [ ] Troubleshooting/FAQ und Beispiel-Output in der Doku
-- [ ] Video/Screen-Demo für Onboarding 
+- [ ] Automatic mapping of all findings to OWASP Top 10, GDPR, NIST, etc.
+- [ ] Generate compliance report
+- [ ] Plug-in system for new tools/checks
+- [ ] Auto-fix suggestions for trivial findings
+- [ ] False-positive handling (whitelist, suppression)
+- [ ] History/trend analysis of findings
+- [ ] Dashboard for security status and trends
+- [ ] Automatic detection of tech stack and adjustment of checks
+- [ ] Ticket creation for critical findings (Jira, GitHub Issues)
+- [ ] PDF export of the report
+- [ ] Troubleshooting/FAQ and example output in the documentation
+- [ ] Video/screen demo for onboarding 

docs/plan/task_8.md

@@ -24,20 +24,3 @@ Enhance the SecuLite dashboard to provide a robust, interactive, and user-friend
 - [ ] Test all dashboard features (scan trigger, status, auto-refresh, error handling)
 - [ ] Validate user experience and accessibility
 
-## Dependencies
-- Backend API (Flask: `/scan`, `/status`)
-- `scripts/webui.js`
-- `results/security-summary.html`
-
-## Success Criteria
-- User can trigger scan via button
-- Status is displayed and updated correctly
-- Dashboard auto-refreshes after scan completion
-- Errors are clearly shown to the user
-- UI is clear, accessible, and user-friendly
-- Documentation and screenshots are up to date
-
-## IST-Stand
-- Scan button and status display are implemented
-- Auto-refresh, error handling, and UI feedback are missing
-- Documentation/screenshots not updated