prompt-factory

Prompt Factory - World-Class Prompt Powerhouse

A comprehensive system for generating world-class, production-ready prompts in one shot, eliminating the need for iteration.

---

⚠️ CRITICAL CONSTRAINTS - READ FIRST

This skill generates PROMPTS only. It does NOT implement the work described in the prompt.

What This Skill DOES:

✅ Generate a comprehensive PROMPT (text document in chosen format) ✅ Ask 5-7 questions to understand requirements (MANDATORY - no skipping) ✅ Validate prompt quality before delivery ✅ Output a SINGLE prompt document with token count ✅ Provide the prompt ready to copy and use elsewhere

What This Skill DOES NOT DO:

❌ Implement the actual work (no code files, no diagrams, no APIs) ❌ Create architectural diagrams or technical implementations ❌ Write actual marketing campaigns or business strategies ❌ Build infrastructure or deploy anything ❌ Create multiple files or deliverables ❌ Execute the prompt after generating it

Expected Workflow:

1. User asks for help creating a prompt
2. Skill MUST ask 5-7 questions (even if context seems obvious)
3. User answers questions with specific details
4. Skill generates ONE comprehensive prompt document
5. Skill announces token count (e.g., "Generated prompt: 4,200 tokens")
6. STOP - Do not implement anything from the prompt
7. Ask: "Would you like me to modify the prompt or create a variation?"

Why This Matters:

• Prevents scope creep: You're making a prompt, not doing the work
• Saves context: One prompt document vs. dozens of implementation files
• Clear deliverable: User gets a prompt to use with any LLM
• Reusability: The prompt can be used multiple times

If user says "now implement this": Clarify they should use the generated prompt with a fresh conversation or different tool, as this skill only creates prompts.

---

Overview

Transform any requirement into an optimized mega-prompt through:

1. Mandatory 5-7 question flow (MUST ask, even if context obvious) with example answers
2. 69 comprehensive presets across 15 professional domains (technical, business, creative, legal, finance, HR, design, customer, executive, manufacturing, R&D, regulatory, specialized-technical, research, creative-media, specialized)
3. Multi-format output (XML/Claude/ChatGPT/Gemini)
4. 7-point quality validation before delivery
5. Contextual best practices from OpenAI, Anthropic, Google
6. Core & Advanced modes for different needs
7. Complete coverage of role × industry × task combinations

---

Relationship to PROMPTS_FACTORY_PROMPT.md

This skill works alongside the meta-prompt template:

• prompt-factory skill (this file): Generates individual mega-prompts for specific roles using 69 presets

  • Use when: You need a single prompt for a common role (e.g., "Product Manager", "Full-Stack Engineer")
  • Output: One ready-to-use mega-prompt (~4-12K tokens)
  • Example: "Create a prompt for a Growth Hacker in B2B SaaS" → generates one prompt

• PROMPTS_FACTORY_PROMPT.md: Meta-prompt that generates domain-specific prompt builders

  • Use when: You want to create a new prompt generation system for a specific domain (e.g., Healthcare, FinTech, Legal)
  • Output: A complete prompt builder with 10-20 role presets for that domain
  • Example: "Generate a FinTech Prompt Builder" → creates a system with 10-20 FinTech role presets
  • Location: documentation/templates/PROMPTS_FACTORY_PROMPT.md

Quick Decision:

• Need one prompt now? → Use this skill (prompt-factory)
• Building a prompt system for a new domain? → Use PROMPTS_FACTORY_PROMPT.md

---

Quick Start: Choose Your Path

Path 1: Quick-Start Preset (Fastest)

Use when: You need a prompt for a common role

1. User says: "I need a prompt for [preset name]"
2. Show matching preset with customizable variables
3. Customize (optional) → Generate → Deliver

Available Presets (69 total across 15 domains):

Technical (8): Full-Stack Engineer, DevOps Engineer, Mobile Engineer, Data Scientist, Security Engineer, Cloud Architect, Database Engineer, QA Engineer

Business (8): Product Manager, Product Engineer, Product Owner, Project Manager, Operations Manager, Sales & Business Manager, Business Analyst, Marketing Manager

Legal & Compliance (4): Legal Counsel, Compliance Officer, Contract Manager, Regulatory Affairs Specialist

Finance & Accounting (4): Financial Analyst, CFO/Controller, Accountant/Tax Specialist, Investment Analyst

Human Resources (4): HR Manager, Talent Acquisition Specialist, Learning & Development Manager, Compensation & Benefits Analyst

Design (4): UI/UX Designer, Graphic Designer, Brand Designer, Product Designer

Customer-Facing (4): Customer Success Manager, Support Engineer, Account Manager, Customer Experience Manager

Executive Leadership (7): CEO/Founder, CTO/VP Engineering, Chief Strategy Officer, General Manager, Chief Product Officer, Chief Marketing Officer, Chief Operations Officer

Specialized Technical (6): Machine Learning Engineer, Blockchain Developer, Game Developer, Embedded Systems Engineer, Network Engineer, Site Reliability Engineer (SRE)

Research & Analysis (3): Research Scientist, Quantitative Analyst, Market Researcher

Creative & Media (4): Copywriter, Social Media Manager, SEO Specialist, Video Producer

Manufacturing (4): Manufacturing Engineer, Supply Chain Manager, Quality Engineer (Physical Products), Industrial Designer

R&D - Research & Development (2): Clinical Specialist (PhD-level), Senior AI R&D Expert

Regulatory Affairs (1): Quality Management Responsible Person (ISO 13485, MDR, ISO 27001)

Specialized (1): AEO Specialist (Answer Engine Optimization for LLMs)

Path 2: Custom Prompt (5-7 Questions - MANDATORY)

Use when: Building a unique prompt from scratch

1. Detect intent from user request
2. MUST ask 5-7 questions with example answers (no skipping allowed)
3. Generate with contextual best practices
4. Validate quality → Deliver

Note: Even if the request seems clear (e.g., "product manager PRD prompt"), you MUST still ask questions to gather specifics, validate assumptions, and ensure a high-quality output.

---

Workflow: Custom Prompt Generation

Step 1: Intent Detection & Context Inference

Analyze user's request for trigger keywords:

Role Triggers:

• Technical: "engineer", "developer", "architect", "DevOps", "backend", "frontend", "full-stack", "ML", "data scientist"
• Business: "manager", "strategist", "analyst", "consultant", "executive", "director", "VP"
• Creative: "designer", "writer", "content", "UX", "brand", "marketing"
• Specialized: "healthcare", "fintech", "legal", "education", "security"

Task Triggers:

• Build: "create", "build", "develop", "implement", "code", "write"
• Analyze: "analyze", "review", "evaluate", "assess", "audit", "research"
• Optimize: "optimize", "improve", "refactor", "enhance", "fix"
• Plan: "strategy", "plan", "roadmap", "architecture", "design"

Output Triggers:

• "code", "documentation", "strategy", "analysis", "plan", "design", "report"

Infer from context:

• Primary role
• Domain/industry
• Task complexity (basic/intermediate/advanced/expert)
• Output type
• Technical depth needed

Step 2: Smart 7-Question Flow

MANDATORY: You MUST ask questions before generating any prompt.

Questioning Rules:

• MINIMUM: Ask at least 5 questions (even if context seems clear)
• MAXIMUM: Ask up to 7 questions (skip only truly redundant ones)
• Always ask for CONFIRMATION of inferred details, don't just assume
• Purpose: Validate assumptions, gather specifics, ensure quality output

When to skip a question:

• ✅ ONLY if user explicitly provided that exact detail in their request
• ✅ Example: User says "React 18 with TypeScript" → skip tech stack question

When to ask even if you think you know:

• ✅ ALWAYS ask for domain/industry context (gets specifics)
• ✅ ALWAYS ask for constraints (budget, timeline, team size)
• ✅ ALWAYS ask for success criteria (measurable outcomes)
• ✅ Ask for confirmation: "I'm inferring [X], is that correct?"

Question Bank (Select 5-7):

Category 1: Role & Domain (Ask 2 max)

Q1: What role should the AI assume? Examples:

• "Senior Backend Engineer"
• "Marketing Growth Strategist"
• "Data Analyst"
• "Product Manager"
• "UX Designer"

Your answer: ___

Q2: What domain or industry context? Examples:

• "FinTech / Payment Processing"
• "Healthcare SaaS"
• "E-commerce Platform"
• "B2B Marketing Agency"
• "Mobile Gaming"

Your answer: ___

Category 2: Use Case & Output (Ask 2)

Q3: What is the primary task or goal? Examples:

• "Build REST APIs for payment processing"
• "Create content marketing strategies"
• "Analyze user behavior data"
• "Design mobile app interfaces"
• "Optimize database performance"

Your answer: ___

Q4: What output format do you need? Options:

• code - Implementation code with tests
• documentation - Technical/user docs
• strategy - Strategic plans/roadmaps
• analysis - Data analysis/insights
• design - UI/UX designs
• plan - Project/implementation plans

Your answer: ___

Category 3: Context & Constraints (Ask 1-2)

Q5: Tech stack, tools, or methodologies to use/follow? Examples:

• "Python, FastAPI, PostgreSQL, AWS"
• "React, TypeScript, Next.js"
• "Agile/Scrum methodology"
• "SEO best practices, Google Analytics"
• "Figma, Design Systems, WCAG 2.1"

Your answer: ___

Q6: Any critical constraints or requirements? Examples:

• "HIPAA compliant, healthcare regulations"
• "Budget < $10k, 2-week timeline"
• "Must support 10k+ concurrent users"
• "PCI-DSS compliance for payments"
• "Mobile-first, accessibility AA"

Your answer: ___

Category 4: Style & Format (Ask 1-2)

Q7: Communication style and response format? Options:

• Tone: Professional

---

Content truncated.