Source profileQuality 68/100

nexu-io/open-design/design-templates/gamified-app/SKILL.md

gamified-app

A multi-frame gamified mobile-app prototype — three phone frames on a dark showcase stage. Frame 1: cover / poster, Frame 2: today's quests with XP ribbons and a level bar, Frame 3: quest detail. Vivid quest tiles, level ribbon, bottom tab bar. Use when the brief asks for a "gamified app", "habit tracker", "RPG-style life app", "level-up app", "daily quests", "XP / streak app", or "ELI5-style explainer app".

Source repository stars
82,073
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Produce a multi-screen mobile prototype on a single dark showcase page. Three phone frames side-by-side, each one its own moment in the journey.

Best for

  • Use when the brief asks for a "gamified app", "habit tracker", "RPG-style life app", "level-up app", "daily quests", "XP / streak app", or "ELI5-style explainer app".

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/nexu-io/open-design --skill "design-templates/gamified-app"
Safe inspection promptEditorial

Inspect the Agent Skill "gamified-app" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/design-templates/gamified-app/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Read the active DESIGN.md (injected above). For gamified apps, lean on bold display type for headlines and a brighter, broader palette than most products — quests look like quests because the colors do. 2. Pick the brand + value prop from the brief. Generate real quest names…

    Read the active DESIGN.md (injected above). For gamified apps, leanPick the brand + value prop from the brief. Generate real questStage — full-bleed dark page (near-black 0e0d0c or DS dark token)
  2. 02

    Output contract

    One sentence before the artifact, nothing after.

    One sentence before the artifact, nothing after.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score68/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars82,073SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
nexu-io/open-design
Skill path
design-templates/gamified-app/SKILL.md
Commit
89d6d4ef21baf80f871595abdf6f7de6e941dd44
License
Apache-2.0
Collected
2026-07-28
Default branch
main
View the original SKILL.md

Gamified App Skill

Produce a multi-screen mobile prototype on a single dark showcase page. Three phone frames side-by-side, each one its own moment in the journey.

Workflow

  1. Read the active DESIGN.md (injected above). For gamified apps, lean on bold display type for headlines and a brighter, broader palette than most products — quests look like quests because the colors do.
  2. Pick the brand + value prop from the brief. Generate real quest names (e.g. "Body — 20-min strength: pushups & planks", "Read — Four Thousand Weeks", "Listen — Huberman Lab · Sleep Architecture", "Nourish — Cook a high-protein lunch", "Mind — 10-min focus meditation", "Watch — The Bear · S3 E4").
  3. Stage — full-bleed dark page (near-black #0e0d0c or DS dark token) with a soft top spotlight gradient. Above the phones, a small caption row: "HI-FI PROTOTYPE · IPHONE" left, brand wordmark right, both in mono.
  4. Phones — three 360×780 phone frames in a horizontal row (wraps to stack on narrow viewports). Each phone:
    • 12px black bezel, 44px corner radius, dynamic-island notch.
    • Status bar (time / signal / battery).
    • Phone-specific content (below).
    • Bottom tab bar with 5 icons (Today, Library, Stats, ⊕ central CTA, Profile). Active tab in accent.
  5. Phone 1 — cover poster (sales/value prop):
    • Status bar.
    • HI-FI PROTOTYPE · IPHONE eyebrow.
    • Big display headline ("Daily quests for becoming a better human."), accent on "becoming".
    • 1–2 sentence body in muted serif/sans.
    • Mono tip line ("Tap quests to open detail. Toggle [theme] in the toolbar to switch theme & layout.")
    • Subtle scrolling teaser of the next screen at the bottom edge.
  6. Phone 2 — today's quests dashboard (the hero screen):
    • Greeting "Good morning, Sam" + small XP-bell ringing.
    • Level ribbon — "LV 14 · Level 14 · 1648 / 2480 XP" with a progress bar inside a glassmorphic ribbon.
    • Sub-line: "8 quests waiting · earn 430 XP today".
    • 3×2 grid of quest tiles. Each tile: rounded corner, pastel accent color, glyph chip in top-left, title, mini-meta line, "+NN XP" pill in bottom-right.
    • Bottom tab bar.
  7. Phone 3 — quest detail:
    • Back arrow + screen title ("Quest").
    • Hero block with the quest's accent color, big serif quest title ("Body — strength"), short narrative body, "REWARD +90 XP" stamp.
    • Steps checklist (3–4 micro-tasks, one done, two pending).
    • Big primary CTA "Start quest" pill at the bottom in accent.
  8. Write a single HTML document:
    • <!doctype html> through </html>, CSS inline.
    • All in CSS — no images. Use linear-gradient and inline SVG glyphs for tile chips and tab icons.
    • data-od-id on stage, each phone, each frame's regions.
  9. Self-check:
    • Three frames, each with a distinct purpose. Not three copies of the same screen.
    • Tile colors don't overpower — each quest tile uses a different pastel against the same neutral surface.
    • Reads as gamified and adult — playful, not childish.

Output contract

Emit between <artifact> tags:

<artifact identifier="game-slug" type="text/html" title="Mobile — App Name">
<!doctype html>
<html>...</html>
</artifact>

One sentence before the artifact, nothing after.

Alternatives

Compare before choosing