steering

Analyze codebases to generate steering documents and persistent project memory.

12|2|Updated Nov 26, 2025

Search Tags:#architecture #documentation #consistency #collaboration #memory #steering

Ready to run

npx skills add https://github.com/nahisaho/CodeGraphMCPServer --skill steering-nahisaho

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: steering
Source: https://github.com/nahisaho/CodeGraphMCPServer/tree/main/.claude/skills/steering
Command: npx skills add https://github.com/nahisaho/CodeGraphMCPServer --skill steering-nahisaho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill maintains a persistent, shared memory of the project's architecture, technical stack, and business context to guide all agents. It ensures consistent decisions, faster onboarding, and cohesive collaboration across tasks.

Core Features & Use Cases

Memory generation: Create and maintain steering documents that capture architecture patterns, directory structures, and product context.
Knowledge sharing: Synchronize steering content across agents to ensure a unified understanding of the project.
Onboarding & alignment: Quickly bootstrap memory for new projects or teams, reducing setup time.

Quick Start

Start by bootstrapping steering memory from the repository root, then review steering/structure.md, steering/tech.md, and steering/product.md for context.

Frequently Asked Questions about steering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain a shared project memory across multiple agents and sessions?▼

Architecture steering generates and maintains persistent steering documents describing your codebase's patterns, technology stack, and business context. It analyzes directory structure, package files, and framework signatures to create structure.md, tech.md, and product.md artifacts stored in a memories/ directory for cross-session collaboration and unified agent understanding.

Can I use architecture steering with monorepo and multi-repository projects?▼

Yes, steering applies to both monorepo and multi-repository projects. It analyzes directory hierarchies, package dependencies, and framework signatures across repositories to detect architecture patterns and extract the complete technology stack regardless of repository structure.

How do I bootstrap project memory for a new team or codebase?▼

Run steering from your repository root to analyze the codebase and auto-generate steering documents. It extracts architecture patterns, technology stack, and business context from your code structure and documentation, then stores ADR-style decisions and workflows in memories/ for immediate team onboarding and alignment.

What does steering capture about my project's architecture and technology stack?▼

Steering detects architecture patterns, documents directory structures, identifies frameworks and technologies in use, captures business context, and generates steering artifacts. It produces structure.md for architecture layout, tech.md for technology decisions, and product.md for business goals in both English and Japanese.

How does steering ensure consistent architectural decisions across development cycles?▼

Steering stores ADR-style architectural decisions and workflows in a persistent memories/ directory. Agents access this shared memory across sessions to make consistent decisions aligned with documented patterns, reducing conflicts and maintaining cohesive collaboration.

Do I need documentation already in place to use architecture steering?▼

No. Steering analyzes your codebase directly—directory structure, package files, framework signatures—to generate steering documents. Existing documentation accelerates context extraction, but steering produces artifacts from code structure alone.