원클릭으로 Manus에서 모든 스킬 실행

sprang-onboard

스타1

포크1

업데이트2026년 6월 4일 08:48

Guided architecture tour for new team members — adapts to junior, senior, or PM persona. Use when the user says "/sprang-onboard", "onboard me", "give me a tour", "I'm new to this codebase", or "walk me through the architecture".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

FavioVazquez

FavioVazquez/sprang

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

소프트웨어 개발자컴퓨터 및 수학직·SOC 15-1252

SKILL.md

readonly

name	sprang-onboard
description	Guided architecture tour for new team members — adapts to junior, senior, or PM persona. Use when the user says "/sprang-onboard", "onboard me", "give me a tour", "I'm new to this codebase", or "walk me through the architecture".

Guided architecture tour for new team members.

Ensure .sprang/knowledge-graph.json exists with phase: complete. If not, run /sprang-analyze first.
Call sprang_health to summarize total nodes, edges, top risk areas, and smell counts.
Ask about persona (or infer from context):
- non-technical — business-level overview, domain names, no code details
- junior — full tour with explanations (default)
- experienced — skip basics, go straight to risk areas and architecture decisions
Call sprang_tour with the appropriate persona (junior, senior, or pm) to load the guided tour. Present each step with its explanation.
For any tour node with risk_score > 0.6, call sprang_why to surface decision context and team annotations.
Call sprang_node on the top 3 highest-risk tour nodes to show layer membership, in/out degree, and annotation status.
Call sprang_domain to list all business domains and explain how code maps to real-world processes.
Highlight the top 3 highest-risk nodes the newcomer must be aware of before making changes.
Recommend:
- Read .sprang/SPRANG_REPORT.md for the full architectural summary
- Run /sprang-diff before submitting any PR
- Open the dashboard: pnpm --filter @sprang/dashboard dev → switch to the Learn tab

이 저장소의 다른 Skills

같은 저장소

sprang-analyze

FavioVazquez/sprang

Analyze a codebase to produce a rich semantic knowledge graph — file summaries, architecture layers, guided tour, domain map, risk scores. Use when the user says "/sprang-analyze", "analyze the codebase", "full analysis", or "run sprang-analyze".

Build or refresh the Sprang knowledge graph for this workspace. Use when the user says "/sprang", "build the knowledge graph", "scan the codebase", "index this project", or "run sprang".

2026-06-171

sprang

FavioVazquez/sprang

Build or refresh the Sprang knowledge graph for this workspace. Use when the user says "/sprang", "build the knowledge graph", "scan the codebase", "index this project", or "run sprang".

Browse and write team annotations attached to graph nodes — institutional knowledge, decision history, ownership. Use when the user says "/sprang-team", "add annotation", "team knowledge", "who owns this", or "document this decision".

2026-06-081

name	sprang-onboard
description	Guided architecture tour for new team members — adapts to junior, senior, or PM persona. Use when the user says "/sprang-onboard", "onboard me", "give me a tour", "I'm new to this codebase", or "walk me through the architecture".

Guided architecture tour for new team members.

Ensure .sprang/knowledge-graph.json exists with phase: complete. If not, run /sprang-analyze first.
Call sprang_health to summarize total nodes, edges, top risk areas, and smell counts.
Ask about persona (or infer from context):
- non-technical — business-level overview, domain names, no code details
- junior — full tour with explanations (default)
- experienced — skip basics, go straight to risk areas and architecture decisions
Call sprang_tour with the appropriate persona (junior, senior, or pm) to load the guided tour. Present each step with its explanation.
For any tour node with risk_score > 0.6, call sprang_why to surface decision context and team annotations.
Call sprang_node on the top 3 highest-risk tour nodes to show layer membership, in/out degree, and annotation status.
Call sprang_domain to list all business domains and explain how code maps to real-world processes.
Highlight the top 3 highest-risk nodes the newcomer must be aware of before making changes.
Recommend:
- Read .sprang/SPRANG_REPORT.md for the full architectural summary
- Run /sprang-diff before submitting any PR
- Open the dashboard: pnpm --filter @sprang/dashboard dev → switch to the Learn tab