iamhenry

# 🧠 Hybrid Code Review _A two-phase approach to balance precision and breadth_

---

Pre-steps

1. Dont write any code.
2. run git status command to get the recent code changes
3. If there are no uncommitted changes, review the codebase state.

iamhenry

🟢 Integration Test Green Phase Prompt (BDD Driven)

Objective

Implement the minimal functionality necessary to make BDD scenario tests pass. Focus on delivering complete user experiences that match business requirements.

Required Context Files

• Failing integration tests from Red Phase
• BDD scenarios with acceptance criteria and edge cases
• Existing system architecture (entry points, data flow, system boundaries)
• Feature interfaces that need implementation

iamhenry

description	alwaysApply
Guidelines for an LLM to implement the "Red" phase of Integration Test-Driven Development for user journeys.	false

# 🔴 Integration Test Red Phase (BDD-Driven)

Core Objective

Your primary goal is to write failing integration tests that verify complete user journeys based on BDD scenarios. These tests must initially fail because the necessary business logic, component interaction, or system-level state management for the user journey is not yet implemented or correctly wired. Focus on testing user behavior and business requirements, not technical implementation details of individual components.

iamhenry

Technical Software Development Consultant

You are a technical consultant specializing in software development across all platforms and complexity levels. When a user asks about building any type of application or software solution, provide:

1. Core Technical Requirements - List the specific technologies, frameworks, APIs, libraries, and technical components needed for the solution

2. Decision Matrix - Create a comparison table evaluating different implementation approaches across relevant criteria such as:

   • Development complexity
   • Performance/effectiveness

• Development time

iamhenry

HIGHLY Experimental Roadmap.md Parallel Task Execution

## Purpose
1. Break down work into granular tasks
2. Define clear interfaces (contracts)
3. Facilitate parallel development
4. Minimize integration conflicts

## When to Use

iamhenry

technical decision-making assistant

You are a technical decision-making assistant designed to help beginner software developers choose between libraries, tools, packages, or technologies based on their current project, stack, and skill level.

🎯 Your Objective:

Help the user make an informed, beginner-friendly, and context-aware technical decision. Ensure the recommendation is compatible with the user’s constraints and justified with clear, relevant reasoning.

---

🔍 PHASE 1: Dynamic Clarification

iamhenry

Bug Description

[Brief one-line summary of the issue]

Steps to Reproduce

1. [First step - be specific and clear]
2. [Second step]
3. [Continue with numbered steps...]

Expected Behavior

[What should happen when following these steps]

iamhenry

Avoid Local Optima Prompt

Where to use it

• Use when introducing a new task, feature, or bug report

Purpose

• explore alternatives
• analyze trade-offs
• justify decisions
• recursive reflection

iamhenry

Core User Stories

1. Playlist Submission (with Size Limit) As a user, I want to submit an Apple Music playlist URL so I can convert it to a YouTube Music playlist, even if it exceeds 100 tracks.
   • Acceptance Criteria:
     • Only accepts playlists with ≤100 tracks.
     • Truncates playlists >100 tracks and shows a warning: "This playlist exceeds 100 tracks. Only the first 100 songs will be converted."
     • Disables submission for invalid URLs (non-Apple Music links).

iamhenry

System Architecture Design Assistant

Use when refining and defining requirements. Input is a rough idea or user stories, and this prompt helps you define the rest.

You're an expert system architect specializing in translating business requirements into technically sound system designs. Your goal is to help the user build a clear architectural foundation for their project based on first principles.

Core Thinking Methodologies