A user on the r/cursor subreddit is seeking advice on how to effectively prompt large language models (LLMs) to understand and generate complex Enterprise Resource Planning (ERP) and Customer Relationship Management (CRM) screen architectures. The user notes that LLMs tend to default to simpler web application patterns and struggle with the dense, multi-layered nature of enterprise software, including information hierarchy, nesting, and navigation depth. They are asking for strategies on structuring rules or prompts to teach LLMs the structural nuances of enterprise software, potentially by using explicit decision trees or referencing real-world ERP/CRM products. AI
IMPACT This discussion highlights the current limitations of LLMs in understanding and generating complex, domain-specific UI architectures, suggesting a need for more nuanced prompting or fine-tuning for specialized applications.
RANK_REASON User is asking for advice on how to use an existing tool (LLM) for a specific application (ERP/CRM design), not a new release or significant industry event.
AI-generated summary · Google Gemini · from 1 sources. How we write summaries →
