refactor: update branding, visual identity and output style

.cursor/commands/create-branch.md

@@ -1,5 +1,4 @@
-Meticulously catalog and analyze all the changes in this Git working tree, staged or unstaged
-and create a new branch with a suitable name.
+Based on the changes made to this repository create a new branch with a suitable name.
 
 Create the branch only (no commits yet). Use Conventional Commit types as branch prefixes:
 feat/, fix/, docs/, style/, refactor/, perf/, test/, build/, ci/, chore/, revert/.

.cursor/commands/create-commits.md

@@ -1,5 +1,4 @@
-Meticulously catalog and analyze all the changes in this Git working tree, staged or unstaged
-and create one or more commits with suitable titles.
+Based on the changes made to this repository create one or more commits with suitable titles.
 
 Use Conventional Commits to group related changes into cohesive commits (commits should be independently meaningful).
 

.cursor/commands/deslop.md

@@ -0,0 +1,12 @@
+# Remove AI code slop
+
+Check the diff against main, and remove all AI-generated slop introduced in this branch.
+
+This includes:
+
+- Extra comments that a human wouldn't add or are inconsistent with the rest of the file
+- Extra defensive checks or try/catch blocks that are abnormal for that area of the codebase (especially if called by trusted / validated codepaths)
+- Casts to any to get around type issues
+- Any other style that is inconsistent with the file
+
+Report at the end with only a 1-3 sentence summary of what you changed

.cursor/rules/00-main.mdc

@@ -10,7 +10,7 @@ All rules MANDATORY.
 
 Build Deployer PHP: Composer package and CLI tool simplifying server provisioning and deployment across multiple Cloud providers.
 
-### Before ANY Task
+### References
 
 - Check `composer.json` and `package.json` for installed packages
 - Plan with features from installed major versions
@@ -31,8 +31,8 @@ Build Deployer PHP: Composer package and CLI tool simplifying server provisionin
 
 - Catalog like a librarian
 - Group related functions into comment-separated sections
-- Prefer alphabetical ordering when no logical grouping exists
-- Code should be functional and visually appealing
+- Order alphabetically after grouping logically
+- Code should be both functional and visually appealing
 
 **Consistency:**
 
@@ -47,8 +47,8 @@ Build Deployer PHP: Composer package and CLI tool simplifying server provisionin
 2. STEP BY STEP - break into logical steps
 3. ACT - implement systematically
 
-### Tests
+### Test later
 
 Don't run or create or update tests UNLESS explicitly instructed to do so.
 
-Test are something we need to focus on separately from building features.
+Tests are something we will focus on separately from building features.

.cursor/rules/01-architecture.mdc

@@ -35,7 +35,7 @@ Always add `use` statements for vendor packages and project classes. Root namesp
 ```php
 // ✅ CORRECT
 use Symfony\Component\Filesystem\Filesystem;
-use Bigpixelrocket\DeployerPHP\Services\IOService;
+use PHPDeployer\Services\IOService;
 
 $fs = new Filesystem();
 throw new \InvalidArgumentException('Error');

.cursor/rules/02-tests.mdc

@@ -8,7 +8,7 @@ All rules MANDATORY.
 
 **Philosophy:** "A test that never fails is not a test, it's a lie."
 
-**Framework:** Pest exclusively, `it()` syntax, 80%+ coverage
+**Framework:** Pest exclusively, `it()` syntax, 70%+ coverage
 
 ### Running Tests