Authentication Strategy Prompt
Choose how users prove who they are — sessions vs tokens, passwords vs passwordless, SSO and MFA — decided on your real constraints, not the default tutorial.
Prompt Builders
Turn "act as a product manager" into a role the AI can actually inhabit — with the perspective, responsibilities, and decision criteria a real expert brings. Pick a role, set the level and style, and generate.
Who should the AI act as? A title, not a description — e.g. "Product Manager", "Technical Recruiter".
Recognized roles offer focus areas — selected ones get extra weight in the prompt.
Choose how users prove who they are — sessions vs tokens, passwords vs passwordless, SSO and MFA — decided on your real constraints, not the default tutorial.
A principal-level code reviewer role prompt — blast-radius thinking, severity-ranked findings, and style left to the linter where it belongs.
Make AI act as a copywriter that sells — clarity over cleverness, benefit-first, one clear action — instead of producing flat, generic marketing text.
A CSM role prompt built on leading indicators — churn is decided months before the cancellation, adoption beats satisfaction, renewals are earned in the boring quarters.
A data analyst role prompt with statistical honesty built in — clarify the decision first, treat correlation as a hypothesis, and never launder uncertainty into precision.
Make AI act as a DevOps engineer — CI/CD, infrastructure as code, observability, and reliability — instead of a generic assistant.
A marketing strategist role prompt that thinks positioning-first — channel saturation curves, attribution honesty, and one testable angle per recommendation.
Keep tenants out of each other's data — design the isolation model, the tenant-scoping rule every query must obey, and the cross-tenant leaks to test for.
An operations manager role prompt that thinks in flows — map the actual process, find the constraint that matters, and never automate a bad process into a faster bad process.
A complete 'act as a product manager' role prompt — the perspective, responsibilities, and decision criteria a real PM brings, not just the job title.
Make AI act as a QA engineer — test strategy, edge cases, regression prevention, and validation — instead of an assistant that writes happy-path tests.
An expert sales consultant role prompt — qualification-first, discovery-before-pitch, with exact phrasings and the situations where each technique backfires.
Make AI act as a security engineer — threat modeling, secure design, risk assessment, and defensive recommendations — instead of a generic assistant.
Make AI act as a software architect — system design, scalability, service boundaries, and trade-offs — instead of jumping straight to code.
Make AI act as a software engineer — design, implementation, and testing trade-offs — instead of a generic assistant that writes whatever you ask.
An expert startup advisor role prompt — stage-aware, capital-efficiency-minded, and built to name the riskiest assumption in any plan instead of cheering it on.
A technical recruiter role prompt that evaluates hiring quality at month six — screening design, evidence-based assessment, and bias flags built in.
Make AI act as a tutor that actually teaches — plain language first, understanding checks, building from what you know — not a wall of dense explanation.
A UX researcher role prompt that respects evidence — observation over opinion, sample-size honesty, and findings that name their own limitations.
Design a system's architecture on its real trade-offs instead of a confident diagram — put the model in an architect's seat, work the decisions one at a time, and write down the why.
Design an API on its contract instead of discovering it endpoint by endpoint — model the resources, design the endpoints and payloads, pin the contract, then review it before code locks it in.
Design a schema on its data, not a hunch — model the entities and relationships, set the constraints that protect integrity, plan indexes around real queries, then document the schema and migration.
Design access control before you build it, not after a breach — choose the authentication approach, model the roles and permissions, review the design for gaps, then document the identity model.
Connect systems so they don't break each other — map the integration boundaries, design the event and webhook contracts, plan retries and failure handling, then document the integration.
Review code for what an attacker would do, not just what tests catch — anchor the model as a security engineer, run a threat-focused review, then back the findings with auth and input tests.
Cross the gap between 'tests pass' and 'safe in production' — assess release readiness, plan the deploy and its rollback, and set up the monitoring and launch checks before you ship, not after.
Design a system prompt that holds up in production — define the role precisely, engineer the behavior and guardrails on top of it, then check it reads clearly before you ship.
Instruct an AI agent that runs on its own without it wandering off — anchor it to a role, write the agent system prompt, then lay out the multi-step plan it works through.
Find out whether an AI agent behaves before users do — define what correct means, build test scenarios with expected outputs, catch failures and hallucinations, then regression-test each version.
Find out whether the thing you shipped actually worked — define the success metric, plan the measurement, classify the real evidence, then render a verdict and an iterate / pivot / scale decision.
Design a pipeline that moves data without corrupting it — map the sources and ingestion, design the transformation stages, set validation and quality gates, then document the pipeline and monitoring.
Cut a product idea down to the smallest first release that proves the core value — separate the real must-haves from everything that can wait, then define the MVP and its success signal.
Decide what to publish and why before you write a word — set the business goals and audience, map needs to topics, brief the priority pieces, then turn it into a content plan you publish against.
Organize a site so people and crawlers find things — inventory the content, group it into a real hierarchy, design the sitemap and navigation, then document the information architecture for the build.
Write a landing page that converts, not one that just describes — sharpen the value proposition, draft the hero and benefits, answer objections at the CTA, then A/B the variants to pick the stronger.
Structure a UI so it stays consistent as it grows — inventory the screens, break them into reusable components, specify the component system and its rules, then review the structure for drift.
The full path from idea to a shipped SaaS MVP — define and scope the requirements, design the architecture, API, and data model, then build it reviewed, tested, secured, cost-controlled, and deployed.
The full path to an AI document processing system — define the use case, design the intake pipeline, extract fields from unstructured documents, classify and route them, pin the output contract, evaluate accuracy, then ship it monitored.
The full path to a backend you can put clients on — define the requirements, design the architecture, API contract, data model, and access control, then build it reviewed, tested, secured, and shipped.
The full path to a business website that holds together — plan the content, structure the site, design the components, write the page copy, then ship it as one coherent whole.
The full path to a booking and reservation system — model resources, availability, and reservations, design the booking API, set customer accounts, wire calendar and notification integrations, design the UI, review security, then ship.
The full path to a two-sided platform — define the buyer-and-seller requirements, model the data, design the API, build roles and permissions, wire integrations, design the UI, then test, secure, and ship it.
The full path to a CRM that fits your sales process — define the contacts, deals, and pipeline, model the data that ties them together, then build the roles, integrations, and pipeline UI, and ship.
The full path to a store you own end to end — model the catalog and orders, design the storefront and checkout, add customer accounts and payments, then secure it, test it, and ship.
The full path to a pipeline that moves data without corrupting it — design the ingestion and transforms, extract and structure the sources, gate the quality, store it, then deliver and ship it monitored.
Type the role the AI should act as — or pick a preset — then set the experience level, an optional industry, and a working style. Recognized roles unlock focus areas you can multi-select. Click Generate Role Prompt and the generator builds a complete persona from its browser-side role profile system: the perspective that role views problems through, the responsibilities it owns, the decision criteria it weighs, and output expectations that match how that expert actually communicates. Nothing leaves your browser. Unknown roles get an honest scaffold with [bracketed] placeholders instead of invented expertise.
The System Prompt Generator designs how an AI worker should behave — objectives, behavior rules, restrictions, escalation paths — for operational systems like a support agent or bug triage assistant. The Role Prompt Generator answers a smaller, different question: who should the AI act as? It defines an expert persona — perspective, responsibilities, decision criteria — in seconds. Building an AI worker → SPG. Wanting advice from a convincing expert → this tool.
The role profile system. Each recognized role carries researched content: how that role actually thinks (a recruiter evaluates hiring quality at month six, not offer acceptance), what it owns, and what criteria it weighs. That's the difference between a model wearing a name tag and one that reasons in character.
You get the same professional structure with [bracketed] placeholders where the role-specific knowledge belongs — the lenses, responsibilities, and criteria only someone who knows that role can fill in. The generator never fakes expertise it doesn't have.
Eleven, chosen for quality over quantity: Product Manager, Startup Advisor, Technical Recruiter, Senior Code Reviewer, UX Researcher, Marketing Strategist, Sales Consultant, Data Analyst, Customer Success Manager, Operations Manager, and SEO Consultant. Matching is fuzzy — 'PM', 'product owner', and 'tech lead' resolve to the right profiles.
Yes — it changes the instructions, not just the adjective. Junior adds uncertainty-flagging and clarifying questions; Senior adds push-back and second-order effects; Principal adds systems-level reasoning and reversibility awareness; Expert adds first-principles reasoning and explicit opinions.
Absolutely — it's a starting point built to be edited. Copy it, tighten the focus areas, and if you want to strengthen the wording further, run it through the Prompt Rewriter.