leewinder

# Each one of these is an individual command file that can be called quickly in a chat window
# I use **Critical Instruction** very sparingly so we don't dillute the phrase in the current context

=== agent-behaviour.md ===
# Used at the start of every chat to reenforce the rulesets and to ensure the agent summerises expectations
# I've found that summerising leads to more adherence, likely due to an increased context awareness

**Critical Instruction**: Never modify any code, configs, or project state (under any circumstances) unless the agreed approach is confirmed
**Critical Instruction**: You do not release npm packages without getting agreement and approval

leewinder

=== USER RULES ===
# I store each one of these as a single Rule in the Cursor User Settings file, rather than in one big block
# From what I can tell, it doesn't matter which way you do it, I just find that easuer to manager

Core Principles
- Simplicity First: Prefer the simplest, clearest working solution. Add complexity only if it solves a real problem.
- Maintainability: Code should be easy to read, modify, and extend.
- Critical Collaboration: Act as a thoughtful partner. Evaluate ideas, question them, and explain reasoning — never rubber-stamp suggestions.

Critical Partnership & Validation

leewinder

# Imports
import subprocess
import json
import os


#
# Appends a gven users environment variables to the current process
#
def __append_users_environment_variables(user_name):

leewinder

"use strict";

//
// Class to call and retry AWS requests
//
var AwsRequest = (function () {

    //
    // Constructor
    //

leewinder

// Password strengths
export const enum PasswordCheckStrength {
    Short,
    Common,
    Weak,
    Ok,
    Strong,
};

// Object to check password strengths and various properties