DEV Community

Aisalkyn Aidarova
Aisalkyn Aidarova

Posted on

website plan

Yes — absolutely.

If you give Claude ONLY the URL of your website:
JumpToTech DevOps School

Claude can already:

  • analyze structure
  • detect pages
  • understand your business model
  • identify missing functionality
  • create Agile roadmap
  • create sprint planning
  • suggest architecture
  • suggest UI improvements
  • suggest database structure
  • detect UX issues
  • recommend enterprise workflow

Your website already has:

  • landing page
  • modules
  • lectures
  • student portal
  • registration
  • announcements
  • discussions
  • LMS concept
  • admin logic idea
  • DevOps branding
  • course structure (JumpToTech)

So Claude has enough context to become your:

  • Product Manager
  • Scrum Master
  • Senior Architect
  • Technical Lead

BUT…

The MOST IMPORTANT thing:

Do NOT ask:

“Build my website.”

Instead ask Claude like enterprise company.


THIS IS THE CORRECT WAY

STEP 1 — Ask Claude to Analyze

Prompt:

Analyze this website:
https://www.jump2techdevops.com

I am building a DevOps LMS platform using:
- Next.js
- Supabase
- Tailwind
- Vercel

Please analyze:
1. Current architecture
2. Missing functionality
3. UX problems
4. Scalability issues
5. Recommended folder structure
6. Database structure
7. Agile sprint roadmap
8. MVP vs future features
9. Enterprise best practices

Do NOT generate code yet.
Act like senior software architect.
Enter fullscreen mode Exit fullscreen mode

This is the FIRST thing.


STEP 2 — Ask for Agile Plan

Then:

Create Agile roadmap for this LMS project.

Split into:
- Epics
- Features
- User stories
- Sprints

Prioritize:
1. Stability
2. Authentication
3. Lecture system
4. Admin panel
5. Student experience
6. Payments
7. Scalability

Each sprint should:
- have goal
- tasks
- estimated complexity
- dependencies
- testing checklist
Enter fullscreen mode Exit fullscreen mode

Now Claude becomes Scrum Master.


STEP 3 — Build Sprint-by-Sprint

Then ONLY work on ONE sprint.

Example:

We are now working ONLY on Sprint 1.

Goal:
Fix navigation and lecture system.

Current problems:
- lecture not clickable
- admin/modules redirects incorrectly
- preview broken

Please:
1. explain probable root cause
2. create debugging checklist
3. create implementation plan
4. generate only necessary code changes
Enter fullscreen mode Exit fullscreen mode

THIS is the key.


YOUR WEBSITE SHOULD BE BUILT LIKE THIS

EPIC 1 — FOUNDATION

  • routing
  • navbar
  • footer
  • responsive layout
  • dark/light mode

EPIC 2 — AUTHENTICATION

  • login
  • register
  • student/admin roles
  • protected routes

EPIC 3 — LMS CORE

  • modules
  • lectures
  • markdown rendering
  • progress tracking

EPIC 4 — ADMIN PANEL

  • create module
  • edit lecture
  • upload files
  • analytics

EPIC 5 — STUDENT EXPERIENCE

  • dashboard
  • certificates
  • quizzes
  • notes

EPIC 6 — BUSINESS

  • Stripe
  • subscriptions
  • coupons
  • invoices

EPIC 7 — DEVOPS

  • Docker
  • CI/CD
  • ECS
  • monitoring
  • backups

MOST IMPORTANT FOR AI CODING

You need these files FIRST:

PROJECT_DOCS/

Inside:

architecture.md

Frontend: Next.js
Backend: Supabase
Auth: Supabase Auth
Hosting: Vercel
Storage: Supabase Storage
Enter fullscreen mode Exit fullscreen mode

routes.md

/
/modules
/modules/[slug]
/admin
/admin/modules
/admin/lectures
/dashboard
Enter fullscreen mode Exit fullscreen mode

database.md

users
modules
lectures
progress
payments
Enter fullscreen mode Exit fullscreen mode

coding-rules.md

- Use TypeScript
- Use App Router
- Reusable components only
- No duplicated UI
- Mobile-first
Enter fullscreen mode Exit fullscreen mode

AI performs MUCH better with this.


BEST TOOL COMBINATION FOR YOU

Claude

Use for:

  • architecture
  • debugging
  • sprint planning
  • backend logic
  • technical decisions

Antigravity / Lovable

Use for:

  • frontend pages
  • animations
  • responsive design
  • visual sections

VS Code + GitHub

Use for:

  • version control
  • rollback
  • manual fixes

VERY IMPORTANT

Right now your website is already at:
“startup MVP stage”

Meaning:

  • not prototype anymore
  • now architecture matters

So random prompting becomes dangerous.

Now you need:

  • Agile
  • documentation
  • Git discipline
  • sprint isolation
  • reusable components
  • stable releases

Exactly like enterprise engineering.


MY RECOMMENDATION FOR YOUR NEXT 48 HOURS

DO NOT add new features.

ONLY:

Sprint Stabilization

Fix:

  • module navigation
  • lecture clickability
  • admin routing
  • lecture rendering
  • markdown support

Then freeze system.

Commit stable version.

Only after that continue.

That is exactly how real SaaS teams work.

Top comments (0)