Loading...
Loading...
Generate a professional, comprehensive README.md file for full-stack software features, automatically analyzing backend, database, and frontend code to document architecture, flows, setup, and best practices.
You are an expert software architect and technical documentation specialist. Your task is to generate an extensive, professional README.md file for the new feature named [FEATURE_NAME], which implements [BRIEF_OVERVIEW_OF_FEATURE]. This feature spans backend ([BACKEND_TECHNOLOGIES]), database ([DB_TECHNOLOGY_AND_SCHEMA_OVERVIEW]), and frontend ([FRONTEND_TECHNOLOGIES]). Here is all relevant code and details: **Backend Files and Code:** [PASTE_BACKEND_FILES_AND_CODE_HERE] **Database Schema and Migrations:** [PASTE_DB_SCHEMA_MIGRATIONS_AND_QUERIES_HERE] **Frontend Files and Code:** [PASTE_FRONTEND_FILES_AND_CODE_HERE] **Additional Details:** [ANY_OTHER_RELEVANT_INFO_LIKE_APIS_ENDPOINTS_CONFIG_SETUP_STEPS_DEPENDENCIES] Analyze the provided code thoroughly to understand the full architecture, data flows, APIs, components, and interactions between backend, DB, and frontend. Generate a complete README.md in Markdown format with these exact sections: 1. **Overview**: High-level description of the feature, its purpose, and key benefits. 2. **Architecture Diagram**: A text-based ASCII or Mermaid diagram showing the high-level architecture (backend -> DB -> frontend flows). 3. **Step-by-Step Functionality**: Detailed walkthrough of everything the feature does, from user interaction to backend processing, DB operations, and response. 4. **Backend Details**: File structure, key endpoints/routes, logic explanation, error handling. 5. **Database Schema**: Tables, relationships, indexes, sample data/queries. 6. **Frontend Details**: Components, UI flows, state management, API integrations. 7. **Setup and Installation**: Prerequisites, environment setup, running locally, deployment notes. 8. **Usage Examples**: Code snippets or screenshots for common use cases. 9. **Testing**: Unit/integration tests overview if applicable. 10. **Troubleshooting**: Common issues and fixes. 11. **Future Improvements**: Suggestions based on analysis. Ensure the README is clear, concise yet detailed, uses badges/icons if relevant, and is ready to be copied into a GitHub repo. Make it extensive (2000+ words) but well-structured.
This prompt generates a comprehensive Markdown roadmap for building professional, interactive, agentic CLI coding tools with stunning TUIs, inspired by Claude Code and Aider. Customize placeholders and feed to an AI for an executable build plan.
Generate ultra-detailed, canonical image prompts for Simpsons characters like Ralph Wiggum, optimized for AI generators like Midjourney or DALL-E, ensuring faithful 2D cel-shaded portraits with no background.
Generate a comprehensive, step-by-step Markdown tutorial for building a production-ready Flask web app using a strict 3-layer architecture (presentation, business logic, data), fully customizable for any app functionality.
This reusable prompt template enhances raw AI skill descriptions into clear, structured, markdown-formatted documentation with actionable instructions, examples, and SEO optimization for maximum usability.
Transform vague AI skill descriptions into clear, structured, and professional documentation with this expert prompt template designed for technical writers and prompt engineers.
A professional prompt template for thorough AI-powered code reviews, assessing readability, performance, security, best practices, bugs, and design with scored feedback, detailed breakdowns, refactored code, and prioritized fixes.