leveling-up

name	leveling-up
description	Use when the user mentions 'level-up', 'leveling up', 'awakening', 'rebuilding', 'systematizing', 'thriving', or references personal transformation, existential recovery, resilience, habits, or purpose. Guides the creation and maintenance of narrative content in the level-up/ subject.

Skill: Leveling Up

This skill governs all work in the level-up/ subject of DevBook.

Core Principles

• Narrative, not academic. level-up/ describes the experience of the journey — what it feels like to hit bottom, awaken, rebuild, systematize, and thrive. It does NOT teach academic knowledge.
• Reference, don't duplicate. Every narrative file links to other DevBook subjects for the actual knowledge and theoretical grounding. Use Prerequisites and Next Steps to cross-reference broadly — philosophy, psychology, biology, neuroscience, sociology, or any subject that provides depth to the narrative.
• Journey arc. The stages follow a progression: the lowest point → awakening → rebuilding → systematizing → thriving. Each stage is a module inside level-up/.
• Narrative voice. Use first/second-person perspective — the reader is on this journey. Tone is direct, raw, and honest. No fluff, no padding.
• RPG-like learning experience. Structure the content as if the reader is playing a story-driven RPG. Every element should reinforce the feeling of progression, challenge, and reward — while remaining grounded in scientific theory and evidence. All mandatory section headings remain unchanged.

Code Examples

Code examples are optional in level-up content. The narrative is primary. Use code only when it serves as a metaphor or illustration that prose cannot achieve as effectively. When code is used, write it in a popular language (Python, JavaScript, TypeScript, Go, Rust, etc.) — do not default to a single language. Never force code into a section where it feels artificial.

RPG-Like Learning Experience

The level-up journey follows the universal RPG learning experience defined in AGENTS.md and content-writing skill, with these level-up-specific extensions:

The Narrative Arc

The overall journey follows a classic RPG narrative arc:

1. The Descent (intro/fundamentals) — the hero falls. The world is dark. The player learns the controls.
2. The Awakening (meaning) — the hero discovers the quest. The objective becomes clear.
3. The Grind (resilience, healthy-living, digital-wellness) — the hero builds strength through repeated challenges. Stats go up. Skills unlock.
4. The System (habits) — the hero builds automated routines. Progress becomes self-sustaining.
5. The Endgame (purpose, thriving) — the hero discovers their ultimate purpose. The final boss is faced.

Tone

The tone should feel like a wise NPC companion — someone who has walked the path before, who knows the dangers, who offers guidance without preaching. Not a tutorial. Not a lecture. A companion on the road.

When Creating Content

1. Read the parent index files and sibling files first to understand what exists.
2. Write narrative content following the mandatory 9-section format.
3. In Prerequisites, link to the relevant knowledge files from ANY subject in DevBook that supports the narrative — not just philosophy or psychology, but also biology, neuroscience, social sciences, or domain-specific knowledge as needed.
4. In Next Steps, link to the next stage in the journey and to any related knowledge elsewhere in DevBook.
5. Keep the focus on the experience of the stage, not the theory behind it.