sg-context

Prime the relevant files and decisions before the thread starts guessing about the codebase.

A context-loading skill that retrieves the most relevant repo surface before implementation begins.

Problem

What problem this solves

Fresh threads waste time rediscovering files, flows, and hotspots that should have been identified before the first implementation decision.

Outcome

What changes when it works

The thread starts with a tighter map of what matters, which reduces blind exploration and bad assumptions.

Why It Matters

What this changes for a solo founder

This skill pays off whenever startup cost is the problem. It makes the next move faster by shrinking the search space first.

When to use it

At the start of a task in a non-trivial repository
When the relevant code surface is unclear
When you want to reduce repeated exploration work across threads

What you give it

A task or problem statement
The current repository context

What you get back

A narrowed set of relevant files and entry points
A better starting map for implementation or review
Less context rebuild cost in fresh threads

Typical examples

/sg-context auth bug in onboarding
/sg-context pricing page update
/sg-context API export flow

Limits

It improves orientation; it does not replace deeper analysis
Bad project structure can still limit how much context can be recovered cleanly

Related Skills

See the rest of the loop around this move.

Plan & Decide

sg-spec

Turn a fuzzy request into an implementation-ready contract before code starts mutating the repo.

The spec-writing skill for shaping non-trivial work into a clear user story, behavior contract, executable task list, and chantier history.

Open skill page

Build & Fix

sg-start

Start implementation when the task is ready, and force a stronger path when it is not.

The main execution entrypoint for beginning real work after the problem and contract are clear enough, while keeping the chantier flow visible.

Open skill page

Build & Fix

sg-fix

Triage a bug fast, decide whether it is safe to patch now, and route it correctly.

The bug-first entrypoint for ShipGlows when the work starts from broken behavior instead of a new feature request.

Open skill page

Go Deeper

This public page explains the move. The repository explains the execution contract.

Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.

Documentation Overview Open skills on GitHub Return to the skills hub