Aveenix Full-Stack Debug and Integration

Full-Stack Debugging & Integration Expert
Overview
Aveenix is an all-in-one AI-powered platform combining E-Commerce, SaaS Business Apps, and AI automation. The platform uses a modular architecture built with:
• Frontend: React (TypeScript) + Tailwind CSS
• Backend: Node.js (Express) + PostgreSQL (Neon) + Drizzle ORM
• Environments: Replit (development), GitHub (version control), Railway (deployment)
The system has two main pillars:
1. Aveenix Express (E-Commerce) — Affiliate, dropshipping, and branded product marketplace with multi-vendor support, WooCommerce API integration, and Stripe payments.
2. Aveenix Digital (SaaS Apps) — Suite of business management modules (CRM, Invoicing, Analytics, HR, Projects, Calendar, POS, Rewards, etc.) under a single login/dashboard, with role-based access and theming.
Production-ready foundations already exist:
Authentication
Light/Dark theming with accents
Jarvis AI assistant
Responsive UI
Admin dashboards
Product import/approval flow
E-commerce skeleton pages (cart, checkout, vendor, account)
________________________________________
Development & Deployment Workflow (Replit → GitHub → Railway)
To ensure smooth collaboration and avoid version conflicts, the setup is standardized across environments:
1. Replit (Development Sandbox)
o Each developer works in a feature branch.
o Testing happens directly in Replit with hot-reload and debug tools.
o Replit DB can be used for local mocks; Neon PostgreSQL used for integration testing.
2. GitHub (Source of Truth)
o Branches:
 main → production-ready code (always stable).
 dev → staging/integration branch (all features tested together).
 feature/* → per-task branches.
o All changes merged via PR with code review.
o CI/CD: linting, testing, and build checks run automatically on PRs.
3. Railway (Staging + Production Deployment)
o Railway pulls directly from GitHub.
o Staging: optional deploys from dev.
o Production: auto-deploy from main.
o Rollbacks: one-click revert to previous deploy.
o Backups: Neon PostgreSQL auto-backups enabled; Railway env vars stored securely.
________________________________________
Immediate Priorities
Phase 1 – Get E-Commerce Live (Top Priority)
1. Environment Setup (first task)
o Protect main branch; enforce PR + passing checks.
o Create backup-pre-stabilize branch for safe rollback.
o Configure GitHub Actions CI: npm run lint → npm run typecheck → npm run build.
o Enable Railway Preview Deploys for PRs and verify rollback strategy.
o Document environment variables:
 VITE_STRIPE_PUBLIC_KEY, STRIPE_SECRET_KEY
 VITE_WOO_BASE_URL, VITE_WOO_KEY, VITE_WOO_SECRET
2. Clean & Stabilize the Codebase
o Remove duplicate pages, redundant code, and inconsistencies.
o Standardize layout, navigation, and component reuse.
o Split oversized files (>300 LOC) into subcomponents.
o Move uncertain/legacy versions to /legacy/ (don’t delete outright).
o Add Error Boundaries to PLP (/category/:slug), PDP, and Checkout routes.
3. Launch E-Commerce with Affiliate + Dropshipping
o Finalize product workflows (affiliate, dropship).
o Complete checkout and payment flows (WooCommerce + Stripe test → production).
o Polish vendor onboarding + dashboard.
o Ensure in-app rewards tracking (affiliate + dropship).
4. Deploy Production E-Commerce
o Test staging deploys from dev.
o Deploy stable main branch to production.
o Confirm full sales flow is live and bug-free.
Phase 2 – Expand After E-Commerce Launch
• Complete Rewards & Payouts dashboard (admin approval, reporting).
• Expand workflows to include custom + multi-vendor products.
• Strengthen SaaS modules (CRM, Sales, Analytics, HR, Helpdesk, etc.).
• Add missing apps (Expenses, Surveys, SMS Marketing).
• Enforce role-based permissions across all modules.
________________________________________
Acceptance Criteria (Definition of Done)
• PR from stabilize-ecommerce → main where:
o CI is green (lint, typecheck, build).
o Railway Preview URL loads successfully.
o Smoke test path works end-to-end:
Home → Category (PLP) → Product (PDP) → Add to Cart → Cart → Checkout → Account.
o LAUNCH_NOTES.md (setup, env vars, changes) and CHANGELOG.md included.
o Git tag created for the green commit (e.g., v0.1.0-stable).
o Railway production deploy succeeds after merge.
o Previous deploy available for rollback.
________________________________________
Tech Stack
• Frontend: React (TypeScript), Tailwind CSS
• Backend: Node.js (Express), PostgreSQL (Neon), Drizzle ORM
• Integrations: WooCommerce API, Stripe API, SMTP/Email
• Environments: Replit (development), GitHub (source control), Railway (deployment)
________________________________________
Ideal Skills & Experience
• Strong debugging and troubleshooting skills.
• Proven experience with CI/CD pipelines (GitHub Actions → Railway).
• Hands-on with WooCommerce + Stripe API integrations.
• Familiarity with end-to-end testing tools (Playwright, Cypress, Puppeteer).
• Experience with multi-vendor marketplaces and SaaS dashboards.
• Bonus: PWA, mobile responsiveness, AI API integration experience.
________________________________________
Application Requirements
• Share relevant project links (marketplaces, SaaS apps, API-heavy projects).
• Describe your approach to testing, cleaning, and deployment.
• Provide a portfolio of similar projects.
• Explain your strategy for ensuring bug-free, production-ready deployments.
• Applications without portfolio links and answers to these questions will not be considered.
________________________________________
Goal
Deliver a stable, deployable version of the Aveenix e-commerce platform.
Success = stable build, cleaned codebase, required routes/pages working, CI/CD pipeline live, rollback/backup strategies proven, and full e-commerce sales flow operational.