How to use Gamesense

Agent setup

Copy instructions for your agent

Paste this into your coding agent so it knows the simple retrieval rule.

Copy instructions

Gamesense is Grindhub’s shared wiki for product knowledge, runbooks, architecture notes, feature plans, and operational context.

The goal is simple:

Canonical knowledge lives in normal human-readable docs.
Agents retrieve those same docs through flashback-mcp before working.

Source of truth

The wiki pages under src/content/docs/** are the source of truth. They should contain the useful details that humans, developers, and agents need.

Avoid maintaining separate “human docs” and “agent docs” for the same feature. If a detail matters, put it in the wiki.

Agent access through flashback-mcp

Agents should use Gamesense through flashback-mcp tools, for example:

• search Gamesense for relevant pages
• read a specific Gamesense page by slug
• load all required pages for a feature such as Flashback Challenges

Every repo that depends on Gamesense should say this in its AGENTS.md:

Use Gamesense through flashback-mcp before making feature-specific changes. If Gamesense or flashback-mcp access fails, clearly warn the human that required project knowledge could not be loaded.

For example, when working on Flashback live challenges, agents should load the Flashback Challenges wiki pages before touching /challenges, challenge API routes, FACEIT sync, scoreboards, analytics, demo-pipeline integration, or related Supabase tables/RPCs.

Human workflow

Use Gamesense like a classic wiki:

1. Open the relevant feature or software page.
2. Read the product plan, architecture, debugging guide, and technical debt where applicable.
3. Update the page when behavior, decisions, architecture, operations, or release criteria change.

Feature documentation rule

New feature sections should follow the Feature Template structure unless there is a strong reason not to.

The standard structure is:

• parent feature page / overview
• product plan
• architecture
• debugging
• change checklist
• technical debt

This makes Gamesense predictable for humans and lets agents load the right context consistently.

Diagram rule

Interactive diagrams should sit beside nearby prose when the page has enough horizontal space, so readers can scan the text and diagram together.

Every interactive diagram must include a fullscreen button. If a diagram is too dense at inline size, readers must be able to open it fullscreen without leaving the page.

What Gamesense is not

Gamesense is not meant to be a second implementation backlog hidden from the team.

Do not hide important product decisions inside agent-only files. Agents should consume the same pages the team reads.

Optional future generated files

If a future agent framework needs a special skill/index format, generate it from these wiki pages instead of hand-maintaining a second source of truth.