- Introduced a new code snippets resource for common FiveM patterns in Lua and JavaScript. - Added a framework comparison document outlining Standalone, ESX, and QBCore features. - Created search results view for FiveM documentation queries. - Developed client and server template scripts for ESX and QBCore frameworks. - Implemented NUI templates including HTML, CSS, and JavaScript for user interfaces. - Established routes for documentation and console commands. - Added tests for various features including documentation routes and tool functionalities. - Configured Vite for asset management with Laravel. - Updated .gitignore files for storage and framework directories.
14 lines
951 B
Markdown
14 lines
951 B
Markdown
---
|
|
applyTo: "**"
|
|
description: Aikido MCP Security Rules
|
|
---
|
|
|
|
# Project security best practices
|
|
|
|
- Always run **aikido_full_scan** on generated, added and modified first-party code, unless the prompt explicitly says not to.
|
|
- Always provide the full file content to the scanner.
|
|
- If the scan identifies any security issues in newly generated or modified code, fix the issues using the scan result and remediation provided by **Aikido**.
|
|
- After applying fixes, run aikido_full_scan again to verify that the issues were successfully resolved, and no new issues were introduced.
|
|
- Repeat the fix-and-rescan cycle until the code passes with zero remaining or newly introduced security issues.
|
|
- If the **Aikido MCP server** required to run scans is not installed or not started successfully, inform the user with a message directing them to install it using the official Aikido MCP setup guide at:
|
|
**https://help.aikido.dev/ide-plugins/aikido-mcp**. |