17bce709de
🚀 Impact Significantly expands the capabilities of **Antigravity Awesome Skills** by integrating official skill collections from **Microsoft** and **Google Gemini**. This update increases the total skill count to **845+**, making the library even more comprehensive for AI coding assistants. ✨ Key Changes 1. New Official Skills - **Microsoft Skills**: Added a massive collection of official skills from [microsoft/skills](https://github.com/microsoft/skills). - Includes Azure, .NET, Python, TypeScript, and Semantic Kernel skills. - Preserves the original directory structure under `skills/official/microsoft/`. - Includes plugin skills from the `.github/plugins` directory. - **Gemini Skills**: Added official Gemini API development skills under `skills/gemini-api-dev/`. 2. New Scripts & Tooling - **`scripts/sync_microsoft_skills.py`**: A robust synchronization script that: - Clones the official Microsoft repository. - Preserves the original directory heirarchy. - Handles symlinks and plugin locations. - Generates attribution metadata. - **`scripts/tests/inspect_microsoft_repo.py`**: Debug tool to inspect the remote repository structure. - **`scripts/tests/test_comprehensive_coverage.py`**: Verification script to ensure 100% of skills are captured during sync. 3. Core Improvements - **`scripts/generate_index.py`**: Enhanced frontmatter parsing to safely handle unquoted values containing `@` symbols and commas (fixing issues with some Microsoft skill descriptions). - **`package.json`**: Added `sync:microsoft` and `sync:all-official` scripts for easy maintenance. 4. Documentation - Updated `README.md` to reflect the new skill counts (845+) and added Microsoft/Gemini to the provider list. - Updated `CATALOG.md` and `skills_index.json` with the new skills. 🧪 Verification - Ran `scripts/tests/test_comprehensive_coverage.py` to verify all Microsoft skills are detected. - Validated `generate_index.py` fixes by successfully indexing the new skills.
3.9 KiB
3.9 KiB
name, description
| name | description |
|---|---|
| wiki-onboarding | Generates two complementary onboarding guides — a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation for a codebase. |
Wiki Onboarding Guide Generator
Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase.
When to Activate
- User asks for onboarding docs or getting-started guides
- User runs
/deep-wiki:onboardcommand - User wants to help new team members understand a codebase
Language Detection
Scan the repository for build files to determine the primary language for code examples:
package.json/tsconfig.json→ TypeScript/JavaScript*.csproj/*.sln→ C# / .NETCargo.toml→ Rustpyproject.toml/setup.py/requirements.txt→ Pythongo.mod→ Gopom.xml/build.gradle→ Java
Guide 1: Principal-Level Onboarding
Audience: Senior/staff+ engineers who need the "why" behind decisions.
Required Sections
- System Philosophy & Design Principles — What invariants does the system maintain? What were the key design choices and why?
- Architecture Overview — Component map with Mermaid diagram. What owns what, communication patterns.
- Key Abstractions & Interfaces — The load-bearing abstractions everything depends on
- Decision Log — Major architectural decisions with context, alternatives considered, trade-offs
- Dependency Rationale — Why each major dependency was chosen, what it replaced
- Data Flow & State — How data moves through the system (traced from actual code, not guessed)
- Failure Modes & Error Handling — What breaks, how errors propagate, recovery patterns
- Performance Characteristics — Bottlenecks, scaling limits, hot paths
- Security Model — Auth, authorization, trust boundaries, data sensitivity
- Testing Strategy — What's tested, what isn't, testing philosophy
- Operational Concerns — Deployment, monitoring, feature flags, configuration
- Known Technical Debt — Honest assessment of shortcuts and their risks
Rules
- Every claim backed by
(file_path:line_number)citation - Minimum 3 Mermaid diagrams (architecture, data flow, dependency graph)
- All Mermaid diagrams use dark-mode colors (see wiki-vitepress skill)
- Focus on WHY decisions were made, not just WHAT exists
Guide 2: Zero-to-Hero Contributor Guide
Audience: New contributors who need step-by-step practical guidance.
Required Sections
- What This Project Does — 2-3 sentence elevator pitch
- Prerequisites — Tools, versions, accounts needed
- Environment Setup — Step-by-step with exact commands, expected output at each step
- Project Structure — Annotated directory tree (what lives where and why)
- Your First Task — End-to-end walkthrough of adding a simple feature
- Development Workflow — Branch strategy, commit conventions, PR process
- Running Tests — How to run tests, what to test, how to add a test
- Debugging Guide — Common issues and how to diagnose them
- Key Concepts — Domain-specific terminology explained with code examples
- Code Patterns — "If you want to add X, follow this pattern" templates
- Common Pitfalls — Mistakes every new contributor makes and how to avoid them
- Where to Get Help — Communication channels, documentation, key contacts
- Glossary — Terms used in the codebase that aren't obvious
- Quick Reference Card — Cheat sheet of most-used commands and patterns
Rules
- All code examples in the detected primary language
- Every command must be copy-pasteable
- Include expected output for verification steps
- Use Mermaid for workflow diagrams (dark-mode colors)
- Ground all claims in actual code — cite
(file_path:line_number)