🎨 Nexa Build: Project Documentation

📁 File Organization

This project is organized into three main folders based on development phases and relevance:

🏗️ ARCHITECTURE.md (Root)

Single source of truth for the hybrid approach implementation plan

• Complete 3-phase roadmap (Hybrid MVP → Optimization → Proprietary Engine)
• Detailed technical specifications and success criteria
• Implementation checklists and timelines
• This is the main document to reference for development

---

🚀 FirstRelease/

Files for immediate implementation (Phase 1: Hybrid MVP)

• requirements.md - Technical requirements and specifications
• backend.md - Backend architecture and implementation details
• frontend.md - User experience and onboarding flows
• installation.md - Installation methods and setup guides
• planning.md - Implementation roadmap and best practices
• promptcoach.md - Embedded prompt optimization functionality

---

🔮 Future/

Files for future phases (Phase 2-3: Optimization & Proprietary Engine)

• Future1.md - Long-term vision and proprietary engine plans

---

📚 Archive/

Reference materials and case studies

• casestudyfuture1.md - Real-world hybrid orchestration case studies
• answersoncasestudyfuture1.md - Feasibility analysis and recommendations
• feedbackfuture1.md - Senior developer feedback and insights
• Future.md - Original future vision document

---

🎯 Current Status

✅ COMPLETED

• Consolidated conflicting architectures into single source of truth
• Organized files into logical folder structure
• Created comprehensive hybrid approach plan
• Established realistic 3-week MVP timeline

🔄 NEXT STEPS

• Start Phase 1 implementation using ARCHITECTURE.md as guide
• Reference FirstRelease/ files for detailed specifications
• Use Archive/ case studies for proven patterns
• Plan future phases using Future/ documents

---

🚀 Getting Started

1. Read ARCHITECTURE.md - Understand the complete hybrid approach
2. Review FirstRelease/planning.md - See detailed implementation roadmap
3. Study Archive/casestudyfuture1.md - Learn from proven patterns
4. Begin Phase 1 - Start with MCP server foundation

---

💬 Using /nexa in Cursor Chat

Type these natural-language commands directly in Cursor’s chat using the /nexa tool. This triggers the MCP server tool named nexa (configured in .cursor/mcp.json) and routes your request to the correct engine.

Examples:

• /nexa Create a modern login form with email and password
• /nexa Validate the checkout page for a mobile user journey
• /nexa Generate A/B variants for the homepage hero; hypothesis: bigger CTA improves CTR
• /nexa Simulate personas interacting with src/components/Button.tsx
• /nexa Analyze the project structure and recommend improvements
• /nexa Deploy a preview of the current project

Notes:

• Chat in Cursor uses the MCP tool nexa; Terminal commands use the CLI nexa (legacy alias: nw).
• The same engines are used behind both interfaces; chat is not a separate CLI.

---

📋 Key Decisions Made

• Architecture: Hybrid approach (Dyad.sh + OSS registry) instead of proprietary engine
• Timeline: 3-week MVP → 2-week optimization → 6-week proprietary engine
• Commands: nexa for terminal CLI; /nexa for Cursor chat
• Branding: "Magic Nuggetwise" maintained throughout
• Tech Stack: OSS libraries + Dyad.sh + semantic search + preview deployment

---

This organization eliminates all conflicts and provides a clear path forward for Magic Nuggetwise development.

Nexa Build – Deployment

Deploy to Vercel (Production)

Option A – Static (frontend): keep root as frontend for simple pages.

Option B – Next.js app (apps/web):

• In Vercel: New Project → Import this repo
• Root Directory: apps/web
• Build Command: npm run build
• Output: (Next.js default)
• Domain: add nexa.build

Local dev

For Next.js app:

• cd apps/web
• npm i
• npm run dev
• open http://localhost:5173

For static pages:

• cd frontend && python3 -m http.server 8003
• open http://localhost:8003