Skill Introduction

Overview

Use when you need to generate an onboarding guide for new team members joining a project

Core value

Turns reusable Documentation know-how into an installable skill, helping users complete github, community, antigravity-skills, business-knowledge work faster.

Target users

Developers, testers, and maintainers who handle Documentation tasks in Focus Code.
Teams that already trust workflows or content from Lum1104.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community, antigravity-skills, business-knowledge that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Documentation, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, antigravity-skills, business-knowledge, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install understand-onboard-9f8ff3

View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

name: understand-onboard description: Use when you need to generate an onboarding guide for new team members joining a project

/understand-onboard

Generate a comprehensive onboarding guide from the project's knowledge graph.

Graph Structure Reference

The knowledge graph JSON has this structure:

project — {name, description, languages, frameworks, analyzedAt, gitCommitHash}
nodes[] — each has {id, type, name, filePath, summary, tags[], complexity, languageNotes?}
- Node types: file, function, class, module, concept
- IDs: file:path, function:path:name, class:path:name
edges[] — each has {source, target, type, direction, weight}
- Key types: imports, contains, calls, depends_on
layers[] — each has {id, name, description, nodeIds[]}
tour[] — each has {order, title, description, nodeIds[]}

How to Read Efficiently

Use Grep to search within the JSON for relevant entries BEFORE reading the full file
Only read sections you need — don't dump the entire graph into context
Node names and summaries are the most useful fields for understanding
Edges tell you how components connect — follow imports and calls for dependency chains

Instructions

Check that .understand-anything/knowledge-graph.json exists. If not, tell the user to run /understand first.
Read project metadata — use Grep or Read with a line limit to extract the "project" section (name, description, languages, frameworks).
Read layers — Grep for "layers" to get the full layers array. These define the architecture and will structure the guide.
Read the tour — Grep for "tour" to get the guided walkthrough steps. These provide the recommended learning path.
Read file-level nodes only — use Grep to find nodes with "type": "file" in the knowledge graph. Skip function-level and class-level nodes to keep the guide high-level. Extract each file node's name, filePath, summary, and complexity.
Identify complexity hotspots — from the file-level nodes, find those with the highest complexity values. These are areas new developers should approach carefully.
Generate the onboarding guide with these sections:
- Project Overview: name, languages, frameworks, description (from project metadata)
- Architecture Layers: each layer's name, description, and key files (from layers + file nodes)
- Key Concepts: important patterns and design decisions (from node summaries and tags)
- Guided Tour: step-by-step walkthrough (from the tour section)
- File Map: what each key file does (from file-level nodes, organized by layer)
- Complexity Hotspots: areas to approach carefully (from complexity values)
Format as clean markdown
Offer to save the guide to docs/ONBOARDING.md in the project
Suggest the user commit it to the repo for the team

understand onboard