Send this as your FIRST message in Claude — sets context for everything

I am a final year computer science student. I have built a [Project Name]
using PHP and MySQL for my capstone project submission.

Project overview:
- System name: [e.g. ISP Management System]
- Main purpose: [e.g. Allows ISPs to manage customers, billing, and inventory]
- Key modules: [e.g. Customer management, Monthly billing, Stock tracking, Expenses]
- Tech stack: PHP 8, MySQL, HTML/CSS, JavaScript, XAMPP
- Target users: [e.g. Small ISP administrators]
- Database tables: [e.g. customers, internet_plans, bills, collections, expenses, stock]

I need your help generating professional documentation for my project.
I will be sharing code files and asking you to produce specific documents.
Please write all documentation in formal academic language suitable for
a university final year project submission.

Do you understand the project? Ask me any clarifying questions before we start.

Paste into Claude — generates a full SRS outline and content

Based on the project context I shared, generate a complete Software
Requirements Specification (SRS) document following IEEE 830 standard format.

Include all of these sections with full content — not just headings:

1. Introduction
   - Purpose of the document
   - Scope of the system
   - Definitions and abbreviations
   - Overview of the document

2. Overall System Description
   - Product perspective (standalone vs part of a larger system)
   - Product functions (brief summary of major functions)
   - User characteristics (who uses the system and their technical level)
   - Operating environment (XAMPP / PHP / MySQL / browser-based)
   - Design and implementation constraints
   - Assumptions and dependencies

3. Specific Functional Requirements
   - Write one numbered requirement per module
   - Format: REQ-[number]: The system shall [action]
   - Cover all modules: [list your modules]
   - Include admin authentication requirements
   - Include CRUD operation requirements for each module
   - Include reporting and billing requirements

4. Non-Functional Requirements
   - Performance requirements
   - Security requirements (session management, input validation)
   - Usability requirements
   - Reliability requirements
   - Maintainability requirements
   - Compatibility requirements (browsers, PHP version)

5. External Interface Requirements
   - User interface description
   - Hardware interface
   - Software interface (PHP version, MySQL version, browser)
   - Communication interface

6. Database Requirements
   - List all database tables with their purpose
   - Describe the key relationships between tables
   - Describe data validation rules

Write this as a formal, professional document ready for academic submission.
Use complete sentences and paragraphs — not just bullet points.

Follow-up — expand functional requirements for a specific module

The billing module is the most complex part of my project and the examiner
will focus on it heavily. Please expand the functional requirements section
specifically for the billing module with at least 8 detailed requirements,
covering: bill generation logic, duplicate prevention, payment recording,
overdue detection, and admin reporting. Use the REQ-[number] format.

Paste into Claude — generates a complete professional README.md

Generate a complete, professional README.md file for my project using
standard Markdown formatting. Include all of these sections:

# [Project Name]
> One-sentence description of what the system does and who it is for.

## Overview
Two paragraphs: what the system does and the problem it solves.

## Features
List every major feature with a brief description. Group by module.

## Tech Stack
Table format: Technology | Version | Purpose

## Prerequisites
What the user needs installed before they can run the project.
(PHP, XAMPP/WAMP, MySQL, browser — with recommended versions)

## Installation
Numbered step-by-step installation guide:
1. XAMPP setup
2. Database import steps
3. Configuration file setup
4. How to access the system
5. Default login credentials

## Project Structure
Show the file/folder structure with a brief note on each key file.

## Database Schema
List the main tables and their purpose.
Describe the key foreign key relationships.

## Screenshots
[Section with placeholder text: "Screenshots coming soon" — I will add images]

## Use Cases
Who this system is built for and real-world scenarios where it would be used.

## Future Improvements
List 5 realistic features that could be added to extend the project.

## License
MIT License — free to use for educational purposes.

## Author
[My name], [University name], Final Year Project [Year]

Write in clear, professional English. Use proper Markdown syntax throughout.

Paste into Claude with your PHP file attached

Read the PHP file I have uploaded (chatbot.php / api.php).
Generate professional API documentation in the following format for
each endpoint you can identify:

---
### POST /chatbot.php

**Description**
What this endpoint does in one sentence.

**Request Body** (JSON)
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| message | string | Yes | The user's message text |
| history | array | No | Previous conversation messages |

**Request Example**
```json
{
  "message": "How does billing work?",
  "history": []
}
```

**Response** (JSON)
| Field | Type | Description |
|-------|------|-------------|
| reply | string | The AI-generated response |
| tokens_used | integer | Total tokens consumed |

**Response Example**
```json
{
  "reply": "The billing module generates monthly invoices...",
  "tokens_used": 245
}
```

**Error Responses**
| HTTP Status | Error Message | Cause |
|-------------|---------------|-------|
| 405 | Method not allowed | Non-POST request |
| 400 | No message provided | Empty message field |
---

Generate documentation like this for every endpoint or public function
in the file. Use professional technical writing throughout.

The viva preparation prompt — generates 15 questions with model answers

Based on everything you know about my project from this conversation,
generate 15 tough viva examination questions that a professor might ask,
covering these areas:

Database Design (3 questions):
- Why did you design the database this way?
- How do your tables relate to each other?
- What normalisation form did you achieve and why?

Code and Implementation (4 questions):
- Explain your most complex function in detail
- How does your authentication system work?
- What would happen if two admins clicked Generate Bills at the same time?
- Walk me through what happens from when the admin clicks login to when
  they see the dashboard

Security (3 questions):
- How did you prevent SQL injection?
- How are sessions protected in your system?
- What are the security weaknesses in your current implementation?

System Improvement (3 questions):
- What would you add if you had 3 more months?
- How would you scale this system to handle 10,000 customers?
- What testing did you do and what would you do differently?

Reflection (2 questions):
- What was the hardest part of building this system?
- What would you do differently if you started again?

For each question, write:
Q: [The question]
A: [A 4–5 sentence model answer that is specific to my project, not generic]

The answers must reference my actual modules, table names, and code logic
— not generic CS concepts.