World Vibe Web
The distributed app store for vibe-coded projects. Browse, discover, and install open-source apps from across GitHub.
翻译准备中
尚未检测到更新。GitHub 发布版本后会显示在这里。
按最近已完成的 8 小时观测回合间的 GitHub 星标增量排序
The distributed app store for vibe-coded projects. Browse, discover, and install open-source apps from across GitHub.
翻译准备中
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权，自行管理介绍，无需管理员批准。
登录并生成验证文件，在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件，即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录，将前往登录页面。登录后请回到此处，再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify，即可验证所有权并自行管理介绍。
一分钟完成验证A cyberfunky-themed, highly interactive e-commerce platform for custom gaming rigs. Features a fully integrated CLI, an intelligent AI shopping assistant, a gamified user experience, and a secure admin dashboard. Built with Node.js, Express, and MongoDB.
翻译准备中
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
🦅 Phoenix Codex - Cyberpunk PC Store DEMO
🔗 Live Demo: https://codex-iota-nine.vercel.app
A high-end custom PC retail platform featuring a cyberpunk aesthetic and AI integration.
🚀 Features
• Cyberpunk UI: Built with CSS Grid and Flexbox for a full "Matrix" experience.
• Secure API Communication
• Support Assistant: Guided help menu (Codex Support) covering the most common customer questions.
• Holographic Effects Dynamic product showcase with hover effects.
• Mobile Optimized: Fully responsive layout for smartphones and tablets.查看完整 README ↗🔗 Live Demo: https://codex-iota-nine.vercel.app A high-end custom PC retail platform featuring a cyberpunk aesthetic and AI integration.
/css: Contains all styling and media queries./js: Store logic and Chatbot functionality./assets: Images, GIFs, and sound effects.This project follows the Git Flow model. All development and testing occur in the main-test branch before merging into main.
Vercel is wired to match: a push to main-test builds a Preview deployment, and merging the
pull request into main is what promotes it to Production. The API lives in the separate
codex-backend repository and follows the same flow,
deployed on Render.
A single feature often touches both repositories, and they deploy independently. Deploy the backend first, wait for Render to report Live, and only then merge the frontend pull request.
An older frontend works fine against a newer API, because backend changes are additive. A frontend that ships first calls routes that do not exist yet and breaks production.