product-gamification

Files (1)

• SKILL.md

SKILL.md (first lines)

# Product Gamification

Gamification must improve clarity, motivation, learning, or sustained progress
toward a goal the user already values. If it does not, recommend no gamification.

## Start with behavior

Define:

- the user and valuable real-world outcome;
- the behavior that advances that outcome;
- the present obstacle: unclear progress, weak feedback, low confidence, delayed
  reward, poor onboarding, or lack of meaningful choice;
- the product and user metrics that prove improvement without encouraging abuse.

## Select the lightest fitting mechanic

- Progress visualization for long or multi-stage work.
- Missions or challenges for a clear next action.
- Levels or skill trees for growing capability and choice.
- Achievements for meaningful milestones, not routine clicks.
- Collections for exploration and completion where content has real value.
- Streaks only when daily consistency is healthy and recovery is humane.
- Narrative framing when it improves meaning and comprehension.
- Social mechanics only with privacy, consent, fair comparison, and abuse controls.
- Celebration, motion, and sound proportional to the significance of the event.

Explain the loop as trigger, action, feedback, progress, and return condition.
Specify onboarding, empty, paused, missed, recovered, completed, capped, and
opt-out states. Preserve a conventional path for users who do not want the layer.

## Guardrails

- Never use deceptive urgency, artificial scarcity, coercive loss aversion, or
  variable rewards intended to create compulsive use.
- Do not penalize illness, disability, weekends, timezone differences, or healthy breaks.
- Do not turn private performance into public ranking by default.
- Keep rewards subordinate to intrinsic purpose; avoid teaching users to optimize
  points instead of outcomes.
- Make costs, eligibility, odds, progress, and unlock conditions understandable.
- Keep critical, financial, administrative, and destructive workflows calm and explicit.

## Deliverable

Provide the user problem, proposed mechanic, behavioral rationale, core loop,
screen and state implications, abuse cases, accessibility requirements, metrics,
guardrails, and the smallest experiment that can invalidate the idea. Challenge
mechanics whose maintenance and cognitive cost exceed their likely value.

From NeroWasTrolled/gabriel-ai-devkit, MIT.

More from NeroWasTrolled/gabriel-ai-devkit