C
Claude Flow v2.3 · Nota Kelas
AI-Native Workflow

Claude AI
Dev Flow.

Enterprise workflow blueprint dengan strategi optimisasi token yang menjimatkan kos sehingga 85%.

Phases
11
Development
Tips
10
Token saving
Models
3
Tier matrix
Window
5h
Rolling reset
Overview

Token economy dulu.

Sebelum develop, faham macam mana Claude makan token.

Layer 00 cost · efficiency

Setiap mesej ada kos.

Mesej awal ~200 token. Mesej ke-30 boleh sampai 50,000 token kerana Claude baca semula seluruh history.

!
Insight: Dokumen panjang, extended thinking, dan web search adalah top 3 penyumbang token. Optimize chat lifecycle sebelum apa-apa.
Quick start

Mula dari sini.

Tap menu di bawah untuk navigate antara sections.

Start here

3 langkah permulaan.

1
Setup Memory & Custom Instructions Settings → Memory & User Preferences. Setup sekali sahaja.
2
Create Claude Project Upload semua reusable assets ke dalam Projects.
3
Plan sebelum code Analyze architecture dulu. Phase-by-phase migration.
Tutorial Setup

Nota Kelas.

Video langkah demi langkah untuk pasang tools yang anda perlukan.

5 Videos tools · setup

Setup tools dari sifar.

Tonton tutorial step-by-step untuk install semua tools yang diperlukan untuk start develop dengan Claude.

01
Download & Install Claude AI Setup Claude desktop app & web access.
02
Download & Install Git Version control essential untuk semua project.
03
Daftar GitHub Cloud repository untuk simpan & manage code.
04
Download & Install Python Required untuk Claude Code & scripting.
05
Download & Install XAMPP Local server untuk develop PHP/MySQL apps.
Buka Tab Baru (Full Screen)
notakelasclaude.lovable.app
📺
Embedded live: Scroll dalam frame untuk tonton 5 video tutorials. Tap ⛶ Fullscreen untuk pengalaman penuh.
Optimization

10 cara jimat token.

Practical habits untuk maximize plan Claude harian.

1
Edit prompt, jangan hantar follow-upKlik edit pada mesej asal, betulkan, regenerate. Follow-up baru tambah conversation history.
2
New chat setiap 15–20 mesejMinta summary, copy, paste dalam chat baru. Reset context = reset cost.
3
Gabung soalan dalam satu mesej3 soalan = 1 turn, bukan 3 turn. Jawapan lebih baik.
4
Upload fail ke ProjectsPDF, brief, guideline — upload sekali. Projects cache, tak charge token berulang.
5
Setup Memory & Custom InstructionsSetup sekali. Claude ingat selama-lamanya.
6
Tutup feature yang tak gunaWeb search, Research mode, Connectors — off kalau tak guna.
7
Guna Haiku untuk kerja ringanBrainstorm, formatting, grammar — guna Haiku. Simpan Opus untuk kerja berat.
8
Bahagikan kerja 2–3 sesi sehariRolling 5-jam window. Split = 150–200 mesej vs hentam sekali = 45.
9
Pantau task yang makan tokenDokumen panjang, extended thinking, web search — top 3.
10
Bina prompt library reusableSave prompts berkesan. Copy-paste lebih jimat.
Sessions

5-jam rolling window.

Bahagikan kerja kepada sesi untuk maksimumkan output.

🌅
Sesi 1
08:00 — 13:00
Planning & architecture (Opus)
☀️
Sesi 2
14:00 — 19:00
Implementation (Sonnet)
🌙
Sesi 3
20:00 — 01:00
Polish & docs (Haiku/Sonnet)
Prompt Library

Copy-paste ready.

Semua prompt enterprise siap untuk Claude. Tap copy untuk salin.

Quick Prompts

Prompt siap pakai.

Copy-paste terus untuk hasil pantas. Practical examples untuk daily use.

Phase 0 initialization

Project structure.

Create proper AI-native folder structure.

folder tree
PROJECT/
├── PROJECT_SUMMARY.md
├── frontend/
├── backend/
├── database/
├── screenshots/
├── docs/
├── branding/
├── deployment/
├── ui-reference/
└── exports/
prompt claude
Help me prepare a scalable AI-native SaaS
project structure.

Requirements:
- GitHub-ready
- Claude Code-ready
- scalable modular architecture
- production-ready organization
- mobile-first SaaS workflow
- enterprise-grade structure

Generate:
1. recommended folder structure
2. recommended naming conventions
3. recommended documentation structure
4. scalable architecture recommendations
5. deployment structure
Phase 1 context · persistence

Project summary.

Generate persistent context untuk Claude.

prompt md
Generate a professional PROJECT_SUMMARY.md
for this project.

Requirements:
- enterprise SaaS structure
- scalable architecture direction
- modular workflow
- migration-safe rules
- premium UI/UX direction
- future scalability support

Include:
1. project overview
2. current stack
3. target stack
4. core features
5. business goals
6. architecture goals
7. critical rules
8. preferred UI/UX direction
9. scalability considerations
Phase 2 claude project

Project instructions.

Paste ke Claude Project Instructions.

instructions project
This project may contain:
- source code
- frontend/backend files
- Lovable exports
- Supabase structure
- zip archives
- screenshots
- reusable assets
- workflows
- architecture documents
- branding files

IMPORTANT:
This is NOT a rebuild-from-scratch project
unless explicitly stated.

Your task:
1. analyze the uploaded project structure
2. understand the current architecture
3. identify existing workflows
4. identify risky modules/files
5. identify modernization opportunities
6. identify scalability opportunities
7. identify UI/UX improvements
8. identify migration requirements
9. propose phased implementation roadmap

Always:
- preserve working logic
- preserve compatibility
- avoid unnecessary rewrites
- prioritize modular improvements
- prioritize scalability
- prioritize mobile-first UX

Focus on:
- enterprise-grade quality
- scalable architecture
- production-ready implementation
- premium user experience

Do not code yet. Analyze first.
Phase 3 analysis

Architecture audit.

Faham dulu sebelum modify.

prompt analysis
Read PROJECT_SUMMARY.md first before continuing.

Analyze the uploaded project architecture first.

Do not code yet.

Identify:
1. architecture structure
2. workflows
3. dependencies
4. risky modules
5. scalability opportunities
6. modernization opportunities
7. migration requirements

Then produce:
- architecture understanding
- affected module list
- migration opportunities
- phased roadmap
Phase 4 migration plan

Migration planning.

Map Lovable/Supabase → PHP/MySQL.

prompt migration
Now proceed with migration planning.

Target stack: PHP + MySQL + JavaScript.

IMPORTANT:
This is NOT a rebuild-from-scratch project.

Preserve whenever possible:
- workflows
- business logic
- UI structure
- feature behavior
- existing modules
- user flow

Your task:
1. map Supabase tables to MySQL structure
2. identify authentication migration strategy
3. identify storage/upload migration strategy
4. identify frontend migration approach
5. identify backend architecture approach
6. identify reusable components
7. identify risky migration areas
8. identify safest migration order
9. propose scalable PHP folder structure
10. propose enterprise-grade architecture

Requirements:
- cPanel compatible
- modular PHP architecture
- scalable structure
- maintainable codebase
- responsive mobile-first UI
- enterprise SaaS quality

Do not migrate everything immediately.
Plan first.
Phase 5 foundation

Foundation architecture.

Setup base PHP structure & routing.

prompt foundation
Proceed with Phase 1 only.

Create:
- scalable PHP folder structure
- database connection architecture
- reusable layout structure
- reusable component system
- environment configuration
- routing structure
- authentication foundation

Rules:
- preserve original files
- do not overwrite source project
- create migration-ready structure
- enterprise-grade architecture
- cPanel-ready structure
Phase 6 dashboard

Dashboard modernization.

Upgrade ke premium workforce intelligence UI.

prompt dashboard
Proceed with Dashboard migration only.

Preserve:
- workflows
- existing KPIs
- analytics logic

Upgrade:
- UI/UX
- responsiveness
- modular structure
- enterprise SaaS experience

Target:
Premium futuristic workforce intelligence
dashboard.

Requirements:
- glassmorphism UI
- responsive design
- floating KPI cards
- premium dark mode
- mobile-first UX
- command center aesthetic
- scalable component structure
Phase 7 module migration

Module-by-module migration.

Replace [MODULE NAME] dengan nama modul anda.

prompt module
Proceed with [MODULE NAME] migration only.

Preserve:
- workflows
- business logic
- feature behavior
- compatibility

Upgrade:
- architecture
- UI/UX
- responsiveness
- scalability
- maintainability

Requirements:
- enterprise-grade implementation
- modular structure
- reusable components
- responsive mobile-first UX
- production-ready quality

Do not affect unrelated modules.
Phase 8 security · hardening

Security hardening.

Audit & harden untuk production.

prompt security
Audit the system for:
- security risks
- SQL injection risks
- authentication weaknesses
- file upload vulnerabilities
- session vulnerabilities
- API exposure risks
- cPanel deployment risks

Then:
1. identify risky files
2. identify critical vulnerabilities
3. propose safest hardening plan
4. generate phased security roadmap

Requirements:
- enterprise-grade security
- cPanel compatibility
- maintainable architecture
- scalable protection
Phase 9 pwa · mobile

PWA optimization.

App-like experience untuk mobile.

prompt pwa
Convert the system into a premium PWA-ready
experience.

Add:
- install app support
- splash screen
- responsive app-like UX
- offline fallback page
- touch-friendly navigation
- mobile transitions
- app-style interaction
- performance optimization

Requirements:
- lightweight
- smooth UX
- mobile-first
- enterprise SaaS quality
Phase 10 final polish

Enterprise polish.

Final audit & refinement.

prompt polish
Perform final enterprise SaaS optimization.

Audit:
- UI consistency
- UX quality
- scalability
- maintainability
- responsiveness
- visual hierarchy
- SaaS polish
- enterprise branding consistency

Then:
1. identify weak areas
2. identify outdated UI patterns
3. identify scalability risks
4. identify performance bottlenecks
5. propose optimization roadmap

Target:
Premium enterprise SaaS platform.
Phase 11 deployment

Production deployment.

cPanel-ready deployment checklist.

prompt deploy
Prepare the system for production deployment.

Requirements:
- cPanel-ready
- production-safe
- optimized structure
- scalable deployment
- environment-safe configuration

Generate:
1. deployment checklist
2. production optimization checklist
3. security checklist
4. backup strategy
5. rollback strategy
6. environment setup guide
7. deployment roadmap
Selection

Pilih model betul.

Right tool, right job. 80% kerja boleh dengan Sonnet.

Haiku Light · Cheap

Pantas dan murah. Untuk volume kerja harian.

  • Ringkasan pendek
  • Brainstorming
  • Formatting & grammar
  • Quick Q&A
  • Classification tasks

Sonnet Balanced · Default

Workhorse harian. Quality vs cost balanced.

  • Code generation
  • Analysis sederhana
  • Content creation
  • Migration planning
  • Daily development

Opus Heavy · Premium

Kuasa tertinggi. Guna sparingly.

  • Architecture decisions
  • Complex refactoring
  • Deep analysis
  • Strategic planning
  • Multi-step reasoning
$
Rule of thumb: Mula Haiku → naik Sonnet kalau perlu → Opus untuk decision kritikal sahaja.
Discipline

Golden rules.

Prinsip teras untuk AI-native development.

01
Never blindly rebuildJangan rewrite tanpa sebab kuat.
02
Analyze firstFaham sebelum sentuh code.
03
Phase-by-phaseMigrate modul demi modul.
04
Commit every phaseGitHub rollback selamat.
05
Token economySetiap mesej ada kos.
06
Right modelHaiku, Sonnet, Opus — pilih bijak.
07
Edit, don't follow-upEdit lebih jimat dari mesej baru.
08
Projects = cacheUpload sekali, guna selamanya.
Tech Stack

Recommended stack.

Production-ready
⚙
Stack: HTML · Tailwind CSS · JavaScript · Chart.js · PHP · MySQL · PDO · cPanel · GitHub · Claude Projects · Claude Code · Antigravity IDE.
Build smarter. Ship faster.
Claude AI Development Flow © SIFUROBOT SOLUTIONS
v2.3 · Nota Kelas Edition
Copied to clipboard