MIRENA prompt library
Every prompt category. Every prompt type. One clean directory.
Browse the page that owns the prompt set you need. The library indexes the sources without copying hundreds of prompts into one crowded page.
The ten core workbenches contain 453 verified controls. Full-process, generator, template, and specialist prompts remain on their own source pages.
Choose the part of the prompt system that owns the work.
Categories keep the library compact. Each card filters the directory to the source pages that belong to that operating layer.
Core prompt libraries
Large, searchable workbenches that hold the 453 verified MIRENA controls.
View source pages →Team and business-model workflows
Full-process master prompts shaped around a team, operating model, site type, or commercial structure.
View source pages →Project workflow prompts
Master prompts for a defined project such as routing, restructuring, refreshing, drafting, or rewriting.
View source pages →Generators and audit tools
Focused interfaces that build or audit a brief, rewrite, link map, entity map, result-format plan, or semantic page.
View source pages →Templates and specialist prompt pages
Reusable structures and narrow master prompts for specialist production and identity work.
View source pages →Use the prompt shape that matches the size of the decision.
A large workbench contains many controls. A master prompt carries a complete process. A generator, audit, template, or specialist page owns a narrower production job.
Multi-prompt library
Large workflow pages with searchable modules, master packs, single controls, return fields, guardrails, and route rules.
Full-process master prompt
A complete process adjusted for a team, operating model, site type, or commercial structure.
Project workflow prompt
A complete route for a defined project such as a restructure, refresh, workflow decision, or page repair.
Generator or audit tool
A focused interface that produces or reviews one controlled output before routing the next step.
Template or specialist prompt
A reusable structure or narrow plan for a specialist production task.
Search the page directory, then open the prompt at its source.
This is a route library, not a duplicate prompt archive. Every result links to the page that owns the prompt, controls, examples, fields, and current maintenance state.
Source Context and Project Control
Set site purpose, audience, offer, topic boundaries, protected pages, proof sources, project state, and the next safe route.
Evidence Intake and Data Readiness
Review files, exports, crawls, analytics, behavior notes, old outputs, risks, missing fields, and handoff readiness.
Workflow Routing and Module Selection
Classify the request, check readiness, choose one owning workflow, select the smallest module, and return a gated handoff.
Raw Semantic Discovery
Collect and qualify entities, concepts, modifiers, query paths, competitor evidence, consensus, divergence, and accepted findings.
Topical Mapping and Site Architecture
Assign page ownership, roles, clusters, hierarchy, page-versus-section decisions, overlap controls, routes, and build order.
Behavioral Mapping and User Path
Add user state, journey stage, friction, trust, effort, next steps, fallback routes, testing, and monitoring.
Content Brief Workflow
Turn an approved page decision into writer-ready blocks, evidence, answer forms, links, exclusions, QA, approval, and handoff.
Drafting and Rewriting Workflow
Draft from an approved brief or repair an existing page while preserving purpose, evidence, page role, links, and approval.
Entity SEO and Salience
Define identity, hierarchy, attributes, relationships, placement, salience, support pages, conflicts, and later markup cues.
Information Gain
Keep useful baseline coverage, remove weak repetition, find missing answers and proof, score sections, and route repairs.
Content Design Teams
Connect user tasks, page roles, content blocks, components, proof, routes, and review ownership.
Editorial Leads
Control briefs, drafts, revision reasons, evidence, approvals, page ownership, and publish handoffs.
MIRENA for B2B Software
Connect product, feature, use-case, industry, integration, comparison, documentation, pricing, and proof pages.
MIRENA for B2B Services
Connect service scope, buyer fit, process, proof, comparisons, expertise, and contact routes.
MIRENA for Ecommerce Categories
Map category, subcategory, attribute, brand, buying-guide, comparison, product, and support routes.
Multi-Location Sites
Separate core service-location pages from shared support assets while controlling overlap, proof, and maintenance.
Ecommerce Teams
Coordinate category planning, buying support, refresh work, internal routes, approvals, and maintenance.
Local Service Brands
Connect service pages, location pages, proof, policies, support content, contact actions, and maintenance.
SaaS Teams
Run the complete process across product, docs, use cases, comparisons, integrations, proof, and buyer routes.
Publishers
Govern topic hubs, archives, refresh queues, editorial routes, evidence, ownership, and maintenance.
Consultants
Turn diagnosis into client-ready decisions, briefs, repair queues, evidence, owners, and implementation handoffs.
Startups
Build the first search system without locking weak page, proof, and architecture choices into fast growth.
Solo Operators
Run the complete process with explicit checkpoints, small batches, evidence gates, and no hidden team dependencies.
In-House Teams
Carry approved site and page decisions through stakeholders, production, review, release, measurement, and maintenance.
Agencies
Preserve client context, evidence, scope, production roles, approvals, delivery boundaries, and implementation handoffs.
Site Restructure Workflows
Decide the future home and action for affected pages while preserving value, routes, redirects, and migration requirements.
Content Refresh Workflows
Decide what to keep, remove, merge, move, rebuild, prove, link, or hold before copy changes.
MIRENA Workflow Router
Choose the workflow that owns the first real decision before any production begins.
Drafting and Rewriting
Rebuild a draft or live page around answer clarity, entity support, useful detail, retrieval, and internal routes.
Content Brief Generator
Build a writer-ready brief from page role, intent, entities, evidence, answer forms, links, exclusions, and approval.
SEO Rewrite Generator
Diagnose intent, ownership, structure, repetition, proof, entities, and links before choosing a rewrite boundary.
Internal Link Map Generator
Map source pages, destinations, relationships, user states, anchors, route roles, priorities, and owners.
Information Gain Audit
Separate baseline from repetition, find missing answers and proof, and assign a repair action and owner.
Entity Map Generator
Map primary, supporting, and relational entities, attributes, page ownership, routes, and later schema cues.
SERP Feature Brief Generator
Turn observed result formats into page-specific paragraph, list, table, FAQ, and PAA writing instructions.
Semantic Content Optimizer
Diagnose page purpose, entity coverage, drift, overlap, links, answer formats, and information gain before changing copy.
SEO Content Brief Template
Copy a complete content-brief structure covering page basics, job, intent, queries, entities, proof, links, exclusions, QA, and approval.
Person and Profile Page Identity Plan
Plan person identity, profile-page evidence, visible support, identifiers, schema timing, validation, and handoff.
Internal Links for Refresh Projects
Review and repair incoming links, outgoing links, anchors, page role, cluster position, and the next route during a refresh.
No source pages match those filters.
Directory rule
The hub indexes prompts. The source page owns the prompt.
Counts, controls, guardrails, copy actions, templates, and workflow notes stay on the page responsible for them. This keeps the hub fast, readable, maintainable, and useful as the library grows.
Next route
Open the page that owns the decision.
Start with source context when the project boundary is missing, evidence intake when the inputs are unclear, or workflow routing when the project is ready but the next module is not.