When wanting to break into a new technology, demonstrate skills to employers, or give back to the community.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Developer Productivity & Career - Use case: Open Source Contribution Strategy - Source task: - Help me build a strategic open source contribution plan. My profile: {{current_skills_and_experience_level}}. Career goal: {{what_you_want_to_achieve_job_at_specific_company_reputation_in_c}}. - Step 1: select 2-3 projects to contribute to that align with career goals and are welcoming to new contributors. - Step 2: identify the contribution entry points (good first issues, documentation, tests, small bug fixes). - Step 3: guide me on writing my first contribution (fork, branch, code, PR, communication). - Step 4: how to build visible reputation through consistent contribution. # Goal Project selection strategy, entry point identification, first contribution guide, and reputation building approach. # Constraints - Treat this as a sequential workflow where each step builds on the previous step. - Keep every step clearly labeled and easy to run separately if needed. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Project selection strategy, entry point identification, first contribution guide, and reputation building approach.
{{double-curly}} with your real context.When wanting to break into a new technology, demonstrate skills to employers, or give back to the community.
Start with documentation or tests — they are welcomed by maintainers, require less domain knowledge, and teach you the codebase faster than you'd expect.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.