Skill

steering-docs

Generate persistent project context files — product.md, tech.md, structure.md — that guide every coding session. Use when setting up a new project, creating project context, or when the user mentions "steering documents", "project context", "product vision", or "tech stack documentation".

From project-orchestrator
Install
1
Run in your terminal
$
npx claudepluginhub vivekmano27/agent-orchestrator --plugin project-orchestrator
Tool Access

This skill is limited to using the following tools:

ReadWriteEditGrepGlob
Skill Content

Steering Documents Skill

Create three persistent context files in .claude/steering/ that the agent reads at the start of every session.

1. product.md — Product Context

# Product Context

## Vision
[One paragraph: what this product will become]

## Problem Statement
[What pain point does this solve?]

## Target Users
- Primary: [Who, demographics, tech proficiency]
- Secondary: [Who else uses it]

## Success Metrics
| Metric | Target | Measurement |
|--------|--------|-------------|
| [KPI]  | [Goal] | [How to measure] |

## Competitive Landscape
| Competitor | Strengths | Our Differentiation |
|-----------|-----------|-------------------|
| [Name]   | [What they do well] | [Why we're different] |

2. tech.md — Technical Context

# Technical Context

## Stack
- Language: [e.g., TypeScript 5.4]
- Framework: [e.g., Next.js 14 App Router]
- Database: [e.g., PostgreSQL 16 via Prisma]
- Auth: [e.g., NextAuth.js v5]
- Hosting: [e.g., Vercel + Supabase]
- CI/CD: [e.g., GitHub Actions]

## Architecture Pattern
[e.g., "Modular monolith with clean architecture layers"]

## Key Libraries
| Library | Purpose | Version |
|---------|---------|---------|
| [name]  | [what it does] | [version] |

## Performance Targets
- Page load: < [X]s
- API response: < [X]ms
- Lighthouse score: > [X]

## Third-Party Services
| Service | Purpose | Env Var |
|---------|---------|---------|
| [name]  | [use]   | [VAR_NAME] |

3. structure.md — Project Structure

# Project Structure

## Directory Layout

src/ ├── app/ → Next.js routes and pages ├── components/ → Reusable UI components │ ├── ui/ → Primitive components (Button, Input) │ └── features/ → Feature-specific components ├── lib/ → Shared utilities and helpers ├── services/ → Business logic and API calls ├── models/ → Data models and types ├── hooks/ → Custom React hooks └── config/ → App configuration


## Naming Conventions
- Files: kebab-case (user-profile.tsx)
- Components: PascalCase (UserProfile)
- Functions: camelCase (getUserProfile)
- Constants: SCREAMING_SNAKE (MAX_RETRIES)
- Types: PascalCase with suffix (UserProfileProps)

## Module Rules
- Components NEVER import from services directly — use hooks
- Services NEVER import from components
- Models are shared across all layers
- Config is read-only at runtime
Stats
Parent Repo Stars0
Parent Repo Forks0
Last CommitMar 15, 2026