القائمة
Codebase onboarding orchestrator that scans, documents, summarizes, and teaches a codebase to new developers or to the AI agent itself.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/InugamiDev/ultrathink-oss --skill onboardيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Unified design foundations — design system architecture, tokens, component specs, visual principles, creative vision, figma integration, plus brand design system loader (66 real brands via DESIGN.md). Absorbs design, design-system, design-systems, design-principles, design-router, creative-vision, figma, design-md.
Render, summarize, and present markdown documents and structured content in multiple output modes
Ultra UI skill - combines Google's DESIGN.md spec (machine-readable design tokens) with the ui-ux-pro-max knowledge base (91 styles, 161 palettes, 73 font pairings, 161 products, 104 UX guidelines, 25 chart types). Generates lint-clean DESIGN.md files, validates token references and WCAG contrast, exports Tailwind/DTCG tokens, and diffs design systems version-over-version.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | onboard |
| description | Codebase onboarding orchestrator that scans, documents, summarizes, and teaches a codebase to new developers or to the AI agent itself. |
| layer | orchestrator |
| category | orchestration |
| triggers | ["/onboard","onboard me to this codebase","explain this codebase","walk me through this project","learn this codebase","what does this project do"] |
| inputs | ["Codebase path or repository","Optional focus area (specific module, feature, or layer)","Optional audience level (junior, senior, architect)","Optional output format (interactive walkthrough, written guide, diagram-heavy)"] |
| outputs | ["Project overview and architecture summary","Module-by-module breakdown with key files","Data flow and dependency diagrams","Key patterns and conventions guide","Entry points and critical paths map","Onboarding guide document"] |
| linksTo | ["scout","research","sequential-thinking","mermaid","docs-writer","plan","brainstorm"] |
| linkedFrom | ["team","audit"] |
| preferredNextSkills | ["cook","audit","kanban"] |
| fallbackSkills | ["scout","research"] |
| riskLevel | low |
| memoryReadPolicy | full |
| memoryWritePolicy | always |
| sideEffects | ["Reads all source files (read-only)","May generate documentation files (if requested)","May generate diagram files (if requested)","Writes comprehensive codebase knowledge to memory for future sessions"] |
Onboard is the codebase learning and teaching orchestrator. It systematically explores a codebase and produces a comprehensive understanding that it can either present to a human developer or internalize for its own future use. Onboard answers the question every new team member asks: "How does this all fit together?"
Onboard goes beyond just listing files and directories. It traces data flows, identifies architectural patterns, maps dependencies, finds the critical paths, and explains the "why" behind design decisions when evidence is available. It produces both high-level summaries for quick orientation and deep-dive documentation for reference.
scout -- Perform a comprehensive codebase scan:
research (if needed) -- For unfamiliar frameworks or libraries, look up their purpose and patterns via Context7 to understand what role they play.mermaid -- Generate architecture diagrams:
sequential-thinking -- For complex architectural decisions, reason through why they were made based on evidence in the code.Generate the onboarding guide -- Structure the knowledge into a consumable format:
Section 1: Quick Start
Section 2: Architecture Overview
Section 3: Key Concepts
Section 4: Code Map
Section 5: Data Flow
Section 6: Development Guide
Invoke docs-writer (if writing to file) -- Format and write the onboarding guide as a document.
Project: [name] - [one-line description]
Stack: [language] + [framework] + [database] + [deployment]
Architecture: [pattern] with [key characteristic]
Entry: [main entry file] -> [routing] -> [handlers] -> [data layer]
Tests: [test runner] in [test directory], run with [command]
Key dirs: [dir1] (purpose), [dir2] (purpose), [dir3] (purpose)
Complete multi-section document as described in Phase 4.
Focused on architectural decisions, trade-offs, and technical debt with supporting diagrams.
| Condition | Action |
|---|---|
| Small project (< 50 files) | Quick summary format, skip deep architecture |
| Large project (> 500 files) | Full onboarding with all sections |
| Monorepo | Document each package/app separately, then integration |
| User asks about specific area | Focus onboard on that area, brief overview of rest |
| Unfamiliar technology detected | Invoke research via Context7 before documenting |
| Complex architecture | Invoke sequential-thinking to explain design rationale |
| Codebase already scanned in memory | Skip Phase 1, update only changed areas |
Use Onboard when encountering a new codebase for the first time, when a new team member joins, or when you need to refresh understanding of a project you haven't worked on recently.
Best for:
Not ideal for:
cook after onboarding)code-review)audit)User: /onboard Walk me through this codebase
Onboard workflow:
1. scout -> Scan: Next.js app, 234 files, TypeScript, Prisma, Tailwind
2. Architecture -> App Router pattern, API routes, Prisma data layer
3. mermaid -> System diagram, module deps, auth flow, data creation flow
4. Patterns -> Feature-based directories, custom hooks pattern, Zod validation
5. Document -> Full 6-section onboarding guide
6. Present -> Deliver guide, offer to deep-dive on any section
User: /onboard Explain the payment system in this codebase
Onboard workflow:
1. scout -> Focus scan on payment-related files and dependencies
2. Architecture -> Payment module boundaries, Stripe integration points
3. mermaid -> Payment flow diagram (checkout -> webhook -> fulfillment)
4. Patterns -> Payment-specific error handling, retry logic, idempotency
5. Document -> Payment system deep-dive document
6. Present -> Walkthrough of the payment flow with key files
User: /onboard Learn this codebase so you can help me effectively
Onboard workflow:
1. scout -> Full codebase scan
2. Architecture -> Map all modules and patterns
3. Key abstractions -> Identify core utilities, shared types, conventions
4. Memory write -> Store complete codebase map, conventions, and patterns
5. Present -> Brief summary to user, deep knowledge stored for future use
6. Ready -> "I've learned the codebase. Here's a quick overview..."
User: /onboard I want to contribute to this open-source project, help me understand it
Onboard workflow:
1. scout -> Scan codebase + look for CONTRIBUTING.md, CODE_OF_CONDUCT.md
2. Architecture -> Map the project structure and key modules
3. research -> Check project docs, issue tracker patterns, PR conventions
4. Document -> Contributor-focused guide: where to add code, test patterns,
PR expectations, coding style
5. Present -> "Here's how this project works and how to contribute..."