Skip to content

Commit 0be42ae

Browse files
kamilstanuchkamilstanuch
committed
Update to version 0.1.33: 10 new prompts added to library
1 parent b1f3b34 commit 0be42ae

13 files changed

+472
-46
lines changed

‎README.md‎

Lines changed: 43 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,4 +97,46 @@ You can use these prompts with various LLM interfaces:
9797
- [Unit Test Generation for Codebase](prompt_library/testing_unit_test_generation.md)
9898
- [Security Vulnerability Analysis of Codebase](prompt_library/security_vulnerability_analysis.md)
9999

100-
For detailed instructions on how to use these prompts, please refer to the individual files in the `prompt_library` directory.
100+
For detailed instructions on how to use these prompts, please refer to the individual files in the `prompt_library` directory.
101+
102+
# Code Analysis Prompt Library
103+
104+
This repository contains a collection of prompts designed to assist in various aspects of code analysis, improvement, and documentation.
105+
106+
## Available Prompts
107+
108+
1. **User Story Reconstruction** (`learning_user_story_reconstruction.md`)
109+
- Reconstruct and structure user stories based on the provided codebase.
110+
111+
2. **Risk Assessment** (`quality_risk_assessment.md`)
112+
- Identify potential risks within the codebase.
113+
114+
3. **Best Practice Analysis** (`improvement_best_practice_analysis.md`)
115+
- Analyze the codebase for good and bad programming practices.
116+
117+
4. **Language Translation** (`improvement_language_translation.md`)
118+
- Translate the codebase from one programming language to another.
119+
120+
5. **Refactoring** (`improvement_refactoring.md`)
121+
- Suggest refactoring improvements for better readability and performance.
122+
123+
6. **Unit Test Generation** (`testing_unit_test_generation.md`)
124+
- Generate unit tests for the provided codebase.
125+
126+
7. **Business Impact Analysis** (`business_impact_analysis.md`)
127+
- Analyze the codebase to identify key features and their potential business impact.
128+
129+
8. **Stakeholder Persona Generation** (`stakeholder_persona_generation.md`)
130+
- Infer potential stakeholder personas based on the functionalities present in the codebase.
131+
132+
## Usage
133+
134+
To use these prompts, select the appropriate prompt file for your analysis needs and follow the instructions provided within each prompt.
135+
136+
## Contributing
137+
138+
Contributions to expand and improve this prompt library are welcome. Please submit a pull request with your suggested changes or additions.
139+
140+
## License
141+
142+
This project is licensed under the MIT License - see the LICENSE file for details.

‎prompt_library/business_impact_analysis.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Codebase Business Impact Analysis
2+
3+
**Objective:** Analyze the codebase to identify key features and their potential business impact.
4+
5+
**Instructions:**
6+
7+
1. Review the codebase and identify major features or functionalities.
8+
2. For each feature, analyze its potential business impact:
9+
* Revenue generation potential
10+
* Cost-saving opportunities
11+
* Customer satisfaction improvements
12+
* Competitive advantage
13+
3. Prioritize features based on their estimated business value.
14+
4. Suggest potential enhancements or new features that could increase business value.
15+
16+
**Expected Output:** A report detailing the business impact of key features, their prioritization, and suggestions for value-adding enhancements.

‎prompt_library/business_model_canvas_analysis.md‎

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Business Model Canvas Analysis for Codebase
2+
3+
**Objective:** Analyze the codebase using the Business Model Canvas framework to understand its business implications and potential.
4+
5+
**Instructions:**
6+
7+
1. Review the codebase and identify key features and functionalities.
8+
2. For each element of the Business Model Canvas, analyze how the codebase contributes:
9+
10+
a. Value Propositions:
11+
- What user problems does the code solve?
12+
- What value does it deliver to users?
13+
14+
b. Customer Segments:
15+
- Who are the target users/customers for this code?
16+
- Are there different user groups with distinct needs?
17+
18+
c. Channels:
19+
- How does the code facilitate reaching users?
20+
- Are there features for distribution or communication?
21+
22+
d. Customer Relationships:
23+
- How does the code support user engagement and retention?
24+
- Are there features for customer support or community building?
25+
26+
e. Revenue Streams:
27+
- How could this code generate revenue?
28+
- Are there monetization features implemented?
29+
30+
f. Key Resources:
31+
- What are the critical technical assets in the codebase?
32+
- Are there unique algorithms or data structures?
33+
34+
g. Key Activities:
35+
- What are the core functionalities that keep the application running?
36+
- What ongoing processes does the code support?
37+
38+
h. Key Partnerships:
39+
- Does the code integrate with external services or APIs?
40+
- Are there dependencies on third-party libraries?
41+
42+
i. Cost Structure:
43+
- What are the main cost drivers in running this code?
44+
- Are there features aimed at optimizing costs?
45+
46+
3. Identify potential gaps or opportunities in the business model based on the codebase analysis.
47+
4. Suggest improvements or new features that could enhance the business model.
48+
49+
**Expected Output:** A comprehensive analysis of the codebase using the Business Model Canvas framework, highlighting how the code supports different aspects of the business model and identifying areas for improvement or expansion.

‎prompt_library/customer_journey_map_analysis.md‎

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
# Customer Journey Map Analysis for Codebase
2+
3+
**Objective:** Analyze the codebase to map out how different parts support various stages of the user's journey or experience.
4+
5+
**Instructions:**
6+
7+
1. Review the codebase and identify key features and functionalities.
8+
9+
2. Define the main stages of the customer journey that the code supports. Typical stages might include:
10+
- Awareness
11+
- Consideration
12+
- Decision
13+
- Onboarding
14+
- Usage
15+
- Support
16+
- Retention
17+
- Advocacy
18+
19+
3. For each stage of the journey:
20+
a. Identify the specific code components or features that support this stage.
21+
b. Analyze how these components contribute to the user's experience:
22+
- What actions can the user take?
23+
- What information or feedback does the user receive?
24+
- How does the code facilitate the user's progression to the next stage?
25+
26+
4. Evaluate the user's emotional state at each stage:
27+
- How might the user feel when interacting with this part of the code?
28+
- Are there potential pain points or moments of delight?
29+
30+
5. Identify touchpoints where the code interacts with the user:
31+
- User interface elements
32+
- Data input/output points
33+
- Notifications or alerts
34+
- Integration with external services or platforms
35+
36+
6. Analyze the flow and continuity between stages:
37+
- How smoothly does the code facilitate the user's transition between stages?
38+
- Are there any gaps or disconnects in the user's journey?
39+
40+
7. Identify opportunities for improvement:
41+
- Are there stages of the journey that lack adequate support in the code?
42+
- Could additional features enhance the user's experience at any stage?
43+
- Are there ways to streamline the journey or reduce friction points?
44+
45+
8. Consider personalization and adaptability:
46+
- Does the code account for different user personas or use cases?
47+
- How flexible is the implementation in supporting various journey paths?
48+
49+
**Expected Output:** A comprehensive analysis of how the codebase supports the customer journey, including:
50+
- A mapping of code components to each stage of the journey
51+
- Insights into the user's experience and emotional state at each stage
52+
- Identified strengths and weaknesses in the current implementation
53+
- Opportunities for enhancing the user journey through code improvements or new features
54+
55+
This analysis should provide a clear picture of how the code facilitates the user's experience from start to finish, and guide decisions for future development to optimize the customer journey.

‎prompt_library/jobs_to_be_done_analysis.md‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
# Jobs to be Done (JTBD) Analysis for Codebase
2+
3+
**Objective:** Analyze the codebase using the Jobs to be Done framework to understand the core user needs it addresses and identify potential improvements or new opportunities.
4+
5+
**Instructions:**
6+
7+
1. Review the codebase and identify key features and functionalities.
8+
9+
2. For each major feature or component, analyze:
10+
11+
a. Functional Job:
12+
- What practical task does this code help the user accomplish?
13+
- How does it make a process more efficient or effective?
14+
15+
b. Emotional Job:
16+
- How does this code make the user feel?
17+
- Does it reduce anxiety, increase confidence, or provide a sense of accomplishment?
18+
19+
c. Social Job:
20+
- How does this code help the user in their social or professional context?
21+
- Does it improve status, strengthen relationships, or enhance reputation?
22+
23+
3. Identify the circumstances that trigger the use of each feature:
24+
- What situation prompts the user to engage with this functionality?
25+
- What are the user's goals and constraints in this moment?
26+
27+
4. Analyze the current solutions and workarounds:
28+
- How are users currently addressing these jobs without your code?
29+
- What are the limitations or frustrations with existing solutions?
30+
31+
5. Evaluate how well the code fulfills each identified job:
32+
- Does it fully satisfy the user's needs?
33+
- Are there aspects of the job that are not adequately addressed?
34+
35+
6. Identify potential improvements or new opportunities:
36+
- How could existing features be enhanced to better fulfill the jobs?
37+
- Are there unaddressed jobs that present new development opportunities?
38+
39+
7. Prioritize potential enhancements based on their importance to users and alignment with business goals.
40+
41+
**Expected Output:** A comprehensive analysis of the codebase through the Jobs to be Done lens, highlighting how well it addresses user needs, identifying gaps, and suggesting prioritized improvements or new features to better fulfill user jobs.

‎prompt_library/lean_canvas_analysis.md‎

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Lean Canvas Analysis for Codebase
2+
3+
**Objective:** Analyze the codebase using the Lean Canvas framework to evaluate its business potential and identify areas for improvement or pivot.
4+
5+
**Instructions:**
6+
7+
1. Review the codebase and identify key features and functionalities.
8+
9+
2. For each element of the Lean Canvas, analyze how the codebase contributes:
10+
11+
a. Problem:
12+
- What user problems does the code address?
13+
- Are there existing alternatives or workarounds?
14+
15+
b. Solution:
16+
- How does the code solve the identified problems?
17+
- What are the key features that address user needs?
18+
19+
c. Unique Value Proposition:
20+
- What makes this code unique or innovative?
21+
- How does it differ from existing solutions?
22+
23+
d. Unfair Advantage:
24+
- Does the code leverage any unique technologies or algorithms?
25+
- Are there any hard-to-replicate aspects of the implementation?
26+
27+
e. Customer Segments:
28+
- Who are the target users for this code?
29+
- Are there different user groups with distinct needs?
30+
31+
f. Key Metrics:
32+
- What metrics could be used to measure the success of this code?
33+
- Are there features for tracking user engagement or performance?
34+
35+
g. Channels:
36+
- How could this code reach its target users?
37+
- Are there built-in distribution or marketing features?
38+
39+
h. Cost Structure:
40+
- What are the main cost drivers in developing and maintaining this code?
41+
- Are there features aimed at optimizing costs?
42+
43+
i. Revenue Streams:
44+
- How could this code generate revenue?
45+
- Are there monetization features implemented?
46+
47+
3. Identify potential gaps or inconsistencies in the Lean Canvas based on the codebase analysis.
48+
49+
4. Suggest improvements or new features that could enhance the overall business model.
50+
51+
5. Consider potential pivot opportunities if the current approach doesn't align well with the Lean Canvas analysis.
52+
53+
**Expected Output:** A comprehensive analysis of the codebase using the Lean Canvas framework, highlighting how the code supports different aspects of a lean business model, identifying areas for improvement, and suggesting potential pivots or new directions for development.

‎prompt_library/okr_analysis.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# OKR (Objectives and Key Results) Analysis for Codebase
2+
3+
**Objective:** Analyze the codebase to align its features and capabilities with potential business Objectives and Key Results (OKRs).
4+
5+
**Instructions:**
6+
7+
1. Review the codebase and identify key features, functionalities, and architectural decisions.
8+
9+
2. Based on the codebase analysis, infer potential high-level business objectives that the code might support. For each objective:
10+
a. Formulate a clear, ambitious yet achievable objective statement.
11+
b. Identify 3-5 key results that would indicate progress towards this objective.
12+
c. Explain how specific aspects of the code contribute to these key results.
13+
14+
3. Consider the following categories of objectives:
15+
- User Acquisition and Growth
16+
- User Engagement and Retention
17+
- Revenue Generation
18+
- Operational Efficiency
19+
- Product Innovation
20+
- Market Expansion
21+
22+
4. For each set of OKRs:
23+
a. Evaluate how well the current codebase supports achieving the key results.
24+
b. Identify any gaps or limitations in the code that might hinder achieving the OKRs.
25+
c. Suggest potential code improvements or new features that could better support the OKRs.
26+
27+
5. Analyze the overall alignment of the codebase with the inferred OKRs:
28+
- Are there features that don't clearly contribute to any of the key results?
29+
- Are there important OKRs that lack sufficient support in the current codebase?
30+
31+
6. Propose a prioritized list of development initiatives that would improve the codebase's alignment with the most critical OKRs.
32+
33+
**Expected Output:** A comprehensive analysis of how the codebase aligns with potential business OKRs, including:
34+
- A set of inferred Objectives and Key Results based on the codebase capabilities
35+
- An evaluation of how well the code supports each OKR
36+
- Identified gaps and limitations in the current implementation
37+
- Prioritized suggestions for code improvements or new features to better support critical OKRs
38+
39+
This analysis should provide insights into how the technical implementation aligns with potential business goals and guide future development priorities.

‎prompt_library/stakeholder_persona_generation.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Codebase Stakeholder Persona Generation
2+
3+
**Objective:** Infer potential stakeholder personas based on the functionalities present in the codebase.
4+
5+
**Instructions:**
6+
7+
1. Analyze the codebase to identify distinct user roles and interactions.
8+
2. For each identified role, create a stakeholder persona:
9+
* Name and role
10+
* Goals and motivations
11+
* Pain points and challenges
12+
* Key interactions with the system
13+
3. Map specific code functionalities to each persona's needs.
14+
4. Identify potential gaps in meeting stakeholder needs.
15+
16+
**Expected Output:** A set of detailed stakeholder personas derived from the codebase, including their goals, challenges, and how the current system addresses their needs.

‎prompt_library/swot_analysis.md‎

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# SWOT Analysis for Codebase
2+
3+
**Objective:** Conduct a SWOT (Strengths, Weaknesses, Opportunities, Threats) analysis of the codebase to evaluate its current state and future potential.
4+
5+
**Instructions:**
6+
7+
1. Review the codebase thoroughly, considering its architecture, features, and implementation.
8+
9+
2. Analyze the codebase according to the SWOT framework:
10+
11+
a. Strengths:
12+
- What does the code do exceptionally well?
13+
- What unique features or efficient implementations stand out?
14+
- Are there any innovative algorithms or data structures?
15+
- How scalable or maintainable is the code?
16+
17+
b. Weaknesses:
18+
- What are the limitations or shortcomings of the current implementation?
19+
- Are there any performance bottlenecks or scalability issues?
20+
- Are there areas where the code quality could be improved?
21+
- Are there missing features or incomplete implementations?
22+
23+
c. Opportunities:
24+
- What market trends or user needs could the code capitalize on?
25+
- Are there potential new features or functionalities that could be added?
26+
- Could the code be adapted for new platforms or use cases?
27+
- Are there opportunities for integration with other systems or services?
28+
29+
d. Threats:
30+
- Are there competing solutions that might make this code obsolete?
31+
- Are there potential security vulnerabilities or compliance issues?
32+
- Could changes in technology or standards negatively impact the code?
33+
- Are there dependencies on external libraries or services that pose risks?
34+
35+
3. For each point in the SWOT analysis, provide specific examples from the codebase to support your assessment.
36+
37+
4. Suggest strategies to:
38+
- Leverage strengths
39+
- Address weaknesses
40+
- Capitalize on opportunities
41+
- Mitigate threats
42+
43+
**Expected Output:** A comprehensive SWOT analysis of the codebase, providing insights into its current state and future potential, with actionable recommendations for improvement and strategic direction.

0 commit comments

Comments
 (0)