College Core — Master App Prompt
Page 1
COLLEGE CORE
Master AI Prompt for Android Studio / Claude Code
Project: ITG Gopeshwar College Management App | Package: com.itg.collegecore
mentor. Help me build a complete Android college-management application named “College Core”
for Govt. Institute of Technology (ITG) Gopeshwar.
MAIN PURPOSE:
Create one central app where students can access academic material, notices, exam papers,
gallery and college updates. Administrators should be able to manage content without editing
the app code.
College Core — Master App Prompt
Page 2
College Core — Master App Prompt
Page 3
College Core — Master App Prompt
The project name is crimson-vivid.
CORE MODULES:
USER ROLES AND AUTHENTICATION:
Login using a college-issued email/ID or approved credentials.
Student profile should include name, student ID/roll number, course, branch, year, semester
and profile photo (optional).
USER ROLES AND AUTHENTICATION:
Separate admin sign-in and protected admin dashboard.
Only authorized admins can create, edit, publish or delete notices, study material, papers
and gallery items.
A. Student Dashboard
Clean home screen with welcome message and profile summary.
Quick access cards for Notices, Syllabus, Notes, Previous Papers, Gallery and Profile.
Show latest notices and recently added study material.
Bottom navigation where appropriate.
B. Notices / Notifications
Admin can publish notices with title, message, date, attachment and target audience.
Target audience filters: all students, course, branch, year and semester.
Students see only notices relevant to them plus general notices.
Include read/unread status and notice details screen.
Plan push notifications for important notices; ask before adding a paid service.
C. Syllabus
Organize syllabus by course → branch → year → semester → subject.
Support PDF links/files and subject descriptions.
Admin can add, update or remove syllabus entries.
Students can view and open/download permitted PDFs.
D. Notes / Study Material
Organize notes by course, branch, year, semester and subject.
Support PDF documents and optionally images.
Include title, subject, unit, upload date and uploaded-by information.
Add search and filters.
Admin can upload, edit and delete material.
E. Previous Year / Exam Papers
Support 2 internal examinations and 1 external examination as configurable exam categories.
Organize papers by course, branch, year, semester, subject, exam type and year.
Students can search and download/view papers.
Admin can add papers and update metadata.
F. Photo Gallery
Show college events, cultural programs, technical events, sports and other activities.
Albums with event title, date, description and multiple photos.
Admin-only upload and management.
G. Admin Dashboard
Summary counts for students, notices, notes, syllabus files, papers and gallery albums.
Forms to add/edit content with validation.
Content preview before publishing.
Confirmation before destructive actions.
Clear success/failure messages.
Courses: B.Tech, BCA (and future courses)
B.Tech: 5 configurable branches, 4 academic years
BCA: 3 academic years
Semesters: configurable according to course duration
Subjects mapped to the correct course/branch/year/semester
Do not invent the names of the five branches. Make them manageable by the admin.
Store documents and images in cloud storage, and keep metadata in the database.
Validate file type and size for uploads.
Explain how to create the first admin account safely.
DELIVERABLES:
First inspect my existing Android Studio project and tell me what is already present.
Propose the complete folder/package structure.
Create a phase-wise development roadmap.
Explain the database tables/collections and relationships before implementation.
Build one working module at a time.
For every phase, provide:
files to create or edit,
complete code,
exact paste location,
required Gradle dependencies,
setup/configuration steps,
how to run and test,
common errors and fixes.
DEVELOPMENT ORDER:
Phase 3: Authentication and student/admin roles.
DEVELOPMENT ORDER:
Phase 4: Student dashboard and profile.
DEVELOPMENT ORDER:
Phase 5: Notices.
DEVELOPMENT ORDER:
Phase 6: Syllabus and notes.
DEVELOPMENT ORDER:
Phase 7: Previous exam papers.
DEVELOPMENT ORDER:
Phase 8: Gallery.
DEVELOPMENT ORDER:
Phase 9: Admin content-management dashboard.
Phase 10: Security rules, testing, performance and bug fixing.
Phase 11: APK build, installation and project backup.
Important project notes
• Test admin and student permissions separately. A hidden admin screen is not a security system; backend rules must
enforce permissions.
College Core serves two human roles, each with a separate sign-in path. Content storage and notification delivery are supporting systems, not personas.
| Role | Responsibilities and goals | Inputs | Decisions | Access |
|---|---|---|---|---|
| Student | Reach academic material, notices, exam papers, gallery and college updates from one central app; see what is new and relevant to their own programme | College-issued email/ID or approved credentials; profile details (name, student ID/roll number, course, branch, year, semester, optional profile photo) | Which notices, syllabus, notes and papers to view, search or download | Student dashboard with welcome message, profile summary, latest notices, recently added study material, quick-access cards (Notices, Syllabus, Notes, Previous Papers, Gallery, Profile) and bottom navigation where appropriate; content filtered to their course/branch/semester where applicable; read-only on admin content; no access to another student's private profile data |
| Administrator | Keep app content current without editing app code; manage notices, study material, syllabus, papers and gallery | Admin credentials; content files (PDFs, optional images) and metadata (title, subject, unit, upload date, uploaded-by, date, target audience, exam type, year) | What to create, edit, publish or delete; which audience a notice targets; how courses, branches, years, semesters and subjects are configured | Separate admin sign-in and protected admin dashboard with summary counts for students, notices, notes, syllabus files, papers and gallery albums; sole authority for uploads and content management |
Administrators maintain the course structure: B.Tech with five admin-managed branches and four academic years, BCA with three academic years, and semesters configurable per course duration, with subjects mapped to the correct course/branch/year/semester. Branch names are deliberately left to admin configuration rather than fixed in the app. This batch establishes these two roles only; it does not define a complete persona catalog.
Trigger: A student opens the app and chooses student login.
Failure/recovery: If credentials are rejected, the student remains on the login screen and can retry; no dashboard content is shown until authentication succeeds.
Trigger: The student opens Notices from the dashboard or bottom navigation.
Failure/recovery: If no notices match the student's scope, the list shows only general notices rather than an error.
Trigger: The student opens Syllabus.
Failure/recovery: If a subject has no syllabus entry yet, the subject shows no document; the student can pick another subject.
Trigger: The student opens Notes.
Failure/recovery: A search with no matches returns an empty result set; the student can clear filters and browse instead.
Trigger: The student opens Previous Papers.
Failure/recovery: No matching papers yields an empty result set; the student can broaden the filters.
Trigger: An authorized admin chooses the separate admin sign-in.
Failure/recovery: Unauthenticated or unauthorized attempts do not reach the dashboard; the admin remains at sign-in.
Trigger: The admin opens notice management.
Failure/recovery: Validation errors block publishing and return the admin to the form with the entered values.
Trigger: The admin opens the relevant content area.
Failure/recovery: Invalid or incomplete forms are rejected with validation messages; existing content stays unchanged until a valid save.
Trigger: The admin opens course configuration.
Failure/recovery: A mapping that omits a level leaves that content unscoped for students until the admin completes it.
Trigger: The admin opens gallery management.
Failure/recovery: Unpublished changes remain hidden from students until the admin publishes.
Page 4
Recommended first message after pasting the prompt
“I have opened my College Core project in Android Studio. Please inspect the existing project first. Do not change any
file yet. Tell me the current project structure, what is already working, and the exact next step for Phase 1.”
[Design proposal; unspecified choices are defaults.]
Muse and headline. Tobias van Schneider's editorial swagger, tuned for an Android college companion: College Core, all your college in one place. Paper ground, oversized crimson type, one hot accent — clear and professional, warm enough for a first-year student.
Palette (light theme only; dark theme is a later phase). Paper #F4F0EA covers roughly 70% of every screen; surface #FFFFFF for cards and sheets; ink #141414 for all text; primary crimson #B3122B for the active section and main buttons; ember #E4572E reserved for notices only, at about 5%; muted #6E6660 for secondary labels and counts. No blue or indigo anywhere.
Typography. Headings in Archivo — Archivo Black caps, tight tracking, flush left, large scale contrast. Body in Source Serif 4. Modular scale of 1.333: display 44px mobile to 96px desktop, then 32 / 24 / 18 / 16.
Shape and spacing. Sharp corners only — no rounded cards, no soft shadows. Full-width ink rules separate sections. At most one crimson block per screen. Spacing follows a consistent rhythm so reusable components (buttons, notice rows, photo cards, form fields) share one set of tokens across student and admin screens.
Layout. Asymmetric two-column grid: a wide left text column against a narrow right rail of labels and counts. Sections stack with full-width rules. Layouts stay responsive across Android screen sizes, and headlines, wordmarks, labels, numbers, card text and controls stay whole inside the viewport and their container at 375px, 768px and 1280px, wrapping or scaling (e.g. clamp()) to fit.
Imagery. Large campus and classroom photos with a warm monochrome tint; type carries the page when no photo is present.
Avoid. Rounded cards with soft shadows, blue/indigo buttons on white, gradient blobs and glass panels, identical hover-lift card grids, centred headline with small subtext and one button.
States. Loading, empty, offline and error states use the same paper ground and ink rules, with clear success/failure messages and confirmation before destructive actions styled as crimson primary actions.
DESIGN DIRECTION:
Modern, professional, simple college-app design.
Consistent colors, typography, spacing, icons and reusable components.
Easy for first-year students to understand.
Responsive layouts for different Android screen sizes.
Avoid clutter, unnecessary animations and heavy effects.
Provide a light theme; dark theme can be added as a later phase.
[Design proposal; unspecified choices are defaults.]
Signature moves.
clamp(44px, 9vw, 96px).#B3122B block at the hero edge holding the CTA in white.Public entry hero. Paper ground #F4F0EA. A huge Archivo Black headline in ink fills the left 8 of 12 columns and wraps to three lines: College Core, all your college in one place. A thin ink rule runs under it. The subline reads Notices, syllabus, notes and papers for ITG Gopeshwar, sorted by your branch and semester. A solid crimson block sits at the right edge holding the white CTA Open dashboard. This recomposes only accepted content and the accepted entry control — no new behaviour or destination.
Component coverage. The same tokens carry the student dashboard, notices, syllabus, notes, previous papers, gallery and profile, plus the admin content-management screens: one reusable button, notice row, photo card, form field and section opener, so admins manage content without touching app code and first-year students meet the same familiar shapes everywhere.
[Design proposal; unspecified choices are defaults.]
Interaction Model: Static (direction) Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief. Focal subject: the oversized Archivo Black headline on paper ground, with the crimson CTA block at the right edge. Input → transformation → outcome: on load, the headline reveals once with a slow type reveal (line-by-line, no bounce); the ink rule draws under it; the crimson block and Open dashboard CTA settle last, ready to open the dashboard. Motion vocabulary: one slow type reveal and a slow crossfade on image hover — nothing bouncy, no parallax, no heavy effects. Composed first frame: headline fully legible, rule and CTA in place, so the page reads complete even before motion runs. Reduced-motion state: the same static arrangement with no reveal — headline, rule and CTA simply present, all text and controls whole at every viewport.
rules.
Optimize image loading and avoid downloading full-resolution images unnecessarily.
Implement role-based access control and server/database security rules. Hiding admin buttons
in the UI is NOT sufficient security.
Use pagination or lazy loading for lists and efficient image loading.
Add basic offline/error/loading/empty states where practical.
Include validation, crash-safe error handling and basic accessibility.
SECURITY AND PRIVACY:
Students must not be able to modify admin content.
Students must not access another student's private profile data.
Admin permissions must be verified by the backend/database rules.
Do not expose private student information in public lists.
Provide a testing checklist for student and admin accounts.
Explain how to build a signed APK and install it on a phone.
Explain how to back up the project and continue on a second laptop using Git.
APP IDENTITY:
App name: College Core
College context: Govt. Institute of Technology (ITG) Gopeshwar
Android application ID / package: com.itg.collegecore
Platform: Android
Preferred development environment: Android Studio
Preferred language: Kotlin
UI: Jetpack Compose with Material 3
Target users: students and college administrators
TECHNICAL REQUIREMENTS:
Use Kotlin and Jetpack Compose + Material 3.
Use a maintainable architecture (MVVM, repositories, ViewModels and UI state).
Recommend a suitable backend/database/storage solution for a beginner and explain its
free-tier limits, security and future cost. Prefer Firebase or Supabase only after comparing
the trade-offs; do not silently assume one.
How to use this PDF
Copy the master prompt below and paste it into Claude Code or your coding AI while working in your Android Studio
project. Ask the AI to complete the app in small phases. Do not ask it to generate the entire project in one huge step.
MASTER PROMPT (copy from here)
You are a senior Android developer, software architect, UI/UX designer, and patient coding
IMPORTANT ABOUT ME:
I am a complete beginner. Assume I know almost nothing about programming.
Explain every step in very simple Hinglish (Hindi written in English letters).
Give exact Android Studio menu paths, file names, and where each code block must be pasted.
Never skip setup steps or assume I know a technical term.
Build the app in small, testable phases. After each phase, tell me how to run it and what I
should see.
existing project, inspect its current structure and reuse working code where possible.
beginner-friendly.
Initial expected scale: approximately 200–500 students
Academic structure: B.Tech with 5 branches and 4 years; also allow BCA with 3 years. Make
courses, branches, semesters and academic years configurable rather than hard-coded.
ACADEMIC DATA MODEL:
Design the database so it can support:
DEVELOPMENT ORDER:
Phase 1: Inspect project, confirm Android Studio setup, app launch and navigation.
DEVELOPMENT ORDER:
Phase 2: Design system, data model and backend choice.
WORKING RULES:
activity, package name, Gradle setup and existing screens.
guess.
Ask only one important question at a time.
If a feature requires a paid plan or service, warn me before implementation and suggest a
low-cost alternative.
Never claim something is completed unless the code and steps are actually provided.
At the end of each phase, give me a short checklist and wait for my confirmation before
moving to the next phase.
Begin now by inspecting my current project and guiding me through Phase 1 in Hinglish.
Important project notes
• Keep a backup or Git commit before major code changes.
Important project notes
• Do not share passwords, private keys, student personal data or production credentials in chat.
Important project notes
• Build and test one module at a time. A working small app is better than a large app full of errors.
College Core — the Android college-management application (package com.itg.collegecore) built for Govt. Institute of Technology (ITG) Gopeshwar.
Course — a configurable programme of study offered by the college. B.Tech and BCA are the courses in scope; further courses are anticipated and must be addable without code changes.
Branch — a configurable specialization within a course. B.Tech has five branches, whose names are not fixed by the requirements and are managed by the admin.
Academic year — a configurable year of study within a course. B.Tech spans four academic years; BCA spans three.
Semester — a configurable division of a course, with the number of semesters derived from the course duration rather than hard-coded.
Subject — a unit of study mapped to the correct course, branch, academic year and semester.
Admin — the human role responsible for managing courses, branches, semesters, academic years and subject mappings.

Notices, syllabus, notes and papers for ITG Gopeshwar, sorted by your branch and semester.
Everything a student opens day to day, sorted by your branch and semester: Notices to Profile.
Targeted notices with read and unread status
Course to subject hierarchy with PDF files
Study material with search and filters
Internal and external exam papers by year
Event albums with photos and dates
Your name, roll number, course, branch, year and semester
Admin access is separate and protected.

Notices, syllabus, notes and papers for ITG Gopeshwar, sorted by your branch and semester.
Everything a student opens day to day, sorted by your branch and semester: Notices to Profile.
Targeted notices with read and unread status
Course to subject hierarchy with PDF files
Study material with search and filters
Internal and external exam papers by year
Event albums with photos and dates
Your name, roll number, course, branch, year and semester
Admin access is separate and protected.
No comments yet. Be the first!