Claude for thinking and writing
I use Claude as a reasoning partner: drafting specs, stress testing arguments, and turning messy notes into clear docs. It is strongest where the work is language and judgment, which is the majority of a PM's output.
Cursor for building and prototyping
Cursor lets me go from idea to a working prototype without a full engineering team, enough to validate a flow, test an API, or make a stakeholder feel the product instead of reading about it. Prototyping in code beats a slide every time.
Right tool, right job
I do not use AI tools as one undifferentiated blob. Research, drafting, data analysis and prototyping each have a tool that fits, and knowing which to reach for is half the productivity gain. The other half is knowing when not to.
Verify everything that matters
These tools are fast and occasionally, confidently wrong. Anything factual, financial or customer facing gets checked before it leaves my hands. I trust them for speed, never for final authority.
Real example
This very portfolio and its skill pages were built and iterated with AI tooling in the loop: Claude for content and structure, code assistants for the build. It is the same approach I bring to product work. Use the tools to move fast, keep the judgment human.