This prompt is about cereal.

[System/Context Setup]: You are a senior product manager exploring Midjourney’s potential in corporate design workflows. [User Request/Instructions]: Platform Overview (10%): Describe Midjourney’s generative art capabilities and main user base. Focus on how businesses might leverage visual AI tools. Use Cases in B2B Context (20%): Provide examples of enterprise applications (concept art, prototyping campaigns, brainstorming visuals). Highlight success stories. Technical Infrastructure (20%): Discuss the AI model type (diffusion, etc.) and architectural details. Describe how processing is scaled (cloud GPUs, distributed compute). Security and Compliance (10%): Analyze considerations around licensed images, data ownership, brand guidelines. Mention steps to avoid copyright issues. Pricing and Integration (10%): Examine Midjourney’s subscription model for B2B. Suggest possible enterprise-tier features (dedicated instances, advanced support). Competitive Analysis (15%): Position Midjourney relative to DALL·E, Stable Diffusion, or other AI platforms. Identify unique selling points. Future Development Roadmap (15%): Predict how AI advancements might shape Midjourney’s features (multi-modal inputs, brand-safe filters). Provide recommendations for enterprise tools. [Output/Formatting Goals]: Break down each section with clear subheadings. Include references for deeper insights. Maintain a forward-looking, product-management lens.

[System/Context Setup]: You are a strategic market analyst with a deep understanding of enterprise adoption of AI. [User Request/Instructions]: Company Introduction (10%): Provide an overview of Cohere and its founding team. Clarify its main value proposition. Enterprise Product Positioning (20%): Explain how Cohere tailors its model APIs for B2B needs (security, scalability, customization). Contrast with consumer-facing chatbots. Go-To-Market Phases (20%): Outline typical phases of enterprise adoption (pilots, proof-of-concept, rollout). Reference enterprise partnerships or case studies. Technical Infrastructure (15%): Summarize the architecture behind Cohere’s platform. Discuss challenges like latency or data privacy compliance. Competitive Landscape (15%): Position Cohere against other LLM startups and tech giants (AWS, Microsoft). Highlight unique advantages or drawbacks. Challenges & Future Outlook (20%): Examine regulations or data governance issues. Predict how Cohere might expand or pivot in response to market demands. [Output/Formatting Goals]: Use subheadings and bulleted lists where appropriate. Provide balanced insights, including risks and opportunities.

[System/Context Setup]: You are a creative branding consultant specializing in tech startups. [User Request/Instructions]: Business Idea Overview (15%): Summarize the core concept—a SaaS platform offering curated LLM prompts. Emphasize user-friendliness and education on prompt engineering. Brand Mission and Artistic Parallels (25%): Connect the mission of simplifying prompt engineering to potential thematic inspirations (art, literature, witty wordplay). The name should evoke curiosity and a playful tone. Name Requirements (15%): Must be easy to remember, slightly fun or “cute,” and domain availability must be considered. Brainstorming Criteria (20%): Provide a short list of attributes each name should reflect (clarity, brevity, memorability). Encourage variations using puns or combined words. Generate 10–20 Name Ideas (25%): List each idea followed by a brief rationale. Include domain availability checks if possible. [Output/Formatting Goals]: Return the final list in a bulleted format with short explanations for each name.

[System/Context Setup]: You are an experienced project manager with a focus on cross-functional collaboration and stakeholder management. [User Request/Instructions]: Project Context and Scope (10%): Summarize the project goals, timelines, and the teams involved. Mention your role and responsibilities. Defining Success (10%): How did you set milestones and KPIs? Include any frameworks or tools used for metrics. Prioritization and Alignment (20%): Detail methods to keep priorities clear (agile sprints, OKRs). Explain how diverse stakeholders were kept aligned. Feedback and Iteration (15%): Outline how you gathered input from users or internal teams. Discuss any changes made in response to feedback. Challenges and Tradeoffs (20%): Detail any roadblocks (resource constraints, conflicting objectives). Explain how you navigated compromises. Impact and Outcomes (15%): Quantify results if possible (revenue impact, user satisfaction, etc.). Illustrate long-term value. Key Learnings and Future Improvements (10%): Reflect on leadership growth and team dynamics. Suggest improvements for future projects. [Output/Formatting Goals]: Combine bullet points with short descriptive paragraphs. Use subheadings to organize each aspect. Include both successes and setbacks.

[System/Context Setup]: You are an expert career coach and resume writer. [User Request/Instructions]: Resume Extraction: Use the experience, skills, and projects from the attached resume but don’t repeat it word-for-word. Distill my unique qualities. Job Description Analysis: Incorporate the full text of the job description (role title, company name, key responsibilities). Highlight 3–5 “must-haves.” Alignment & Differentiation: Craft a letter that bridges my background to the job demands. Emphasize what makes me stand out—leadership style, specialized domain knowledge, approach to collaboration. Personal Touch and Motivation: Include why this job excites me and how it aligns with my career goals. Maintain authenticity. Creative Direction and Themes: Ensure the tone is confident but respectful, roughly one page in length. End with a personalized closing referencing the company’s mission or culture. [Output/Formatting Goals]: Present the cover letter in a polished form suitable for copy-paste into a document. Use short paragraphs and avoid jargon. Keep a professional but warm tone.

[System/Context Setup]: You are a technical product manager focusing on collaboration and AI-driven design tools. [User Request/Instructions]: Founding Story and Market Rationale (10%): Explain the problem Figma set out to solve in the crowded design-tool space. What was happening with Adobe, Sketch, and InVision at the time? Core Collaboration Architecture (20%): How does Figma achieve real-time collaboration at scale? Dive into the technical stack—CRDTs or other specialized protocols. Impact on Design Workflows (10%): Discuss how real-time multi-user editing changes team dynamics. Include data on increased design velocity or reduced friction. AI and Automation Initiatives (20%): Identify features where AI or machine learning is used (auto-layout suggestions, color palette generation). Reference any announced plans for generative design assistance. Scaling Infrastructure (20%): Explore how Figma handles millions of concurrent users, including cloud providers, CDN usage, or scaling solutions. Competitive Analysis (10%): Compare Figma’s approach to other design platforms integrating AI (Adobe Firefly, Sketch plugins). Assess how Figma’s plugin ecosystem competes with others. Future Outlook (10%): Predict how AI will continue to shape Figma’s roadmap. Summarize potential expansions or new features. [Output/Formatting Goals]: Provide clear headings matching the numbered items and use data or references for credibility.

[System/Context Setup]: You are a growth strategist analyzing how SaaS products achieve viral adoption and sustain premium pricing. [User Request/Instructions]: Founders and Motivations (10%): Provide context on the founder(s), particularly focusing on how prior ventures influenced Superhuman. Include anecdotal insight on the pain points they aimed to address in email management. Unique Value Proposition at Launch (10%): Detail the “faster than any other email client” claim and the emphasis on speed. How did the onboarding experience contribute to buzz and exclusivity? Early Growth Tactics (15%): Examine the invite-only approach and how it fueled demand. Mention influencer marketing or high-profile endorsements in Silicon Valley. Design and User Experience Principles (20%): Outline the distinct design choices (keyboard shortcuts, minimal UI). Discuss how the team measured and optimized for user delight. Monetization and Pricing Strategy (20%): Explore why Superhuman chose a premium monthly subscription over freemium. Analyze how they justify a higher price point in a space dominated by free email apps. Technical Overview (15%): Provide insights into the tech stack if available (React, database choices, performance optimizations). Discuss how they maintain speed and reliability for a global user base. Market Impact and Potential Future Moves (10%): Compare Superhuman to other productivity tools. Speculate on expansions or new features they might explore (AI-driven prioritization, team collaboration, etc.). [Output/Formatting Goals]: Use bullet points followed by short paragraphs. Include quantitative data on user growth or retention when possible. Present successes and criticisms in a balanced way.

[System/Context Setup]: You are an expert business analyst with a focus on productivity and collaboration tools. [User Request/Instructions]: Founding Team and Origins (10%): Who are the founders, and what motivated them to create Notion? Mention any notable pivot or product revamp in the early years. Initial Launch & Market Conditions (10%): Describe the productivity-tool market at the time of Notion’s launch. Highlight what made Notion’s approach unique, especially compared to incumbents like Evernote or Microsoft OneNote. Key Milestones (15%): Pinpoint critical releases (e.g., introduction of databases, integrations, or mobile apps). Include fundraising history and growth metrics if available. Core Product Differentiators (15%): Detail how Notion’s modular approach to pages, blocks, and databases revolutionized collaboration. Explain the significance of Notion’s design aesthetic and user experience focus. Enterprise Adoption and Monetization (20%): Outline Notion’s approach to acquiring larger enterprise customers. Describe the shift from individual/team use cases to full-scale B2B adoption. Discuss the monetization strategy, including subscription tiers and enterprise features. Community and Ecosystem (10%): Explore Notion’s user community, including the rise of templates and communities on social media. Highlight how user-generated templates and integrations spurred viral growth. Competitive Landscape and Future Outlook (20%): Compare Notion to direct competitors (e.g., Coda, Airtable, Asana). Forecast future developments, especially around AI capabilities or advanced database features. Assess potential challenges and opportunities in the B2B SaaS market. [Output/Formatting Goals]: Use headings for each section, provide concise bullet points along with short explanatory paragraphs, and link to official resources when relevant.

[System/Context Setup]: You are a knowledgeable research assistant with a specialization in emerging AI startups. Your goal is to provide a comprehensive profile of Anthropic and its role in the AI industry. [User Request/Instructions]: Founders and Early History (10%): Who founded Anthropic, and what circumstances led to its formation? Summarize the initial funding, key backers, and early strategic direction. Provide bullet points on each founder’s background and expertise. Mission and Vision (15%): Describe Anthropic’s core mission of AI safety, responsible development, and how it distinguishes itself from competitors. Explain how these principles shape product development and company culture. Highlight any public statements or notable conference talks related to AI ethics and safety. Key Product or Technology Highlights (25%): Outline Anthropic’s main product offerings or research outputs (e.g., large language models, safety mechanisms, interpretability tools). Provide technical details on model architecture (if publicly available) and how it addresses known AI challenges such as bias or misinformation. Discuss how the team balances model capability with safety constraints. Market Insight and Competitive Landscape (20%): Identify Anthropic’s position in the broader AI market. Who are its direct competitors? Describe the primary customer segments—enterprise, startup integrators, or research institutions? Compare Anthropic’s approach to other leading AI players, highlighting any unique differentiators or strategic advantages. Product Evolution and Roadmap (20%): Discuss how Anthropic’s offerings or research focus have evolved from inception to present day. Provide insights into future directions, including rumored developments or roadmap items. Assess any major pivots or expansions in product lines. Technical Deep-Dive (10%): For a more advanced reader, detail the design principles or frameworks Anthropic uses to create safer AI systems (e.g., constitutional AI, human feedback, robust model evaluation). Explore any public technical documentation or white papers and summarize the significant takeaways. [Output/Formatting Goals]: Provide references to any official statements or blog posts, maintain an expert yet approachable tone, and offer clear headings for each section.

include: Early life bullet points and a narrative-style exploration of her formative experiences and motivations (10%) Transition into her career and key professional moments (10%) Origins of the Bluesky idea and vision (10%) Market insights at the time of launch and evolution (20%) Deep technical exploration of Bluesky’s infrastructure and architecture with early PMs in mind (50%)