Market & users
Market context
Section titled âMarket contextâProduct teams increasingly build with AI agent harnesses (Cursor, Claude Code, Codex, and peers). Those agents are strong at layout and weak at intentional affect. Demand is for feeling-first guidance that fits the same install/skill workflow as craft and docs companions.
Primary users
Section titled âPrimary usersâPeople across the product development lifecycle who learn and apply feeling guidance:
| Segment | What they need from ProductFeeling |
|---|---|
| Product designers & PMs | Name the emotional north star; review flows/copy/states before polish |
| Engineers pairing with Impeccable | Emotion briefs that are executable without re-litigating strategy |
Teams using DocSlime / docs/ |
Feeling woven into product, strategy, and experience docs â not a parallel SoT |
Jobs (emotional / product)
Section titled âJobs (emotional / product)â- Before: Uncertainty or âit just feels offâ with no shared language.
- During: Structured review against an intentional feeling; selective handbook depth when needed.
- After: Clear brief or durable docs update; handoff to craft or docs without bloat.
Where strategy lives for this product
Section titled âWhere strategy lives for this productâFor ProductFeeling itself, durable strategic narrative lives in docs/strategy/ (this folder). The skill should treat that tree as a primary workspace when improving ProductFeelingâs own product experience â not only when reviewing third-party apps.