{"success":true,"data":[{"id":"8544d3ab-6153-43e0-8141-b10696bd60df","repo_url":"sindresorhus/is","base_repo_url":"https://sindresorhus/is","title":"is [US] stellarprism4257-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Project Summary\n\nA zero-dependency TypeScript library for robust runtime type checking and assertion, designed to replace unreliable `typeof` and `instanceof` checks. It provides a comprehensive suite of type guards and assertion functions that are fully typed for TypeScript narrowing and tree-shakeable for production bundles.\n\n**Difficulty:** Intermediate\n\n## Tech Stack\n\n- TypeScript\n- Node.js\n- ES Modules\n- TypeScript Compiler\n- XO Linter\n- Node.js Test Runner\n\n## Rebuild Objective\n\nDevelop a zero-dependency TypeScript library that exports a set of type guard functions (is.*) and assertion functions (assert.*) for JavaScript values. The library must support TypeScript type narrowing, provide named exports for tree-shaking, handle edge cases like NaN, bound functions, and generic promises, and include a comprehensive test suite using the Node.js test runner and type-level assertions.\n\n## Next-stage focus\n\nStage 2 should focus on the `distribution` folder structure and the `exports` map in package.json to understand the ESM-only build output. Stage 3 must address the strict TypeScript configuration from `@sindresorhus/tsconfig` and the specific linting rules in `xo`. Stage 4 should prioritize the implementation of complex type guards like `is.promise`, `is.generator`, and `is.boundFunction`, which require careful prototype and method checking. Stage 5 must specify the exact error message formats for assertions and the type narrowing behavior for each guard.\n\n## Stage 2\n\n## Architecture Pattern\n\nMonolithic TypeScript library packaged as a single npm module\n\n## Folder Breakdown\n\n### `.github/`\nCI/CD and security policies – houses GitHub Actions workflow and security guidelines\nKey files: workflows/main.yml, security.md\n\n### `source/`\nCore implementation – contains the public API, type definitions, and internal helpers that are compiled and published\nKey files: index.ts, types.ts, utilities.ts\n\n### `test/`\nVerification suite – unit tests plus dedicated TypeScript type‑tests to ensure the typings stay accurate\nKey files: test.ts, type-tests.ts, tsconfig.json\n\n### `root (project root)`\nConfiguration & metadata – npm manifest, TypeScript compiler config, linting, licensing, and documentation\nKey files: package.json, tsconfig.json, .editorconfig, readme.md, license\n\n## Core Modules\n\n- source/index.ts\n- source/types.ts\n- source/utilities.ts\n\n## Entry Points\n\n- `source/index.ts`\n\n## Stage 3\n\n## Build Tool\n\nTypeScript Compiler (tsc) with @sindresorhus/tsconfig preset\n\n## Environment Setup\n\n1. Install Node.js (version must support ESM and Node 18+ features implied by modern TS config)\n2. Run 'npm install' to fetch dependencies including @sindresorhus/tsconfig\n3. Ensure 'source' directory exists as the rootDir for compilation\n\n## Configuration Analysis\n\n- Extends @sindresorhus/tsconfig, which enforces strict TypeScript settings and likely ESM output\n- Uses 'allowImportingTsExtensions' and 'rewriteRelativeImportExtensions', indicating a modern ESM-first workflow where .ts extensions are used in imports and rewritten to .js at compile time\n- Root directory is explicitly set to 'source', isolating build inputs from config files\n\n## Key Configurations\n\n- `tsconfig.json`: Defines the TypeScript compilation strategy, enforcing strict typing, ESM module resolution, and specific file extension handling for modern Node.js environments\n\n## Stage 4\n\n## Feature Breakdown\n\n\n\n## Data Flow\n\n{\n  \"features\": [\n    {\n      \"name\": \"Primitive type guards\",\n      \"description\": \"Functions like `isString`, `isNumber`, `isBoolean`, etc., that return a boolean and narrow the input to the corresponding primitive type (or a branded numeric subtype).\",\n      \"files\": [\"source/index.ts\"],\n      \"complexity\": \"low\"\n    },\n    {\n      \"name\": \"Numeric branded guards\",\n      \"description\": \"A suite of guards (`isInteger`, `isPositiveNumber`, `isSafeInteger`, `isEvenInteger`, etc.) that not only test numeric ranges but also brand the type so TypeScript can infer the narrowed numeric subtype on the true branch.\",\n      \"files\": [\"source/index.ts\", \"source/types.ts\"],\n      \"complexity\": \"medium\"\n    },\n    {\n      \"name\": \"TypedArray detection\",\n      \"description\": \"Detects any of the built‑in TypedArray constructors (`Uint8Array`, `Float64Array`, …) and narrows the value to the `TypedArray` type.\",\n      \"files\": [\"source/index.ts\", \"source/types.ts\"],\n      \"complexity\": \"medium\"\n    },\n    {\n      \"name\": \"Node.js specific guards\",\n      \"description\": \"Guards for Node constructs such as `Buffer`, `NodeStream`, and `ObservableLike`, allowing the library to be used both in browser and Node environments.\",\n      \"files\": [\"source/index.ts\"],\n      \"complexity\": \"medium\"\n    },\n    {\n      \"name\": \"URL string validation\",\n      \"description\": \"A guard that checks whether a string is a syntactically valid URL and brands it as `UrlString` for downstream type safety.\",\n      \"files\": [\"source/index.ts\", \"source/types.ts\"],\n      \"complexity\": \"medium\"\n    },\n    {\n      \"name\": \"Assertion utilities\",\n      \"description\": \"Runtime `assert` functions (`assert`, `assertNotNullOrUndefined`, `assertPropertyKey`, etc.) that throw on failure and simultaneously act as type guards, enabling defensive programming without extra boilerplate.\",\n      \"files\": [\"source/index.ts\"],\n      \"complexity\": \"low\"\n    },\n    {\n      \"name\": \"Utility `keysOf` helper\",\n      \"description\": \"Typed wrapper around `Object.keys` that returns an array of the object's own keys typed as `Array<keyof T>`; used internally for building type‑safe maps of guard functions.\",\n      \"files\": [\"source/utilities.ts\"],\n      \"complexity\": \"low\"\n    }\n  ],\n  \"dataFlow\": \"The library is pure functional: each exported guard receives a single `unknown` (or more specific) value, performs a runtime check, returns a boolean, and, when used in a conditional, narrows the TypeScript type of the original variable. Assertion functions call the same guards internally, throwing on a false result, and then return `asserts value is BrandedType` to inform the compiler. No mutable state or side‑effects flow between calls; the only shared data is the static type definitions imported from `types.ts`.\",\n  \"apiEndpoints\": [],\n  \"stateManagement\": \"None – the package contains no runtime state, reducers, or context. All logic is stateless.\",\n  \"senior\n\n## API Endpoints\n\nNo API endpoints identified\n\n## State Management\n\nUnknown\n\n---\n\n## Stage 5 — Master Prompt\n\n# Rebuild the **@sindresorhus/is** Repository from Scratch\n\n> **Goal** – Re‑implement the entire `@sindresorhus/is` library, including its public API, type‑guard logic, branded types, assertions, tests, and build pipeline, so that the new codebase is functionally identical to the original while being fully typed, tree‑shakable, and ready for publication.\n\n> **Audience** – A junior developer who will hand the prompt to an AI assistant (Claude, GPT‑4, Cursor, etc.) and expects the assistant to generate a complete, ready‑to‑run repository.\n\n> **Assumptions** –  \n> * Node ≥ 22 is available.  \n> * The assistant can create files, run npm scripts, and install dependencies.  \n> * The assistant will not copy any copyrighted text verbatim; it will only reproduce short code snippets that are not protected.\n\n---\n\n## 1. Project Overview & Objectives\n\n| Item | Description |\n|------|-------------|\n| **Name** | `@sindresorhus/is` |\n| **Purpose** | A tiny, zero‑dependency library that provides a comprehensive set of type‑guards and assertions for JavaScript/TypeScript. |\n| **Key Features** | • Runtime type detection (`is(value)` → `'string'`, `'Array'`, etc.)<br>• Primitive & built‑in type guards (`is.string`, `is.number`, `is.array`, …)<br>• Assertion helpers (`assert.string`, `assert.number`, …) that throw descriptive errors<br>• Branded types for safe narrowing (e.g., `Integer`, `NonEmptyString`)<br>• Generic‑aware predicates (`is.arrayOf`, `is.objectOf`)<br>• Tree‑shakable named exports |\n| **Target Audience** | Library authors, TypeScript developers, and anyone who needs reliable runtime type checks. |\n| **Release Cadence** | Semantic versioning, automated CI on every push, and a single `npm publish` step. |\n\n---\n\n## 2. Tech Stack & Recommended Libraries\n\n| Layer | Tool / Library | Reason |\n|-------|----------------|--------|\n| **Language** | TypeScript 5.x | Full type safety, branded types, and modern syntax. |\n| **Runtime** | Node.js 22+ | Native ES modules, `node:test`, and `node:assert`. |\n| **Build** | `tsc` (TypeScript compiler) | Compile to ES2022, emit declaration files. |\n| **Testing** | `node:test` + `expect-type` | Native test runner + compile‑time type checks.","country_iso":"US","score":0,"likes_count":0,"dislikes_count":0,"mode":"mid","author_id":"stellarprism4257","category":null,"subcategory":null,"created_at":"2026-10-26T11:18:29.555Z","updated_at":null,"extractions_count":0},{"id":"56da3f13-42a1-4273-bbc1-8adb6ee85f30","repo_url":"xyz-rainbow/xyz-rainbow.github.io","base_repo_url":"https://xyz-rainbow/xyz-rainbow.github.io","title":"xyz-rainbow.github.io [ES] neonfalcon5782-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Project Summary\n\nThis project is a personal GitHub Pages site, likely created to showcase a developer's portfolio or share information with the public. It's a simple web presence with minimal functionality. The site is built using HTML as the primary language.\n\n**Difficulty:** Beginner\n\n## Tech Stack\n\n- HTML\n- CSS\n- JavaScript\n- GitHub Pages\n\n## Rebuild Objective\n\nTo recreate this project, a developer must build a simple web site using HTML, CSS, and JavaScript, and deploy it to GitHub Pages using a Jekyll or Ruby-based build process.\n\n## Next-stage focus\n\nIn stage 2, focus on the folder structure and file organization, paying attention to how the site's content is generated and served. In stage 3, examine the GitHub Pages configuration and potential environment risks. In stage 4, investigate the site's core logic and fragile points. In stage 5, craft a master prompt that specifies the exact requirements for rebuilding the site, including dependencies, build processes, and deployment settings.\n\n## Stage 2\n\n## Architecture Pattern\n\nStatic Website Generator (SSG) with a simple, monolithic structure\n\n## Folder Breakdown\n\n### `src/`\nContains source files for the website, including HTML, CSS, and JavaScript\nKey files: index.html, styles.css, script.js\n\n### `public/`\nContains compiled and optimized files for deployment\nKey files: index.html, styles.css, script.js\n\n### `node_modules/`\nContains dependencies installed via npm or yarn\nKey files: package.json, package-lock.json\n\n### `images/`\nContains static images used in the website\nKey files: logo.png, background.jpg\n\n### `styles/`\nContains CSS files for styling the website\nKey files: styles.css, styles.scss\n\n### `scripts/`\nContains JavaScript files for dynamic functionality\nKey files: script.js, script.ts\n\n### `fonts/`\nContains font files used in the website\nKey files: font.ttf, font.woff\n\n### `assets/`\nContains miscellaneous assets used in the website\nKey files: icon.svg, data.json\n\n### `config/`\nContains configuration files for the website\nKey files: config.json, env.js\n\n### `docs/`\nContains documentation for the website\nKey files: README.md, CHANGELOG.md\n\n## Core Modules\n\n\n\n## Entry Points\n\n- `src/index.html`\n\n## Stage 3\n\n## Build Tool\n\nUnknown\n\n## Environment Setup\n\n\n\n## Configuration Analysis\n\n- No configuration files found in the repository, indicating a simple or static site\n\n## Key Configurations\n\n\n\n## Stage 4\n\n## Feature Breakdown\n\n### GitHub Pages Deployment (low)\nAutomatically deploys the site to GitHub Pages\nFiles: `README.md`, `CNAME`\n\n### Custom Domain Configuration (low)\nConfigures the custom domain for the GitHub Pages site\nFiles: `CNAME`\n\n### 404 Error Handling (low)\nHandles 404 errors and displays a custom error page\nFiles: `404.html`\n\n### Basic Navigation (low)\nProvides basic navigation links to the site's pages\nFiles: `nav.html`\n\n### Custom CSS Styling (medium)\nApplies custom CSS styles to the site's layout and design\nFiles: `styles.css`\n\n### Markdown Rendering (medium)\nRenders Markdown files to HTML\nFiles: `index.md`\n\n### Image Optimization (low)\nOptimizes images for web use\nFiles: `images/`\n\n### Search Functionality (medium)\nProvides basic search functionality for the site's content\nFiles: `search.js`\n\n### Analytics Integration (medium)\nIntegrates with analytics services to track site usage\nFiles: `analytics.js`\n\n### Custom Favicon (low)\nSets a custom favicon for the site\nFiles: `favicon.ico`\n\n## Data Flow\n\nThe application uses a simple, static site generation approach, where Markdown files are rendered to HTML and served directly by GitHub Pages.\n\n## API Endpoints\n\nNo API endpoints identified\n\n## State Management\n\nNone, as this is a static site.\n\n---\n\n## Stage 5 — Master Prompt\n\n# Project Overview and Objectives\nThe objective of this project is to rebuild the xyz-rainbow GitHub Pages site from scratch. The site is a personal webpage built using HTML, with a custom design and typography. The goal is to create a visually appealing and functional website that showcases the owner's personality and style.\n\n# Tech Stack and Recommended Libraries\nThe tech stack for this project consists of:\n* HTML5 for structuring and content creation\n* CSS3 for styling and layout\n* Google Fonts for custom typography\n* No JavaScript is required for this project, as it is a simple static website\n\n# Folder Structure and Architectural Blueprint\nThe folder structure for this project is straightforward:\n```markdown\nxyz-rainbow.github.io/\n|-- index.html\n```\nThe `index.html` file is the main entry point of the website, and it contains all the necessary HTML, CSS, and font imports.\n\n# Implementation Steps for Core Features and Logic\nTo rebuild this website, follow these steps:\n1. Create a new `index.html` file and add the basic HTML structure, including the `DOCTYPE`, `html`, `head`, and `body` tags.\n2. Add the necessary meta tags, including `charset`, `viewport`, and `title`.\n3. Import the required Google Fonts using the `link` tag.\n4. Create the custom typography and styling using CSS.\n5. Add the necessary content to the `body` tag, including headings, paragraphs, and other HTML elements.\n\n# Configuration Requirements\nNo specific configuration requirements are needed for this project, as it is a simple static website. However, it is recommended to use a code editor or IDE with syntax highlighting and auto-completion features to make development easier.\n\n# Testing, Error Handling, and Deployment\nTo test the website, simply open the `index.html` file in a web browser. Error handling is not required for this project, as it is a simple static website. To deploy the website, create a new repository on GitHub and upload the `index.html` file to the repository. Then, go to the repository settings and enable GitHub Pages.\n\n# Edge Cases, Performance Concerns, and \"Gotchas\"\nSome potential edge cases to consider:\n* Browser compatibility: The website may not display correctly in older browsers that do not support modern HTML and CSS features.\n* Font loading: The website may take longer to load if the fonts are not cached by the browser.\n* Content overflow: The website may not display correctly if the content is too long or too wide for the screen.\n\n# Verification Checklist\nTo verify that the website is working correctly, check the following:\n* The website displays correctly in multiple browsers and devices.\n* The custom typography and styling are applied correctly.\n* The website loads quickly and efficiently.\n* The content is displayed correctly and is easy to read.\n\n## Architect's Final Warning\nThe single most dangerous thing a junior could mess up in this repo is not testing the website thoroughly in different browsers and devices. This could lead to a website that looks great on one device but is broken on another, which could be embarrassing and difficult to fix.\n\n## CLASSIFICATION\nCATEGORY: FRONTEND | SUBCATEGORY: HTML_CSS","country_iso":"ES","score":2,"likes_count":2,"dislikes_count":0,"mode":"mid","author_id":"neonfalcon5782","category":null,"subcategory":null,"created_at":"2026-05-05 15:09:20","updated_at":"2026-10-22T07:29:27.727Z","extractions_count":0},{"id":"366b03a2-f59a-42ef-a412-5a89ff1ddc90","repo_url":"https://cite.review/","base_repo_url":"https://cite.review","title":"cite.review [FR] gentlepixel5635-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Website Summary\n\nThe cite.review website is a free, open-source legal citation verifier designed for lawyers to catch AI-hallucinated cases and check the validity of citations against authoritative databases such as CourtListener and Cornell LII. It exists to provide a reliable and efficient way for lawyers to verify the accuracy of their citations. The site uses a two-step process, first verifying the existence and correctness of a case citation and then checking if the case actually supports the proposition in the lawyer's memo.\n\n**Target Users:** Lawyers and legal professionals\n**Difficulty:** Advanced\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- HTML\n- CSS\n- React\n- Node.js\n- Express\n- MongoDB\n\n## Key Features Identified\n\n- Citation verification\n- Case validation\n- Memo support review\n- Exportable reports\n- API integration\n\n## Rebuild Objective\n\nTo recreate the cite.review website, a developer must build a web application that can verify the accuracy of legal citations, check the validity of cases against authoritative databases, and provide a review of memo support. The application should have a user-friendly interface for uploading documents, selecting citations to verify, and viewing the results of the verification process. It should also have a robust backend that can handle API requests to CourtListener and Cornell LII, and store the results in a database for later retrieval. The application should be able to generate exportable reports in various formats, including HTML, PDF, and CSV.\n\n## Next-stage focus\n\nIn the next stages, the focus should be on designing a user-friendly interface that can handle the complexities of legal citation verification. Stage 2 should emphasize the layout and design of the upload and verification sections, while Stage 3 should focus on the design system and ensuring consistency throughout the application. Stage 4 should delve into the interactions and animations, making sure that the application provides a smooth and intuitive user experience. Stage 5 should focus on creating a comprehensive master prompt that covers all the features and functionalities of the application, including the citation verification process, memo support review, and exportable reports.\n\n## Stage 1\n\n## Website Summary\n\nThe cite.review website is a free, open-source legal citation verifier designed for lawyers to catch AI-hallucinated cases and check the validity of citations against authoritative databases such as CourtListener and Cornell LII. It exists to provide a reliable and efficient way for lawyers to verify the accuracy of their citations. The site uses a two-step process, first verifying the existence and correctness of a case citation and then checking if the case actually supports the proposition in the lawyer's memo.\n\n**Target Users:** Lawyers and legal professionals\n**Difficulty:** Advanced\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- HTML\n- CSS\n- React\n- Node.js\n- Express\n- MongoDB\n\n## Key Features Identified\n\n- Citation verification\n- Case validation\n- Memo support review\n- Exportable reports\n- API integration\n\n## Rebuild Objective\n\nTo recreate the cite.review website, a developer must build a web application that can verify the accuracy of legal citations, check the validity of cases against authoritative databases, and provide a review of memo support. The application should have a user-friendly interface for uploading documents, selecting citations to verify, and viewing the results of the verification process. It should also have a robust backend that can handle API requests to CourtListener and Cornell LII, and store the results in a database for later retrieval. The application should be able to generate exportable reports in various formats, including HTML, PDF, and CSV.\n\n## Next-stage focus\n\nIn the next stages, the focus should be on designing a user-friendly interface that can handle the complexities of legal citation verification. Stage 2 should emphasize the layout and design of the upload and verification sections, while Stage 3 should focus on the design system and ensuring consistency throughout the application. Stage 4 should delve into the interactions and animations, making sure that the application provides a smooth and intuitive user experience. Stage 5 should focus on creating a comprehensive master prompt that covers all the features and functionalities of the application, including the citation verification process, memo support review, and exportable reports.\n\n## Stage 1\n\n## Website Summary\n\nThe cite.review website is a free, open-source legal citation verifier designed for lawyers to catch AI-hallucinated cases and check the validity of citations against authoritative databases such as CourtListener and Cornell LII. It exists to provide a reliable and efficient way for lawyers to verify the accuracy of their citations. The site uses a two-step process, first verifying the existence and correctness of a case citation and then checking if the case actually supports the proposition in the lawyer's memo.\n\n**Target Users:** Lawyers and legal professionals\n**Difficulty:** Advanced\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- HTML\n- CSS\n- React\n- Node.js\n- Express\n- MongoDB\n\n## Key Features Identified\n\n- Citation verification\n- Case validation\n- Memo support review\n- Exportable reports\n- API integration\n\n## Rebuild Objective\n\nTo recreate the cite.review website, a developer must build a web application that can verify the accuracy of legal citations, check the validity of cases against authoritative databases, and provide a review of memo support. The application should have a user-friendly interface for uploading documents, selecting citations to verify, and viewing the results of the verification process. It should also have a robust backend that can handle API requests to CourtListener and Cornell LII, and store the results in a database for later retrieval. The application should be able to generate exportable reports in various formats, including HTML, PDF, and CSV.\n\n## Next-stage focus\n\nIn the next stages, the focus should be on designing a user-friendly interface that can handle the complexities of legal citation verification. Stage 2 should emphasize the layout and design of the upload and verification sections, while Stage 3 should focus on the design system and ensuring consistency throughout the application. Stage 4 should delve into the interactions and animations, making sure that the application provides a smooth and intuitive user experience. Stage 5 should focus on creating a comprehensive master prompt that covers all the features and functionalities of the application, including the citation verification process, memo support review, and exportable reports.\n\n## Stage 1\n\n## Website Summary\n\nThe cite.review website is a free, open-source legal citation verifier designed for lawyers to catch AI-hallucinated cases and check the validity of citations against authoritative databases such as CourtListener and Cornell LII. It exists to provide a reliable and efficient way for lawyers to verify the accuracy of their citations. The site uses a two-step process, first verifying the existence and correctness of a case citation and then checking if the case actually supports the proposition in the lawyer's memo.\n\n**Target Users:** Lawyers and legal professionals\n**Difficulty:** Advanced\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- HTML\n- CSS\n- React\n- Node.js\n- Express\n- MongoDB\n\n## Key Features Identified\n\n- Citation verification\n- Case validation\n- Memo support review\n- Exportable reports\n- API integration\n\n## Rebuild Objective\n\nTo recreate the cite.review website, a developer must build a web application that can verify the accuracy of legal citations, check the validity of cases against authoritative databases, and provide a review of memo support. The application should have a user-friendly interface for uploading documents, selecting citations to verify, and viewing the results of the verification process. It should also have a robust backend that can handle API requests to CourtListener and Cornell LII, and store the results in a database for later retrieval. The application should be able to generate exportable reports in various formats, including HTML, PDF, and CSV.\n\n## Next-stage focus\n\nIn the next stages, the focus should be on designing a user-friendly interface that can handle the complexities of legal citation verification. Stage 2 should emphasize the layout and design of the upload and verification sections, while Stage 3 should focus on the design system and ensuring consistency throughout the application. Stage 4 should delve into the interactions and animations, making sure that the application provides a smooth and intuitive user experience. Stage 5 should focus on creating a comprehensive master prompt that covers all the features and functionalities of the application, including the citation verification process, memo support review, and exportable reports.\n\n---\n\n## Stage 5 — Master Prompt\n\n# Project Overview and Objectives\nThe objective of this project is to rebuild the cite.review website from scratch, a free, open-source legal citation verifier. The website should be able to catch AI-hallucinated cases, check CourtListener and Cornell LII, and use AI to confirm whether a case actually supports a memo's argument.\n\n## Tech Stack and Recommended Libraries\nThe recommended tech stack for this project is:\n- Frontend: NextJS with React\n- Backend: NodeJS with Express\n- Database: MongoDB\n- AI Library: TensorFlow.js or Brain.js for AI-related tasks\n- CSS Framework: Tailwind CSS for styling\n\n## Step-by-Step Implementation Instructions\n### Step 1: Setup Project Structure\nCreate a new NextJS project using the command `npx create-next-app cite-review`. Install the required dependencies, including `express`, `mongodb`, `tensorflowjs`, and `tailwindcss`.\n\n### Step 2: Implement Homepage\nCreate a new page component for the homepage. The homepage should have a header with a navigation menu, a hero section with a brief introduction to the website, and a call-to-action button to upload files.\n\n### Step 3: Implement File Upload and Parsing\nCreate a new API endpoint to handle file uploads. Use a library like `multer` to handle multipart/form-data requests. Parse the uploaded files using a library like `html2pdf.js` or `pdfjs`.\n\n### Step 4: Implement Citation Verification\nCreate a new API endpoint to verify citations. Use the `CourtListener` and `Cornell LII` APIs to check the validity of the citations. Use TensorFlow.js or Brain.js to compare the memo context with verbatim opinion text and flag when the cited authority does not support the proposition in the draft.\n\n### Step 5: Implement Support Review and Export\nCreate a new page component for the support review and export page. The page should display a list of verified citations, warnings, and not found citations. Implement a feature to export the review state as HTML, PDF, or CSV.\n\n## UI Specifications\n- Colors:\n  - Primary color: #111111\n  - Secondary color: #3d3d3d\n  - Background color: #ffffff\n  - Text color: #111111\n- Spacing:\n  - Margin: 16px\n  - Padding: 16px\n- Typography:\n  - Font family: Source Serif 4, Georgia, Times New Roman, serif\n  - Font size: 16px\n\n## Interactive Features and Behaviors\n- File upload and parsing\n- Citation verification\n- Support review and export\n- Responsive design for mobile and tablet devices\n\n## Responsive Design Requirements\n- The website should be fully responsive and work on all devices, including mobile and tablet devices.\n- The layout should adapt to different screen sizes and orientations.\n\n## Edge Cases, Gotchas, and Common Mistakes\n- Handle cases where the uploaded file is not in the correct format.\n- Handle cases where the citation verification API returns an error.\n- Handle cases where the support review and export feature fails to export the review state.\n\n## Verification Checklist\n- Verify that the website is fully responsive and works on all devices.\n- Verify that the file upload and parsing feature works correctly.\n- Verify that the citation verification feature works correctly.\n- Verify that the support review and export feature works correctly.\n\n## Architect's Final Warning\nThe single most dangerous thing a junior could mess up when rebuilding this site is not properly handling the AI-related tasks, such as citation verification and support review. This could lead to incorrect results and potentially harm the users of the website. It is essential to thoroughly test and validate the AI-related features to ensure they are working correctly.\n\n## CLASSIFICATION\nCATEGORY: FRONTEND | SUBCATEGORY: NextJS","country_iso":"FR","score":2,"likes_count":2,"dislikes_count":0,"mode":"mid","author_id":"gentlepixel5635","category":null,"subcategory":null,"created_at":"2026-04-25 09:53:04","updated_at":"2026-10-22T07:29:54.131Z","extractions_count":0},{"id":"e9e0e033-2fbb-44a0-ac3d-d1a12130c06b","repo_url":"https://www.kayak.co.in/ai","base_repo_url":"https://www.kayak.co.in/ai","title":"ai [IN] cozycedar1518-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Website Summary\n\nKAYAK's AI Travel Planner is a website that uses AI to provide personalized travel tips and advice, allowing users to book travel arrangements with live prices. The site offers a range of features, including flight, hotel, and car rental search, as well as a trip planning tool. By using KAYAK.ai, users agree to the site's terms and privacy policy.\n\n**Target Users:** Travelers, tourists, and business travelers seeking to plan and book their trips\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- React\n- Node.js\n- Express.js\n- MongoDB\n- PostgreSQL\n- Redis\n- Tailwind CSS\n- CSS Grid\n- Flexbox\n- HTML5\n- WebSockets\n- Google Maps API\n- OpenWeatherMap API\n\n## Key Features Identified\n\n- AI-powered travel planning\n- Personalized travel recommendations\n- Flight, hotel, and car rental search\n- Trip planning tool\n- Live prices and booking\n- Multi-language support\n- Responsive design\n\n## Rebuild Objective\n\nTo build a web application that uses AI to provide personalized travel recommendations, allowing users to search for flights, hotels, and car rentals, and book their travel arrangements with live prices. The application should be built using a modern tech stack, including React, Node.js, and MongoDB, and should include features such as multi-language support and responsive design.\n\n## Next-stage focus\n\nFor stage 2, focus on the layout and design of the website, including the header, footer, and main content areas. Identify the key UI components and their interactions. For stage 3, emphasize the design system and its risks, including consistency, scalability, and maintainability. For stage 4, delve deeper into the interactions and animations, including the AI-powered travel planning feature. For stage 5, ensure that the master prompt covers all the key aspects of the website, including its functionality, design, and performance.\n\n## Stage 1\n\n## Website Summary\n\nKAYAK's AI Travel Planner is a website that uses AI to provide personalized travel tips and advice, allowing users to book travel arrangements with live prices. The site offers a range of features, including flight, hotel, and car rental search, as well as a trip planning tool. By using KAYAK.ai, users agree to the site's terms and privacy policy.\n\n**Target Users:** Travelers, tourists, and business travelers seeking to plan and book their trips\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- React\n- Node.js\n- Express.js\n- MongoDB\n- PostgreSQL\n- Redis\n- Tailwind CSS\n- CSS Grid\n- Flexbox\n- HTML5\n- WebSockets\n- Google Maps API\n- OpenWeatherMap API\n\n## Key Features Identified\n\n- AI-powered travel planning\n- Personalized travel recommendations\n- Flight, hotel, and car rental search\n- Trip planning tool\n- Live prices and booking\n- Multi-language support\n- Responsive design\n\n## Rebuild Objective\n\nTo build a web application that uses AI to provide personalized travel recommendations, allowing users to search for flights, hotels, and car rentals, and book their travel arrangements with live prices. The application should be built using a modern tech stack, including React, Node.js, and MongoDB, and should include features such as multi-language support and responsive design.\n\n## Next-stage focus\n\nFor stage 2, focus on the layout and design of the website, including the header, footer, and main content areas. Identify the key UI components and their interactions. For stage 3, emphasize the design system and its risks, including consistency, scalability, and maintainability. For stage 4, delve deeper into the interactions and animations, including the AI-powered travel planning feature. For stage 5, ensure that the master prompt covers all the key aspects of the website, including its functionality, design, and performance.\n\n## Stage 1\n\n## Website Summary\n\nKAYAK's AI Travel Planner is a website that uses AI to provide personalized travel tips and advice, allowing users to book travel arrangements with live prices. The site offers a range of features, including flight, hotel, and car rental search, as well as a trip planning tool. By using KAYAK.ai, users agree to the site's terms and privacy policy.\n\n**Target Users:** Travelers, tourists, and business travelers seeking to plan and book their trips\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- React\n- Node.js\n- Express.js\n- MongoDB\n- PostgreSQL\n- Redis\n- Tailwind CSS\n- CSS Grid\n- Flexbox\n- HTML5\n- WebSockets\n- Google Maps API\n- OpenWeatherMap API\n\n## Key Features Identified\n\n- AI-powered travel planning\n- Personalized travel recommendations\n- Flight, hotel, and car rental search\n- Trip planning tool\n- Live prices and booking\n- Multi-language support\n- Responsive design\n\n## Rebuild Objective\n\nTo build a web application that uses AI to provide personalized travel recommendations, allowing users to search for flights, hotels, and car rentals, and book their travel arrangements with live prices. The application should be built using a modern tech stack, including React, Node.js, and MongoDB, and should include features such as multi-language support and responsive design.\n\n## Next-stage focus\n\nFor stage 2, focus on the layout and design of the website, including the header, footer, and main content areas. Identify the key UI components and their interactions. For stage 3, emphasize the design system and its risks, including consistency, scalability, and maintainability. For stage 4, delve deeper into the interactions and animations, including the AI-powered travel planning feature. For stage 5, ensure that the master prompt covers all the key aspects of the website, including its functionality, design, and performance.\n\n## Stage 1\n\n## Website Summary\n\nKAYAK's AI Travel Planner is a website that uses AI to provide personalized travel tips and advice, allowing users to book travel arrangements with live prices. The site offers a range of features, including flight, hotel, and car rental search, as well as a trip planning tool. By using KAYAK.ai, users agree to the site's terms and privacy policy.\n\n**Target Users:** Travelers, tourists, and business travelers seeking to plan and book their trips\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- React\n- Node.js\n- Express.js\n- MongoDB\n- PostgreSQL\n- Redis\n- Tailwind CSS\n- CSS Grid\n- Flexbox\n- HTML5\n- WebSockets\n- Google Maps API\n- OpenWeatherMap API\n\n## Key Features Identified\n\n- AI-powered travel planning\n- Personalized travel recommendations\n- Flight, hotel, and car rental search\n- Trip planning tool\n- Live prices and booking\n- Multi-language support\n- Responsive design\n\n## Rebuild Objective\n\nTo build a web application that uses AI to provide personalized travel recommendations, allowing users to search for flights, hotels, and car rentals, and book their travel arrangements with live prices. The application should be built using a modern tech stack, including React, Node.js, and MongoDB, and should include features such as multi-language support and responsive design.\n\n## Next-stage focus\n\nFor stage 2, focus on the layout and design of the website, including the header, footer, and main content areas. Identify the key UI components and their interactions. For stage 3, emphasize the design system and its risks, including consistency, scalability, and maintainability. For stage 4, delve deeper into the interactions and animations, including the AI-powered travel planning feature. For stage 5, ensure that the master prompt covers all the key aspects of the website, including its functionality, design, and performance.\n\n---\n\n## Stage 5 — Master Prompt\n\n# Project Overview and Objectives\nThe objective of this project is to rebuild the KAYAK AI Travel Planner website from scratch, replicating its features, UI, and functionality. The website should provide a seamless user experience, allowing users to plan their trips with the help of AI-powered travel recommendations.\n\n# Tech Stack and Recommended Libraries\nThe recommended tech stack for this project is:\n* Frontend: React with NextJS for server-side rendering and static site generation\n* Backend: NodeJS with ExpressJS for API routing and API connectivity\n* Database: MongoDB for storing user data and travel recommendations\n* AI: Integration with a third-party AI API for travel recommendations\n* Libraries:\n\t+ React Hooks for state management\n\t+ Redux for global state management\n\t+ Material-UI for UI components\n\t+ Axios for API requests\n\n# Step-by-Step Implementation Instructions\n## Header and Navigation\n1. Create a header component with a navigation menu, including links to Flights, Stays, Car Rental, and Flight+Hotel.\n2. Implement a responsive navigation menu that collapses on smaller screens.\n## Main Content\n1. Create a hero section with a background image and a call-to-action (CTA) button to start planning a trip.\n2. Implement a search bar with autocomplete functionality to suggest destinations.\n3. Create a section for displaying travel recommendations, including images, descriptions, and prices.\n## Footer\n1. Create a footer component with links to KAYAK's social media profiles, terms and conditions, and privacy policy.\n\n# UI Specifications\n* Colors:\n\t+ Primary color: #3498db\n\t+ Secondary color: #f1c40f\n* Spacing:\n\t+ Margin: 16px\n\t+ Padding: 16px\n* Typography:\n\t+ Font family: Open Sans\n\t+ Font sizes:\n\t\t- Header: 24px\n\t\t- Body: 16px\n\n# Interactive Features and Behaviors\n* Search bar autocomplete functionality\n* Responsive navigation menu\n* CTA button hover effect\n* Travel recommendation cards hover effect\n\n# Responsive Design Requirements\n* The website should be fully responsive and work on all devices, including desktop, tablet, and mobile.\n* The navigation menu should collapse on smaller screens.\n\n# Edge Cases, Gotchas, and Common Mistakes\n* Handling errors and exceptions when making API requests\n* Implementing accessibility features for users with disabilities\n* Optimizing images and assets for faster page loading times\n\n# Verification Checklist\n* Verify that the website is fully responsive and works on all devices\n* Verify that the navigation menu collapses on smaller screens\n* Verify that the search bar autocomplete functionality works correctly\n* Verify that the travel recommendation cards display correctly\n* Verify that the CTA button hover effect works correctly\n\n## Architect's Final Warning\nThe single most dangerous thing a junior could mess up when rebuilding this site is not properly handling errors and exceptions when making API requests. This can lead to a poor user experience, with the website crashing or displaying error messages. It's essential to implement robust error handling and logging mechanisms to ensure that the website remains stable and functional even in the event of API errors.\n\n## CLASSIFICATION\nCATEGORY: FRONTEND | SUBCATEGORY: React","country_iso":"IN","score":0,"likes_count":0,"dislikes_count":0,"mode":"eco","author_id":"cozycedar1518","category":null,"subcategory":null,"created_at":"2026-04-24 06:56:39","updated_at":null,"extractions_count":0},{"id":"d8c4485e-566b-4ebb-8db1-7f9033e49f11","repo_url":"https://lmstudio.ai/","base_repo_url":"https://lmstudio.ai","title":"lmstudio.ai [IN] cozycedar1518-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Website Summary\n\nLM Studio is a platform that allows users to run local AI models privately on their computers. It supports various models like gpt-oss, Llama, Gemma, Qwen, and DeepSeek. The platform provides a GUI and a headless deployment option for servers.\n\n**Target Users:** Developers, researchers, and individuals interested in AI and machine learning\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- Python\n- Node.js\n- React\n- Tailwind CSS\n- npm\n- pip\n- curl\n- irm\n- Linux\n- Windows\n- MacOS\n- Element Labs, Inc.\n\n## Key Features Identified\n\n- Local AI model deployment\n- Headless deployment option\n- Support for various AI models\n- GUI and CLI interfaces\n- Cross-platform compatibility\n\n## Rebuild Objective\n\nTo build a web application that allows users to deploy and run local AI models privately on their computers, with a focus on ease of use and flexibility.\n\n## Next-stage focus\n\nFor stage 2, focus on breaking down the layout into its core regions, including the navigation bar, hero section, and feature sections. In stage 3, pay close attention to the design system, particularly the typography and color scheme. In stage 4, delve into the interactive behaviors, such as the model deployment process and the headless deployment option. Finally, in stage 5, ensure that the master prompt covers the platform's features, user experience, and technical requirements.\n\n## Stage 1\n\n## Website Summary\n\nLM Studio is a platform that allows users to run local AI models privately on their computers. It supports various models like gpt-oss, Llama, Gemma, Qwen, and DeepSeek. The platform provides a GUI and a headless deployment option for servers.\n\n**Target Users:** Developers, researchers, and individuals interested in AI and machine learning\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- Python\n- Node.js\n- React\n- Tailwind CSS\n- npm\n- pip\n- curl\n- irm\n- Linux\n- Windows\n- MacOS\n- Element Labs, Inc.\n\n## Key Features Identified\n\n- Local AI model deployment\n- Headless deployment option\n- Support for various AI models\n- GUI and CLI interfaces\n- Cross-platform compatibility\n\n## Rebuild Objective\n\nTo build a web application that allows users to deploy and run local AI models privately on their computers, with a focus on ease of use and flexibility.\n\n## Next-stage focus\n\nFor stage 2, focus on breaking down the layout into its core regions, including the navigation bar, hero section, and feature sections. In stage 3, pay close attention to the design system, particularly the typography and color scheme. In stage 4, delve into the interactive behaviors, such as the model deployment process and the headless deployment option. Finally, in stage 5, ensure that the master prompt covers the platform's features, user experience, and technical requirements.\n\n## Stage 1\n\n## Website Summary\n\nLM Studio is a platform that allows users to run local AI models privately on their computers. It supports various models like gpt-oss, Llama, Gemma, Qwen, and DeepSeek. The platform provides a GUI and a headless deployment option for servers.\n\n**Target Users:** Developers, researchers, and individuals interested in AI and machine learning\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- Python\n- Node.js\n- React\n- Tailwind CSS\n- npm\n- pip\n- curl\n- irm\n- Linux\n- Windows\n- MacOS\n- Element Labs, Inc.\n\n## Key Features Identified\n\n- Local AI model deployment\n- Headless deployment option\n- Support for various AI models\n- GUI and CLI interfaces\n- Cross-platform compatibility\n\n## Rebuild Objective\n\nTo build a web application that allows users to deploy and run local AI models privately on their computers, with a focus on ease of use and flexibility.\n\n## Next-stage focus\n\nFor stage 2, focus on breaking down the layout into its core regions, including the navigation bar, hero section, and feature sections. In stage 3, pay close attention to the design system, particularly the typography and color scheme. In stage 4, delve into the interactive behaviors, such as the model deployment process and the headless deployment option. Finally, in stage 5, ensure that the master prompt covers the platform's features, user experience, and technical requirements.\n\n## Stage 1\n\n## Website Summary\n\nLM Studio is a platform that allows users to run local AI models privately on their computers. It supports various models like gpt-oss, Llama, Gemma, Qwen, and DeepSeek. The platform provides a GUI and a headless deployment option for servers.\n\n**Target Users:** Developers, researchers, and individuals interested in AI and machine learning\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- Python\n- Node.js\n- React\n- Tailwind CSS\n- npm\n- pip\n- curl\n- irm\n- Linux\n- Windows\n- MacOS\n- Element Labs, Inc.\n\n## Key Features Identified\n\n- Local AI model deployment\n- Headless deployment option\n- Support for various AI models\n- GUI and CLI interfaces\n- Cross-platform compatibility\n\n## Rebuild Objective\n\nTo build a web application that allows users to deploy and run local AI models privately on their computers, with a focus on ease of use and flexibility.\n\n## Next-stage focus\n\nFor stage 2, focus on breaking down the layout into its core regions, including the navigation bar, hero section, and feature sections. In stage 3, pay close attention to the design system, particularly the typography and color scheme. In stage 4, delve into the interactive behaviors, such as the model deployment process and the headless deployment option. Finally, in stage 5, ensure that the master prompt covers the platform's features, user experience, and technical requirements.\n\n---\n\n## Stage 5 — Master Prompt\n\n# Project Overview and Objectives\nThe objective of this project is to rebuild the LM Studio website from scratch, focusing on creating a responsive, interactive, and user-friendly interface that showcases the features and capabilities of LM Studio. The website should be built using a modern tech stack, with a emphasis on scalability, maintainability, and performance.\n\n# Tech Stack and Recommended Libraries\nThe recommended tech stack for this project includes:\n* Frontend: NextJS (React) with TypeScript\n* Backend: NodeJS with ExpressJS\n* Database: MongoDB\n* CSS Framework: Tailwind CSS\n* UI Library: React Bootstrap\n* Animation Library: Framer Motion\n* API Library: Axios\n\n# Step-by-Step Implementation Instructions\n## Home Page\n1. Create a new NextJS project using the `npx create-next-app` command.\n2. Install the required dependencies, including `tailwindcss`, `react-bootstrap`, `framer-motion`, and `axios`.\n3. Create a new component for the hero section, including a background image, title, and description.\n4. Create a new component for the features section, including a grid of cards with icons, titles, and descriptions.\n5. Create a new component for the call-to-action section, including a button and a link to the download page.\n\n## Models Page\n1. Create a new page for the models section, including a grid of cards with model names, descriptions, and links to the model pages.\n2. Create a new component for the model page, including a description, features, and a link to the download page.\n\n## Docs Page\n1. Create a new page for the docs section, including a grid of cards with doc titles, descriptions, and links to the doc pages.\n2. Create a new component for the doc page, including a description, code examples, and a link to the GitHub repository.\n\n## Download Page\n1. Create a new page for the download section, including a link to the download page and a description of the download process.\n\n## Login and Signup Pages\n1. Create a new page for the login section, including a form with email and password fields, and a link to the signup page.\n2. Create a new page for the signup section, including a form with email, password, and confirm password fields, and a link to the login page.\n\n# UI Specifications\n* Colors:\n\t+ Primary color: #3498db\n\t+ Secondary color: #2ecc71\n\t+ Background color: #f9f9f9\n* Spacing:\n\t+ Margin: 16px\n\t+ Padding: 16px\n* Typography:\n\t+ Font family: Open Sans\n\t+ Font size: 16px\n\t+ Line height: 24px\n\n# Interactive Features and Behaviors\n* Hover effects: add a hover effect to the buttons and links, including a change in background color and text color.\n* Scroll effects: add a scroll effect to the hero section, including a change in background color and text color.\n* Animation effects: add an animation effect to the features section, including a fade-in effect.\n\n# Responsive Design Requirements\n* The website should be responsive and work on all devices, including desktop, tablet, and mobile.\n* The website should have a minimum width of 320px and a maximum width of 1920px.\n\n# Edge Cases, Gotchas, and Common Mistakes\n* Make sure to handle errors and exceptions properly, including 404 errors and API errors.\n* Make sure to validate user input, including email and password fields.\n* Make sure to use secure protocols, including HTTPS and SSL.\n\n# Verification Checklist\n1. Verify that the website is responsive and works on all devices.\n2. Verify that the website has a minimum width of 320px and a maximum width of 1920px.\n3. Verify that the website handles errors and exceptions properly.\n4. Verify that the website validates user input properly.\n5. Verify that the website uses secure protocols properly.\n\n## Architect's Final Warning\nThe single most dangerous thing a junior could mess up when rebuilding this site is not properly handling errors and exceptions, including 404 errors and API errors. This could lead to a poor user experience, security vulnerabilities, and a loss of trust in the website. Make sure to handle errors and exceptions properly, including logging errors, displaying error messages, and providing a fallback experience.\n\n## CLASSIFICATION\nCATEGORY: FRONTEND | SUBCATEGORY: NextJS","country_iso":"IN","score":2,"likes_count":2,"dislikes_count":0,"mode":"mid","author_id":"cozycedar1518","category":null,"subcategory":null,"created_at":"2026-04-24 06:52:14","updated_at":"2026-10-22T07:29:56.945Z","extractions_count":0},{"id":"dc0b35b2-a338-41db-bc1b-dfce94a6c340","repo_url":"bend10/whatmodels","base_repo_url":"https://bend10/whatmodels","title":"whatmodels [ES] solarriver2887-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Project Summary\n\nThis project, whatmodels, is a static website that helps users find out which AI models their GPU can run and how well. It uses SvelteKit, Vite, and static JSON data to provide a user-friendly interface for GPU selection and model matching. The project aims to provide an accurate estimation of model performance based on user-provided GPU specifications.\n\n**Difficulty:** Intermediate\n\n## Tech Stack\n\n- Svelte\n- SvelteKit\n- Vite\n- Vite 6\n- Static JSON\n- JavaScript\n- HTML\n- CSS\n- Svelte 5\n- adapter-static\n- vite-plugin-svelte\n\n## Rebuild Objective\n\nTo build a static website that takes user-provided GPU specifications and model data as input, and outputs a list of matching models with estimated performance metrics. The project should utilize SvelteKit, Vite, and static JSON data to provide a user-friendly interface and accurate model matching.\n\n## Next-stage focus\n\nFor stage 2, focus on analyzing the project structure and identifying key components such as the GPU database, model database, and matching logic. For stage 3, emphasize the importance of environment variables and config files in setting up the project. For stage 4, highlight the fragile logic in the model matching algorithm and the need for careful testing. For stage 5, specify the master prompt as a detailed description of the project's architecture and key components.\n\n## Stage 2\n\n## Architecture Pattern\n\nThe repository appears to be a monolithic web application built using a Svelte frontend and a Python backend. The application is designed to manage and display information about GPUs and models, with features such as data extraction, model addition, and GPU specification updates.\n\n## Folder Breakdown\n\n### `src/`\nThis folder contains the application's frontend code, written in Svelte and JavaScript. It includes HTML templates, CSS styles, and JavaScript logic for rendering the application's UI and handling user interactions.\nKey files: app.html, app.css, GpuInput.svelte, ModelResults.svelte\n\n### `scripts/`\nThis folder contains Python scripts that interact with the application's data and perform tasks such as adding GPUs, extracting model IDs, and updating GPU specifications.\nKey files: add_gpu.py, extract_gpu_ids.py, gpu_script_utils.py\n\n### `.github/workflows/`\nThis folder contains GitHub Actions workflows that automate tasks such as deployment and testing.\nKey files: deploy.yml\n\n### `src/lib/`\nThis folder contains reusable JavaScript libraries and utilities used throughout the application.\nKey files: analytics.js, calculations.js\n\n### `src/routes/`\nThis folder contains Svelte components that define the application's routes and handle user navigation.\nKey files: +layout.js, +layout.svelte\n\n### `static/`\nThis folder contains static assets such as images, icons, and stylesheets.\nKey files: favicon.svg, logo.png\n\n### `src/data/`\nThis folder contains JSON files that store data about GPUs and models.\nKey files: gpus.json, models.json\n\n### `src/components/`\nThis folder contains Svelte components that render specific parts of the application's UI.\nKey files: GpuInput.svelte, ModelResults.svelte\n\n### `src/service-worker.js`\nThis file contains a service worker that handles caching and offline support for the application.\nKey files: service-worker.js\n\n### `src/lib/data/`\nThis folder contains data-related utilities and libraries used throughout the application.\nKey files: data.test.js\n\n## Core Modules\n\n- svelte\n- python\n- javascript\n- github-actions\n\n## Entry Points\n\n- `src/app.html`\n\n## Stage 3\n\n## Build Tool\n\n{\n  \"buildTool\": \"Vite\",\n  \"envSetup\": [\n    \"Step 1: Install Vite and SvelteKit by running `npm install` or `yarn install` in the project root.\",\n    \"Step 2: Ensure Node.js is installed on the system, as Vite requires it to function.\",\n    \"Step 3: Set up the project environment by creating a `.env` file in the project root to store environment variables.\"\n  ],\n  \"configNotes\": [\n    \"The `vite.config.js` file is the primary configuration file for Vite in this project.\",\n    \"The `sveltekit` plugin is imported from `@sveltejs/kit/vite` and used to enable SvelteKit functionality in Vite.\",\n    \"The `defineConfig` function from `vite` is used to define the Vite configuration object.\"\n  ],\n  \"keyConfigurations\": {\n    \"vite.config.js\": \"This file configures Vite to use SvelteKit, enabling the use of SvelteKit's features such as server-side rendering and routing.\",\n    \".env\": \"This file stores environment variables that can be accessed in the project using the `process.env` object.\"\n  },\n  \"seniorTip\": \"Be cautious when using environment variables in the `.env` file, as they can be committed to the repository and exposed publicly. Consider using a `.env.example` file instead and instructing users to create their own `.env` file with sensitive information.\"\n}\n\nAdditional analysis:\n\n- The `vite.config.js` file is a minimal configuration file that enables SvelteKit functionality in Vite. It does not contain any custom configuration settings, which suggests that the project is using the default SvelteKit configuration.\n- The `.env` file is not explicitly mentioned in the `vite.config.js` file, but it is likely used to store environment variables that can be accessed in the project using the `process.env` object.\n- The project does not appear to use any other configuration files or tools, which suggests that it is a relatively simple project with a minimal configuration.\n- The use of SvelteKit and Vite suggests that the project is focused on building a web application with a strong emphasis on performance and scalability.\n- The project does not appear to use any advanced features such as server-side rendering or routing, which suggests that it may be a relatively simple web application.\n\nCode example:\n\n```javascript\n// .env\nVITE_API_KEY=your_api_key_here\n```\n\n```javascript\n// src/lib/api.js\nimport { VITE_API_KEY } from '../.env';\n\nconst api = {\n  key: VITE_API_KEY,\n  // ...\n};\n\nexport default api;\n```\n\nThis code example demonstrates how to access environment variables stored in the `.env` file using the `process.env` object. The `VITE_API_KEY` variable is accessed in the `src/lib/api.js` file and used to configure the API object.\n\nFile references:\n\n- `vite.config.js`: The primary configuration file for Vite in this project.\n- `.env`: The file that stores environment variables that can be accessed in the project using the `process.env` object.\n- `src/lib/api.js`: A file that demonstrates how to access environment variables stored in the `.env` file using the `process.env` object.\n\nArchitectural reasoning:\n\n- The use of SvelteKit and Vite suggests that the project is focused on building a web application with a strong emphasis on performance and scalability.\n- The minimal configuration file `vite.config.js` suggests that the project is using the default SvelteKit configuration, which is suitable for a relatively simple web application.\n- The use of environment variables stored in the `.env` file suggests that the project is designed to be flexible and adaptable to different environments.\n\n## Environment Setup\n\n\n\n## Configuration Analysis\n\n\n\n## Key Configurations\n\n\n\n## Stage 4\n\n## Feature Breakdown\n\n\n\n## Data Flow\n\n**Analysis of the whatmodels Repository**\n\n**Core Features:**\n\n1.  **Model Compatibility Checker**: The repository provides a set of tools to determine which machine learning models can run on a given GPU. This is achieved through a combination of data-driven approaches and mathematical calculations.\n2.  **GPU Database**: The repository maintains a database of GPUs, including their specifications, such as VRAM, bandwidth, and manufacturer. This database is used to determine the compatibility of models with GPUs.\n3.  **Model Database**: The repository also maintains a database of machine learning models, including their specifications, such as parameters, quantization, and file size.\n4.  **Analytics and Tracking**: The repository includes tools for tracking user interactions, such as GPU selection and model usage, using PostHog analytics.\n5.  **Service Worker**: The repository includes a service worker that caches assets and provides offline support for the application.\n\n**Data Flow:**\n\nThe data flow in the whatmodels repository can be described as follows:\n\n1.  **User Input**: The user selects a GPU and a model, which triggers the compatibility checker to determine if the model can run on the selected GPU.\n2.  **GPU Database Query**: The compatibility checker queries the GPU database to retrieve the specifications of the selected GPU.\n3.  **Model Database Query**: The compatibility checker queries the model database to retrieve the specifications of the selected model.\n4.  **Calculation**: The compatibility checker performs mathematical calculations to determine if the model can run on the selected GPU based on its specifications.\n5.  **Result**: The compatibility checker returns the result of the calculation to the user, indicating whether the model can run on the selected GPU.\n\n**API Endpoints:**\n\nThe whatmodels repository does not expose any API endpoints. However, it does provide a service worker that caches assets and provides offline support for the application.\n\n**State Management:**\n\nThe whatmodels repository uses a combination of state management techniques, including:\n\n1.  **Context API**: The repository uses the Context API to manage state across components.\n2.  **Redux**: The repository uses Redux to manage state in a predictable and scalable way.\n3.  **PostHog Analytics**: The repository uses PostHog analytics to track user interactions and manage state in the analytics pipeline.\n\n**Senior Tip:**\n\nThe most complex and fragile part of this codebase is the compatibility checker, which performs mathematical calculations to determine if a model can run on a given GPU. This component is critical to the functionality of the application and requires careful testing and validation to ensure its accuracy.\n\n**Code Examples:**\n\nHere are some code examples from the whatmodels repository:\n\n```javascript\n// src/lib/calculations.js\nexport function calcMultiGpuResources(vram, bandwidth, quantity) {\n  if (quantity === 1 || quantity == null) {\n    return { vram, bandwidth };\n  }\n\n  // VRAM pools linearly\n  const totalVram = vram * quantity;\n  // Bandwidth has communication overhead, so we don't pool it\n  const bandwidthPerGpu = bandwidth;\n  return { vram: totalVram, bandwidth: bandwidthPerGpu };\n}\n```\n\n```javascript\n// src/lib/analytics.js\nexport function trackGpuSelected(gpuName, vramGb, bandwidthGbps) {\n  capture('gpu_selected', {\n    gpu_name: gpuName,\n    vram_gb: vramGb,\n    bandwidth_gbps: bandwidthGbps,\n  });\n}\n```\n\n```javascript\n// src/service-worker.js\nself.addEventListener('install', (event) => {\n  event.waitUntil(\n    caches\n      .open(CACHE_NAME)\n      .then((cache) => cache.addAll(ASSETS))\n      .then(() => self.skipWaiting())\n  );\n});\n```\n\n**File References:**\n\nThe following files are relevant to the analysis:\n\n*   `src/lib/calculations.js`: Contains mathematical calculations for determining model compatibility with GPUs.\n*   `src/lib/analytics.js`: Contains tools for tracking user interactions using PostHog analytics.\n*   `src/service-worker.js`: Contains the service worker that caches assets and provides offline support for the application.\n*   `src/lib/data/gpus.json`: Contains the GPU database.\n*   `src/lib/data/models.json`: Contains the model database.\n\n**Architectural Reasoning:**\n\nThe whatmodels repository is designed to provide a set of tools for determining which machine learning models can run on a given GPU. The repository uses a combination of data-driven approaches and mathematical calculations to achieve this goal. The compatibility checker is a critical component of the repository, and its accuracy is essential to the functionality of the application. The repository also includes tools for tracking user interactions and managing state in a predictable and scalable way.\n\n## API Endpoints\n\nNo API endpoints identified\n\n## State Management\n\nUnknown\n\n---\n\n## Stage 5 — Master Prompt\n\n# Project Overview and Objectives\nRebuild the `whatmodels` repository from scratch, which is a static website that helps users determine which AI models their GPU can run and how well. The website allows users to select a GPU or enter VRAM manually, set a minimum context window, and instantly see which models fit, how much context they can afford, and estimated generation speed.\n\n## Tech Stack and Recommended Libraries\n- **Frontend Framework:** SvelteKit (Svelte 5) with `adapter-static`\n- **Bundler and Dev Server:** Vite 6\n- **Data Storage:** Static JSON files for GPU and model data\n- **Testing Framework:** Vitest\n- **Analytics:** PostHog\n\n## Folder Structure and Architectural Blueprint\n```markdown\nwhatmodels/\n├── .cursor/\n│   └── rules/\n│       ├── calculations-and-testing.mdc\n│       ├── data-files.mdc\n│       ├── deploy.mdc\n│       ├── project-overview.mdc\n│       └── svelte-components.mdc\n├── .github/\n│   └── workflows/\n│       └── deploy.yml\n├── .gitignore\n├── LICENSE.md\n├── README.md\n├── package-lock.json\n├── package.json\n├── scripts/\n│   ├── README.md\n│   ├── __pycache__/\n│   │   └── ...\n│   ├── add_gpu.py\n│   ├── add_model.py\n│   ├── extract_gpu_ids.py\n│   ├── extract_model_ids.py\n│   ├── gpu_script_utils.py\n│   ├── list_recent_gpus.py\n│   ├── list_recent_models.py\n│   ├── update_gpu_specs.py\n│   └── update_model_stats.py\n├── src/\n│   ├── app.css\n│   ├── app.html\n│   ├── lib/\n│   │   ├── analytics.js\n│   │   ├── calculations.js\n│   │   ├── calculations.test.js\n│   │   └── data/\n│   │       ├── gpus.json\n│   │       └── models.json\n│   ├── routes/\n│   │   ├── +layout.js\n│   │   ├── +layout.svelte\n│   │   └── +page.svelte\n│   └── service-worker.js\n├── static/\n│   ├── .nojekyll\n│   ├── favicon.svg\n│   └── logo.png\n├── svelte.config.js\n└── vite.config.js\n```\n\n## Implementation Steps for Core Features and Logic\n1. **GPU and Model Data Management:**\n   - Create `gpus.json` and `models.json` in `src/lib/data/`.\n   - Implement scripts to update these files (`update_gpu_specs.py`, `update_model_stats.py`).\n\n2. **GPU Input and Model Results Components:**\n   - Develop `GpuInput.svelte` for user input.\n   - Develop `ModelResults.svelte` for displaying compatible models.\n\n3. **Calculations:**\n   - Implement calculation functions in `src/lib/calculations.js` for:\n     - VRAM budget\n     - KV cache calculation\n     - Maximum context window\n\n4. **SvelteKit Configuration:**\n   - Configure `svelte.config.js` for static site generation.\n\n5. **Vite Configuration:**\n   - Configure `vite.config.js` for development and building.\n\n## Configuration Requirements\n- **Environment Variables:** None\n- **Build Scripts:** `npm run build`\n- **Development Server:** `npm run dev`\n\n## Testing, Error Handling, and Deployment\n- **Testing Framework:** Use Vitest for unit tests.\n- **Error Handling:** Implement try-catch blocks for critical calculations and API calls.\n- **Deployment:** Configure GitHub Actions for automated deployment.\n\n## Edge Cases, Performance Concerns, and \"Gotchas\"\n- **Data Validation:** Ensure input data is validated for GPU and model specifications.\n- **Performance Optimization:** Optimize calculation functions for performance.\n\n## Verification Checklist\n1. Ensure all dependencies are installed.\n2. Verify GPU and model data are correctly imported and used.\n3. Test all components for correct functionality.\n4. Validate calculation functions.\n5. Deploy and test the live site.\n\n## Architect's Final Warning\nThe single most dangerous thing a junior could mess up in this repo is not properly handling the data validation for GPU and model specifications, leading to incorrect calculations and potentially misleading results for users.\n\n## CLASSIFICATION\nCATEGORY: FRONTEND | SUBCATEGORY: Svelte","country_iso":"ES","score":0,"likes_count":0,"dislikes_count":0,"mode":"full","author_id":"solarriver2887","category":null,"subcategory":null,"created_at":"2026-04-22 22:12:30","updated_at":null,"extractions_count":0},{"id":"c18b3605-2c53-4eec-bb8f-b0d1c2440495","repo_url":"https://kanso-dark.framer.media/","base_repo_url":"https://kanso-dark.framer.media","title":"kanso-dark.framer.media [FR] mellowmaple572-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Website Summary\n\nKanso is a design agency that offers premium Framer templates for creative studios and design agencies, focusing on clarity, precision, and timeless aesthetics. They provide a range of services including brand identity, digital design, art direction, and strategy. Their website showcases their portfolio, services, and process, with a focus on simplicity and purposeful design.\n\n**Target Users:** Design agencies, creative studios, startups, and established brands\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- Framer\n- JavaScript\n- HTML\n- CSS\n- React\n- Tailwind CSS\n- TypeScript\n- Storybook\n- Webpack\n- Babel\n- ESLint\n- Prettier\n- Git\n- GitHub\n- Figma\n- Adobe Creative Cloud\n\n## Key Features Identified\n\n- Responsive design\n- Customizable templates\n- Framer integration\n- Design system\n- Brand identity services\n- Digital design services\n- Art direction services\n- Strategy services\n- Portfolio showcase\n- Blog with articles on design and simplicity\n\n## Rebuild Objective\n\nRecreate the Kanso website using Framer, with a focus on simplicity, precision, and timeless aesthetics. The project should include a responsive design, customizable templates, and integration with Framer. The design system should be well-structured and easy to maintain. The website should showcase the agency's portfolio, services, and process, with a focus on clarity and purposeful design.\n\n## Next-stage focus\n\nFor stage 2, focus on recreating the layout regions, including the hero section, services section, and portfolio section. For stage 3, emphasize the design system, including the color palette, typography, and spacing. For stage 4, focus on the interactions and animations, including the scrolling effects and hover states. For stage 5, ensure that the master prompt includes all the necessary details for a developer to recreate the site, including the Framer code, CSS styles, and JavaScript functionality.\n\n## Stage 1\n\n## Website Summary\n\nKanso is a design agency that offers premium Framer templates for creative studios and design agencies, focusing on clarity, precision, and timeless aesthetics. They provide a range of services including brand identity, digital design, art direction, and strategy. Their website showcases their portfolio, services, and process, with a focus on simplicity and purposeful design.\n\n**Target Users:** Design agencies, creative studios, startups, and established brands\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- Framer\n- JavaScript\n- HTML\n- CSS\n- React\n- Tailwind CSS\n- TypeScript\n- Storybook\n- Webpack\n- Babel\n- ESLint\n- Prettier\n- Git\n- GitHub\n- Figma\n- Adobe Creative Cloud\n\n## Key Features Identified\n\n- Responsive design\n- Customizable templates\n- Framer integration\n- Design system\n- Brand identity services\n- Digital design services\n- Art direction services\n- Strategy services\n- Portfolio showcase\n- Blog with articles on design and simplicity\n\n## Rebuild Objective\n\nRecreate the Kanso website using Framer, with a focus on simplicity, precision, and timeless aesthetics. The project should include a responsive design, customizable templates, and integration with Framer. The design system should be well-structured and easy to maintain. The website should showcase the agency's portfolio, services, and process, with a focus on clarity and purposeful design.\n\n## Next-stage focus\n\nFor stage 2, focus on recreating the layout regions, including the hero section, services section, and portfolio section. For stage 3, emphasize the design system, including the color palette, typography, and spacing. For stage 4, focus on the interactions and animations, including the scrolling effects and hover states. For stage 5, ensure that the master prompt includes all the necessary details for a developer to recreate the site, including the Framer code, CSS styles, and JavaScript functionality.\n\n## Stage 1\n\n## Website Summary\n\nKanso is a design agency that offers premium Framer templates for creative studios and design agencies, focusing on clarity, precision, and timeless aesthetics. They provide a range of services including brand identity, digital design, art direction, and strategy. Their website showcases their portfolio, services, and process, with a focus on simplicity and purposeful design.\n\n**Target Users:** Design agencies, creative studios, startups, and established brands\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- Framer\n- JavaScript\n- HTML\n- CSS\n- React\n- Tailwind CSS\n- TypeScript\n- Storybook\n- Webpack\n- Babel\n- ESLint\n- Prettier\n- Git\n- GitHub\n- Figma\n- Adobe Creative Cloud\n\n## Key Features Identified\n\n- Responsive design\n- Customizable templates\n- Framer integration\n- Design system\n- Brand identity services\n- Digital design services\n- Art direction services\n- Strategy services\n- Portfolio showcase\n- Blog with articles on design and simplicity\n\n## Rebuild Objective\n\nRecreate the Kanso website using Framer, with a focus on simplicity, precision, and timeless aesthetics. The project should include a responsive design, customizable templates, and integration with Framer. The design system should be well-structured and easy to maintain. The website should showcase the agency's portfolio, services, and process, with a focus on clarity and purposeful design.\n\n## Next-stage focus\n\nFor stage 2, focus on recreating the layout regions, including the hero section, services section, and portfolio section. For stage 3, emphasize the design system, including the color palette, typography, and spacing. For stage 4, focus on the interactions and animations, including the scrolling effects and hover states. For stage 5, ensure that the master prompt includes all the necessary details for a developer to recreate the site, including the Framer code, CSS styles, and JavaScript functionality.\n\n## Stage 1\n\n## Website Summary\n\nKanso is a design agency that offers premium Framer templates for creative studios and design agencies, focusing on clarity, precision, and timeless aesthetics. They provide a range of services including brand identity, digital design, art direction, and strategy. Their website showcases their portfolio, services, and process, with a focus on simplicity and purposeful design.\n\n**Target Users:** Design agencies, creative studios, startups, and established brands\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- Framer\n- JavaScript\n- HTML\n- CSS\n- React\n- Tailwind CSS\n- TypeScript\n- Storybook\n- Webpack\n- Babel\n- ESLint\n- Prettier\n- Git\n- GitHub\n- Figma\n- Adobe Creative Cloud\n\n## Key Features Identified\n\n- Responsive design\n- Customizable templates\n- Framer integration\n- Design system\n- Brand identity services\n- Digital design services\n- Art direction services\n- Strategy services\n- Portfolio showcase\n- Blog with articles on design and simplicity\n\n## Rebuild Objective\n\nRecreate the Kanso website using Framer, with a focus on simplicity, precision, and timeless aesthetics. The project should include a responsive design, customizable templates, and integration with Framer. The design system should be well-structured and easy to maintain. The website should showcase the agency's portfolio, services, and process, with a focus on clarity and purposeful design.\n\n## Next-stage focus\n\nFor stage 2, focus on recreating the layout regions, including the hero section, services section, and portfolio section. For stage 3, emphasize the design system, including the color palette, typography, and spacing. For stage 4, focus on the interactions and animations, including the scrolling effects and hover states. For stage 5, ensure that the master prompt includes all the necessary details for a developer to recreate the site, including the Framer code, CSS styles, and JavaScript functionality.\n\n---\n\n## Stage 5 — Master Prompt\n\n# Project Overview and Objectives\nThe objective of this project is to rebuild the Kanso design agency website from scratch, replicating its exact functionality, design, and user experience. The website is a premium Framer template designed for design agencies and creative studios that value clarity, precision, and timeless aesthetics.\n\n## Tech Stack and Recommended Libraries\nThe recommended tech stack for this project includes:\n* Frontend: NextJS (React) for building the website's UI components and handling client-side logic\n* Styling: CSS-in-JS solution like Styled Components or Emotion for styling and layout management\n* Typography: Google Fonts (specifically, the \"Inter\" and \"Geist\" font families) for consistent typography throughout the website\n* Responsive Design: Utilize CSS media queries and a mobile-first approach to ensure a seamless user experience across various devices and screen sizes\n* Interactive Features: JavaScript and React libraries like React-Spring or Framer Motion for animations and interactive behaviors\n* State Management: React Context API or a library like Redux for managing global state and props\n\n## Step-by-Step Implementation Instructions\n### Home Page\n1. Create a new NextJS project using `npx create-next-app my-kanso-website`\n2. Set up the project structure, including components, pages, and styles\n3. Design the home page layout, including the header, hero section, about section, projects section, and footer\n4. Implement the hero section with a background image, title, and call-to-action (CTA) button\n5. Create a reusable `ProjectCard` component for displaying project information\n\n### About Page\n1. Create a new page for the about section\n2. Design the about page layout, including the introduction, team section, and contact information\n3. Implement the team section with a grid layout and reusable `TeamMember` component\n4. Add a contact form with validation and submission handling\n\n### Projects Page\n1. Create a new page for the projects section\n2. Design the projects page layout, including the project grid and filtering options\n3. Implement the project grid with a reusable `ProjectGrid` component\n4. Add filtering options with JavaScript and CSS\n\n### Services Page\n1. Create a new page for the services section\n2. Design the services page layout, including the introduction, service cards, and call-to-action (CTA) button\n3. Implement the service cards with a reusable `ServiceCard` component\n4. Add a CTA button with a link to the contact page\n\n## UI Specifications\n* Colors:\n\t+ Primary color: `#333` (dark gray)\n\t+ Secondary color: `#666` (light gray)\n\t+ Accent color: `#0099ff` (blue)\n* Spacing:\n\t+ Margin: 16px (default)\n\t+ Padding: 24px (default)\n* Typography:\n\t+ Font family: \"Inter\" (primary) and \"Geist\" (secondary)\n\t+ Font sizes:\n\t\t- Heading 1: 48px\n\t\t- Heading 2: 36px\n\t\t- Body text: 18px\n\t+ Line height: 1.5 (default)\n\n## Interactive Features and Behaviors\n* Animations:\n\t+ Hero section background image fade-in\n\t+ Project card hover effects\n\t+ Service card hover effects\n* Scroll-to-top button with smooth scrolling\n* Mobile menu with toggle button and slide-in animation\n\n## Responsive Design Requirements\n* Mobile-first approach\n* CSS media queries for different screen sizes:\n\t+ Small: `max-width: 768px`\n\t+ Medium: `max-width: 1024px`\n\t+ Large: `max-width: 1280px`\n* Ensure consistent layout and spacing across different devices and screen sizes\n\n## Edge Cases, Gotchas, and Common Mistakes\n* Ensure proper handling of images and assets for different screen sizes and devices\n* Use CSS media queries to handle different screen sizes and devices\n* Test for common browser inconsistencies and edge cases\n\n## Verification Checklist\n* Verify that the website is built with the recommended tech stack and libraries\n* Ensure that the website's design and layout match the original Kanso website\n* Test all interactive features and behaviors\n* Verify that the website is responsive and works well across different devices and screen sizes\n* Test for common browser inconsistencies and edge cases\n\n## Architect's Final Warning\nWhen rebuilding this website, the single most dangerous thing a junior could mess up is not properly handling the responsive design and layout for different screen sizes and devices. This could result in a broken or inconsistent user experience, which could negatively impact the website's overall usability and credibility. To avoid this, it's essential to thoroughly test the website on different devices and screen sizes, using tools like CSS media queries and mobile simulators to ensure a seamless and consistent user experience.\n\n## CLASSIFICATION\nCATEGORY: FRONTEND | SUBCATEGORY: NextJS","country_iso":"FR","score":0,"likes_count":0,"dislikes_count":0,"mode":"full","author_id":"mellowmaple572","category":null,"subcategory":null,"created_at":"2026-04-22 07:18:35","updated_at":null,"extractions_count":0},{"id":"d343cfde-e31d-424c-8e69-8ff19c38b625","repo_url":"xyz-rainbow/xyz-dashboard","base_repo_url":"https://xyz-rainbow/xyz-dashboard","title":"xyz-dashboard [ES] cosmicotter661-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Project Summary\n\nThe XYZ Dashboard is a floating macro-pad launcher built with Tauri, React, and TypeScript, designed to centralize frequent tasks such as shell commands, scripts, URLs, and custom iconized shortcuts. It features a configurable button grid, global shortcut, command history, and theme presets. The project aims to provide a compact, always-on-top launcher workflow for users. The tech stack includes Tauri for desktop app development, React for the UI, and TypeScript for strict type checking.\n\n**Difficulty:** Intermediate\n\n## Tech Stack\n\n- Tauri\n- React\n- TypeScript\n- pnpm\n- Rust\n- Howler\n- i18next\n- Framer Motion\n- Zustand\n\n## Rebuild Objective\n\nTo recreate the XYZ Dashboard project, a developer must build a desktop application using Tauri, with a React-based UI and TypeScript for type checking. The application should feature a configurable button grid, global shortcut, command history, and theme presets. The developer must also implement the necessary dependencies, including Howler for sound effects, i18next for internationalization, and Framer Motion for animations. Additionally, the project requires a Rust backend, which will be used to handle system-level tasks, such as executing shell commands and scripts. The developer must also set up a build and release process using GitHub Actions, which will automate the creation of installers for various platforms, including Linux, macOS, and Windows.\n\n## Next-stage focus\n\nIn the next stages, the focus should be on the architecture and configuration of the project. Stage 2 should emphasize the setup of the Tauri and React environments, including the installation of necessary dependencies and the configuration of the build process. Stage 3 should focus on the implementation of the core logic, including the button grid, global shortcut, and command history. Stage 4 should concentrate on the implementation of the theme presets and the internationalization of the application. Stage 5 should focus on the creation of the master prompt, which should specify the exact requirements for the project, including the tech stack, dependencies, and features. The master prompt should also provide guidance on the setup of the development environment, the implementation of the core logic, and the creation of the build and release process.\n\n## Stage 2\n\n## Architecture Pattern\n\nThe overall architectural pattern of this project is a hybrid desktop application, utilizing both web technologies (for the frontend) and native desktop capabilities (via Tauri). This approach allows for a unified codebase across multiple platforms, including Windows, macOS, and Linux, while leveraging the strengths of both web and native development.\n\n## Folder Breakdown\n\n### `src/`\nThis folder contains the frontend code of the application, written in TypeScript and utilizing React for building the user interface. It includes components, hooks, utilities, and the main application entry point.\nKey files: App.tsx, main.tsx, store.ts\n\n### `src-tauri/`\nThis folder holds the Rust code for the Tauri desktop application, including the build configuration, native capabilities, and the Rust entry point.\nKey files: Cargo.toml, build.rs, lib.rs\n\n### `assets/`\nContains static assets used by the application, including images, icons, and other media.\nKey files: app-preview-3x3-last-empty.svg, banner-main.svg, error.svg\n\n### `assets/icon-packs/`\nHolds a collection of icon packs, each containing a set of icons for different themes or purposes.\nKey files: index.json, packs/apps-brands/icons/browser.svg\n\n### `public/`\nServes as the public directory for the application, containing files that can be directly accessed by the user or the application itself.\nKey files: app-icon.png, splash-logo.svg\n\n### `packaging/`\nIncludes files necessary for packaging the application for distribution, such as metadata for different package managers.\nKey files: com.cloud-xyz.xyz-dashboard.metainfo.xml, store-listing.md\n\n### `src/components/`\nContains reusable React components used throughout the application, such as buttons, grids, and overlays.\nKey files: ErrorOverlay.tsx, GridButton.tsx, SettingsIcon.tsx\n\n### `src/hooks/`\nHolds custom React hooks that provide functionality for managing state, handling events, and interacting with the application's logic.\nKey files: useDragSnap.ts, useInactivityTimer.ts, useResolvedPackIcon.ts\n\n### `src/utils/`\nContains utility functions that can be used across the application, such as file handling and image processing.\nKey files: fileImageSrc.ts\n\n### `.github/workflows/`\nIncludes GitHub Actions workflow definitions for automating tasks like continuous integration and deployment.\nKey files: ci.yml, release.yml\n\n## Core Modules\n\n- React\n- Tauri\n- Rust\n\n## Entry Points\n\n- `src/main.tsx`\n- `src-tauri/lib.rs`\n\n## Stage 3\n\n## Build Tool\n\n```json\n{\n  \"buildTool\": \"Vite\",\n  \"envSetup\": [\n    \"Install Node.js and npm on your system\",\n    \"Run `npm install` to install all dependencies specified in package.json\",\n    \"Set up the environment variables, specifically TAURI_DEV_HOST, if necessary\",\n    \"Verify that TypeScript is installed and configured properly, as indicated by the tsconfig.json file\"\n  ],\n  \"configNotes\": [\n    \"The tsconfig.json file specifies the compiler options for TypeScript, including the target version (ES2020), module system (ESNext), and bundler mode\",\n    \"The vite.config.ts file defines the configuration for Vite, including plugins (React, Tailwind CSS), build options, and server settings\"\n  ],\n  \"keyConfigurations\": {\n    \"tsconfig.json\": \"Configures the TypeScript compiler, including the target version, module system, and bundler mode. This file is crucial for ensuring that the code is compiled correctly and efficiently.\",\n    \"vite.config.ts\": \"Defines the configuration for Vite, including plugins, build options, and server settings. This file is essential for setting up the development environment and building the application.\"\n  },\n  \"seniorTip\": \"Be cautious when using the `isolatedModules` option in tsconfig.json, as it can lead to issues with module resolution and bundling. Make sure to thoroughly test your application after enabling this option. Additionally, when using Vite with React, ensure that you are using the correct version of React and the `@vitejs/plugin-react` plugin to avoid compatibility issues.\"\n}\n```\n\nAdditional analysis:\n\nThe `tsconfig.json` file specifies the compiler options for TypeScript, including the target version (ES2020), module system (ESNext), and bundler mode. The `moduleResolution` option is set to `bundler`, which allows Vite to handle module resolution. The `allowImportingTsExtensions` option is set to `true`, which enables importing TypeScript files with the `.ts` extension.\n\nThe `vite.config.ts` file defines the configuration for Vite, including plugins (React, Tailwind CSS), build options, and server settings. The `plugins` option specifies the plugins to use, including `react()` and `tailwindcss()`. The `build` option specifies the build configuration, including the output format and chunking strategy. The `server` option specifies the server settings, including the port, host, and hot module replacement (HMR) configuration.\n\nThe `vite.config.ts` file also includes a reference to `tsconfig.node.json`, which suggests that there is a separate TypeScript configuration file for Node.js. This file is not included in the provided code snippet, but it is likely used to configure the TypeScript compiler for Node.js-specific code.\n\nThe use of `process.env.TAURI_DEV_HOST` in `vite.config.ts` suggests that the application is using Tauri, a framework for building desktop applications with web technologies. The `TAURI_DEV_HOST` environment variable is likely used to configure the development environment for Tauri.\n\nOverall, the configuration files suggest that the application is a React-based desktop application built with Vite and Tauri. The use of TypeScript and the `isolatedModules` option suggests that the application is designed to be modular and efficient.\n\nExample code snippets:\n\n* `tsconfig.json`:\n```json\n{\n  \"compilerOptions\": {\n    \"target\": \"ES2020\",\n    \"useDefineForClassFields\": true,\n    \"lib\": [\"ES2020\", \"DOM\", \"DOM.Iterable\"],\n    \"module\": \"ESNext\",\n    \"skipLibCheck\": true,\n    \"moduleResolution\": \"bundler\",\n    \"allowImportingTsExtensions\": true,\n    \"resolveJsonModule\": true,\n    \"isolatedModules\": true,\n    \"noEmit\": true,\n    \"jsx\": \"react-jsx\"\n  }\n}\n```\n\n* `vite.config.ts`:\n```typescript\nimport { defineConfig } from \"vite\";\nimport react from \"@vitejs/plugin-react\";\nimport tailwindcss from \"@tailwindcss/vite\";\n\nexport default defineConfig(async () => ({\n  plugins: [react(), tailwindcss()],\n  test: {\n    environment: \"node\",\n    include: [\"src/**/*.test.ts\"],\n  },\n  build: {\n    rollupOptions: {\n      output: {\n        manualChunks: {\n          react: [\"react\", \"react-dom\"],\n          motion: [\"framer-motion\"],\n          tauri: [\"@tauri-apps/api\", \"@tauri-apps/plugin-dialog\"],\n          icons: [\"lucide-react\"],\n        },\n      },\n    },\n  },\n  clearScreen: false,\n  server: {\n    port: 1420,\n    strictPort: true,\n    host: process.env.TAURI_DEV_HOST || false,\n    hmr: process.env.TAURI_DEV_HOST\n      ? {\n          protocol: \"ws\",\n          host: process.env.TAURI_DEV_HOST,\n          port: 1421,\n        }\n      : undefined,\n    watch: {\n      ignored: [\"**/src-tauri/**\"],\n    },\n  },\n}));\n```\n\nFile references:\n\n* `tsconfig.json`\n* `vite.config.ts`\n* `package.json` (not included in the provided code snippet)\n* `tsconfig.node.json` (not included in the provided code snippet)\n\nArchitectural reasoning:\n\nThe application is designed to be modular and efficient, with a focus on desktop development using Tauri. The use of Vite and React suggests a modern and flexible architecture, with a focus on performance and scalability. The `isolatedModules` option in `tsconfig.json` suggests that the application is designed to be highly modular, with each module being compiled and bundled separately. The use of `process.env.TAURI_DEV_HOST` in `vite.config.ts` suggests that the application is designed to be highly configurable, with environment variables being used to customize the development environment.\n\n## Environment Setup\n\n\n\n## Configuration Analysis\n\n\n\n## Key Configurations\n\n\n\n## Stage 4\n\n## Feature Breakdown\n\n### Macro Grid (high)\nA customizable grid of buttons that can be used to launch applications, execute commands, or perform other actions\nFiles: `src/components/MacroGrid.tsx`, `src/components/GridButton.tsx`\n\n### Settings Panel (medium)\nA panel that allows users to customize the application's settings, including the grid layout, icon packs, and more\nFiles: `src/components/SettingsPanel.tsx`, `src/iconLibrary.ts`\n\n### Icon Library (medium)\nA library of icons that can be used in the macro grid, with support for custom icon packs and filtering\nFiles: `src/iconLibrary.ts`, `src/components/SettingsPanel.tsx`\n\n### Drag and Drop (high)\nThe ability to drag and drop icons and other elements within the application\nFiles: `src/hooks/useDragSnap.ts`, `src/components/SettingsIcon.tsx`\n\n### Inactivity Timer (medium)\nA feature that hides the application window after a period of inactivity\nFiles: `src/hooks/useInactivityTimer.ts`, `src/store.ts`\n\n### Audio Synthesis (high)\nThe ability to synthesize audio effects, such as sound effects and music\nFiles: `src/audio/sfx.ts`, `src/components/ErrorOverlay.tsx`\n\n### Error Handling (medium)\nA system for handling and displaying errors within the application\nFiles: `src/components/ErrorOverlay.tsx`, `src/store.ts`\n\n### Window Management (medium)\nThe ability to manage the application window, including hiding and showing it\nFiles: `src/hooks/useInactivityTimer.ts`, `src/store.ts`\n\n### Tauri Integration (high)\nIntegration with the Tauri framework for building cross-platform desktop applications\nFiles: `vite.config.ts`, `src/store.ts`\n\n### Internationalization (medium)\nSupport for multiple languages and locales within the application\nFiles: `src/components/SettingsPanel.tsx`, `src/iconLibrary.ts`\n\n## Data Flow\n\nThe application's data flows through a combination of React state, Redux-like stores, and Tauri API calls. The main store is defined in src/store.ts and is used to manage the application's state, including the grid layout, icon packs, and more. The store is updated through a combination of user interactions, API calls, and internal events. The data is then propagated to the various components through React props and context.\n\n## API Endpoints\n\n- `GET /api/icon-packs`\n- `POST /api/icon-packs`\n- `GET /api/settings`\n- `POST /api/settings`\n\n## State Management\n\nThe application uses a combination of React state and a Redux-like store to manage its state. The store is defined in src/store.ts and is used to manage the application's state, including the grid layout, icon packs, and more. The store is updated through a combination of user interactions, API calls, and internal events.\n\n---\n\n## Stage 5 — Master Prompt\n\n# XYZ Dashboard Rebuild Prompt\n## Project Overview and Objectives\nRebuild the XYZ Dashboard repository from scratch using Tauri, React, and TypeScript. The application is a floating macro-pad launcher that centralizes frequent tasks such as shell commands, scripts, executables, URLs, and custom iconized shortcuts.\n\n## Tech Stack and Recommended Libraries\n- **Frontend:** React (v19.1.0), TypeScript (v5.8.3), Vite (v7.0.4)\n- **Backend:** Tauri (v2), Rust (for Tauri backend)\n- **Package Manager:** pnpm (v9.0)\n- **Styling:** Tailwind CSS (v4.2.2), Lucide React (v1.7.0)\n- **Audio:** Howler (v2.2.4)\n- **State Management:** Zustand (v5.0.12)\n- **Testing:** Vitest (v3.2.4)\n\n## Folder Structure and Architectural Blueprint\n```markdown\nxyz-dashboard/\n├── .github/\n│   └── workflows/\n│       ├── ci.yml\n│       └── release.yml\n├── .vscode/\n│   └── extensions.json\n├── assets/\n│   ├── banner-main.svg\n│   ├── app-preview.svg\n│   └── brand/\n│       └── app-icon.svg\n├── packaging/\n│   └── com.cloud-xyz.xyz-dashboard.metainfo.xml\n├── public/\n│   ├── app-icon.png\n│   └── rainbow-splash-logo.png\n├── releases/\n│   └── .gitkeep\n├── src-tauri/\n│   ├── Cargo.toml\n│   └── src/\n│       └── main.rs\n├── src/\n│   ├── App.tsx\n│   ├── components/\n│   │   ├── GridButton.tsx\n│   │   └── SettingsPanel.tsx\n│   ├── hooks/\n│   │   └── useDragSnap.ts\n│   ├── utils/\n│   │   └── fileImageSrc.ts\n│   └── index.css\n├── tsconfig.json\n└── vite.config.ts\n```\n\n## Implementation Steps for Core Features and Logic\n1. **Tauri Setup:** Configure Tauri for desktop application, including setup for React and TypeScript.\n2. **React Components:** Implement core components such as `GridButton`, `SettingsPanel`, and `MacroGrid`.\n3. **Icon Picker and Catalog:** Develop icon picker functionality with catalog integration.\n4. **Command and URL Handling:** Implement command and URL execution using Tauri's plugin-shell.\n5. **Global Shortcut:** Set up global shortcut for showing/hiding the dashboard.\n6. **Sound Effects:** Integrate Howler for sound effects.\n\n## Configuration Requirements\n- **Environment Variables:** Define `TAURI_DEV_HOST` for development.\n- **Build Scripts:** Configure `vite build` and `tauri` commands.\n\n## Testing, Error Handling, and Deployment\n- **Testing Framework:** Use Vitest for unit testing.\n- **Error Handling:** Implement error handling for components and Tauri commands.\n- **Deployment:** Configure CI/CD for automated builds and releases.\n\n## Edge Cases, Performance Concerns, and \"Gotchas\"\n- **Icon Pack Loading:** Handle large icon packs efficiently.\n- **Command Execution:** Validate and sanitize commands to prevent security issues.\n- **Performance:** Optimize rendering and updates for smooth UI.\n\n## Verification Checklist\n1. Verify Tauri and React setup.\n2. Test core features (icon picker, command execution, global shortcut).\n3. Ensure cross-platform compatibility.\n4. Validate performance and responsiveness.\n\n## Architect's Final Warning\nThe single most dangerous thing a junior could mess up in this repo is not properly handling command execution, which could lead to security vulnerabilities. Always validate and sanitize commands.\n\n## CLASSIFICATION\nCATEGORY: MOBILE | SUBCATEGORY: Tauri","country_iso":"ES","score":0,"likes_count":0,"dislikes_count":0,"mode":"full","author_id":"cosmicotter661","category":null,"subcategory":null,"created_at":"2026-04-22 05:19:04","updated_at":null,"extractions_count":0},{"id":"a611fa33-cdf7-4599-b761-76580dc15de2","repo_url":"https://pubmed.ncbi.nlm.nih.gov/35416105/","base_repo_url":"https://pubmed.ncbi.nlm.nih.gov/35416105","title":"35416105 [US] bravecoral7073-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Website Summary\n\nThis site is a PubMed abstract viewer, allowing users to access and analyze scientific research articles, particularly those related to the long-term safety of ketamine and esketamine in treating depression. The site provides features for searching, saving, and sharing articles, as well as tools for citation management and data export. It is primarily designed for researchers, scientists, and medical professionals seeking to stay up-to-date on the latest research in their field.\n\n**Target Users:** Researchers, scientists, medical professionals, and anyone interested in accessing and analyzing scientific research articles\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- HTML5\n- CSS3\n- React\n- Redux\n- Express.js\n- Node.js\n- PostgreSQL\n- Material-UI\n- Bootstrap\n- Tailwind CSS\n- WebSockets\n- OAuth 2.0\n- OpenID Connect\n- JSON Web Tokens\n- AWS Lambda\n- AWS API Gateway\n- AWS S3\n- AWS CloudFront\n\n## Key Features Identified\n\n- Search and filtering of PubMed articles\n- Saving and sharing articles\n- Citation management and data export\n- User authentication and authorization\n- Real-time updates and notifications\n- Customizable layout and design\n- Integration with external services and APIs\n\n## Rebuild Objective\n\nTo build a robust and scalable PubMed abstract viewer that allows users to easily search, save, and share scientific research articles, while also providing tools for citation management and data export. The site should be designed with a modern and responsive layout, and should integrate with external services and APIs to provide a seamless user experience.\n\n## Next-stage focus\n\nFor stage 2, the focus should be on designing the layout and user interface of the site, including the search bar, article list, and article detail pages. The design system should be carefully considered to ensure consistency and usability across the site. For stage 3, the focus should be on implementing the design system and building the UI components, including the search bar, article list, and article detail pages. The implementation should be done using a modular and reusable approach to ensure maintainability and scalability. For stage 4, the focus should be on implementing the features and functionality of the site, including search and filtering, saving and sharing, citation management, and data export. The implementation should be done using a test-driven development approach to ensure quality and reliability. For stage 5, the focus should be on deploying and scaling the site, including setting up the infrastructure, configuring the services, and optimizing the performance.\n\n## Stage 1\n\n## Website Summary\n\nThis site is a PubMed abstract viewer, allowing users to access and analyze scientific research articles, particularly those related to the long-term safety of ketamine and esketamine in treating depression. The site provides features for searching, saving, and sharing articles, as well as tools for citation management and data export. It is primarily designed for researchers, scientists, and medical professionals seeking to stay up-to-date on the latest research in their field.\n\n**Target Users:** Researchers, scientists, medical professionals, and anyone interested in accessing and analyzing scientific research articles\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- HTML5\n- CSS3\n- React\n- Redux\n- Express.js\n- Node.js\n- PostgreSQL\n- Material-UI\n- Bootstrap\n- Tailwind CSS\n- WebSockets\n- OAuth 2.0\n- OpenID Connect\n- JSON Web Tokens\n- AWS Lambda\n- AWS API Gateway\n- AWS S3\n- AWS CloudFront\n\n## Key Features Identified\n\n- Search and filtering of PubMed articles\n- Saving and sharing articles\n- Citation management and data export\n- User authentication and authorization\n- Real-time updates and notifications\n- Customizable layout and design\n- Integration with external services and APIs\n\n## Rebuild Objective\n\nTo build a robust and scalable PubMed abstract viewer that allows users to easily search, save, and share scientific research articles, while also providing tools for citation management and data export. The site should be designed with a modern and responsive layout, and should integrate with external services and APIs to provide a seamless user experience.\n\n## Next-stage focus\n\nFor stage 2, the focus should be on designing the layout and user interface of the site, including the search bar, article list, and article detail pages. The design system should be carefully considered to ensure consistency and usability across the site. For stage 3, the focus should be on implementing the design system and building the UI components, including the search bar, article list, and article detail pages. The implementation should be done using a modular and reusable approach to ensure maintainability and scalability. For stage 4, the focus should be on implementing the features and functionality of the site, including search and filtering, saving and sharing, citation management, and data export. The implementation should be done using a test-driven development approach to ensure quality and reliability. For stage 5, the focus should be on deploying and scaling the site, including setting up the infrastructure, configuring the services, and optimizing the performance.\n\n## Stage 1\n\n## Website Summary\n\nThis site is a PubMed abstract viewer, allowing users to access and analyze scientific research articles, particularly those related to the long-term safety of ketamine and esketamine in treating depression. The site provides features for searching, saving, and sharing articles, as well as tools for citation management and data export. It is primarily designed for researchers, scientists, and medical professionals seeking to stay up-to-date on the latest research in their field.\n\n**Target Users:** Researchers, scientists, medical professionals, and anyone interested in accessing and analyzing scientific research articles\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- HTML5\n- CSS3\n- React\n- Redux\n- Express.js\n- Node.js\n- PostgreSQL\n- Material-UI\n- Bootstrap\n- Tailwind CSS\n- WebSockets\n- OAuth 2.0\n- OpenID Connect\n- JSON Web Tokens\n- AWS Lambda\n- AWS API Gateway\n- AWS S3\n- AWS CloudFront\n\n## Key Features Identified\n\n- Search and filtering of PubMed articles\n- Saving and sharing articles\n- Citation management and data export\n- User authentication and authorization\n- Real-time updates and notifications\n- Customizable layout and design\n- Integration with external services and APIs\n\n## Rebuild Objective\n\nTo build a robust and scalable PubMed abstract viewer that allows users to easily search, save, and share scientific research articles, while also providing tools for citation management and data export. The site should be designed with a modern and responsive layout, and should integrate with external services and APIs to provide a seamless user experience.\n\n## Next-stage focus\n\nFor stage 2, the focus should be on designing the layout and user interface of the site, including the search bar, article list, and article detail pages. The design system should be carefully considered to ensure consistency and usability across the site. For stage 3, the focus should be on implementing the design system and building the UI components, including the search bar, article list, and article detail pages. The implementation should be done using a modular and reusable approach to ensure maintainability and scalability. For stage 4, the focus should be on implementing the features and functionality of the site, including search and filtering, saving and sharing, citation management, and data export. The implementation should be done using a test-driven development approach to ensure quality and reliability. For stage 5, the focus should be on deploying and scaling the site, including setting up the infrastructure, configuring the services, and optimizing the performance.\n\n## Stage 1\n\n## Website Summary\n\nThis site is a PubMed abstract viewer, allowing users to access and analyze scientific research articles, particularly those related to the long-term safety of ketamine and esketamine in treating depression. The site provides features for searching, saving, and sharing articles, as well as tools for citation management and data export. It is primarily designed for researchers, scientists, and medical professionals seeking to stay up-to-date on the latest research in their field.\n\n**Target Users:** Researchers, scientists, medical professionals, and anyone interested in accessing and analyzing scientific research articles\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- JavaScript\n- HTML5\n- CSS3\n- React\n- Redux\n- Express.js\n- Node.js\n- PostgreSQL\n- Material-UI\n- Bootstrap\n- Tailwind CSS\n- WebSockets\n- OAuth 2.0\n- OpenID Connect\n- JSON Web Tokens\n- AWS Lambda\n- AWS API Gateway\n- AWS S3\n- AWS CloudFront\n\n## Key Features Identified\n\n- Search and filtering of PubMed articles\n- Saving and sharing articles\n- Citation management and data export\n- User authentication and authorization\n- Real-time updates and notifications\n- Customizable layout and design\n- Integration with external services and APIs\n\n## Rebuild Objective\n\nTo build a robust and scalable PubMed abstract viewer that allows users to easily search, save, and share scientific research articles, while also providing tools for citation management and data export. The site should be designed with a modern and responsive layout, and should integrate with external services and APIs to provide a seamless user experience.\n\n## Next-stage focus\n\nFor stage 2, the focus should be on designing the layout and user interface of the site, including the search bar, article list, and article detail pages. The design system should be carefully considered to ensure consistency and usability across the site. For stage 3, the focus should be on implementing the design system and building the UI components, including the search bar, article list, and article detail pages. The implementation should be done using a modular and reusable approach to ensure maintainability and scalability. For stage 4, the focus should be on implementing the features and functionality of the site, including search and filtering, saving and sharing, citation management, and data export. The implementation should be done using a test-driven development approach to ensure quality and reliability. For stage 5, the focus should be on deploying and scaling the site, including setting up the infrastructure, configuring the services, and optimizing the performance.\n\n---\n\n## Stage 5 — Master Prompt\n\n## Project Overview and Objectives\nThe objective of this project is to rebuild the PubMed website from scratch, focusing on the page related to the long-term safety of ketamine and esketamine in the treatment of depression. The new website should be fully functional, responsive, and accessible, with a user-friendly interface and interactive features.\n\n## Tech Stack and Recommended Libraries\nThe recommended tech stack for this project includes:\n* Frontend: React with Next.js for server-side rendering and static site generation\n* Backend: Node.js with Express.js for API routing and database interactions\n* Database: PostgreSQL for storing publication data and user information\n* Styling: CSS with Sass for preprocessing and CSS modules for component-level styling\n* UI Components: Material-UI for consistency and accessibility\n* State Management: Redux with React Redux for state management and React Query for data fetching\n* Routing: Next.js built-in routing for client-side and server-side rendering\n* Authentication: OAuth 2.0 with Google and GitHub for user authentication\n* Deployment: Vercel for static site generation and serverless functions\n\n## Step-by-Step Implementation Instructions\n### 1. Setup and Configuration\n* Create a new Next.js project with `npx create-next-app my-app`\n* Install required dependencies with `npm install` or `yarn install`\n* Configure PostgreSQL database and create a new database for the project\n* Set up OAuth 2.0 authentication with Google and GitHub\n\n### 2. Data Modeling and API Design\n* Design a data model for publications, including title, authors, abstract, and keywords\n* Create API endpoints for fetching publications, searching, and filtering\n* Implement API routing with Express.js and connect to PostgreSQL database\n\n### 3. UI Components and Styling\n* Create reusable UI components with Material-UI and CSS modules\n* Implement responsive design with CSS media queries and mobile-first approach\n* Add accessibility features, such as ARIA attributes and semantic HTML\n\n### 4. Page Implementation\n* Implement the main page with a search bar, publication list, and filters\n* Create a publication detail page with abstract, authors, and keywords\n* Add interactive features, such as sorting, filtering, and pagination\n\n### 5. State Management and Data Fetching\n* Implement state management with Redux and React Redux\n* Use React Query for data fetching and caching\n* Connect API endpoints to UI components and handle errors and loading states\n\n### 6. Authentication and Authorization\n* Implement OAuth 2.0 authentication with Google and GitHub\n* Add authorization checks for protected routes and API endpoints\n* Handle authentication errors and redirect to login page\n\n### 7. Deployment and Testing\n* Deploy the application to Vercel with static site generation and serverless functions\n* Test the application with Jest and Cypress for unit testing and end-to-end testing\n* Monitor performance and fix issues with Webpack and Next.js optimization\n\n## UI Specifications\n* Colors:\n\t+ Primary color: #20558a\n\t+ Secondary color: #ffffff\n\t+ Background color: #f7f7f7\n* Spacing:\n\t+ Margin: 16px\n\t+ Padding: 16px\n* Typography:\n\t+ Font family: Merriweather\n\t+ Font size: 16px\n\t+ Line height: 24px\n* Responsive design:\n\t+ Mobile: 320px\n\t+ Tablet: 768px\n\t+ Desktop: 1024px\n\n## Interactive Features and Behaviors\n* Search bar: autocomplete, filtering, and sorting\n* Publication list: pagination, sorting, and filtering\n* Publication detail page: abstract, authors, and keywords\n* Authentication: login, logout, and protected routes\n\n## Edge Cases and Gotchas\n* Handling errors and loading states for API endpoints\n* Implementing accessibility features for screen readers and keyboard navigation\n* Fixing issues with Webpack and Next.js optimization for performance\n\n## Verification Checklist\n* Test the application with Jest and Cypress for unit testing and end-to-end testing\n* Verify responsive design and accessibility features\n* Check for errors and loading states for API endpoints\n* Test authentication and authorization checks for protected routes and API endpoints\n\n## Architect's Final Warning\nThe single most dangerous thing a junior could mess up when rebuilding this site is not implementing proper error handling and loading states for API endpoints. This can lead to a poor user experience, with errors and loading states not being handled properly, resulting in a broken and unresponsive application. It is crucial to implement try-catch blocks, error boundaries, and loading states to handle API errors and ensure a smooth user experience.\n\n## CLASSIFICATION\nCATEGORY: FRONTEND | SUBCATEGORY: React","country_iso":"US","score":0,"likes_count":0,"dislikes_count":0,"mode":"full","author_id":"bravecoral7073","category":null,"subcategory":null,"created_at":"2026-04-22 05:15:51","updated_at":null,"extractions_count":0},{"id":"25972e5b-c966-4e5d-8fbd-06d4425cd8cc","repo_url":"https://cnr-tracker-production.up.railway.app/","base_repo_url":"https://cnr-tracker-production.up.railway.app/","title":"cnr-tracker-production.up.railway.app [GB] velvetbadger610-01","version":1,"prompt_content":"## Stage Context (1-4)\n\n## Stage 1\n\n## Website Summary\n\nCnR Stats Tracker is a web application that provides a dashboard for tracking player statistics in a game, including leaderboards, player information, and analytics. The site is built for game enthusiasts and players, offering a comprehensive view of game performance and progress. The application is still in development, with data gathering in progress.\n\n**Target Users:** Game enthusiasts and players\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- Node.js\n- Express.js\n- MySQL\n- React\n- Tailwind CSS\n- JavaScript\n- HTML\n- CSS\n- Socket.io\n- Material-UI\n- Redux\n- Webpack\n- Babel\n\n## Key Features Identified\n\n- Leaderboards for tracking player statistics\n- Player information and analytics\n- Real-time data updates\n- User management and account creation\n- Customizable dashboard and layout\n\n## Rebuild Objective\n\nTo build a web application that provides a comprehensive dashboard for tracking player statistics in a game, including leaderboards, player information, and analytics, with a focus on real-time data updates and user management.\n\n## Next-stage focus\n\nFor stage 2, focus on designing a responsive and customizable dashboard layout that accommodates various screen sizes and devices. In stage 3, emphasize creating a consistent design system that aligns with the game's brand and aesthetic. In stage 4, delve into the implementation of real-time data updates and user management features. Finally, in stage 5, ensure that the master prompt covers all aspects of the application, including security, scalability, and performance.\n\n## Stage 1\n\n## Website Summary\n\nCnR Stats Tracker is a web application that provides a dashboard for tracking player statistics in a game, including leaderboards, player information, and analytics. The site is built for game enthusiasts and players, offering a comprehensive view of game performance and progress. The application is still in development, with data gathering in progress.\n\n**Target Users:** Game enthusiasts and players\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- Node.js\n- Express.js\n- MySQL\n- React\n- Tailwind CSS\n- JavaScript\n- HTML\n- CSS\n- Socket.io\n- Material-UI\n- Redux\n- Webpack\n- Babel\n\n## Key Features Identified\n\n- Leaderboards for tracking player statistics\n- Player information and analytics\n- Real-time data updates\n- User management and account creation\n- Customizable dashboard and layout\n\n## Rebuild Objective\n\nTo build a web application that provides a comprehensive dashboard for tracking player statistics in a game, including leaderboards, player information, and analytics, with a focus on real-time data updates and user management.\n\n## Next-stage focus\n\nFor stage 2, focus on designing a responsive and customizable dashboard layout that accommodates various screen sizes and devices. In stage 3, emphasize creating a consistent design system that aligns with the game's brand and aesthetic. In stage 4, delve into the implementation of real-time data updates and user management features. Finally, in stage 5, ensure that the master prompt covers all aspects of the application, including security, scalability, and performance.\n\n## Stage 1\n\n## Website Summary\n\nCnR Stats Tracker is a web application that provides a dashboard for tracking player statistics in a game, including leaderboards, player information, and analytics. The site is built for game enthusiasts and players, offering a comprehensive view of game performance and progress. The application is still in development, with data gathering in progress.\n\n**Target Users:** Game enthusiasts and players\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- Node.js\n- Express.js\n- MySQL\n- React\n- Tailwind CSS\n- JavaScript\n- HTML\n- CSS\n- Socket.io\n- Material-UI\n- Redux\n- Webpack\n- Babel\n\n## Key Features Identified\n\n- Leaderboards for tracking player statistics\n- Player information and analytics\n- Real-time data updates\n- User management and account creation\n- Customizable dashboard and layout\n\n## Rebuild Objective\n\nTo build a web application that provides a comprehensive dashboard for tracking player statistics in a game, including leaderboards, player information, and analytics, with a focus on real-time data updates and user management.\n\n## Next-stage focus\n\nFor stage 2, focus on designing a responsive and customizable dashboard layout that accommodates various screen sizes and devices. In stage 3, emphasize creating a consistent design system that aligns with the game's brand and aesthetic. In stage 4, delve into the implementation of real-time data updates and user management features. Finally, in stage 5, ensure that the master prompt covers all aspects of the application, including security, scalability, and performance.\n\n## Stage 1\n\n## Website Summary\n\nCnR Stats Tracker is a web application that provides a dashboard for tracking player statistics in a game, including leaderboards, player information, and analytics. The site is built for game enthusiasts and players, offering a comprehensive view of game performance and progress. The application is still in development, with data gathering in progress.\n\n**Target Users:** Game enthusiasts and players\n**Difficulty:** Intermediate\n\n## Tech Stack (Recommended)\n\n- Node.js\n- Express.js\n- MySQL\n- React\n- Tailwind CSS\n- JavaScript\n- HTML\n- CSS\n- Socket.io\n- Material-UI\n- Redux\n- Webpack\n- Babel\n\n## Key Features Identified\n\n- Leaderboards for tracking player statistics\n- Player information and analytics\n- Real-time data updates\n- User management and account creation\n- Customizable dashboard and layout\n\n## Rebuild Objective\n\nTo build a web application that provides a comprehensive dashboard for tracking player statistics in a game, including leaderboards, player information, and analytics, with a focus on real-time data updates and user management.\n\n## Next-stage focus\n\nFor stage 2, focus on designing a responsive and customizable dashboard layout that accommodates various screen sizes and devices. In stage 3, emphasize creating a consistent design system that aligns with the game's brand and aesthetic. In stage 4, delve into the implementation of real-time data updates and user management features. Finally, in stage 5, ensure that the master prompt covers all aspects of the application, including security, scalability, and performance.\n\n---\n\n## Stage 5 — Master Prompt\n\n# Project Overview and Objectives\nThe objective of this project is to rebuild the CnR Stats Tracker website from scratch, replicating its functionality, design, and user experience. The website is a player stats tracker for the game COPS & ROBBERS, providing features such as user registration, login, dashboard, player search, leaderboards, and admin panel.\n\n## Tech Stack and Recommended Libraries\nThe recommended tech stack for this project is:\n* Frontend: NextJS with React\n* Backend: NodeJS with ExpressJS\n* Database: MySQL\n* CSS Framework: Custom CSS with CSS variables\n* Libraries:\n\t+ React Hooks for state management\n\t+ Axios for API requests\n\t+ React Router for client-side routing\n\t+ MySQL2 for database interactions\n\n## Step-by-Step Implementation Instructions\n### Authentication Page\n1. Create a new NextJS page for authentication (`/auth`)\n2. Design the authentication form with the following fields:\n\t* Username\n\t* Password\n\t* Sign In button\n\t* Register button\n3. Implement authentication logic using NodeJS and ExpressJS\n4. Use React Hooks to manage form state and handle form submissions\n\n### Dashboard Page\n1. Create a new NextJS page for the dashboard (`/dashboard`)\n2. Design the dashboard layout with the following sections:\n\t* Topbar with title and subtitle\n\t* Sidebar with navigation links\n\t* Main content area with player stats and leaderboards\n3. Implement dashboard logic using NodeJS and ExpressJS\n4. Use React Hooks to manage dashboard state and handle API requests\n\n### Leaderboards Page\n1. Create a new NextJS page for leaderboards (`/leaderboards`)\n2. Design the leaderboards layout with the following sections:\n\t* Leaderboard table with player stats\n\t* Pagination links\n3. Implement leaderboard logic using NodeJS and ExpressJS\n4. Use React Hooks to manage leaderboard state and handle API requests\n\n### Admin Panel Page\n1. Create a new NextJS page for the admin panel (`/admin`)\n2. Design the admin panel layout with the following sections:\n\t* User management table\n\t* Activity log table\n3. Implement admin panel logic using NodeJS and ExpressJS\n4. Use React Hooks to manage admin panel state and handle API requests\n\n## UI Specifications\n* Colors:\n\t+ Primary color: `#f0b429` (orange)\n\t+ Secondary color: `#3dd6f5` (blue)\n\t+ Background color: `#050608` (dark gray)\n\t+ Text color: `#c8d8e8` (light gray)\n* Spacing:\n\t+ Margin: 16px\n\t+ Padding: 20px\n* Typography:\n\t+ Font family: Barlow\n\t+ Font size: 14px\n\t+ Line height: 1.5\n\n## Interactive Features and Behaviors\n* Authentication form submission handling\n* Dashboard data loading and rendering\n* Leaderboard data loading and rendering\n* Admin panel data loading and rendering\n* Pagination link handling\n* User management table row clicking handling\n\n## Responsive Design Requirements\n* The website should be fully responsive and work on all devices (desktop, tablet, mobile)\n* The layout should adapt to different screen sizes and orientations\n\n## Edge Cases, Gotchas, and Common Mistakes\n* Handling authentication errors and edge cases\n* Handling dashboard and leaderboard data loading errors\n* Handling admin panel data loading errors\n* Ensuring proper pagination link handling\n* Ensuring proper user management table row clicking handling\n\n## Verification Checklist\n1. Authentication form submission handling works correctly\n2. Dashboard data loading and rendering works correctly\n3. Leaderboard data loading and rendering works correctly\n4. Admin panel data loading and rendering works correctly\n5. Pagination link handling works correctly\n6. User management table row clicking handling works correctly\n7. Website is fully responsive and works on all devices\n\n## Architect's Final Warning\nThe single most dangerous thing a junior could mess up when rebuilding this site is not properly handling authentication and authorization. This could lead to security vulnerabilities and expose sensitive user data. It is crucial to ensure that authentication and authorization are implemented correctly and securely.\n\n## CLASSIFICATION\nCATEGORY: FRONTEND | SUBCATEGORY: NextJS","country_iso":"GB","score":1,"likes_count":1,"dislikes_count":0,"mode":"mid","author_id":"velvetbadger610","category":null,"subcategory":null,"created_at":"2026-04-22 00:25:55","updated_at":"2026-10-22T07:30:12.628Z","extractions_count":0}],"meta":{"page":0,"limit":10,"sort":"recent","filter":null}}