haraps 1.0.6 → 1.0.8

package/SKILL.md

@@ -36,10 +36,11 @@ Verify that the following files were successfully created in the root directory:
 
 It is your strict responsibility as the agent to carefully initialize the standard project skeleton if this is the first run (i.e. if the project is empty). You must:
 1. Generate the Next.js frontend and Rust Cloudflare Worker backend in their respective directories (`frontend/` and `backend/`).
-2. Carefully modify the generated files to align with the project guidelines. 
-3. **CRITICAL: Dev and Deploy Scripts**: The generated `dev.ps1`, `dev.sh`, `deploy.ps1`, and `deploy.sh` files are highly optimized custom runners (with clipboard integration, aggressive process cleanup, and error reporting). **Never** overwrite them with generic start/build scripts. If modifications are needed, surgically edit them to preserve their robust functionality.
-4. Initialize the Git repository (`git init`) and create the initial commit.
+2. **Contextualize Files**: Open the scaffolded `dev.ps1`, `dev.sh`, `deploy.ps1`, `deploy.sh`, and the UI Sniper Telegram configuration (including the webhook route), and **modify them** to precisely match the project name and description.
+3. **Telegram Feedback Customization**: Ensure the Telegram message for UI feedback exactly matches the project context (updating names, tags, or message format as needed).
+4. **Rust Instructions**: Ensure dev and deploy scripts are surgically modified to correctly support the required Rust compilation/cargo instructions for the backend. **Never** overwrite the entire scripts with generic versions; preserve their robust functionality.
+5. Initialize the Git repository (`git init`) and create the initial commit.
 
 ### Step 4: Inform the User
 
-Notify the user that the project has been successfully scaffolded and all the lazy senior dev standards, security reviews, UI sniper setups, and AI slop removers are in place. Remind them to use `./dev.ps1` or `./dev.sh` once their `frontend/` and `backend/` directories are initialized.
+Notify the user that the project has been contextualized, customized, and scaffolded. Remind them to run `./dev.ps1` or `./dev.sh`.

package/bin/index.js

@@ -4,7 +4,8 @@ const fs = require('fs');
 const path = require('path');
 const { execSync } = require('child_process');
 
-console.log('🚀 Scaffold Project Environment (Hara-XY) 🚀');
+const pkg = require(path.join(__dirname, '../package.json'));
+console.log(`🚀 Scaffold Project Environment (Hara-XY) v${pkg.version} 🚀`);
 
 function ensureDir(dir) {
     if (!fs.existsSync(dir)) {
@@ -20,7 +21,7 @@ function writeFile(filePath, content) {
 }
 
 // 1. Dev Scripts
-writeFile('dev.sh', `
+writeFile('dev.sh', `
 #!/usr/bin/env bash
 # =============================================
 # Medizys Local Development Runner
@@ -384,7 +385,7 @@ node "$runnerPath"
 `);
 fs.chmodSync(path.resolve(process.cwd(), 'dev.sh'), '755');
 
-writeFile('dev.ps1', `
+writeFile('dev.ps1', `
 # =============================================
 # Medizys Local Development Runner
 # =============================================
@@ -798,22 +799,22 @@ if ($null -ne (Get-Variable -Name watcherJob -ErrorAction SilentlyContinue)) {
 `);
 
 // 2. Deploy Scripts
-writeFile('deploy.sh', `
-TARGET=$(readlink -f ~/mediqueue_linux/mediqueue/frontend/node_modules/@cloudflare/next-on-pages/dist/index.js)
-sed -i 's/await (0, import_esbuild.build)({/await (0, import_esbuild.build)({ logLevel: "error",/g' $TARGET
-sed -i 's/await (0, import_esbuild2.build)({/await (0, import_esbuild2.build)({ logLevel: "error",/g' $TARGET
-cd ~/mediqueue_linux/mediqueue/frontend
-export NODE_OPTIONS="--max_old_space_size=16384"
-npx @cloudflare/next-on-pages
-cp -r .vercel /mnt/c/Users/shivg/Desktop/Hara-XY/mediqueue-main/mediqueue/frontend/
-cd /mnt/c/Users/shivg/Desktop/Hara-XY/mediqueue-main/mediqueue/frontend
-$env:WRANGLER_SEND_METRICS="false"
-npx wrangler pages deploy .vercel/output/static
+writeFile('deploy.sh', `
+TARGET=$(readlink -f ~/mediqueue_linux/mediqueue/frontend/node_modules/@cloudflare/next-on-pages/dist/index.js)
+sed -i 's/await (0, import_esbuild.build)({/await (0, import_esbuild.build)({ logLevel: "error",/g' $TARGET
+sed -i 's/await (0, import_esbuild2.build)({/await (0, import_esbuild2.build)({ logLevel: "error",/g' $TARGET
+cd ~/mediqueue_linux/mediqueue/frontend
+export NODE_OPTIONS="--max_old_space_size=16384"
+npx @cloudflare/next-on-pages
+cp -r .vercel /mnt/c/Users/shivg/Desktop/Hara-XY/mediqueue-main/mediqueue/frontend/
+cd /mnt/c/Users/shivg/Desktop/Hara-XY/mediqueue-main/mediqueue/frontend
+$env:WRANGLER_SEND_METRICS="false"
+npx wrangler pages deploy .vercel/output/static
 
 `);
 fs.chmodSync(path.resolve(process.cwd(), 'deploy.sh'), '755');
 
-writeFile('deploy.ps1', `
+writeFile('deploy.ps1', `
 param(
     [switch]$SkipSentry = $false,
     [switch]$SkipSeed = $false,
@@ -1259,8 +1260,13 @@ writeFile('AGENTS.md', `
 When the user says "start project", you MUST immediately:
 1. Ask the user for the name of the project and a brief description of what they want to build.
 2. Wait for their response.
-3. Once they respond, use their details to initialize the Next.js frontend (in \`frontend/\`) and Rust backend (in \`backend/\`), adhering to all High-Performance Engineering Standards.
+3. Once they respond, it is YOUR strict responsibility to initialize the standard project skeleton and apply contextual modifications:
+   a. Generate the Next.js frontend and Rust Cloudflare Worker backend in their respective directories (\`frontend/\` and \`backend/\`).
+   b. **Contextualize Files**: Open the scaffolded \`dev.ps1\`, \`dev.sh\`, \`deploy.ps1\`, \`deploy.sh\`, and the UI Sniper Telegram configuration (including the webhook route), and **modify them** to precisely match the project name and description.
+   c. **Telegram Feedback Customization**: Ensure the Telegram message for UI feedback exactly matches the project context (updating names, tags, or message format as needed).
+   d. **Rust Instructions**: Ensure dev and deploy scripts are surgically modified to correctly support the required Rust compilation/cargo instructions for the backend. **Never** overwrite the entire scripts with generic versions; preserve their robust functionality.
 4. Initialize a new git repository in the root directory (\`git init\`) and create an initial commit.
+5. Notify the user that the project has been contextualized, customized, and scaffolded. Remind them to run \`./dev.ps1\` or \`./dev.sh\`.
 `);
 
 // 4. Workflows

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "haraps",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "description": "NPM package to scaffold standard development environment, deployment scripts, AGENTS.md guidelines, and core workflows for a Next.js frontend + Rust Cloudflare Worker backend.",
   "main": "bin/index.js",
   "bin": {