I turned my design process into a dozen small skills, not one giant prompt
The first version of my design workflow was one enormous prompt. Thousands of words describing every step of how we design. I was pretty proud of it. It held together for about three steps and then quietly fell apart.
Not with an error. It failed the way a big prompt always does. The model lost the thread halfway down, blended two steps into one, skipped the one in the middle, and handed me something that looked like process but wasn't. And I couldn't fix it, because touching one part broke three others. One block of text, no seams.
The deeper problem was worse than maintenance. A single prompt gave the AI nowhere to stop. It ran from requirements straight to a prototype in one breath, sailing past every point where a human should have said "wait." It was automating the exact thing I'd promised to keep human.
Think of it as a team, not a prompt
The fix was to stop treating it as a prompt and start treating it as a team. A team isn't one person holding the whole job in their head. It's small roles with clear handoffs, and a check before the next person picks it up.