gaslighting-engine 0.1.0

package/examples/landing-page/MEMORY.md

@@ -0,0 +1,63 @@
+# MEMORY.md
+
+This is the local project memory for Gaslighting-engine.
+
+It is inspired by agent memory systems, but it is not a vague diary.
+
+It records stable project facts, recurring workflow rules, known failure patterns, and decisions that future AI-agent sessions must not forget.
+
+Keep required rules in `AGENTS.md`, `GASLIGHTING.md`, and checked-in documents. Treat this file as a compact recall layer, not the only source of truth.
+
+## Stable Project Facts
+
+- Original request: Build a landing page for a new service that captures leads.
+- Project type: landing_page
+- Classification confidence: high
+- Stack hints: none
+
+## Working Preferences
+
+- Prefer the shortest useful command: `gaslighting "project request"`.
+- Default discipline mode is hardcore.
+- Full-scope enforcement is default.
+- No-TODO escape prevention is default.
+- No-shortcut enforcement is default.
+- Missing information should be assumed, documented, and carried forward unless truly blocking.
+
+## Known Agent Failure Patterns
+
+- Summarizing remaining work instead of doing it.
+- Treating representative examples as full implementation.
+- Using TODO comments as a substitute for requested work.
+- Creating placeholders and calling them structure.
+- Forgetting the project purpose after the first implementation pass.
+- Over-engineering instead of delivering the concrete MVP.
+
+## Hades-Style Audit Rules
+
+These are cleanup and verification rules:
+
+- Zero fake completion.
+- Zero TODO escape.
+- Zero dead placeholder files pretending to be implementation.
+- Zero unexplained scope reductions.
+- Zero unverified success claims.
+- Every destructive cleanup must be intentional and explainable.
+- If code or files are removed, record why in `DECISION_LOG.md`.
+
+## Memory Write Rules
+
+Add to this file only when a fact is stable and useful across future sessions.
+
+Do not store secrets, API keys, credentials, private tokens, or sensitive personal data.
+
+When a memory becomes wrong, do not silently delete it. Mark it outdated and append the corrected fact.
+
+## Current Assumptions To Remember
+
+- The page has one primary conversion goal.
+- Offer details are temporary and must be replaced by the owner.
+- A lead form and repeated CTA path are required.
+- Use the default practical web stack unless the user later specifies otherwise.
+- Build an MVP that can be implemented locally without a SaaS backend for this generator.
+- Treat unspecified brand/content details as temporary copy that must be human-reviewed before production.

package/examples/landing-page/MISSING_INFO.md

@@ -0,0 +1,13 @@
+# MISSING_INFO.md
+
+Missing information must be classified honestly.
+
+Most missing information is not blocking.
+
+If information is missing but implementation can proceed with a practical assumption, document it and continue.
+
+| Item | Current Status | Temporary Assumption | Impact | Blocking? | Recommended Action |
+|---|---|---|---|---|---|
+| Exact offer and conversion goal | Missing but non-blocking | Use one primary lead capture CTA. | high | risky but workable | Confirm the offer, target audience, ad source, CTA, and lead destination. |
+| Final brand identity and production copy | Missing but non-blocking | Use clear temporary copy and document it as replaceable. | medium | blocking before production | Collect final brand name, tone, assets, and legally approved copy before launch. |
+| Exact deployment credentials and accounts | Missing but non-blocking | Prepare the app for Vercel-style deployment without requiring credentials during implementation. | medium | blocking before production | Add project-specific env vars and provider accounts before production deployment. |

package/examples/landing-page/PRD.md

@@ -0,0 +1,103 @@
+# PRD.md
+
+## 1. Product Overview
+
+Build an MVP for this request:
+
+> Build a landing page for a new service that captures leads.
+
+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/STACK_POLICY.md

@@ -0,0 +1,64 @@
+# STACK_POLICY.md
+
+## Detected Stack Hints
+
+- No stack hints detected.
+
+If detected stack hints conflict with the project purpose, the project purpose wins.
+
+## Default Web Stack
+
+- Framework: Next.js latest stable version
+- Language: TypeScript
+- Styling: Tailwind CSS
+- UI: shadcn/ui
+- Database: PostgreSQL
+- DB Provider: NeonDB first, Supabase alternative
+- Hosting: Vercel
+- File Storage: Vercel Blob or Cloudflare R2
+- Analytics: GA4 + Google Tag Manager
+- Email: Resend or equivalent
+- ORM: Prisma or Drizzle
+
+## Stack Selection Rules
+
+### Choose NeonDB when
+
+- The project needs PostgreSQL.
+- The project is deployed on Vercel.
+- Serverless-friendly PostgreSQL is useful.
+- A clean MVP database is enough.
+
+### Choose Supabase when
+
+- Auth, DB, and storage should be bundled.
+- Admin/user accounts are likely.
+- The project benefits from Supabase dashboard operations.
+- Storage and database need to live together.
+
+### Choose Vercel Blob when
+
+- The project is Vercel-centered.
+- File uploads are simple.
+- Operational simplicity matters.
+
+### Choose Cloudflare R2 when
+
+- Storage volume may grow.
+- CDN/cost strategy matters.
+- Cloudflare DNS/cache is already part of the plan.
+
+## Forbidden by Default
+
+Do not introduce the following unless explicitly required:
+
+- Kubernetes
+- Kafka
+- RabbitMQ
+- Microservices
+- GraphQL Federation
+- Redis Cluster
+- Terraform-heavy infrastructure
+- Event sourcing
+- Multi-region deployment
+- Complex distributed systems

package/package.json

@@ -0,0 +1,37 @@
+{
+  "name": "gaslighting-engine",
+  "version": "0.1.0",
+  "description": "LUDGI Gaslighting-engine: a hardcore project-discipline generator for AI coding agents.",
+  "type": "module",
+  "license": "MIT",
+  "bin": {
+    "gaslighting-engine": "dist/index.js",
+    "gaslighting": "dist/index.js"
+  },
+  "files": [
+    "dist",
+    "docs",
+    "examples",
+    ".codex",
+    "README.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "build": "tsc",
+    "start": "node dist/index.js",
+    "dev": "tsx src/index.ts",
+    "test": "npm run build && node dist/index.js doctor --path examples/hospital-homepage"
+  },
+  "dependencies": {
+    "commander": "^14.0.2"
+  },
+  "devDependencies": {
+    "@types/node": "^24.10.1",
+    "tsx": "^4.20.6",
+    "typescript": "^5.9.3"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "packageManager": "pnpm@10.22.0"
+}