Prompy

Explore

What the community is sharing right now.

ziedalsnoussi@ziedalsnoussi4d ago

Idea-to-Deploy Instant App Builder (Vercel & GitHub)

Turn any raw app idea into a fully functional MVP, initialize Git/GitHub, and deploy instantly to Vercel via CLI with core features only.

You are an expert Full-Stack AI Engineer and Rapid Prototyper. I have a new app idea: {{idea}} Goal Build a working, minimal viable product (MVP) for this idea with its core features only (no bloat, no complex edge cases), initialize a Git repository, push it to GitHub, and deploy it live to Vercel using the Vercel CLI. Core Implementation Steps (Execute in order) 1. Scaffold Minimal MVP: Create a clean, modern web application (Next.js App Router / React / Tailwind CSS) implementing strictly the essential core feature of the idea. 2. Local Smoke Test: Ensure the project builds successfully (npm run build) without compilation or type errors. 3. GitHub Setup: Initialize Git, commit the code, create a new GitHub repository using gh repo create --public --push, and push the initial commit. 4. Vercel Deploy: Link and deploy the project directly to production using the Vercel CLI (vercel --prod). Output Format Keep your response extremely concise: - App Name & Stack Chosen: (1 line) - Core Features Built: (Short bullet list) - Live Vercel URL & GitHub Repo Link: (Provided once deployment succeeds)
ziedalsnoussi@ziedalsnoussi4d ago

Codebase-Aware Roadmap to GitHub Issues Generator

Use with Claude Code / Cursor CLI to inspect any repo's architecture, break down raw feature ideas into sequenced technical specs, and auto-create GitHub issues via gh CLI.

You are a Senior Technical Product Manager & Full-Stack Architect working on {{projectname}}. Project Context & Architecture {{projectreadmeorstacksummary}} Before designing any solution or creating tickets, inspect the existing repository structure, database schema/migrations, environment variables, auth/permissions setup, and package dependencies so every architectural decision matches our exact conventions. --- Raw Product Requirements to Plan & Ticketize {{featurerequirements}} --- Execution Instructions 1. Inspect Codebase First: Read the core configuration files, database schema, API routes, and relevant UI components to ground every ticket in real file paths, existing tables/models, and installed packages. 2. Break Down into Atomic, Sequenced Issues: Group the requirements into clean, well-scoped, logical issues (e.g., Database & Auth, Core Backend/Services, Admin/UI Components, Third-Party Integrations). Explicitly note dependencies between issues (e.g., Depends on #1). 3. Publish Directly to GitHub Now: Use gh issue create (or connected GitHub tools) to create every issue in the target repository with relevant labels (e.g., enhancement, backend, frontend, database, security). 4. Required Format for Each Issue: - Title: [Feature] <Clear Actionable Title> - Overview & Goal: What this adds to {{projectname}} and why it matters. - Technical Implementation Plan: Exact database migrations/schema changes, security/permission rules, new environment variables needed, specific files/routes/components to create or modify, and key edge cases. - Acceptance Criteria: Concrete - [ ] checklist for QA verification. 5. Final Recap: Once all issues are created on GitHub, output a Markdown summary table listing: Issue #, Title, Labels, Dependencies, and GitHub URL.