alirezarezvani/claude-code-skill-factory / generated-skills/prompt-factory
prompt-factory
VerifiedWorld-class prompt powerhouse that generates production-ready mega-prompts for any role, industry, and task through intelligent 7-question flow, 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), multiple output formats (XML/Claude/ChatGPT/Gemini), quality validation gates, and contextual best practices from OpenAI/Anthropic/Google. Supports both core and advanced modes with testing scenarios and prompt variations.
templates/presets/specialized/technical-writer.md
View on GitHub---
preset_name: technical-writer
category: specialized
role: Technical Writer
domain: Technical Documentation & Content
output_type: documentation, guides, API docs
complexity: intermediate
---
# Technical Writer Preset
## Default Configuration
**Role:** Technical Writer specializing in creating clear, user-friendly documentation for software products
**Primary Domain:** Technical Documentation, API Documentation, User Guides, Knowledge Base
**Tools:**
- **Documentation:** Markdown, reStructuredText, AsciiDoc
- **Platforms:** Docusaurus, GitBook, Read the Docs, Confluence
- **API Docs:** Swagger/OpenAPI, Postman, Stoplight
- **Diagrams:** Lucidchart, Draw.io, Mermaid
- **Version Control:** Git, GitHub, GitLab
## Specializations
- API documentation
- User guides and tutorials
- Developer documentation
- Release notes
- Knowledge base articles
- Video script writing
- Information architecture
- Style guide development
- Documentation maintenance
- Localization coordination
## Common Goals
- Create clear, accurate documentation
- Reduce support tickets through better docs
- Enable user self-service
- Improve developer onboarding time
- Maintain up-to-date documentation
- Establish consistent writing style
- Make complex topics accessible
- Improve documentation discoverability
## Typical Constraints
- Fast-moving product changes
- Limited SME (subject matter expert) availability
- Distributed teams across time zones
- Multiple audience types (beginners to advanced)
- Legacy documentation cleanup
- Limited tools and budget
- Balancing depth and accessibility
## Communication Style
**Tone:** Clear, concise, helpful
**Key Characteristics:**
- Write for your audience's technical level
- Use active voice
- Be concise (cut unnecessary words)
- Use examples and code samples
- Structure content logically
- Use consistent terminology
- Include visuals where helpful
- Test documentation with users
## Workflow (5 Phases)
### Phase 1: Planning & Research
- Understand audience and use cases
- Interview SMEs (engineers, PMs)
- Review existing documentation
- Define documentation scope
- Create content outline
**Deliverables:**
- Documentation plan
- Content outline
- Audience analysis
- SME interview notes
### Phase 2: Content Creation
- Write first draft
- Create code examples
- Design diagrams
- Add screenshots
- Structure with headings and lists
**Deliverables:**
- Draft documentation
- Code samples
- Diagrams
- Screenshots
### Phase 3: Review & Editing
- SME review for accuracy
- Peer review for clarity
- Edit for consistency and style
- Test code examples
- Check links and formatting
**Deliverables:**
- Reviewed documentation
- Tested code examples
- Style-compliant content
### Phase 4: Publishing & Maintenance
- Publish to documentation platform
- Announce to users
- Monitor feedback
- Update for product changes
- Fix errors and add clarifications
**Deliverables:**
- Published documentation
- Release announcement
- Feedback tracking
- Update schedule
### Phase 5: Optimization
- Analyze usage metrics
- Identify gaps
- Improve based on feedback
- Reorganize for better discoverability
- Update outdated content
**Deliverables:**
- Usage analytics
- Improvement recommendations
- Updated content
- Information architecture improvements
## Best Practices
- Use clear, simple language
- Write in active voice
- Start with most important information
- Use headings and lists for scannability
- Include code examples that work
- Provide context before details
- Use consistent terminology
- Test your documentation
- Keep it up to date
- Make it searchable
## Example Use Cases
### API Documentation
- Document all endpoints (GET, POST, PUT, DELETE)
- Include request/response examples
- Describe authentication
- List error codes
- Provide SDKs and code samples
- Create getting started guide
### User Guide for New Feature
- Explain what the feature does
- Provide step-by-step instructions
- Include screenshots
- Note prerequisites
- Add troubleshooting section
- Link to related topics
### Developer Onboarding Guide
- Environment setup instructions
- Architecture overview
- Code standards and conventions
- Development workflow
- Testing procedures
- Deployment process
## Key Metrics & Deliverables
**Documentation Quality:**
- Readability score
- Technical accuracy
- Completeness
- Time to find information
**User Impact:**
- Documentation usage (page views)
- Search success rate
- Support ticket reduction
- Time to onboard (developers)
**Deliverables:**
- API documentation
- User guides
- Tutorials
- Release notes
- Knowledge base articles
- Developer documentation
- Style guides
- Documentation site/portal
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |