gaslighting-engine 0.3.1 → 0.4.1

package/examples/landing-page/.gaslighting/operations/GIT.md

@@ -0,0 +1,7 @@
+# Git Operations
+
+Project root: `examples/landing-page`
+
+- Keep meaningful checkpoints.
+- Do not rewrite user changes.
+- Record remote changes in decisions.

package/examples/landing-page/.gaslighting/operations/GITHUB.md

@@ -0,0 +1,7 @@
+# GitHub Operations
+
+Project root: `examples/landing-page`
+
+- If no GitHub remote exists, ask for the GitHub URL and offer to connect it.
+- If a remote exists, preserve it unless the user explicitly asks to replace it.
+- Push only when permission mode allows it or approval is granted.

package/examples/landing-page/.gaslighting/operations/PROJECT_CARE.md

@@ -0,0 +1,75 @@
+# PROJECT_CARE.md
+
+This file is the project-care ledger for Gaslighting-engine.
+
+It is not a blocker wall.
+
+It is the place where the agent keeps noticing operational risk, ownership gaps, Git/GitHub status, deployment readiness, domain ownership, and missing production decisions.
+
+The agent must treat this project as mission-critical. If something can put delivery, trust, data, launch, SEO, legal compliance, or operations at risk, record it here and keep pushing it forward.
+
+## Project Snapshot
+
+- Date: 2026-05-23
+- Original request: Build a landing page for lead capture.
+- Project type: landing_page
+- Classification confidence: high
+- Project purpose:
+  - make the offer clear within 5 seconds
+  - drive CTA clicks
+  - capture leads
+  - support ad traffic
+  - reduce bounce
+  - communicate value clearly
+  - load fast on mobile
+
+## Git And GitHub Registry
+
+| Item | Status | Next Action |
+|---|---|---|
+| Git repository | Detected, branch `main` | Commit meaningful checkpoints. |
+| Origin remote | `https://github.com/nohsangwoo/GaslightingEngineering.git` | Keep remote ownership recorded when it changes. |
+| GitHub remote | Detected | Use GitHub as the source-of-truth remote. |
+
+## Domain And Deployment Registry
+
+| Item | Current Status | Risk | Next Action |
+|---|---|---|---|
+| Production domain | Missing | Users cannot reach production reliably. | Confirm domain owner, DNS provider, and final domain. |
+| DNS provider | Missing | Launch can be delayed by DNS access issues. | Record provider, account owner, and nameserver strategy. |
+| Deployment target | Not confirmed | Environment drift and launch confusion. | Confirm Vercel, Netlify, Cloudflare, or other target. |
+| Preview URL policy | Missing | Stakeholders cannot review safely. | Decide preview deployment workflow. |
+| Rollback path | Missing | Production incidents become slower to recover. | Define rollback command/provider workflow. |
+
+## Care Checklist
+
+- [x] Git repository: Git repository detected on branch main. Next: Keep committing discipline and implementation changes.
+- [x] GitHub remote: GitHub remote detected: https://github.com/nohsangwoo/GaslightingEngineering.git Next: Record repository decisions in DECISION_LOG.md when remote ownership changes.
+- [ ] Project package file: package.json is missing. Next: Create package.json when implementation starts, unless this is not a Node project.
+- [ ] Deployment target: No explicit deployment config detected. Next: Confirm deployment target, production domain, preview environment, and rollback path before launch.
+- [ ] Environment template: .env.example is missing. Next: Add .env.example before sharing the project so required secrets are visible without exposing real values.
+- [ ] Production domain confirmed.
+- [ ] DNS owner confirmed.
+- [ ] Deployment provider confirmed.
+- [ ] Analytics ownership confirmed.
+- [ ] Form/email delivery owner confirmed.
+- [ ] Privacy/legal review path confirmed.
+- [ ] Launch checklist created before production release.
+
+## Agent Care Rules
+
+- Do not stop implementation just because an operational detail is missing.
+- Do make a practical assumption, record it, and keep moving.
+- If Git is not initialized, ask for a GitHub URL and offer the exact commands.
+- If Git is initialized but no GitHub remote exists, ask for the remote URL and offer `git remote add origin <url>`.
+- If the user provides a GitHub URL, run `gaslighting-engine care --github-url <url>` or connect it directly with Git CLI.
+- If GitHub is connected, record the remote URL here and in `DECISION_LOG.md` when it changes.
+- If domain or deployment details are missing, keep warning until they are confirmed.
+- Treat missing domain, deployment, analytics, email, and privacy ownership as mission-critical launch risks, not as reasons to abandon the task.
+- Never turn care warnings into fake blockers.
+
+## Current Care Warnings
+
+- Project package file: package.json is missing. Action: Create package.json when implementation starts, unless this is not a Node project.
+- Deployment target: No explicit deployment config detected. Action: Confirm deployment target, production domain, preview environment, and rollback path before launch.
+- Environment template: .env.example is missing. Action: Add .env.example before sharing the project so required secrets are visible without exposing real values.

package/examples/landing-page/.gaslighting/pages/single-landing-page-with-hero-problem-solution-benefits-social-p/ACCEPTANCE.md

@@ -0,0 +1,7 @@
+# Single landing page with Hero, Problem, Solution, Benefits, Social Proof, Process, Offer, FAQ, Final CTA, Lead Form Acceptance Criteria
+
+- [ ] Page purpose is visible.
+- [ ] Required content is not placeholder-only.
+- [ ] CTA or operational action is usable.
+- [ ] Mobile layout is usable.
+- [ ] No TODO replaces implementation.

package/examples/landing-page/.gaslighting/pages/single-landing-page-with-hero-problem-solution-benefits-social-p/PAGE_PRD.md

@@ -0,0 +1,15 @@
+# Single landing page with Hero, Problem, Solution, Benefits, Social Proof, Process, Offer, FAQ, Final CTA, Lead Form Page PRD
+
+Project type: `landing_page`
+
+## Purpose
+
+This page must support the project purpose and not become decorative filler.
+
+## Required Coverage
+
+- Clear user goal.
+- Clear content hierarchy.
+- Clear CTA or operational action.
+- Mobile usability.
+- Empty/error states when relevant.

package/examples/landing-page/.gaslighting/product/PAGE_MAP.md

@@ -0,0 +1,3 @@
+# Page Map
+
+- [ ] Single landing page with Hero, Problem, Solution, Benefits, Social Proof, Process, Offer, FAQ, Final CTA, Lead Form: define purpose, content, CTA, empty state, and acceptance criteria.

package/examples/landing-page/.gaslighting/product/PRD.md

@@ -0,0 +1,103 @@
+# PRD.md
+
+## 1. Product Overview
+
+Build an MVP for this request:
+
+> Build a landing page for lead capture.
+
+Classified project type: `landing_page`
+
+The product must preserve the user's actual scope and must not become a decorative shell.
+
+## 2. Business Purpose
+
+- make the offer clear within 5 seconds
+- drive CTA clicks
+- capture leads
+- support ad traffic
+- reduce bounce
+- communicate value clearly
+- load fast on mobile
+
+## 3. Target Users
+
+- Ad traffic visitors
+- Qualified leads
+- Operators reviewing submitted leads
+
+## 4. User Flows
+
+- Visitor -> understand offer -> compare benefits -> submit lead form
+- Visitor -> FAQ/social proof -> final CTA
+
+## 5. Page List
+
+- Single landing page with Hero, Problem, Solution, Benefits, Social Proof, Process, Offer, FAQ, Final CTA, Lead Form
+
+## 6. Feature List
+
+- responsive design
+- CTA buttons
+- lead form
+- conversion-oriented copy
+- SEO metadata
+- fast loading
+- analytics-ready structure
+
+## 7. Data Model Draft
+
+- Lead: name, emailOrPhone, source, message, consent, createdAt
+- Offer: headline, benefits, proof, CTA
+
+## 8. MVP Scope
+
+- Implement all pages, flows, and features listed above.
+- Include responsive behavior.
+- Include useful empty, loading, success, and error states where applicable.
+- Include SEO metadata where public pages exist.
+- Include analytics-ready structure where conversion matters.
+- Document every assumption that affects implementation.
+
+## 9. Out of Scope
+
+- LLM API integration unless explicitly requested
+- complex infrastructure
+- unrequested authentication
+- unrequested payments
+- native mobile apps
+
+## 10. Non-Functional Requirements
+
+- Mobile-first where users are likely to arrive from search or ads.
+- Accessible semantic HTML.
+- Fast initial load for public pages.
+- Safe form validation and clear error messages.
+- Maintainable TypeScript structure.
+- No unnecessary distributed systems.
+
+## 11. Tech Stack
+
+No stack hints were provided. Use the default practical web stack unless the user later changes it.
+
+See `STACK_POLICY.md` for defaults and forbidden-by-default technology.
+
+## 12. Risks
+
+- Vague source requirements can cause wrong vertical assumptions.
+- Placeholder copy can look real if not reviewed.
+- Missing production credentials can block deployment.
+- AI agents may reduce scope unless `GASLIGHTING.md` is enforced.
+
+## 13. Missing Information
+
+See `MISSING_INFO.md`.
+
+## 14. Success Criteria
+
+- The project purpose is visible in the implemented product.
+- The core pages and features are implemented, not merely described.
+- No required scope is replaced by representative examples.
+- No TODO is used as a substitute for implementation.
+- Assumptions and decisions remain documented.
+- The output can actually be used for the MVP purpose.

package/examples/landing-page/.gaslighting/product/USER_FLOWS.md

@@ -0,0 +1,14 @@
+# User Flows
+
+Project type: `landing_page`
+
+## Primary Flow
+
+1. User lands on the first relevant page.
+2. User understands the offer or purpose quickly.
+3. User explores the page or feature set needed for trust and decision-making.
+4. User completes the primary conversion or operational action.
+
+## Page Coverage
+
+1. Single landing page with Hero, Problem, Solution, Benefits, Social Proof, Process, Offer, FAQ, Final CTA, Lead Form

package/examples/landing-page/.gaslighting/tasks/TASK-0001.md

@@ -0,0 +1,17 @@
+# TASK-0001: Initialize Mission Scope
+
+Status: pending
+Runtime: codex
+Permission mode: auto_review
+
+## Goal
+
+Turn the original request into implemented project work without fake completion.
+
+## Request
+
+> Build a landing page for lead capture.
+
+## Project Type
+
+`landing_page`

package/examples/landing-page/.gaslighting/verification/latest-report.md

@@ -0,0 +1,3 @@
+# Latest Verification Report
+
+No verification has run yet.

package/examples/landing-page/AGENTS.md

@@ -4,18 +4,20 @@ This repository uses Gaslighting-engine.
 
 The main discipline documents live under `.gaslighting/` to avoid cluttering the project root.
 
+Start with `.gaslighting/INDEX.md`. It points to the mission, product, feature, operation, task, loop, verification, and memory documents.
+
 Before doing any work, read these files in order:
 
-1. `.gaslighting/GASLIGHTING.md`
-2. `.gaslighting/PRD.md`
-3. `.gaslighting/STACK_POLICY.md`
-4. `.gaslighting/MISSING_INFO.md`
-5. `.gaslighting/ASSUMPTIONS.md`
-6. `.gaslighting/DECISION_LOG.md`
-7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/AGENT_RUNTIME.md`
-9. `.gaslighting/PROJECT_CARE.md`
-10. `.gaslighting/AGENTS.md`
+1. `.gaslighting/INDEX.md`
+2. `.gaslighting/mission/PROJECT_PURPOSE.md`
+3. `.gaslighting/mission/EXECUTION_RULES.md`
+4. `.gaslighting/mission/COMPLETION_STANDARD.md`
+5. `.gaslighting/product/PRD.md`
+6. `.gaslighting/product/PAGE_MAP.md`
+7. `.gaslighting/features/core-scope/TASKS.md`
+8. `.gaslighting/operations/PROJECT_CARE.md`
+9. `.gaslighting/loops/current-session.json`
+10. `.gaslighting/GASLIGHTING.md`
 
 Do not reduce scope.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gaslighting-engine",
-  "version": "0.3.1",
+  "version": "0.4.1",
   "description": "LUDGI Gaslighting-engine: a hardcore project-discipline generator for AI coding agents.",
   "type": "module",
   "license": "MIT",
@@ -10,6 +10,7 @@
   },
   "files": [
     "dist",
+    "desktop-dist",
     "docs",
     "examples",
     ".agents",
@@ -18,21 +19,37 @@
     "LICENSE"
   ],
   "scripts": {
-    "build": "tsc",
+    "build": "npm run build:cli && npm run build:desktop",
+    "build:cli": "tsc",
+    "build:desktop": "vite build --config desktop/vite.config.ts",
+    "prepack": "npm run build",
     "start": "node dist/index.js",
     "dev": "tsx src/index.ts",
+    "desktop:dev": "vite --config desktop/vite.config.ts",
     "test": "npm run build && node dist/index.js doctor --path examples/hospital-homepage"
   },
   "dependencies": {
-    "commander": "^14.0.2"
+    "@xterm/xterm": "^6.0.0",
+    "commander": "^14.0.2",
+    "lucide-react": "^1.16.0",
+    "react": "^19.2.6",
+    "react-dom": "^19.2.6"
   },
   "devDependencies": {
     "@types/node": "^24.10.1",
+    "@types/react": "^19.2.15",
+    "@types/react-dom": "^19.2.3",
+    "@vitejs/plugin-react": "^6.0.2",
+    "electron": "^42.2.0",
     "tsx": "^4.20.6",
-    "typescript": "^5.9.3"
+    "typescript": "^5.9.3",
+    "vite": "^8.0.14"
   },
   "engines": {
     "node": ">=20"
   },
-  "packageManager": "pnpm@10.22.0"
+  "packageManager": "pnpm@10.22.0",
+  "optionalDependencies": {
+    "node-pty": "^1.1.0"
+  }
 }