haraps 1.0.8 → 1.0.10

package/bin/index.js

@@ -13,8 +13,12 @@ function ensureDir(dir) {
     }
 }
 
-function writeFile(filePath, content) {
+function writeFile(filePath, content, skipIfExists = false) {
     const fullPath = path.resolve(process.cwd(), filePath);
+    if (skipIfExists && fs.existsSync(fullPath)) {
+        console.log(`⏭️  Skipped: ${filePath} (already exists)`);
+        return;
+    }
     ensureDir(path.dirname(fullPath));
     fs.writeFileSync(fullPath, content.trim() + '\n', 'utf8');
     console.log(`✅ Created: ${filePath}`);
@@ -382,7 +386,7 @@ EOF
 
 node "$runnerPath"
 
-`);
+`, true);
 fs.chmodSync(path.resolve(process.cwd(), 'dev.sh'), '755');
 
 writeFile('dev.ps1', `
@@ -796,7 +800,7 @@ if ($null -ne (Get-Variable -Name watcherJob -ErrorAction SilentlyContinue)) {
     }
 }
 
-`);
+`, true);
 
 // 2. Deploy Scripts
 writeFile('deploy.sh', `
@@ -811,7 +815,7 @@ cd /mnt/c/Users/shivg/Desktop/Hara-XY/mediqueue-main/mediqueue/frontend
 $env:WRANGLER_SEND_METRICS="false"
 npx wrangler pages deploy .vercel/output/static
 
-`);
+`, true);
 fs.chmodSync(path.resolve(process.cwd(), 'deploy.sh'), '755');
 
 writeFile('deploy.ps1', `
@@ -1230,7 +1234,7 @@ Write-Host "[CLIPBOARD] Full report copied to your clipboard!" -ForegroundColor
 Write-Host ""
 Write-Host ">>> Deployment localized and verified." -ForegroundColor Cyan
 
-`);
+`, true);
 
 // 3. Agent Rules
 writeFile('AGENTS.md', `
@@ -1255,6 +1259,12 @@ writeFile('AGENTS.md', `
 18. **Environment Variable Validation**: Fail fast at startup if required \`.env\` variables are missing.
 19. **Kill AI Slop**: Remove aesthetic clichés (indigo gradients, glowing cards, excessive emojis) that serve no functional purpose.
 20. **Security First Principle**: Treat all external input as malicious; leverage the Security Review skill for all external-facing endpoints.
+21. **Standardized Work Delivery**: When completing a task, always provide:
+    - Links or Routes for the work done (clickable URLs/paths).
+    - Manual steps for the user to verify the work.
+    - 3 Things to improve (technical debt, minor issues, or polish).
+    - Future roadmap (what can be done next for the work currently completed).
+22. **Scratch Files**: Any temporary, one-off, or scratch scripts (like \`fix_css.js\`, testing scripts, or data dumps) MUST be placed in a dedicated \`scratch/\` folder at the root. Never clutter the project root directory with these files.
 
 # Start Project Protocol
 When the user says "start project", you MUST immediately:
@@ -1267,6 +1277,21 @@ When the user says "start project", you MUST immediately:
    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\`.
+
+# Continuous Documentation Protocol
+As we develop the project, you MUST maintain living user and developer documentation.
+1. **Always Document**: Every new feature, API route, or major change must be documented immediately.
+2. **Types of Docs**: Include API specifications, how-to guides, architectural overviews, and user instructions.
+3. **Index Everything**: Maintain a well-organized and updated index of all documentation files in the section below.
+
+# Project Documentation Index
+*Keep this section constantly updated as new documentation is written.*
+
+### Frontend Documentation
+- [Developer & User Guide](file:///frontend/src/app/docs/page.tsx) - The primary documentation route for users.
+
+### Backend Documentation
+*(No backend documentation yet. Add API guides and architecture notes here.)*
 `);
 
 // 4. Workflows

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "haraps",
-  "version": "1.0.8",
+  "version": "1.0.10",
   "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": {

package/SKILL.md

@@ -1,46 +0,0 @@
----
-name: scaffold-project-env
-description: Scaffolds the standard development environment, deployment scripts, AGENTS.md guidelines, and core workflows for a Next.js frontend + Rust Cloudflare Worker backend.
----
-
-# Scaffold Project Environment Skill (Rust + Next.js)
-
-This skill automatically sets up a new repository with standard `dev` and `deploy` scripts tailored for a Rust backend (Cloudflare Workers) and a standard Next.js frontend (Vercel/Node deployment, not Pages), along with preferred agent guidelines and workflows.
-
-## Instructions for the Agent
-
-When the user runs this skill, execute the following steps precisely:
-
-### Step 1: Run the Scaffolder CLI
-
-Execute the following command in the terminal to automatically generate the project scaffolding (dev scripts, deploy scripts, AGENTS.md, workflows, and skills):
-
-```bash
-npx --yes haraps
-```
-
-### Step 2: Verification
-
-Verify that the following files were successfully created in the root directory:
-- `dev.sh` / `dev.ps1`
-- `deploy.sh` / `deploy.ps1`
-- `AGENTS.md`
-- `.agents/workflows/git-it.md`
-- `.agents/workflows/deploy-and-talk.md`
-- `.agents/skills/ponytail/SKILL.md`
-- `.agents/skills/ui-sniper-telegram/SKILL.md`
-- `.agents/skills/kill-ai-slop/SKILL.md`
-- `.agents/skills/security-review/SKILL.md`
-
-### Step 3: Project Skeleton Initialization (First Run)
-
-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. **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 contextualized, customized, and scaffolded. Remind them to run `./dev.ps1` or `./dev.sh`.