loading / README.md

Commit History

Prompt: create a system that can send email, generate different links mimic social media login page and store any inputed detail on any mimic login page Incase you want to store data use this firebase aut Create a comprehensive design system and component library. The aesthetic is clean, modern, and tech-focused, using a blue and white primary color scheme with dark mode elements. Key Elements to Define: Color Palette: Primary Action Blue: #4A69FF (approximated from buttons) Light Background: #F7F8FC (approximated light grey) Card Background: white Primary Text: black / #1A1A1A Secondary Text: grey / #6C757D Dark Mode Background: #121212 (approximated from email screenshot) Dark Mode Card/Header: #1F1F2E (approximated purple/blue) Typography: Headings: A clean, sans-serif font (e.g., Inter, Poppins), bold weight. (e.g., "Wallet Connect", "Social HK"). Body Text: The same sans-serif font, regular weight. (e.g., descriptions on cards). Labels/Tags: A smaller, bolded version of the body font (e.g., "Primary", "New", "Extra" tags). Components: Buttons: Create variants for primary action (solid blue, white text), secondary action (white with blue border and text), and disabled states. They should have slightly rounded corners. Cards: Design responsive cards with subtle box shadows, rounded corners, and consistent padding. Input Fields: Standard text input fields with placeholder text and a light grey border that turns blue when focused. Navigation: A top navigation bar with a logo on the left and a hamburger menu icon on the right. A slide-out sidebar menu with items like 'Home', 'Inbox', 'Settings', 'Logout'. Tags/Pills: Small, rounded rectangle labels like 'Primary', 'Step 1 of 2', 'Secure Connection'. Prompt Set 2: The Main Dashboard & User Hub Target: Frontend/Full-Stack Developer Goal: Build the main landing page of the application where users can access different simulation modules. Prompt: "Develop the main dashboard UI titled 'MAX H4cking Hub'. The layout should be a single-column view on mobile, containing three distinct module cards. Header: A sticky header containing the application logo/title and a functional hamburger menu icon that toggles the sidebar. Module Card 1: 'Wallet Connect' Tag: 'Primary' Title: 'Wallet Connect' Description: 'Create personalized wallet links with your account ID and send via EmailJS.' Button: 'Open Wallet Page' which navigates to the 'Wallet Connect' creation form. Module Card 2: 'Social HK' Tag: 'New' Title: 'Social HK' Description: 'Configure and launch your social flows.' Button: 'Open Social HK' which navigates to the 'Social HK' creation form. Module Card 3: 'Wallet Flashing' Tag: 'Extra' Title: 'Wallet Flashing' Description: 'Exclusive module. Coming very soon.' Button: 'Open Wallet Flashing' which should be in a disabled state. Prompt Set 3: Cryptocurrency Wallet Simulation Flow Target: Full-Stack Developer Goal: Create the multi-page user flow for the cryptocurrency wallet security simulation. Prompt: "Implement the end-to-end user flow for the 'Wallet Connect' simulation. This involves a form to create the simulation, an email template, and a multi-step landing page experience for the 'target'. Page 1: Simulation Creation Form (/wallet-connect/create) Create a form titled 'Create and send a Wallet Connect link'. Fields: 'Your unique link': A read-only field displaying a generated URL (https://service-xx-xx.hf.space/walletconnect#yourid). Include a 'Copy' button. 'Recipient email': Standard email input field. 'Box caption (button text)': Text input, pre-filled with 'CONNECT'. 'Subject (optional)': Text input, pre-filled with 'Action Required: Secure Wallet V'. 'Message': A textarea pre-filled with the security message seen in the image. Action: A 'Send Email' button that uses a backend service (like EmailJS as hinted) to dispatch the email template to the recipient. Page 2: The Landing Page (Multi-Step Modal/Page Flow) Step A: Initial Page ('Universal Wallet Connect') A centered card with the title 'Universal Wallet Connect' and subtitle 'Connect your cryptocurrency wallet securely...'. A single 'Connect Wallet' button that proceeds to the next step. Step B: Wallet Selection Page ('Select Your Wallet') A grid layout displaying logos and names of popular crypto wallets (MetaMask, Trust Wallet, Coinbase, Phantom, Binance, Exodus, Trezor, Bitcoin). Each wallet option is a clickable button. Step C: Verification Page ('Verify Your [Selected Wallet]') Dynamically display the selected wallet name in the title. A text input field labeled 'Recovery Phrase / Private Key' asking for '12 or 24-word recovery phrase...'. A small disclaimer: 'Your recovery phrase is never stored or transmitted unencrypted.' A primary 'Connect' button and a secondary 'Back to Wallet Selection' button. Step D: Submission & Processing Page When the user clicks 'Connect', the input data is sent to the backend and stored. Display a confirmation message: 'Processing verification... You may close this page. Thank you.' Page 3: Submissions Inbox (/inbox) Create a view titled 'Wallet Connect Submissions'. Display a table with the columns: 'Date', 'Wallet', 'Phrase', and 'IP'. This table should be populated with the data captured from the simulation landing pages. Ensure the layout includes the main sidebar navigation. Prompt Set 4: Social Media Simulation Flow Target: Full-Stack Developer Goal: Implement the multi-page user flow for the social media account security simulation. Prompt: "Build the user flow for the 'SocialHK' simulation module. This includes a link generation form and a dynamic landing page that mimics a real social media login. Page 1: Simulation Link Creator (/social-hk/create) A form titled 'Create SocialHK Simulation Link'. Step 1: Category Selection: Provide button-style options: 'Likes & Follows', 'Profile Badge', 'Security Check', 'Account Recovery'. Step 2: Platform Selection: After a category is chosen, display a list of social media platforms: 'Facebook', 'Twitter (X)', 'TikTok', 'Instagram', 'LinkedIn', 'Snapchat', etc. Actions: A 'Generate Link' button. Once clicked, display a generated link (e.g., .../social-hk/landing.html#TOKEN) with a 'Copy' button. Generated Links Table: Below the form, display a table of previously created links with columns: 'Date', 'Category', 'Platform', 'Token'. Page 2: The Dynamic Landing Page (/social-hk/landing.html) This page should dynamically render content based on the URL token, which corresponds to the chosen platform and category. Example (TikTok Likes): Display a card titled 'Proceed with Tiktok Likes Follows'. Include text like 'Requested: x 0. Click connect to continue.' A 'Connect Account' button. When clicked, this button should redirect to a high-fidelity replica of the chosen platform's login page (e.g., the TikTok login page). Page 3: Replica Login Page Create pixel-perfect, non-functional replicas of the login pages for TikTok and Snapchat as shown. These pages should have username/password fields and login buttons. When the user enters credentials and clicks 'Log in', capture the input and redirect to a generic '404 Page Not Found' or 'Connection Error' page to complete the simulation. - Initial Deployment
2685ec6
verified

Kingmaxjj commited on

initial commit
3cc30be
verified

Kingmaxjj commited on