| description | tools | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Brainstorm Trooper |
|
Helps user identify and invalidate incorrect assumptions in their code, logic, or approach. This mode is tuned for:
GitHub Copilot Custom Agent Mode
I modified that beast mode to be more robust, and I love it. Refactored an entire older repo I made from years ago just for fun and was able to do perfectly
I call it "Extensive Mode"
"Extensive Mode.chatmode.md"
The tools should be customized per environment and what you have available,
| description | tools | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4.1 Beast Mode |
|
You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.
You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.
Your goal is to complete the entire user request as quickly as possible. You will receive a bonus depending on how fast you can complete the entire task.
Follow these steps EXACTLY to complete the user's request:
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.
The Memory Bank consists of required core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy:
flowchart TD
| # Debian 10 | |
| apt-get -y update | |
| apt-get -y upgrade --without-new-pkgs | |
| apt-get -y full-upgrade | |
| cat > /etc/apt/sources.list <<"EOF" | |
| deb http://deb.debian.org/debian/ bullseye main | |
| deb-src http://deb.debian.org/debian/ bullseye main | |
| deb http://security.debian.org/bullseye-security bullseye-security/updates main | |
| deb-src http://security.debian.org/bullseye-security bullseye-security/updates main |
| { | |
| "recommendations": [ | |
| "aaron-bond.better-comments", | |
| "adrieankhisbe.vscode-ndjson", | |
| "johnsoncodehk.vscode-tsconfig-helper", | |
| "rbuckton.deoptexplorer-vscode", | |
| "helixquar.randomeverything", | |
| "WallabyJs.quokka-vscode", | |
| "bierner.comment-tagged-templates", | |
| "alexcvzz.vscode-sqlite", |
| (cors) { | |
| @cors_preflight{args.0} method OPTIONS | |
| @cors{args.0} header Origin {args.0} | |
| handle @cors_preflight{args.0} { | |
| header { | |
| Access-Control-Allow-Origin "{args.0}" | |
| Access-Control-Allow-Methods "GET, POST, PUT, PATCH, DELETE, OPTIONS" | |
| Access-Control-Allow-Headers * | |
| Access-Control-Max-Age "3600" |
This document was created back in 2020 and might not be actual nowadays. It is not supported anymore, so use thise information at your own risk.
wsl --set-default-version 2 in windows command line, so that all future WSL machine will use WSL2.
Podman is a container engine that is similar to and fully compatible with Docker that has the peculiarity of not requiring a daemon to run and to allow for rootless containers, which are often deemed safer than privileged containers running as root. Podman is a drop-in replacement for Docker that even supports the same syntax and it has good support from Red Hat.
However, running podman rootless containers on Arch Linux may not be obvious, so I'm writing the instructions I have used to achieve that here.
Podman works using control groups and users from which said containers need to be launched need to be assigned an appropriate range of subordinate user and group IDs. On Arch Linux, these files are not present and they need to be created.
From a root shell: