Los osos están cargando la página…
Comunidad de reseñas de IA de XiuZon · dos osos batallando
Private 2
Modelo de IA
Private 2
MASTER PROMPT PART 1 — PROJECT FOUNDATION & DESIGN SPECIFICATION PROJECT OVERVIEW Create a premium enterprise-grade Reac
Claude Opus 4 8
MASTER PROMPT PART 1 — PROJECT FOUNDATION & DESIGN SPECIFICATION PROJECT OVERVIEW Create a premium enterprise-grade Reac
MASTER PROMPT PART 1 — PROJECT FOUNDATION & DESIGN SPECIFICATION PROJECT OVERVIEW Create a premium enterprise-grade React + JavaScript web application that demonstrates a professional historical digital platform dedicated to reconstructing the transportation infrastructure of Turkestan during the early twentieth century through an interactive historical map experience. This project is not intended to simulate a full GIS analysis system. Instead, it is a visually impressive, scientifically credible, and historically authentic concept platform that demonstrates how historical spatial information can be explored interactively. The website language must be 100% Uzbek. Project Title: Raqamli GIS Platformasi Subtitle: 1900-yillar Turkiston transport infratuzilmasining raqamli modeli Footer: Developed by NavSystem PRIMARY OBJECTIVE The website exists to present one central feature: A premium historical interactive map of Tashkent between approximately 1890 and 1917. Everything else on the website must support, explain, enrich, or complement this historical map. The map must immediately become the visual centerpiece of the project. Visitors should feel they are entering a professional historical research laboratory prepared for museums, universities, scientific councils, and historical archives. TARGET IMPRESSION The website must never resemble: a student assignment a university presentation a template a portfolio a slideshow a landing page made from ordinary UI components Instead, the visitor should immediately think: "This looks like a professional historical digital platform created by an international software company for museums and scientific institutions." VISUAL DESIGN PHILOSOPHY The design should combine two identities: Modern premium enterprise software Historical atmosphere of Turkestan around 1900. Every page should feel like entering another room inside a digital historical museum. The design language must remain consistent across the entire project. DESIGN STYLE The interface should appear: Premium Elegant Academic Museum-quality Scientific Luxurious Minimal Sophisticated Timeless Historical Avoid flashy effects. Avoid gaming aesthetics. Avoid cartoon styles. Avoid excessive gradients. Avoid futuristic cyber styles. COLOR SYSTEM Primary palette: Old parchment Warm beige Dark brown Sepia Historic bronze Copper Deep olive Dark green Black ink Muted gray Use subtle gradients only where appropriate. Maintain excellent readability. TYPOGRAPHY Use premium contemporary fonts with excellent readability. Never use: Arial Calibri Georgia Times New Roman Typography should resemble professional scientific publications and museum exhibitions. ICONOGRAPHY Use premium outline icons inspired by historical engineering and cartography. Examples include: Railway Bridge Compass Surveying tools Maps Steam locomotive Archive Navigation Historic document Infrastructure Database Engineering Transport Every icon must belong to one consistent design family. AI-GENERATED VISUALS Do not use stock photography. All historical illustrations, backgrounds, decorative elements, and environmental scenes must be AI-generated. All generated visuals must share one unified artistic style. The entire website should appear as though it was illustrated by a single historical cartographer. Generate historical visuals including: Steam locomotives Railway stations Historical engineers Surveyors Railway workers Old Tashkent Historic bridges Canals Road construction Government offices Engineering equipment Historical documents Navigation instruments Transportation infrastructure BACKGROUND DESIGN Every major section should contain its own AI-generated historical background. Backgrounds should subtly support the content without reducing readability. Avoid repeating backgrounds across sections. Each background should strengthen the historical atmosphere. ANIMATIONS Animations must remain elegant and restrained. Examples: Fade transitions Scroll reveal Smooth content appearance Hover lighting Historical route animations Floating historical symbols Section transitions Loading animation Animations should improve immersion without distracting users. RESPONSIVE DESIGN Perfect responsiveness is mandatory. Support: Desktop Laptop Tablet Mobile Spacing, typography, images, and layout must remain consistent across all devices. NAVSYSTEM BRAND Generate an original premium technology logo. Company: NavSystem The logo should feel modern while harmonizing with the historical atmosphere of the website. Primary colors: Blue Gold The logo must appear consistently throughout the interface. MASTER PROMPT PART 2 — HISTORICAL MAP SYSTEM & USER EXPERIENCE THE HISTORICAL MAP IS THE HEART OF THE PROJECT The historical map is the primary feature of the website and must occupy approximately 60–70% of the user's attention on desktop devices. Everything else—including sections, cards, animations, infographics, and descriptions—must support, explain, and enrich the map rather than compete with it. Visitors should naturally begin exploring the project through the map. REFERENCE IMAGES (MANDATORY) I will upload several reference images together with this prompt. These images are mandatory design references. They are not website assets and must not be displayed directly. Arena AI must carefully analyze them to understand: historical cartographic style composition urban density building footprints railway appearance road hierarchy labeling style historical atmosphere overall quality The final map must reproduce the same professional historical feeling while remaining an original creation. If any conflict exists between this prompt and the uploaded reference images, the reference images define the visual style, while this prompt defines the functionality and architecture. HISTORICAL ACCURACY (HIGHEST PRIORITY) The reconstructed map must represent Tashkent between approximately 1890 and 1917 with the highest possible historical accuracy. Historical authenticity always takes priority over decorative design. The reconstruction should closely follow historical archival sources and reference images. If historical information is unavailable for certain areas, intelligently reconstruct them according to early twentieth-century urban planning principles rather than inventing modern-looking districts. The final result should resemble a professional historical reconstruction prepared by historians and cartographers. MAP RENDERING SYSTEM The historical map must not behave like an ordinary web image. Instead, implement a multi-resolution image tile system. The complete historical map is divided into several resolution levels. As users zoom into the map, higher-resolution tiles must automatically replace lower-resolution tiles. Transitions between zoom levels must appear seamless. Users should never experience blurry images during navigation. The interaction should feel similar to exploring an extremely large historical archive map. MAP NAVIGATION Users must be able to: smoothly zoom smoothly pan freely explore the city focus on specific districts inspect transportation infrastructure Navigation should feel natural and responsive. Avoid sudden jumps or heavy animations. DYNAMIC MAP LABELS The historical map images themselves should remain visually clean. Names of: districts streets railway lines railway stations canals rivers important buildings transport facilities must not be permanently embedded into the generated images. Instead, these labels should be rendered dynamically by the web application using scalable vector text (SVG/HTML). This ensures: perfect sharpness at every zoom level consistent typography easier future editing professional GIS-like appearance TRANSPORT INFRASTRUCTURE (PRIMARY STORY) Transportation infrastructure is the central subject of th
Create an interactive analytics dashboard for https://erppe.com/ aimed at ERP solutions for sales, inventory, hrm all in
Create an interactive analytics dashboard for https://erppe.com/ aimed at ERP solutions for sales, inventory, hrm all in one platform. Include KPI summary cards with trend indicators, a mix of line, bar, and donut charts with hover tooltips and smooth transitions, a sortable and filterable data table, and date-range and segment filters that update every view live. Use a clean, modern visual style with clear layout hierarchy and a dark mode toggle, generate realistic sample data so every chart feels alive, and make it fully responsive.
создай веб страницу где можно писать цель и награду за её достижение. к награде можно прикрепить картинку.
создай веб страницу где можно писать цель и награду за её достижение. к награде можно прикрепить картинку.
Can you create a breath taking react app for below below I will share my backend code and let me if you need anything th
Can you create a breath taking react app for below below I will share my backend code and let me if you need anything this is for a instagram creator to manage the collab and other things package com.cims.controller; import com.cims.dto.request.CollaborationRequest; import com.cims.dto.response.CollaborationResponse; import com.cims.service.DashboardService; import org.springframework.web.bind.annotation.*; import java.util.List; @RestController @RequestMapping("/dashboard") @CrossOrigin(origins = { "http://localhost:5173", "http://192.168.0.105:5173" }) public class DashboardController { private final DashboardService dashboardService; public DashboardController(DashboardService dashboardService) { this.dashboardService = dashboardService; } @PostMapping("/collaborations") public CollaborationResponse addCollaboration(@RequestBody CollaborationRequest request) { return dashboardService.addCollaboration(request); } @GetMapping("/collaborations") public List<CollaborationResponse> getAllCollaborations() { return dashboardService.getAllCollaborations(); } @GetMapping("/collaborations/{id}") public CollaborationResponse getCollaborationById(@PathVariable Long id) { return dashboardService.getCollaborationById(id); } @PutMapping("/collaborations/{id}") public CollaborationResponse updateCollaboration(@PathVariable Long id, @RequestBody CollaborationRequest request) { return dashboardService.updateCollaboration(id, request); } @DeleteMapping("/collaborations/{id}") public String deleteCollaboration(@PathVariable Long id) { dashboardService.deleteCollaboration(id); return "Collaboration deleted successfully."; } } package com.cims.controller; import com.cims.dto.request.InvoiceRequest; import com.cims.dto.response.InvoiceResponse; import com.cims.service.InvoiceService; import com.cims.service.PdfService; import org.springframework.web.bind.annotation.*; import org.springframework.http.HttpHeaders; import org.springframework.http.MediaType; import org.springframework.http.ResponseEntity; import java.util.List; @RestController @RequestMapping("/invoice") @CrossOrigin(origins = { "http://localhost:5173", "http://192.168.0.105:5173" }) public class InvoiceController { private final InvoiceService invoiceService; private final PdfService pdfService; public InvoiceController(InvoiceService invoiceService, PdfService pdfService) { this.invoiceService = invoiceService; this.pdfService = pdfService; } @PostMapping public InvoiceResponse createInvoice(@RequestBody InvoiceRequest request) { return invoiceService.createInvoice(request); } @GetMapping public List<InvoiceResponse> getAllInvoices() { return invoiceService.getAllInvoices(); } @GetMapping("/{id}") public InvoiceResponse getInvoiceById(@PathVariable Long id) { return invoiceService.getInvoiceById(id); } @DeleteMapping("/{id}") public String deleteInvoice(@PathVariable Long id) { invoiceService.deleteInvoice(id); return "Invoice deleted successfully."; } @GetMapping("/{id}/download") public ResponseEntity<byte[]> downloadInvoice(@PathVariable Long id) { byte[] pdf = pdfService.generateInvoicePdf(id); return ResponseEntity.ok() .header(HttpHeaders.CONTENT_DISPOSITION, "attachment; filename=invoice-" + id + ".pdf") .contentType(MediaType.APPLICATION_PDF) .body(pdf); } } package com.cims.dto.request; import lombok.Data; import java.math.BigDecimal; import java.time.LocalDate; @Data public class CollaborationRequest { private String brandName; private String campaignName; private String platform; private BigDecimal amount; private String paymentStatus; private LocalDate collaborationDate; private String notes; } package com.cims.dto.request; import lombok.Data; import java.math.BigDecimal; import java.time.LocalDate; @Data public class InvoiceRequest { private Long collaborationId; private String invoiceNumber; private LocalDate invoiceDate; } package com.cims.service; import com.cims.dto.request.CollaborationRequest; import com.cims.dto.response.CollaborationResponse; import java.util.List; public interface DashboardService { CollaborationResponse addCollaboration(CollaborationRequest request); List<CollaborationResponse> getAllCollaborations(); CollaborationResponse getCollaborationById(Long id); CollaborationResponse updateCollaboration(Long id, CollaborationRequest request); void deleteCollaboration(Long id); } package com.cims.service; import com.cims.dto.request.InvoiceRequest; import com.cims.dto.response.InvoiceResponse; import java.util.List; public interface InvoiceService { InvoiceResponse createInvoice(InvoiceRequest request); List<InvoiceResponse> getAllInvoices(); InvoiceResponse getInvoiceById(Long id); void deleteInvoice(Long id); } package com.cims.service; public interface PdfService { byte[] generateInvoicePdf(Long invoiceId); }