111 prompts
Act as a senior Laravel developer. Laravel version: [version] Resource: [name and fields with types/rules] Relationships: [details] UI: [Blade / Inertia / API only] Generate: migration, model with fillable and casts, form request validation, resource controller, routes, policy for authorisation, views or API resources…
Generate a complete Laravel CRUD feature: migration, model, controller, routes, validation and views.
Act as a senior product manager. Feature: [name] Problem and evidence: [details] Target users: [who] Goals: [outcomes] Write a PRD: background, problem statement, goals and non-goals, user stories with acceptance criteria, functional requirements, UX notes, edge cases, analytics/success metrics, launch plan, and open…
Write a clear PRD with problem, goals, user stories, requirements and success metrics.
Act as an account executive. Prospect: [company, contacts and roles] What they cared about in the demo: [notes] Next step agreed: [details] Write a 4-email follow-up sequence over 2 weeks: recap with value summary, a relevant case study, answers to open questions/business case help, and a respectful check-in. Each und…
Keep deals moving after a demo with helpful, personalised follow-ups.
Act as a sales operations manager. Sales motion: [inbound/outbound, deal size, cycle length] CRM: [tool] Design 6–8 pipeline stages with: definition, entry criteria, exit criteria, required fields, typical probability, and actions at each stage. Add rules for stale deals and a weekly pipeline review agenda.
Define clear pipeline stages with entry and exit criteria so forecasts are reliable.
Rewrite this email to be professional, clear and polite. Recipient and relationship: [details] Goal of the email: [outcome] Tone: [warm, firm, formal] Email: [paste] Keep my key points, make the request clear, remove anything emotional or vague, and suggest a subject line. Give a shorter alternative too.
Turn a rushed, emotional or unclear email into a clear, professional message.
Act as a startup COO. Company stage: [details] Period covered: [quarter] Key topics: [list] Decisions needed: [list] Create a board deck outline: executive summary, KPIs, financials and runway, progress on goals, key risks, strategic discussion topics, decisions requested, and appendix. Give a headline for each slide…
Structure a board meeting deck that focuses discussion on decisions, not just status updates.
Act as a brand consultant. Current brand: [details] Why rebrand: [reasons] What must stay: [elements with equity] Budget and timeline: [details] Create: a rebrand brief, research steps, decisions (name, logo, colours, voice, messaging), a rollout checklist (website, social, packaging, legal), a customer announcement p…
Plan a rebrand: why, what changes, how to roll it out and how to tell customers.
Act as an event marketer. Event: [type, date, location/virtual, capacity] Audience: [who] Budget: [amount] Goal: [registrations, sales, leads] Create a timeline from 8 weeks out: channels, email sequence, social posts, partner promotion, early-bird offers, reminder cadence, on-site/live engagement ideas, and post-even…
Fill your event with the right attendees using a pre-, during- and post-event marketing plan.
Act as a performance marketer. Product: [details] Funnel stages: [visited site, viewed product, added to cart, started trial] Create a retargeting sequence for each segment: message, creative idea, offer (if any), frequency cap, and time window. Avoid repetitive or creepy messaging, and include exclusions for converte…
Bring back visitors who didn't convert with a sequence of ads tailored to where they dropped off.
Act as a technical SEO specialist. Page type: [Article, Product, LocalBusiness, FAQPage, Event, Recipe, HowTo, Organization] Page details: [paste all relevant information] Generate valid JSON-LD schema, explain each property, mark required vs recommended fields, and tell me how to test it with a rich results testing t…
Generate valid JSON-LD structured data for articles, products, FAQs, events, local businesses and more.
Write a formal complaint letter. Company: [name] Product/service: [details] What went wrong: [facts and dates] What I've already tried: [details] What I want: [refund, replacement, repair, apology] Deadline for reply: [days] Keep it factual, polite and firm, with a clear timeline, reference numbers, the resolution req…
Write a firm, polite complaint that gets results, with facts, timeline and the resolution you want.
Give me ways to say no politely. The request: [describe] From: [boss, colleague, friend, family, client] Whether I want to offer an alternative: [yes / no] Write 5 versions: firm, warm, with an alternative, 'not now', and a written message. Add tips for not over-explaining and handling persistent requests.
Decline requests, invitations and extra work gracefully without over-explaining.