User Guide
ProductFeeling helps product development participants — technical and non-technical — decide how a product should feel, then review surfaces and flows against that north star.
It sits upstream of Impeccable (frontend craft) and beside DocSlime (durable docs/). This product aims for grounded clarity — name how something feels and why, on real evidence — with confidence as the residue. It should never leave people blocked or overwhelmed.
Companions
Section titled “Companions”ProductFeeling decides how a product should feel; it hands execution to two sibling skills for AI coding agents.
| Skill | What it is | Hand off when |
|---|---|---|
| Impeccable (impeccable.style) | Design guidance for AI coding agents — frontend craft, live browser iteration, and deterministic detector rules | You have a feeling brief and need the UI built or polished |
DocSlime (DecisionNerd/DocSlime) |
A CLI plus skill pack for creating, filling, reviewing, and publishing an opinionated docs/ tree |
The feeling/product narrative should live durably in docs/ |
RedTeam (CurateLabs/RedTeam) |
Applied critical thinking — premortems, assumptions checks, devil’s advocacy, decision reviews (not security testing) | A feeling decision, north star, or strategy needs adversarial stress-testing before you commit |
In this guide
Section titled “In this guide”| Page | What you’ll learn |
|---|---|
| Quick start | Install and run your first review |
| Installation | skills CLI, project CLI, plugins, ChatGPT |
| Commands | All 23 /productfeeling commands |
| Project context | docs/ vs .productfeeling/ |
| Chat-only mode | Useful reviews with zero project setup |
What it is not
Section titled “What it is not”Not a general UI polish skill (use Impeccable). Not clinical psychology. Not a toolkit for dark patterns or ethics theater.