Skip to content

Instantly share code, notes, and snippets.

@bigsnarfdude
Last active June 26, 2025 20:43
Show Gist options
  • Save bigsnarfdude/bc83a5e7b985099a961cf0d0d2bf7d4c to your computer and use it in GitHub Desktop.
Save bigsnarfdude/bc83a5e7b985099a961cf0d0d2bf7d4c to your computer and use it in GitHub Desktop.
claude_code_prompt.md

I need to

[BRIEF DESCRIPTION OF BUG/FEATURE]

in the workshops system.

Please:

  1. Investigate the codebase - search relevant files to understand current implementation
  2. Ask clarifying questions - what's unclear about my request?
  3. Design solution - create SDD with simple text diagrams
  4. Plan implementation - break into specific steps

Start by exploring the codebase to understand how this area currently works.

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

I need to

[BRIEF DESCRIPTION OF BUG/FEATURE]

in the proposals system.

Please:

  1. Investigate the codebase - search relevant files to understand current implementation
  2. Ask clarifying questions - what's unclear about my request?
  3. Design solution - create SDD with simple text diagrams
  4. Plan implementation - break into specific steps

Start by exploring the codebase to understand how this area currently works.

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Take this SDD apart. Give me 20 points that are underspecified, weird, or inconsistent.

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Bug Fix & Feature Request SDD Workflow:

"I have a [BUG FIX / FEATURE REQUEST] for the [workshops / proposals] system:

REQUEST: [Your description here]

Step 1: Codebase Investigation

  • Search workshops/proposals repos to understand current implementation
  • Identify affected models, controllers, views, and services
  • Look for similar existing patterns and conventions
  • Document current behavior vs desired behavior

Step 2: Impact Analysis

  • What files need modification?
  • Are there database schema changes needed?
  • What existing functionality might be affected?
  • Identify test scenarios and edge cases

Step 3: Solution Design (SDD)

  • Create 2-3 solution approaches with pros/cons
  • Include simple text diagrams for UI changes
  • Show data flow and component interactions
  • Define error handling and validation logic

Step 4: Implementation Plan

  • Prioritized list of code changes
  • Migration requirements if any
  • Testing approach
  • Deployment considerations

Current System: [workshops/proposals - briefly describe the area] User Role: [admin/participant/organizer/etc] Priority: [high/medium/low]

Start by investigating the current codebase - I need to understand how this area works before we design the fix."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment