Overview
This prompt aims to guide developers in creating a cohesive admin section for the “salle de sport” project while adhering to existing project structures. Programmers and project managers will benefit from the clear instructions and structured approach to maintain consistency and functionality.
Prompt Overview
Purpose: This plan aims to develop a cohesive admin section for the “salle de sport” project, ensuring seamless integration.
Audience: The intended audience includes developers familiar with PHP, CSS, and JavaScript who will implement the admin functionalities.
Distinctive Feature: All pages will utilize native CSS for styling, ensuring a consistent and modern design without external frameworks.
Outcome: The result will be a fully functional admin section that adheres to existing backend logic and maintains a uniform appearance.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Development Tools & DevOps, General Business Operations, Productivity & Workflow
- Techniques: Decomposition, Plan-Then-Solve, Structured Output
- Models: Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o, Llama 3.1 70B
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
You are tasked with developing the admin section for the “salle de sport” project by generating code that integrates seamlessly with the existing file structure and backend logic.
**Before starting code generation:**
– Thoroughly review the entire project files to understand the required components for creating the admin section.
– The admin folder contains three subfolders:
– php
– css
– js
– Each functionality in the admin folder has corresponding files:
– e.g., file1.php, file1.css, file1.js.
– There is a separate “includes” folder containing:
– header.php
– footer.php
– logout.php.
– These include files should follow the same structural pattern, having their own CSS and JS files.
**Requirements:**
– All admin pages and includes must maintain a consistent, modern design and style, modeled after the existing shop.php page’s native CSS (do not use Bootstrap or Tailwind).
– Use only native CSS for styling, ensuring all admin pages have a uniform appearance.
– On the backend, strictly adhere to the existing PHP requests and queries as per the current codebase and database schema—do not create new queries or alter existing logic.
– Generate PHP, CSS, and JS files corresponding to each admin page/functionality in the prescribed folder structure.
**Steps:**
1. Analyze the existing project files, focusing on:
– The admin folder
– The includes folder
2. Understand the existing PHP queries and database interactions thoroughly.
3. For each admin PHP page, create matching CSS and JS files using native CSS to replicate the modern style of shop.php.
4. Ensure header.php, footer.php, and logout.php include their own CSS and JS files, following the consistent layout and design.
5. Maintain a uniform look and feel across all admin pages and included files, avoiding any external CSS frameworks.
6. Validate that all PHP code strictly respects existing requests and database schema without introducing new queries.
**Output Format:**
Provide a detailed plan for each admin page including:
– File names and folder locations (php, css, js folders within admin).
– Code snippets or templates for PHP, CSS, and JS files reflecting the required design and functionality.
– Explanation on how backend PHP code adheres to existing requests and database structure.
If asked, generate full code snippets for specific files adhering to these guidelines.
**Notes:**
– Keep the entire work consistent with the existing project architecture.
– Avoid introducing new database queries or altering core backend logic.
– Emphasize native CSS styling matching the modern aesthetic of shop.php.
– Organize your output clearly for easy integration into the project.
Screenshot Examples
How to Use This Prompt
- Copy the prompt provided above.
- Paste the prompt into your coding environment.
- Review the project files as instructed in the prompt.
- Generate PHP, CSS, and JS files for the admin section.
- Ensure all files follow the existing design and structure.
- Validate the code against the database schema and logic.
Tips for Best Results
- Review Project Files: Thoroughly analyze the existing admin and includes folders to understand the current structure and functionality.
- Maintain Consistency: Ensure all new PHP, CSS, and JS files adhere to the design and style of shop.php, using only native CSS for a uniform appearance.
- Follow Existing Logic: Stick to the current PHP queries and database schema without introducing new queries or altering existing logic in the backend.
- Organize Output: Clearly outline file names and locations for PHP, CSS, and JS files to facilitate easy integration into the existing project architecture.
FAQ
- What is the purpose of the admin section in the project?
The admin section manages functionalities like user accounts, content updates, and system settings for the salle de sport project. - How should the admin pages be styled?
Admin pages must use native CSS to replicate the modern design of the existing shop.php page. - What files are included in the admin folder?
The admin folder contains php, css, and js subfolders, each with corresponding functionality files. - Can new database queries be introduced in the admin section?
No, all PHP code must adhere to existing requests and database schema without introducing new queries.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (February 2026): Initial release.
