Context Window Awareness
argument-hint: "[genre or theme hint, or 'open'] [--review full|lean|solo]"
Category: design Source: Donchitos/Claude-Code-Game-StudiosContext Window Awareness
What Is This
Context Window Awareness is a critical capability within the Happycapy Skills platform's "brainstorm" skill, designed to ensure that the AI maintains a coherent understanding of ongoing ideation sessions. This skill enables the AI to track and recall relevant information across multiple interactions, preserving the creative thread during collaborative game concept development. By leveraging context window awareness, the platform avoids redundant questioning, builds upon previous user contributions, and ensures a seamless collaborative experience.
In the context of the "brainstorm" skill, context window awareness refers specifically to the AI's ability to:
- Parse and remember user-provided arguments and preferences (such as genre hints or review mode)
- Detect and incorporate existing design documents (like
game-concept.mdandgame-pillars.md) - Maintain continuity during multi-phase, interactive ideation sessions
- Store and reference user responses at key decision points with the
AskUserQuestionmechanism
This ensures that every brainstorming session is cumulative rather than repetitive, with the AI acting as a creative collaborator that builds intelligently on both user input and previously established design groundwork.
Why Use It
Context window awareness is essential for any interactive, multi-turn design tool, especially in tasks as complex as game concept ideation. Without it, the AI would behave statelessly, leading to:
- Repeated or irrelevant questions
- Loss of user vision or session context
- Overwriting or ignoring established design pillars and concepts
By maintaining a contextual thread, this skill allows for:
- Efficient, non-redundant ideation
- Consistency in design decisions
- Enhanced user experience, as users feel genuinely heard and their contributions valued
- The ability to resume or build upon previous work without loss of fidelity
This is especially important in a professional studio setting, where design sessions can span multiple sittings, involve multiple contributors, or require iterative refinement.
How to Use It
When invoking the "brainstorm" skill, context window awareness is automatically activated as part of the skill’s workflow. Here is how it operates:
1. Argument Parsing and Review Mode Resolution
Upon invocation, the skill parses any provided arguments, such as a genre or theme hint and the desired review mode. The review mode is determined via a prioritized check:
## Pseudocode for review mode resolution
if '--review [full|lean|solo]' in arguments:
review_mode = arguments['--review']
elif os.path.exists('production/review-mode.txt'):
with open('production/review-mode.txt') as f:
review_mode = f.read().strip()
else:
review_mode = 'lean'
This ensures that the user's intent is respected throughout the session and that the review mode remains consistent across all "director gates" for a given run.
2. Integration with Existing Design Documents
Before generating new ideas, the skill checks for existing concept work in design/gdd/game-concept.md and design/gdd/game-pillars.md. If these files exist, their content is incorporated into the current session:
concept = None
pillars = None
if os.path.exists('design/gdd/game-concept.md'):
with open('design/gdd/game-concept.md') as f:
concept = f.read()
if os.path.exists('design/gdd/game-pillars.md'):
with open('design/gdd/game-pillars.md') as f:
pillars = f.read()
This prevents redundant ideation and ensures continuity.
3. Interactive, Context-Aware Ideation
Throughout the brainstorming process, the skill uses the AskUserQuestion tool to engage the user at key points. Each response is stored and referenced in subsequent phases, allowing the AI to build upon prior answers instead of starting from scratch each time.
Example interaction flow:
user_genre = AskUserQuestion("What genre are you interested in?")
## Store user_genre in session context
...
user_mechanics = AskUserQuestion("Which core gameplay mechanics appeal to you?")
## Reference user_genre and user_mechanics in subsequent prompts
This approach ensures that the session is both collaborative and context-rich.
When to Use It
Context window awareness within the "brainstorm" skill is most valuable when:
- Initiating a new game concept from scratch or a high-level theme
- Iteratively refining an existing concept over multiple sessions
- Collaborating with multiple users or creative leads across a project
- Ensuring design coherence as new ideas are layered onto established pillars
It is particularly useful in environments where design documents evolve over time and must remain consistent with the team's goals and previous decisions.
Important Notes
- Persistence: Context is maintained for the duration of the brainstorming run, but long-term persistence depends on explicit saving to design documents.
- Review Mode Consistency: The review mode, once set, should not be changed mid-session, as this can disrupt the contextual thread.
- Scope: Context window awareness is scoped to the current session and the accessible files; external or historical context must be explicitly reintroduced if needed.
- User Interaction: The skill will not proceed silently-collaborative exploration is enforced by requiring user input at each significant decision point.
- Redundancy Avoidance: The system is designed to detect and build upon existing work, preventing unnecessary repetition and ensuring efficient use of the user’s creative input.
By leveraging context window awareness, the "brainstorm" skill provides a robust, studio-grade ideation partner that respects both user vision and the iterative nature of creative design.