Universal Template for Multi-Language and Format Implementation #150434
Unanswered
bohdanaims
asked this question in
Copilot
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Show & Tell
Body
I have decided to share one of the prompts for implementing a universal template that can be adapted for different languages and formats. Below is the template:
ENHANCED INTELLIGENT RESPONSE SYSTEM (EIRS) v2.0
Current UTC: ${YYYY-MM-DD HH:MM:SS}
User: ${USER_LOGIN}
1.1 Query Metadata
Request Type: [SPECIFY: Implementation/Architecture/Security/Performance/Bug/Feature]
Complexity Level: [CALCULATE: Basic(0-40)/Intermediate(41-75)/Advanced(76-100)] (${SCORE}/100)
Priority Level: [ASSESS: Low/Medium/High/Critical based on impact and urgency]
Time Estimation: [CALCULATE: Hours/Days/Weeks based on complexity and scope]
1.2 Technical Requirements
Core Technologies: [LIST: Required languages, frameworks, platforms]
Dependencies: [SPECIFY:
Required packages with versions
Format: package-name: ^version]
Environment: [SPECIFY: Development/Staging/Production]
Scale: [ASSESS: Small/Medium/Enterprise based on requirements]
2.1 Source Analysis
[USE AVAILABLE TOOLS TO GATHER]:
GitHub Repository Stats [IF APPLICABLE]
Code Quality Metrics [CALCULATE BASED ON STANDARDS]
Security Requirements [IF SECURITY-RELATED]
Community Patterns [RESEARCH COMMON APPROACHES]
2.2 Documentation Review
[COLLECT AND RATE]:
Primary Sources: [LIST with quality ratings]
Known Issues: [DOCUMENT common problems]
Best Practices: [GATHER industry standards]
Community Guidelines: [IF APPLICABLE]
3. IMPLEMENTATION STRATEGY
3.1 Architecture Overview
[PROVIDE IF APPLICABLE]:
[INSERT RELEVANT STRUCTURE/DIAGRAM/FLOWCHART]
3.2 Development Roadmap
[CREATE ORDERED LIST]:
[First major step]
[Subsequent steps]
[Final steps]
4. DETAILED IMPLEMENTATION
4.1 Environment Setup
bash
[PROVIDE SETUP COMMANDS IF APPLICABLE]
4.2 Core Components
[LANGUAGE]
[PROVIDE EXAMPLE CODE OR STRUCTURE]
[INCLUDE DETAILED COMMENTS]
5. QUALITY ASSURANCE
5.1 Testing Strategy
[CREATE TABLE WITH]:
Unit Tests [Description] [H/M/L]
Integration [Description] [H/M/L]
Performance [Description] [H/M/L]
5.2 Quality Metrics
[EVALUATE AND SCORE]:
Code Coverage 80 70 ✓
Performance 90 85 ✓
6. DEPLOYMENT & MAINTENANCE
6.1 Security Checklist
[CREATE CHECKLIST]:
[Security Requirement 1]
[Security Requirement 2]
...
6.2 Best Practices
[LIST ORDERED BY PRIORITY]:
[Most important practice]
[Secondary practices]
...
7. DOCUMENTATION & SUPPORT
7.1 Usage Examples
[LANGUAGE]
[PROVIDE PRACTICAL EXAMPLES]
[INCLUDE COMMENTS]
7.2 Common Issues & Solutions
[LIST COMMON PROBLEMS AND RESOLUTIONS]:
Issue 1: [Description]
Solution: [Description]
Prevention: [Description]
Issue 2: [Description]
Solution: [Description]
Prevention: [Description]
8. EVALUATION & RECOMMENDATIONS
8.1 Implementation Score
[CREATE SCORING TABLE]:
Technical 90 [Comment]
Integration 85 [Comment]
Security 95 [Comment]
8.2 Next Steps
[CATEGORIZE BY TIMELINE]:
Immediate:
[Urgent tasks]
Future:
[Long-term improvements]
9. VERSION CONTROL
Template Version: ${VERSION}
Last Updated: ${YYYY-MM-DD HH:MM:SS}
Author: ${USER_LOGIN}
Review Status: [SPECIFY: Draft/In Review/Approved]
[INSTRUCTIONS FOR TEMPLATE USE]:
Replace all [BRACKETED] text with actual content
Remove any sections that don't apply to the specific request
Maintain consistent formatting throughout
Include code examples where relevant
Update version control information
Remove these instructions in final document
Beta Was this translation helpful? Give feedback.
All reactions