Specialist - Domain-Specific Prompt Adaptation
Overview
Specialist adapts prompts for specific domains and industries for PromptForge AI. A prompt that works for general writing won't work for legal contracts, medical summaries, or code review. Specialist ensures prompts are optimized for their specific domain context.
When to Use
- When creating prompts for a specific industry (legal, medical, finance, engineering, etc.)
- When adapting general-purpose prompts for domain-specific use
- When incorporating domain terminology, standards, or regulations into prompts
- When building domain-specific template libraries
- When evaluating whether a prompt is appropriate for a given domain
- Don't use when: Creating general-purpose prompts that work across domains
Core Procedures
Step 1: Analyze Domain Requirements
For each domain:
- Terminology: What specialized terms must the prompt understand and use correctly?
- Standards: What industry standards or frameworks apply? (e.g., HIPAA for healthcare, GAAP for finance)
- Regulations: What legal or compliance requirements affect the output?
- Audience: Who will read the output? (experts, general public, regulators)
- Format: What output formats are standard in this domain?
- Constraints: What must the prompt avoid? (liability, medical advice, etc.)
Step 2: Gather Domain Knowledge
- Domain-specific glossaries and ontologies
- Industry best practices and guidelines
- Regulatory requirements and compliance standards
- Example inputs and outputs from the domain
- Common pitfalls and mistakes in the domain
Step 3: Adapt Prompt Architecture
Modify the base prompt template for the domain:
- Role Definition: Change system role to domain expert (e.g., "You are a senior legal analyst")
- Terminology Injection: Add domain-specific terms and their meanings
- Constraint Addition: Add domain-specific constraints and guardrails
- Format Specification: Change output format to match domain standards
- Example Replacement: Replace generic examples with domain-specific examples
- Validation Criteria: Add domain-specific quality checks
Step 4: Test Domain Adaptation
Step 5: Document Domain Profile
DOMAIN PROFILE
==============
Domain: [industry/field name]
Terminology: [key terms and definitions]
Standards: [applicable standards and frameworks]
Regulations: [compliance requirements]
Audience: [who reads the outputs]
Output Format: [standard format for this domain]
Constraints: [what the prompt must avoid]
Best Practices: [domain-specific prompt tips]
Template Variants: [which templates work best for this domain]
Success Metrics
- Domain adaptation accuracy: >=90% (domain expert approval rate)
- Terminology correctness: >=95% (correct use of domain terms)
- Compliance rate: 100% (no regulatory violations in outputs)
- Domain coverage: >=10 major domains with documented profiles
Error Handling
- Error: Prompt produces outputs that violate domain standards
Response: Add explicit constraint to prompt, re-test with compliance checklist
- Error: Domain terminology used incorrectly
Response: Add terminology gloss to prompt context, provide correct usage examples
- Error: No domain expert available for validation
Response: Use domain documentation and examples as proxy, flag outputs as "unvalidated by expert"
Cross-Team Integration
Related Skills: blueprint-promptforge-template-designer, enhancer-promptforge-advanced-innovation, integrity-promptforge-ethical-ai, compliance-promptforge-regulatory-compliance
Used By: Blueprint, Enhancer, Integrity, Compliance, ALL agents creating domain-specific prompts
1---2name: specialist-promptforge-domain-adaptation3description: Use when adapting prompts for specific industries, domains, or specialized contexts. This skill provides procedures for incorporating domain knowledge, terminology, constraints, and best practices into prompt engineering for domain-specific excellence.4---56# Specialist - Domain-Specific Prompt Adaptation78## Overview9Specialist adapts prompts for specific domains and industries for PromptForge AI. A prompt that works for general writing won't work for legal contracts, medical summaries, or code review. Specialist ensures prompts are optimized for their specific domain context.1011## When to Use12- When creating prompts for a specific industry (legal, medical, finance, engineering, etc.)13- When adapting general-purpose prompts for domain-specific use14- When incorporating domain terminology, standards, or regulations into prompts15- When building domain-specific template libraries16- When evaluating whether a prompt is appropriate for a given domain17- **Don't use when:** Creating general-purpose prompts that work across domains1819## Core Procedures2021### Step 1: Analyze Domain Requirements22For each domain:231. **Terminology:** What specialized terms must the prompt understand and use correctly?242. **Standards:** What industry standards or frameworks apply? (e.g., HIPAA for healthcare, GAAP for finance)253. **Regulations:** What legal or compliance requirements affect the output?264. **Audience:** Who will read the output? (experts, general public, regulators)275. **Format:** What output formats are standard in this domain?286. **Constraints:** What must the prompt avoid? (liability, medical advice, etc.)2930### Step 2: Gather Domain Knowledge31- Domain-specific glossaries and ontologies32- Industry best practices and guidelines33- Regulatory requirements and compliance standards34- Example inputs and outputs from the domain35- Common pitfalls and mistakes in the domain3637### Step 3: Adapt Prompt Architecture38Modify the base prompt template for the domain:39- **Role Definition:** Change system role to domain expert (e.g., "You are a senior legal analyst")40- **Terminology Injection:** Add domain-specific terms and their meanings41- **Constraint Addition:** Add domain-specific constraints and guardrails42- **Format Specification:** Change output format to match domain standards43- **Example Replacement:** Replace generic examples with domain-specific examples44- **Validation Criteria:** Add domain-specific quality checks4546### Step 4: Test Domain Adaptation47- [ ] Test with domain-specific inputs (not generic inputs)48- [ ] Have domain expert review outputs (if available)49- [ ] Check terminology accuracy50- [ ] Verify compliance with domain standards51- [ ] Test edge cases specific to the domain52- [ ] Document domain-specific failure modes5354### Step 5: Document Domain Profile55```56DOMAIN PROFILE57==============58Domain: [industry/field name]59Terminology: [key terms and definitions]60Standards: [applicable standards and frameworks]61Regulations: [compliance requirements]62Audience: [who reads the outputs]63Output Format: [standard format for this domain]64Constraints: [what the prompt must avoid]65Best Practices: [domain-specific prompt tips]66Template Variants: [which templates work best for this domain]67```6869## Success Metrics70- Domain adaptation accuracy: >=90% (domain expert approval rate)71- Terminology correctness: >=95% (correct use of domain terms)72- Compliance rate: 100% (no regulatory violations in outputs)73- Domain coverage: >=10 major domains with documented profiles7475## Error Handling76- **Error:** Prompt produces outputs that violate domain standards77 **Response:** Add explicit constraint to prompt, re-test with compliance checklist78- **Error:** Domain terminology used incorrectly79 **Response:** Add terminology gloss to prompt context, provide correct usage examples80- **Error:** No domain expert available for validation81 **Response:** Use domain documentation and examples as proxy, flag outputs as "unvalidated by expert"8283## Cross-Team Integration84**Related Skills:** blueprint-promptforge-template-designer, enhancer-promptforge-advanced-innovation, integrity-promptforge-ethical-ai, compliance-promptforge-regulatory-compliance85**Used By:** Blueprint, Enhancer, Integrity, Compliance, ALL agents creating domain-specific prompts