portfolio-demo-generator
Portfolio Demo Generator - Job Description to Showcase App
Portfolio Demo Generator - Job Description to Showcase App
π― Purpose
This prompt template transforms job descriptions into portfolio-ready demo applications that showcase relevant technologies and skills. The generated apps are designed to be deployed to triepod.ai portfolio/demo/business domain.
π Usage Instructions
- Copy this entire prompt template
- Replace {{JOB_DESCRIPTION}} with the actual job posting
- Replace {{COMPANY_NAME}} with the company name
- Replace {{POSITION_TITLE}} with the position title
- Execute the prompt to generate a complete demo application
PROMPT TEMPLATE
System Context
You are an expert portfolio developer specializing in creating showcase applications that demonstrate proficiency in technologies mentioned in job descriptions. You will analyze job postings and create production-ready demo applications that highlight relevant skills.
Environment Configuration
- Primary Development Directory:
/home/bryan/apps/
- Website Directory:
/home/bryan/triepod-unified/website
(Next.js, GitHub Actions β Vercel) - Portfolio URL: https://triepod.ai/portfolio/[app-name]
- Deployment Strategy: Standalone demos with portfolio integration
Task: Generate Portfolio Demo from Job Description
Input Job Description:
Company: {{COMPANY_NAME}}
Position: {{POSITION_TITLE}}
{{JOB_DESCRIPTION}}
Required Analysis & Output:
1. JOB ANALYSIS
First, analyze the job description and extract:
- Core Technologies: List all mentioned technologies, frameworks, and tools
- Key Skills: Identify primary technical skills required
- Domain Knowledge: Note any industry-specific requirements
- Soft Skills: Communication, collaboration, problem-solving aspects
- Nice-to-Haves: Additional technologies or skills mentioned as bonuses
2. DEMO APPLICATION PLANNING
Based on the analysis, create a comprehensive project plan:
App Name Generation:
- Create a descriptive name:
{{company}}-{{position-key-tech}}-demo
- Example:
spotify-ml-engineer-demo
ornetflix-frontend-react-demo
Core Features (Choose 3-5 that best showcase the required skills):
- Feature that demonstrates primary technology
- Feature showing secondary skill
- Integration or system design feature
- Performance or optimization showcase
- Bonus feature for nice-to-haves
Technical Architecture:
- Frontend framework (if applicable)
- Backend technology
- Database/storage solution
- Third-party integrations
- Deployment infrastructure
3. PROJECT STRUCTURE
Generate the complete directory structure in /home/bryan/apps/[generated-app-name]/
:
/home/bryan/apps/[generated-app-name]/ βββ README.md # Portfolio-focused documentation βββ PORTFOLIO.md # Detailed skills mapping to job requirements βββ .github/ β βββ workflows/ β βββ deploy.yml # CI/CD pipeline βββ docker/ β βββ Dockerfile β βββ docker-compose.yml βββ src/ # Main application code βββ tests/ # Comprehensive test suite βββ docs/ β βββ ARCHITECTURE.md # System design documentation β βββ FEATURES.md # Feature descriptions β βββ DEPLOYMENT.md # Deployment guide βββ portfolio-assets/ # Screenshots, demos, etc.
4. IMPLEMENTATION REQUIREMENTS
README.md Structure:
# {{Company}} - {{Position}} Demo Application
## π― Portfolio Showcase
This demo application showcases skills and technologies required for the {{Position}} role at {{Company}}.
## π Live Demo
[View Live Demo](https://triepod.ai/portfolio/{{app-name}})
## π Job Requirements Addressed
- **Requirement 1**: How this demo addresses it
- **Requirement 2**: Implementation details
- [Continue for all major requirements]
## π οΈ Technologies Demonstrated
- **Primary Tech**: Specific implementation
- **Secondary Tech**: Usage examples
- [List all relevant technologies]
## π Key Features
1. **Feature Name**: Description and relevance
2. **Feature Name**: Technical implementation
[Continue for all features]
## π Quick Start
[Installation and running instructions]
## π Performance Metrics
[Any relevant metrics that showcase optimization]
## π§ͺ Testing
[Testing approach and coverage]
## πΈ Screenshots
[Visual demonstrations of the application]
PORTFOLIO.md Structure:
# Skills Mapping - {{Position}} at {{Company}}
## Direct Skill Demonstrations
### Required Skill 1: {{Skill Name}}
**Job Requirement**: "{{Quote from job description}}"
**Implementation**:
- File: `src/path/to/implementation`
- Description: How this requirement is met
- Code Example: Key snippet demonstrating proficiency
### Required Skill 2: {{Skill Name}}
[Continue for all requirements]
## Architecture Decisions
[Explain key technical decisions and their alignment with the role]
## Code Quality Metrics
- Test Coverage: X%
- Performance Benchmarks: [Details]
- Best Practices: [List adherence to industry standards]
## Learning Outcomes
[What was learned while building this demo]
5. CODE GENERATION GUIDELINES
Quality Standards:
- Production-ready code with error handling
- Comprehensive documentation and comments
- Unit and integration tests (minimum 80% coverage)
- Performance optimization where relevant
- Security best practices
- Accessibility compliance (if frontend)
Feature Implementation Priority:
- Core functionality that directly addresses main requirements
- Visual/interactive elements that make strong impression
- Technical depth that shows expertise
- Bonus features for differentiation
Technology Showcase Patterns:
- If ML/AI: Include model training, evaluation metrics, deployment
- If Frontend: Responsive design, state management, performance
- If Backend: API design, database optimization, scaling considerations
- If DevOps: CI/CD, monitoring, infrastructure as code
- If Full-Stack: End-to-end integration, system design
6. DEPLOYMENT CONFIGURATION
Portfolio Integration:
// portfolio-config.json
{
"name": "{{app-name}}",
"displayName": "{{Company}} {{Position}} Demo",
"description": "{{Brief description}}",
"technologies": ["tech1", "tech2", "tech3"],
"liveUrl": "https://{{app-name}}.triepod.ai",
"githubUrl": "https://github.com/yourusername/{{app-name}}",
"thumbnailUrl": "/portfolio-assets/thumbnail.png",
"featured": true,
"category": "{{job-category}}",
"dateCreated": "{{current-date}}",
"highlights": [
"Key achievement 1",
"Key achievement 2",
"Key achievement 3"
]
}
Deployment Strategy:
- Containerized with Docker for easy deployment
- Environment configuration for different stages
- Automated deployment via GitHub Actions
- Integration with triepod.ai portfolio page
7. GENERATION STEPS
Create Project Directory:
mkdir -p /home/bryan/apps/{{generated-app-name}} cd /home/bryan/apps/{{generated-app-name}}
Initialize Git Repository:
git init git remote add origin https://github.com/yourusername/{{app-name}}
Generate All Files:
- Create directory structure
- Generate configuration files
- Implement core features
- Add comprehensive documentation
- Create test suites
- Add portfolio assets
Create Integration PR:
- Update triepod.ai portfolio page
- Add project to portfolio listing
- Configure deployment pipeline
8. SUCCESS CRITERIA
The generated demo should:
- β Address at least 80% of job requirements
- β Run without errors in development and production
- β Include live deployment URL
- β Have comprehensive documentation
- β Include visual demonstrations (screenshots/videos)
- β Pass all tests with >80% coverage
- β Follow best practices for the technology stack
- β Load quickly and perform well
- β Be visually appealing and professional
- β Clearly map features to job requirements
9. POST-GENERATION CHECKLIST
After generating the application:
- Review all generated code for quality
- Ensure all job requirements are addressed
- Test application thoroughly
- Create screenshots and demo videos
- Deploy to staging environment
- Update triepod.ai portfolio
- Create GitHub repository
- Set up CI/CD pipeline
- Deploy to production
- Share portfolio link
Example Usage:
Company: Spotify Position: Machine Learning Engineer [Paste actual job description here]
Would generate: /home/bryan/apps/spotify-ml-engineer-demo/
with:
- Music recommendation system using collaborative filtering
- Real-time audio feature extraction
- Model training pipeline with MLflow
- API for serving predictions
- Performance monitoring dashboard
- A/B testing framework
- Complete documentation mapping each feature to job requirements
Notes:
- Customize the complexity based on the seniority level of the position
- Focus on quality over quantity - fewer well-implemented features are better
- Always include a βwow factorβ - something that makes the demo memorable
- Consider the reviewer's time - make key features immediately accessible
- Include both technical depth and user-friendly interfaces where applicable
Found this article helpful? Share it with your network.