game-design-prosocial-session-chapters

Name: game-design-prosocial-session-chapters
Author: Stanestane

34stars3forks

How to install game-design-prosocial-session-chapters?

stanestane/game-design-skills-bundle/game-design-prosocial-session-chapters

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-prosocial-session-chapters

Installs into the current project.

Summary

Design or audit prosocial experiences in session-based multiplayer games using a three-phase chapter model built around Setup, Little Loops, and Long Tail. Use when evaluating co-op games, team shooters, MOBAs, mission-based multiplayer, or other repeat-session formats; when plan

Files · 1

View on GitHub

SKILL.md

1	# Game Design Prosocial Session Chapters
2
3	Use this skill to structure prosocial multiplayer design across the arc of a session-based experience: before the action, inside the repeating social micro-loops, and after the session ends.
4
5	This skill is specifically for games where social experience happens in repeated sessions, matches, runs, or missions rather than primarily through one persistent social world.
6
7	## Core principle
8
9	Prosociality should be designed as an arc, not a lucky accident.
10
11	A healthy session-based multiplayer game does not rely only on one nice feature or one moderation tool. It prepares players for prosocial behavior before the pressure starts, gives them repeated chances to do small useful social actions during play, and then preserves or extends that social value after the match.
12
13	## The chapter model
14
15	### Chapter 1: Setup
16
17	Set the stage before or around the start of play.
18
19	This phase includes:
20	- matchmaking context
21	- lobbies
22	- loading screens
23	- tutorials
24	- expectation setting
25	- early identity and trust cues
26	- pre-session group assembly
27
28	The job of Setup is to make prosocial behavior feel plausible, legible, and normal before players are under stress.
29
30	### Chapter 2: Little Loops
31
32	Create repeatable prosocial actions inside the core loop.
33
34	This phase includes the small repeated actions players do for one another during active play:
35	- revive
36	- heal
37	- ping
38	- cover
39	- share
40	- rescue
41	- assist
42	- coordinate
43	- acknowledge
44	- set up beneficial reciprocity
45
46	The job of Little Loops is to turn prosocial behavior into habit, not just aspiration.
47
48	### Chapter 3: Long Tail
49
50	Make prosocial behavior meaningful beyond the session.
51
52	This phase includes:
53	- commendations
54	- acknowledgements
55	- social memory
56	- regrouping
57	- reconnect surfaces
58	- prosocial stats or recognition
59	- social hubs after play
60	- ways to continue with positive teammates
61
62	The job of the Long Tail is to stop good social moments from evaporating the instant the scoreboard disappears.
63
64	## What to produce
65
66	Generate:
67	1. Audit or design target - what game, mode, or session loop is being reviewed
68	2. Chapter-by-chapter assessment - what currently exists in Setup, Little Loops, and Long Tail
69	3. Prosocial arc diagnosis - whether the three chapters reinforce one another or feel disconnected
70	4. Missed opportunities - where the design could better prime, repeat, or preserve prosocial behavior
71	5. Priority interventions - what to add, change, or strengthen in each chapter
72	6. Use-case judgment - whether this framework is a strong fit for the target or whether another lens would be more appropriate
73
74	## Process
75
76	### 1. Confirm that the game fits the method
77
78	This method is strongest when:
79	- play happens in bounded sessions, matches, rounds, or missions
80	- players repeatedly team up with friends, acquaintances, or strangers
81	- social experience depends on what happens around and inside a repeatable play loop
82
83	This method is weaker when:
84	- the game is mainly a persistent sandbox or MMO social world
85	- the primary problem is broad moderation governance rather than in-session prosocial design
86	- the experience is mostly solitary or asynchronous
87
88	If it is a weak fit, say so and only use the framework selectively.
89
90	### 2. Define the prosocial goal
91
92	Clarify:
93	- what kind of positive social behavior the design wants more of
94	- whether the goal is trust, cooperation, warmth, sportsmanship, return play with others, or reduced hostility
95	- what current social problem is most salient: hostility, social flatness, weak teamwork, weak reconnection, etc.
96
97	Write:
98	- Target
99	- Desired prosocial outcome
100	- Current social problem
101
102	### 3. Audit Setup
103
104	Ask:
105	- how does the game prime prosocial expectations before play begins?
106	- are strangers humanized or made more legible?
107	- are players encouraged to see teamwork as normal and beneficial?
108	- do tutorials, lobbies, or loading surfaces support prosocial norms?
109	- do group assembly tools help compatible people find each other or reform?
110	- is there any thematic or narrative framing that supports helping behavior?
111
112	Setup warning signs:
113	- pure mechanical onboarding with no social framing
114	- strangers feel faceless and disposable
115	- no expectation setting until after conflict starts
116	- no trust scaffolding before high-pressure teamwork
117
118	### 4. Audit Little Loops
119
120	Ask:
121	- what small repeatable prosocial actions happen during pla

People who liked this also viewed

6 picks

Type

game-design-prosocial-session-chapters

34stars3forks

View on GitHub

How to install game-design-prosocial-session-chapters?

stanestane/game-design-skills-bundle/game-design-prosocial-session-chapters

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-prosocial-session-chapters

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Game Design Prosocial Session Chapters
2
3	Use this skill to structure prosocial multiplayer design across the arc of a session-based experience: before the action, inside the repeating social micro-loops, and after the session ends.
4
5	This skill is specifically for games where social experience happens in repeated sessions, matches, runs, or missions rather than primarily through one persistent social world.
6
7	## Core principle
8
9	Prosociality should be designed as an arc, not a lucky accident.
10
11	A healthy session-based multiplayer game does not rely only on one nice feature or one moderation tool. It prepares players for prosocial behavior before the pressure starts, gives them repeated chances to do small useful social actions during play, and then preserves or extends that social value after the match.
12
13	## The chapter model
14
15	### Chapter 1: Setup
16
17	Set the stage before or around the start of play.
18
19	This phase includes:
20	- matchmaking context
21	- lobbies
22	- loading screens
23	- tutorials
24	- expectation setting
25	- early identity and trust cues
26	- pre-session group assembly
27
28	The job of Setup is to make prosocial behavior feel plausible, legible, and normal before players are under stress.
29
30	### Chapter 2: Little Loops
31
32	Create repeatable prosocial actions inside the core loop.
33
34	This phase includes the small repeated actions players do for one another during active play:
35	- revive
36	- heal
37	- ping
38	- cover
39	- share
40	- rescue
41	- assist
42	- coordinate
43	- acknowledge
44	- set up beneficial reciprocity
45
46	The job of Little Loops is to turn prosocial behavior into habit, not just aspiration.
47
48	### Chapter 3: Long Tail
49
50	Make prosocial behavior meaningful beyond the session.
51
52	This phase includes:
53	- commendations
54	- acknowledgements
55	- social memory
56	- regrouping
57	- reconnect surfaces
58	- prosocial stats or recognition
59	- social hubs after play
60	- ways to continue with positive teammates
61
62	The job of the Long Tail is to stop good social moments from evaporating the instant the scoreboard disappears.
63
64	## What to produce
65
66	Generate:
67	1. Audit or design target - what game, mode, or session loop is being reviewed
68	2. Chapter-by-chapter assessment - what currently exists in Setup, Little Loops, and Long Tail
69	3. Prosocial arc diagnosis - whether the three chapters reinforce one another or feel disconnected
70	4. Missed opportunities - where the design could better prime, repeat, or preserve prosocial behavior
71	5. Priority interventions - what to add, change, or strengthen in each chapter
72	6. Use-case judgment - whether this framework is a strong fit for the target or whether another lens would be more appropriate
73
74	## Process
75
76	### 1. Confirm that the game fits the method
77
78	This method is strongest when:
79	- play happens in bounded sessions, matches, rounds, or missions
80	- players repeatedly team up with friends, acquaintances, or strangers
81	- social experience depends on what happens around and inside a repeatable play loop
82
83	This method is weaker when:
84	- the game is mainly a persistent sandbox or MMO social world
85	- the primary problem is broad moderation governance rather than in-session prosocial design
86	- the experience is mostly solitary or asynchronous
87
88	If it is a weak fit, say so and only use the framework selectively.
89
90	### 2. Define the prosocial goal
91
92	Clarify:
93	- what kind of positive social behavior the design wants more of
94	- whether the goal is trust, cooperation, warmth, sportsmanship, return play with others, or reduced hostility
95	- what current social problem is most salient: hostility, social flatness, weak teamwork, weak reconnection, etc.
96
97	Write:
98	- Target
99	- Desired prosocial outcome
100	- Current social problem
101
102	### 3. Audit Setup
103
104	Ask:
105	- how does the game prime prosocial expectations before play begins?
106	- are strangers humanized or made more legible?
107	- are players encouraged to see teamwork as normal and beneficial?
108	- do tutorials, lobbies, or loading surfaces support prosocial norms?
109	- do group assembly tools help compatible people find each other or reform?
110	- is there any thematic or narrative framing that supports helping behavior?
111
112	Setup warning signs:
113	- pure mechanical onboarding with no social framing
114	- strangers feel faceless and disposable
115	- no expectation setting until after conflict starts
116	- no trust scaffolding before high-pressure teamwork
117
118	### 4. Audit Little Loops
119
120	Ask:
121	- what small repeatable prosocial actions happen during pla

People who liked this also viewed

6 picks

Type