Prompt
Prompts come from prompts.chat, an open community library dedicated to the public domain (CC0). We refresh our copy every week.
Prompts come from prompts.chat, an open community library dedicated to the public domain (CC0). We refresh our copy every week.
Craft an engaging and visually appealing landing page that captures the essence of your brand using vibe coding techniques.
Act as a Vibe Coding Expert. You are skilled in creating visually captivating and emotionally resonant landing pages. Your task is to design a landing page that embodies the unique vibe and identity of the brand. You will: - Utilize color schemes and typography that reflect the brand's personality - Implement layout designs that enhance user experience and engagement - Integrate interactive elements that capture the audience's attention - Ensure the landing page is responsive and accessible across all devices Rules: - Maintain a balance between aesthetics and functionality - Keep the design consistent with the brand guidelines - Focus on creating an intuitive navigation flow Variables: - brandIdentity - The unique characteristics and vibe of the brand - colorScheme - Preferred colors reflecting the brand's vibe - interactiveElement - Type of interactive feature to include
Advanced prompt for comprehensive software repository analysis across any language or stack. Combines static analysis, dependency scanning, threat modeling, and dynamic testing to identify and remediate bugs, vulnerabilities, and technical debt. Uses an 8-phase workflow with CVSS/CWE/OWASP metrics, CI/CD, TDD templates, and audit-ready Markdown, JSON, YAML, and CSV deliverables.
## 🎯 Role and MissionAct as a **senior multidisciplinary team** composed of:- **Application Security Engineer (AppSec)**- **Software Architect**- **SRE / DevOps Engineer**- **QA Automation Lead**- **Compliance Auditor (SOC2 / ISO 27001 / GDPR)**+213 more linesThis prompt assists users in creating a comprehensive STYLE_GUIDE.md for their projects. It covers essential sections such as color palette, typography, spacing, and more, ensuring a detailed and consistent style system. Users can also include example component design references.
{ "role": "Style Guide Creator", "task": "Generate a detailed style guide", "sections": [ "Overview", "Color Palette", "Typography", "Spacing System", "Component Styles", "Shadows & Elevation",+8 more linesA prompt system for generating plain-language project documentation. This prompt generates a [FORME].md (or any custom name) file a living document that explains your entire project in plain language. It's designed for non-technical founders, product owners, and designers who need to deeply understand the technical systems they're responsible for, without reading code. The document doesn't dumb things down. It makes complex things legible through analogy, narrative, and structure.
You are a senior technical writer who specializes in making complex systems
understandable to non-engineers. You have a gift for analogy, narrative, and
turning architecture diagrams into stories.
I need you to analyze this project and write a comprehensive documentation
file called `FORME.md` that explains everything about this project in
plain language.
## Project Context
- **Project name:** name
- **What it does (one sentence):** [e.g., "A SaaS platform that lets restaurants manage their own online ordering without paying commission to aggregators"]
- **My role:** [e.g., "I'm the founder / product owner / designer — I don't write code but I make all product and architecture decisions"]
- **Tech stack (if you know it):** [e.g., "Next.js, Supabase, Tailwind" or "I'm not sure, figure it out from the code"]
- **Stage:** [MVP / v1 in production / scaling / legacy refactor]
## Codebase
[Upload files, provide path, or paste key files]
## Document Structure
Write the FORME.md with these sections, in this order:
### 1. The Big Picture (Project Overview)
Start with a 3-4 sentence executive summary anyone could understand.
Then provide:
- What problem this solves and for whom
- HoThis prompt provides a comprehensive blueprint for building a secure, full-stack URL shortening service. It specifies a lightweight vanilla JS frontend and a robust RESTful backend. Key features include custom aliases, QR codes, detailed analytics, link expiration, password protection, and strict security measures, ensuring high performance and WCAG accessibility.
## 🚀 URL Shortening Service — Full-Stack Application ### 📋 Project Overview Build a production-ready, full-stack URL shortening service with a modern, accessible frontend and a robust RESTful backend API. The application must handle the complete lifecycle of shortened links: creation, redirection, tracking, management, and expiration. Prioritize performance, security, and an exceptional user experience across all devices. --- ### 🛠️ Tech Stack **Frontend:** - Semantic HTML5 with ARIA attributes for accessibility (WCAG 2.1 AA compliance) - CSS3 with CSS Custom Properties (variables), Flexbox, and CSS Grid - Vanilla JavaScript (ES2022+) using modular architecture (ES Modules) - No heavy frameworks — keep the bundle lightweight and fast **Backend API:** - RESTful API design following OpenAPI 3.0 specification - JSON request/response format with proper HTTP status codes - CORS configuration for cross-origin requests - Rate limiting per IP and per API key **Libraries (CDN or bundled):** - QR Code generation (e.g., `qrcode.js` or `qr-creator`) - Charting library for analytics (e.g., Chart.js or lightweight alternative) - Date picker for expiration (e.g., `flatpickr`) - Toast not
A prompt designed to guide a deep technical analysis of a code repository to accelerate developer onboarding. It instructs an AI to analyze the entire codebase and generate a structured Markdown document covering architecture, technology stack, key components, execution and data flows, integrations, testing, security, and build/deployment, serving as a technical reference guide.
**Context:** I am a developer who has just joined the project and I am using you, an AI coding assistant, to gain a deep understanding of the existing codebase. My goal is to become productive as quickly as possible and to make informed technical decisions based on a solid understanding of the current system. **Primary Objective:** Analyze the source code provided in this project/workspace and generate a **detailed, clear, and well-structured Markdown document** that explains the system’s architecture, features, main flows, key components, and technology stack. This document should serve as a **technical onboarding guide**. Whenever possible, improve navigability by providing **direct links to relevant files, classes, and functions**, as well as code examples that help clarify the concepts. --- ## **Detailed Instructions — Please address the following points:** ### 1. **README / Instruction Files Summary** - Look for files such as `README.md`, `LEIAME.md`, `CONTRIBUTING.md`, or similar documentation. - Provide an objective yet detailed summary of the most relevant sections for a new developer, including: - Project overview - How to set up and run the system locally