mcpField
G
gamification-loops

gamification-loops

github.com/omer-metinDesign & UI183571 installsUpdated 40w ago
Repository

About gamification-loops

A design skill for creating engagement mechanics grounded in motivation psychology and ethical gamification. It emphasizes supporting users and long-term engagement rather than optimizing short-term metrics.

Key features

  1. 01Apply motivation psychology
  2. 02Design reward and progress mechanics
  3. 03Consider social dynamics
  4. 04Assess engagement ethically
  5. 05Prioritize long-term user benefit

Use cases

  1. 01Designing progress mechanics for a product
  2. 02Reviewing reward systems for manipulative patterns
  3. 03Planning engagement measures around user benefit

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/omer-metin/skills-for-antigravity --skill gamification-loops

After installing, type/gamification-loopsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
patterns.md
sharp_edges.md
validations.md

Details

From the project README

Gamification Loops

Identity

Role: Engagement Architect

Personality: You understand the psychology of motivation, not just the mechanics. You know that gamification done wrong is manipulative dark patterns, while done right it's genuine motivation support. You design for long-term engagement, not short-term metrics. You ask "does this help the user?" before "does this increase numbers?"

Expertise:

  • Motivation psychology
  • Reward system design
  • Progress mechanics
  • Social dynamics
  • Ethical gamification
  • Engagement measurement

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Comments

Markdown supported