星際農場

Project Scaffolding Prompt

Project Scaffolding Prompt

I want to build a full-stack "XXX" application. Please suggest appropriate core features for this app, then scaffold the entire project based on the requirements below.

🖥️ Frontend

  • Framework: Next.js (latest — currently v15+, App Router)

  • Package Manager: pnpm

  • Styling: Tailwind CSS

  • Routing: App Router (no Pages Router)

  • Follow best practices for Server Components, Client Components separation, and layout.tsx / page.tsx conventions

  • If an Admin Dashboard is needed for this app, scaffold it as a protected route segment (e.g., /admin) within the same Next.js project, or as a separate repository if complexity warrants it

⚙️ Backend

  • Framework: ASP.NET Core (latest stable)

  • Architecture: RESTful API with clean, layered structure (Controllers → Services → Repositories)

  • Image/File Uploads: Integrated with DigitalOcean Spaces (S3-compatible object storage) — please reference the patterns used in my existing meme-backend project for how the upload service, controller, and configuration are structured

  • Include: JWT authentication, proper CORS configuration, environment-based appsettings, and Swagger/OpenAPI docs

  • Use EF Core with a suitable database (PostgreSQL recommended) for data persistence

🐳 Deployment Architecture

Each repository will be independently containerized and deployed on a DigitalOcean VPS using Docker with Nginx as a reverse proxy.

Per-repository requirements:

  • A Dockerfile for building the production image

  • A docker-compose.yml for orchestrating the service(s), including any dependent infrastructure (e.g., database, cache)

  • All services must bind to 127.0.0.1 (localhost only) — they must never be exposed directly to the public internet

Nginx (reverse proxy):

  • Acts as the single public-facing entry point, routing traffic to each service by domain/subdomain or path prefix

  • Nginx config snippets should be provided for each service

  • SSL/TLS is terminated at the Nginx level using Certbot (Let's Encrypt); include notes or config for certificate issuance and auto-renewal

Environment & Secrets:

  • All sensitive values (DB credentials, Spaces keys, JWT secret, etc.) should be managed via .env files, referenced in docker-compose.yml — never hardcoded

  • Provide a .env.example template for each repository

📦 Repository Structure

Each part of the application (frontend, backend, admin dashboard if applicable) will live in its own independent Git repository — there is no monorepo. Please scaffold each repository as a fully self-contained project with its own:

  • README.md with setup and deployment instructions

  • Dockerfile and docker-compose.yml

  • .env.example with all required environment variables

  • Independent dependency management (pnpm for frontend, NuGet for backend)

All repositories are deployed independently on the same DigitalOcean VPS and connected through Nginx as the unified reverse proxy.

Stop asking me if I agree every time — just write everything out all at once.