iamhenry

Purpose: Useful in software dev for getting a systemic analysis before implementing a feature/bug. Uses "cloud to ground" methodology (zooming in and out of the codebase to understand it more thoroughly). Applies "tracer bullet" methodology to be more direct with the implementation.

Step 1: Define the Build Target

I need to build: [FEATURE DESCRIPTION]

Step 2: Identify Tracer Bullet

iamhenry

The current conversation is rapidly running out of context. Now, your urgent task is to create a comprehensive detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions. This summary should be thorough in capturing technical details, code patterns, and architectural decisions that would be essential for continuing development work without losing context. You MUST ONLY respond to this message by using the summarize_task tool call.

Before providing your final summary, wrap your analysis in tags to organize your thoughts and ensure you've covered all necessary points. In your analysis process:

1. Chronologically analyze each message and section of the conversation. For each section thoroughly identify:
   • The user's explicit requests and intents
   • Your approach to addressing the user's requests
   • Key decisions, technical concepts and code patterns

• Specific details like file names, full code snippets, function signatures,

iamhenry

Use this workflow when you need to thoroughly understand all relevant parts of a codebase 
or topic before making changes or writing documentation.

Source: https://grantslatton.com/claude-code

1. Enumerate all source code files in the project, explicitly excluding build artifacts and other non-essential directories to ensure a complete and relevant file list.
2. From the list, heuristically identify filenames most likely related to the target topic or feature; at this stage, simply list them without further action.
3. For each relevant file, use pattern-matching tools (such as ripgrep) to locate definitions of types, functions, modules, and other major code constructs—tailoring search patterns to the conventions of the specific programming language.

iamhenry

When to use:
1. Newly released frameworks LLM's havent been trained on
2. A quick primer on a framework to have locally in the project (ex. vercel ai sdk for using llm's for chat and image processing)
3. Can be used to create "contract-first" approach for scaffolding the project
4. Create multiple independent files for each necessary framework

Inputs:
1. Pass in my feature/user stories and have it do research on the necessary docs to build that feature
ex. using the vercel ai sdk to build the recipe ocr features (i need to understand what comes built-in and what i need to build myself)

iamhenry

Transform Prompt to Code

You are an expert prompt engineer whose job is to transform informal or unclear prompts into well-structured, modular, code-like prompt templates suitable for agentic workflows.

Your goal is to produce a structured prompt with these sections:

1. Inputs – explicit parameters the user must supply.
2. Outputs – detailed expected results.
3. State – information to persist across runs.
4. Steps / Modules – logical step-by-step or modular breakdown.

iamhenry

# [App Name]: [Short Tagline/Promise] 🎉

Hey r/[subreddit], I’m [Your Name] — after [X] months of late nights, I’m excited (and a bit nervous) to share my very first app with you!

This project started because [brief personal motivation or pain point]. Today, I finally hit a milestone: [e.g., first paid user, first public release, etc.]. For indie devs, every small win means the world.

iamhenry

Here’s how and where to plug in your product, following Diego’s playbook:

1. After Sharing Value or a Story

First, provide real value—share your journey, a lesson, or a solution to a problem. Once you’ve established credibility and given something useful, you can mention your product as the tool or method you used.

iamhenry

Goal

I need a name for an app I'm building

App Description

[Describe what the app does and provide details of how it works]

Instructions:

1. I need you to first come up with a 10-15 relevant keywords
2. Use these keywords as brain storming session to come up with a name for the app
3. Include trendy like phrases from tv shows/movies. (ex. "Yes Chef" from The Bear tv show for a recipe app). Ensure they arent copywritten

iamhenry

Idea Evaluation Matrix

Criteria	Weight (1–5)	Idea A	Idea B	Idea C	Idea D	Idea E
🟢 Personal Enjoyment / Interest	5
🟢 Build Effort / Complexity	5

iamhenry

Software Design Document (SDD)

1. Introduction

• Purpose: [Describe the purpose of this document. E.g., to define the design of the XYZ system.]
• Scope: [Summarize the system's objectives and what is in/out of scope.]
• Definitions and Acronyms: [List and define important terms.]
• References: [Link to related documents: requirements, API specs, etc.]

---