Files
claude-sync/projects/-Users-csader-shaper-slicer/memory/feedback_design_first.md
T
Chris 33cab10cef Initial sync: memory, agents, commands, and gitignore
Syncs project memory, custom agents, and commands across machines.
Excludes secrets (settings.json), session state, and runtime files.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-06-11 09:19:24 -05:00

722 B

name, description, type
name description type
Design before code User prefers first-principles algorithm design before reading existing code feedback

When tackling complex geometry/algorithm problems, design the ideal approach from first principles BEFORE reading the existing code. Then compare the ideal to what's implemented to find bugs.

Why: User explicitly asked for this workflow — "I'd rather have you think of how you'd recommend doing it FIRST, then compare to the existing code." Jumping straight to code reading led to patches that missed the root cause.

How to apply: For non-trivial algorithm bugs, start with a clean-room design of what the correct approach should be, then diff against the implementation.