Free cheat sheet — six stages, six artifacts

Build personal software like a
​product designer.

How to turn fast AI builds into work people can review, hand off, and build on.

A printable framework and agent skills so every stage of your build produces something you can hand to someone else.

Send me the cheat sheet

✓ Printable 6-stage map — the job and artifact at each stage, reference it while you work.

✓ One agent skill per stage — copy-paste commands for Cursor or any AI coding tool. No setup.

✓ Link to the full rules repo — prompts, examples, and conventions on GitHub when you're ready to go deeper.
​

    You'll get the cheat sheet and repo link immediately, then a few short emails with real projects and practical tips. Unsubscribe anytime.

    Who this is for
    ​

    PMs and founders — you need to align people and hand off without a “you had to be there” demo.

    Designers using AI — you want a frame that produces artifacts per stage, not an endless prompt loop.

    Indie builders — copilots and agents are fine; you want output you can review, share, and reopen next month without an archaeology session.
    ​
    ​

    ​

    Six stages. Six artifacts.
    ​

    01
    ​New project /new-project​
    ​
    Workspace and naming so artifacts have a home; stub brief before real work — less “where did I put that?” next session.

    02
    ​Product requirements /prd​
    ​
    One-page requirements: problem, stories, risks, success metrics — decide scope once instead of rationalizing in Figma or code.
    ​
    03
    ​Lo-fi wireframes /lofi​
    ​
    ASCII structure and flow before pixels — cheap to change before you’re attached to polish.
    ​
    04
    ​Mid-fi /midfi​
    ​
    Tokens, type, components, states — system locked before polish.
    ​
    05
    ​UI prototype /ui-proto​
    ​
    Clickable primary flow — surprises in a click path, not in a late engineering review.
    ​
    06
    ​Hi-fi + handoff /hifi​
    ​
    Kit, screens, annotations — handoff that doesn’t need you in the room to interpret intent.
    ​


    ​

    From Luis
    ​

    I built this process because I needed it. When I started leaning on AI for implementation, I kept producing things that ran but were hard to share or replicate it and were full of AI slop. The problem wasn't the tools — I was skipping the parts that make output legible to others.

    The 6-stage process is my attempt to apply product design discipline to the kind of AI-augmented work I actually do: internal tools, portals, workflow systems. The cheat sheet is the quick reference; the GitHub repo is the full implementation.

    I’ll follow with short — real projects and tips — and an invite to a 30-minute walkthrough if you want to see one real project end to end.
    ​
    — Luis Cielak · Product design consultant

    ​

    ​


    ​

    ​

    Want to pressure-test how this applies to your build?
    ​

    A Thinking Session is a 30-minute conversation where we walk through your current project or process — what's working, where things get stuck, and how the 6-stage framework maps to what you're actually doing. You'll leave with a prioritized next step, not a pitch.
    ​

    Limited availability. I take 3–4 of these per month.

    ​