@ngxtm/devkit 3.15.0 → 3.16.0

package/skills/webapp-testing/SKILL.md

@@ -1,7 +1,9 @@
 ---
 name: webapp-testing
-description: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
+description: "Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browse..."
 license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
 ---
 
 # Web Application Testing
@@ -93,4 +95,7 @@ with sync_playwright() as p:
 - **examples/** - Examples showing common patterns:
   - `element_discovery.py` - Discovering buttons, links, and inputs on a page
   - `static_html_automation.py` - Using file:// URLs for local HTML
-  - `console_logging.py` - Capturing console logs during automation
+  - `console_logging.py` - Capturing console logs during automation
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/webflow-automation/SKILL.md

@@ -0,0 +1,241 @@
+---
+name: webflow-automation
+description: "Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Webflow Automation via Rube MCP
+
+Automate Webflow operations including CMS collection management, site publishing, page inspection, asset uploads, and ecommerce order retrieval through Composio's Webflow toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Webflow connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `webflow`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `webflow`
+3. If connection is not ACTIVE, follow the returned auth link to complete Webflow OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage CMS Collection Items
+
+**When to use**: User wants to create, update, list, or delete items in Webflow CMS collections (blog posts, products, team members, etc.)
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - List sites to find the target site_id [Prerequisite]
+2. `WEBFLOW_LIST_COLLECTIONS` - List all collections for the site [Prerequisite]
+3. `WEBFLOW_GET_COLLECTION` - Get collection schema to find valid field slugs [Prerequisite for create/update]
+4. `WEBFLOW_LIST_COLLECTION_ITEMS` - List existing items with filtering and pagination [Optional]
+5. `WEBFLOW_GET_COLLECTION_ITEM` - Get a specific item's full details [Optional]
+6. `WEBFLOW_CREATE_COLLECTION_ITEM` - Create a new item with field data [Required for creation]
+7. `WEBFLOW_UPDATE_COLLECTION_ITEM` - Update an existing item's fields [Required for updates]
+8. `WEBFLOW_DELETE_COLLECTION_ITEM` - Permanently remove an item [Optional]
+9. `WEBFLOW_PUBLISH_SITE` - Publish changes to make them live [Optional]
+
+**Key parameters for CREATE_COLLECTION_ITEM**:
+- `collection_id`: 24-character hex string from LIST_COLLECTIONS
+- `field_data`: Object with field slug keys (NOT display names); must include `name` and `slug`
+- `field_data.name`: Display name for the item
+- `field_data.slug`: URL-friendly identifier (lowercase, hyphens, no spaces)
+- `is_draft`: Boolean to create as draft (default false)
+
+**Key parameters for UPDATE_COLLECTION_ITEM**:
+- `collection_id`: Collection identifier
+- `item_id`: 24-character hex MongoDB ObjectId of the existing item
+- `fields`: Object with field slug keys and new values
+- `live`: Boolean to publish changes immediately (default false)
+
+**Field value types**:
+- Text/Email/Link/Date: string
+- Number: integer or float
+- Boolean: true/false
+- Image: `{"url": "...", "alt": "...", "fileId": "..."}`
+- Multi-reference: array of reference ID strings
+- Multi-image: array of image objects
+- Option: option ID string
+
+**Pitfalls**:
+- Field keys must use the exact field `slug` from the collection schema, NOT display names
+- Always call `GET_COLLECTION` first to retrieve the schema and identify correct field slugs
+- `CREATE_COLLECTION_ITEM` requires `name` and `slug` in `field_data`
+- `UPDATE_COLLECTION_ITEM` cannot create new items; it requires a valid existing `item_id`
+- `item_id` must be a 24-character hexadecimal MongoDB ObjectId
+- Slug must be lowercase alphanumeric with hyphens: `^[a-z0-9]+(?:-[a-z0-9]+)*$`
+- CMS items are staged; use `PUBLISH_SITE` or set `live: true` to push to production
+
+### 2. Manage Sites and Publishing
+
+**When to use**: User wants to list sites, inspect site configuration, or publish staged changes
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - List all accessible sites [Required]
+2. `WEBFLOW_GET_SITE_INFO` - Get detailed site metadata including domains and settings [Optional]
+3. `WEBFLOW_PUBLISH_SITE` - Deploy all staged changes to live site [Required for publishing]
+
+**Key parameters for PUBLISH_SITE**:
+- `site_id`: Site identifier from LIST_WEBFLOW_SITES
+- `custom_domains`: Array of custom domain ID strings (from GET_SITE_INFO)
+- `publish_to_webflow_subdomain`: Boolean to publish to `{shortName}.webflow.io`
+- At least one of `custom_domains` or `publish_to_webflow_subdomain` must be specified
+
+**Pitfalls**:
+- `PUBLISH_SITE` republishes ALL staged changes for selected domains -- verify no unintended drafts are pending
+- Rate limit: 1 successful publish per minute
+- For sites without custom domains, must set `publish_to_webflow_subdomain: true`
+- `custom_domains` expects domain IDs (hex strings), not domain names
+- Publishing is a production action -- always confirm with the user first
+
+### 3. Manage Pages
+
+**When to use**: User wants to list pages, inspect page metadata, or examine page DOM structure
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - Find the target site_id [Prerequisite]
+2. `WEBFLOW_LIST_PAGES` - List all pages for a site with pagination [Required]
+3. `WEBFLOW_GET_PAGE` - Get detailed metadata for a specific page [Optional]
+4. `WEBFLOW_GET_PAGE_DOM` - Get the DOM/content node structure of a static page [Optional]
+
+**Key parameters**:
+- `site_id`: Site identifier (required for list pages)
+- `page_id`: 24-character hex page identifier
+- `locale_id`: Optional locale filter for multi-language sites
+- `limit`: Max results per page (max 100)
+- `offset`: Pagination offset
+
+**Pitfalls**:
+- `LIST_PAGES` paginates via offset/limit; iterate when sites have many pages
+- Page IDs are 24-character hex strings matching pattern `^[0-9a-fA-F]{24}$`
+- `GET_PAGE_DOM` returns the node structure, not rendered HTML
+- Pages include both static and CMS-driven pages
+
+### 4. Upload Assets
+
+**When to use**: User wants to upload images, files, or other assets to a Webflow site
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - Find the target site_id [Prerequisite]
+2. `WEBFLOW_UPLOAD_ASSET` - Upload a file with base64-encoded content [Required]
+
+**Key parameters**:
+- `site_id`: Site identifier
+- `file_name`: Name of the file (e.g., `"logo.png"`)
+- `file_content`: Base64-encoded binary content of the file (NOT a placeholder or URL)
+- `content_type`: MIME type (e.g., `"image/png"`, `"image/jpeg"`, `"application/pdf"`)
+- `md5`: MD5 hash of the raw file bytes (32-character hex string)
+- `asset_folder_id`: Optional folder placement
+
+**Pitfalls**:
+- `file_content` must be actual base64-encoded data, NOT a variable reference or placeholder
+- `md5` must be computed from the raw bytes, not from the base64 string
+- This is a two-step process internally: generates an S3 pre-signed URL, then uploads
+- Large files may encounter timeouts; keep uploads reasonable in size
+
+### 5. Manage Ecommerce Orders
+
+**When to use**: User wants to view ecommerce orders from a Webflow site
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - Find the site with ecommerce enabled [Prerequisite]
+2. `WEBFLOW_LIST_ORDERS` - List all orders with optional status filtering [Required]
+3. `WEBFLOW_GET_ORDER` - Get detailed information for a specific order [Optional]
+
+**Key parameters**:
+- `site_id`: Site identifier (must have ecommerce enabled)
+- `order_id`: Specific order identifier for detailed retrieval
+- `status`: Filter orders by status
+
+**Pitfalls**:
+- Ecommerce must be enabled on the Webflow site for order endpoints to work
+- Order endpoints are read-only; no create/update/delete for orders through these tools
+
+## Common Patterns
+
+### ID Resolution
+Webflow uses 24-character hexadecimal IDs throughout:
+- **Site ID**: `WEBFLOW_LIST_WEBFLOW_SITES` -- find by name, capture `id`
+- **Collection ID**: `WEBFLOW_LIST_COLLECTIONS` with `site_id`
+- **Item ID**: `WEBFLOW_LIST_COLLECTION_ITEMS` with `collection_id`
+- **Page ID**: `WEBFLOW_LIST_PAGES` with `site_id`
+- **Domain IDs**: `WEBFLOW_GET_SITE_INFO` -- found in `customDomains` array
+- **Field slugs**: `WEBFLOW_GET_COLLECTION` -- found in collection `fields` array
+
+### Pagination
+Webflow uses offset-based pagination:
+- `offset`: Starting index (0-based)
+- `limit`: Items per page (max 100)
+- Increment offset by limit until fewer results than limit are returned
+- Available on: LIST_COLLECTION_ITEMS, LIST_PAGES
+
+### CMS Workflow
+Typical CMS content creation flow:
+1. Get site_id from LIST_WEBFLOW_SITES
+2. Get collection_id from LIST_COLLECTIONS
+3. Get field schema from GET_COLLECTION (to learn field slugs)
+4. Create/update items using correct field slugs
+5. Publish site to make changes live
+
+## Known Pitfalls
+
+### ID Formats
+- All Webflow IDs are 24-character hexadecimal strings (MongoDB ObjectIds)
+- Example: `580e63fc8c9a982ac9b8b745`
+- Pattern: `^[0-9a-fA-F]{24}$`
+- Invalid IDs return 404 errors
+
+### Field Slugs vs Display Names
+- CMS operations require field `slug` values, NOT display names
+- A field with displayName "Author Name" might have slug `author-name`
+- Always call `GET_COLLECTION` to discover correct field slugs
+- Using wrong field names silently ignores the data or causes validation errors
+
+### Publishing
+- `PUBLISH_SITE` deploys ALL staged changes, not just specific items
+- Rate limited to 1 publish per minute
+- Must specify at least one domain target (custom or webflow subdomain)
+- This is a production-affecting action; always confirm intent
+
+### Authentication Scopes
+- Different operations require different OAuth scopes: `sites:read`, `cms:read`, `cms:write`, `pages:read`
+- A 403 error typically means missing OAuth scopes
+- Check connection permissions if operations fail with authorization errors
+
+### Destructive Operations
+- `DELETE_COLLECTION_ITEM` permanently removes CMS items
+- `PUBLISH_SITE` makes all staged changes live immediately
+- Always confirm with the user before executing these actions
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List sites | `WEBFLOW_LIST_WEBFLOW_SITES` | (none) |
+| Get site info | `WEBFLOW_GET_SITE_INFO` | `site_id` |
+| Publish site | `WEBFLOW_PUBLISH_SITE` | `site_id`, `custom_domains` or `publish_to_webflow_subdomain` |
+| List collections | `WEBFLOW_LIST_COLLECTIONS` | `site_id` |
+| Get collection schema | `WEBFLOW_GET_COLLECTION` | `collection_id` |
+| List collection items | `WEBFLOW_LIST_COLLECTION_ITEMS` | `collection_id`, `limit`, `offset` |
+| Get collection item | `WEBFLOW_GET_COLLECTION_ITEM` | `collection_id`, `item_id` |
+| Create collection item | `WEBFLOW_CREATE_COLLECTION_ITEM` | `collection_id`, `field_data` |
+| Update collection item | `WEBFLOW_UPDATE_COLLECTION_ITEM` | `collection_id`, `item_id`, `fields` |
+| Delete collection item | `WEBFLOW_DELETE_COLLECTION_ITEM` | `collection_id`, `item_id` |
+| List pages | `WEBFLOW_LIST_PAGES` | `site_id`, `limit`, `offset` |
+| Get page | `WEBFLOW_GET_PAGE` | `page_id` |
+| Get page DOM | `WEBFLOW_GET_PAGE_DOM` | `page_id` |
+| Upload asset | `WEBFLOW_UPLOAD_ASSET` | `site_id`, `file_name`, `file_content`, `content_type`, `md5` |
+| List orders | `WEBFLOW_LIST_ORDERS` | `site_id`, `status` |
+| Get order | `WEBFLOW_GET_ORDER` | `site_id`, `order_id` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/whatsapp-automation/SKILL.md

@@ -0,0 +1,219 @@
+---
+name: whatsapp-automation
+description: "Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# WhatsApp Business Automation via Rube MCP
+
+Automate WhatsApp Business operations through Composio's WhatsApp toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active WhatsApp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `whatsapp`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+- WhatsApp Business API account required (not regular WhatsApp)
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `whatsapp`
+3. If connection is not ACTIVE, follow the returned auth link to complete WhatsApp Business setup
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send a Text Message
+
+**When to use**: User wants to send a text message to a WhatsApp contact
+
+**Tool sequence**:
+1. `WHATSAPP_GET_PHONE_NUMBERS` - List available business phone numbers [Prerequisite]
+2. `WHATSAPP_SEND_MESSAGE` - Send a text message [Required]
+
+**Key parameters**:
+- `to`: Recipient phone number in international format (e.g., '+14155551234')
+- `body`: Message text content
+- `phone_number_id`: Business phone number ID to send from
+
+**Pitfalls**:
+- Phone numbers must be in international E.164 format with country code
+- Messages outside the 24-hour window require approved templates
+- The 24-hour window starts when the customer last messaged you
+- Business-initiated conversations require template messages first
+
+### 2. Send Template Messages
+
+**When to use**: User wants to send pre-approved template messages for outbound communication
+
+**Tool sequence**:
+1. `WHATSAPP_GET_MESSAGE_TEMPLATES` - List available templates [Prerequisite]
+2. `WHATSAPP_GET_TEMPLATE_STATUS` - Check template approval status [Optional]
+3. `WHATSAPP_SEND_TEMPLATE_MESSAGE` - Send the template message [Required]
+
+**Key parameters**:
+- `template_name`: Name of the approved template
+- `language_code`: Template language (e.g., 'en_US')
+- `to`: Recipient phone number
+- `components`: Template variable values and parameters
+
+**Pitfalls**:
+- Templates must be approved by Meta before use
+- Template variables must match the expected count and format
+- Sending unapproved or rejected templates returns errors
+- Language code must match an approved translation of the template
+
+### 3. Send Media Messages
+
+**When to use**: User wants to send images, documents, or other media
+
+**Tool sequence**:
+1. `WHATSAPP_UPLOAD_MEDIA` - Upload media to WhatsApp servers [Required]
+2. `WHATSAPP_SEND_MEDIA_BY_ID` - Send media using the uploaded media ID [Required]
+   OR
+3. `WHATSAPP_SEND_MEDIA` - Send media using a public URL [Alternative]
+
+**Key parameters**:
+- `media_url`: Public URL of the media (for SEND_MEDIA)
+- `media_id`: ID from upload response (for SEND_MEDIA_BY_ID)
+- `type`: Media type ('image', 'document', 'audio', 'video', 'sticker')
+- `caption`: Optional caption for the media
+
+**Pitfalls**:
+- Uploaded media IDs are temporary and expire after a period
+- Media size limits vary by type (images: 5MB, videos: 16MB, documents: 100MB)
+- Supported formats: images (JPEG, PNG), videos (MP4, 3GPP), documents (PDF, etc.)
+- SEND_MEDIA requires a publicly accessible HTTPS URL
+
+### 4. Reply to Messages
+
+**When to use**: User wants to reply to an incoming WhatsApp message
+
+**Tool sequence**:
+1. `WHATSAPP_SEND_REPLY` - Send a reply to a specific message [Required]
+
+**Key parameters**:
+- `message_id`: ID of the message being replied to
+- `to`: Recipient phone number
+- `body`: Reply text content
+
+**Pitfalls**:
+- message_id must be from a message received within the 24-hour window
+- Replies appear as quoted messages in the conversation
+- The original message must still exist (not deleted) for the quote to display
+
+### 5. Manage Business Profile and Templates
+
+**When to use**: User wants to view or manage their WhatsApp Business profile
+
+**Tool sequence**:
+1. `WHATSAPP_GET_BUSINESS_PROFILE` - Get business profile details [Optional]
+2. `WHATSAPP_GET_PHONE_NUMBERS` - List registered phone numbers [Optional]
+3. `WHATSAPP_GET_PHONE_NUMBER` - Get details for a specific number [Optional]
+4. `WHATSAPP_CREATE_MESSAGE_TEMPLATE` - Create a new template [Optional]
+5. `WHATSAPP_GET_MESSAGE_TEMPLATES` - List all templates [Optional]
+
+**Key parameters**:
+- `phone_number_id`: Business phone number ID
+- `template_name`: Name for the new template
+- `category`: Template category (MARKETING, UTILITY, AUTHENTICATION)
+- `language`: Template language code
+
+**Pitfalls**:
+- New templates require Meta review before they can be used
+- Template names must be lowercase with underscores (no spaces)
+- Category affects pricing and approval criteria
+- Templates have specific formatting requirements for headers, body, and buttons
+
+### 6. Share Contacts
+
+**When to use**: User wants to send contact information via WhatsApp
+
+**Tool sequence**:
+1. `WHATSAPP_SEND_CONTACTS` - Send contact cards [Required]
+
+**Key parameters**:
+- `to`: Recipient phone number
+- `contacts`: Array of contact objects with name, phone, email details
+
+**Pitfalls**:
+- Contact objects must follow the WhatsApp Business API contact schema
+- At least a name field is required for each contact
+- Phone numbers in contacts should include country codes
+
+## Common Patterns
+
+### 24-Hour Messaging Window
+
+- Customers must message you first to open a conversation window
+- Within 24 hours of their last message, you can send free-form messages
+- After 24 hours, only approved template messages can be sent
+- Template messages can re-open the conversation window
+
+### Phone Number Resolution
+
+```
+1. Call WHATSAPP_GET_PHONE_NUMBERS
+2. Extract phone_number_id for your business number
+3. Use phone_number_id in all send operations
+```
+
+### Media Upload Flow
+
+```
+1. Call WHATSAPP_UPLOAD_MEDIA with the file
+2. Extract media_id from response
+3. Call WHATSAPP_SEND_MEDIA_BY_ID with media_id
+4. OR use WHATSAPP_SEND_MEDIA with a public URL directly
+```
+
+## Known Pitfalls
+
+**Phone Number Format**:
+- Always use E.164 format: +[country code][number] (e.g., '+14155551234')
+- Do not include dashes, spaces, or parentheses
+- Country code is required; local numbers without it will fail
+
+**Messaging Restrictions**:
+- Business-initiated messages require templates outside the 24-hour window
+- Template messages cost money per conversation
+- Rate limits apply per phone number and per account
+
+**Media Handling**:
+- Uploaded media expires; use promptly after upload
+- Media URLs must be publicly accessible HTTPS
+- Stickers have specific requirements (WebP format, 512x512 pixels)
+
+**Template Management**:
+- Template review can take up to 24 hours
+- Rejected templates need to be fixed and resubmitted
+- Template variables use double curly braces: {{1}}, {{2}}, etc.
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Send message | WHATSAPP_SEND_MESSAGE | to, body |
+| Send template | WHATSAPP_SEND_TEMPLATE_MESSAGE | template_name, to, language_code |
+| Upload media | WHATSAPP_UPLOAD_MEDIA | (file params) |
+| Send media by ID | WHATSAPP_SEND_MEDIA_BY_ID | media_id, to, type |
+| Send media by URL | WHATSAPP_SEND_MEDIA | media_url, to, type |
+| Reply to message | WHATSAPP_SEND_REPLY | message_id, to, body |
+| Send contacts | WHATSAPP_SEND_CONTACTS | to, contacts |
+| Get media | WHATSAPP_GET_MEDIA | media_id |
+| List phone numbers | WHATSAPP_GET_PHONE_NUMBERS | (none) |
+| Get phone number | WHATSAPP_GET_PHONE_NUMBER | phone_number_id |
+| Get business profile | WHATSAPP_GET_BUSINESS_PROFILE | phone_number_id |
+| Create template | WHATSAPP_CREATE_MESSAGE_TEMPLATE | template_name, category, language |
+| List templates | WHATSAPP_GET_MESSAGE_TEMPLATES | (none) |
+| Check template status | WHATSAPP_GET_TEMPLATE_STATUS | template_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/wiki-architect/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: wiki-architect
+description: "Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or..."
+risk: unknown
+source: community
+---
+
+# Wiki Architect
+
+You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.
+
+## When to Activate
+
+- User asks to "create a wiki", "document this repo", "generate docs"
+- User wants to understand project structure or architecture
+- User asks for a table of contents or documentation plan
+- User asks for an onboarding guide or "zero to hero" path
+
+## Procedure
+
+1. **Scan** the repository file tree and README
+2. **Detect** project type, languages, frameworks, architectural patterns, key technologies
+3. **Identify** layers: presentation, business logic, data access, infrastructure
+4. **Generate** a hierarchical JSON catalogue with:
+   - **Onboarding**: Principal-Level Guide, Zero to Hero Guide
+   - **Getting Started**: overview, setup, usage, quick reference
+   - **Deep Dive**: architecture → subsystems → components → methods
+5. **Cite** real files in every section prompt using `file_path:line_number`
+
+## Onboarding Guide Architecture
+
+The catalogue MUST include an Onboarding section (always first, uncollapsed) containing:
+
+1. **Principal-Level Guide** — For senior/principal ICs. Dense, opinionated. Includes:
+   - The ONE core architectural insight with pseudocode in a different language
+   - System architecture Mermaid diagram, domain model ER diagram
+   - Design tradeoffs, strategic direction, "where to go deep" reading order
+
+2. **Zero-to-Hero Learning Path** — For newcomers. Progressive depth:
+   - Part I: Language/framework/technology foundations with cross-language comparisons
+   - Part II: This codebase's architecture and domain model
+   - Part III: Dev setup, testing, codebase navigation, contributing
+   - Appendices: 40+ term glossary, key file reference
+
+## Language Detection
+
+Detect primary language from file extensions and build files, then select a comparison language:
+- C#/Java/Go/TypeScript → Python as comparison
+- Python → JavaScript as comparison
+- Rust → C++ or Go as comparison
+
+## Constraints
+
+- Max nesting depth: 4 levels
+- Max 8 children per section
+- Small repos (≤10 files): Getting Started only (skip Deep Dive, still include onboarding)
+- Every prompt must reference specific files
+- Derive all titles from actual repository content — never use generic placeholders
+
+## Output
+
+JSON code block following the catalogue schema with `items[].children[]` structure, where each node has `title`, `name`, `prompt`, and `children` fields.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/wiki-changelog/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: wiki-changelog
+description: "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th..."
+risk: unknown
+source: community
+---
+
+# Wiki Changelog
+
+Generate structured changelogs from git history.
+
+## When to Activate
+
+- User asks "what changed recently", "generate a changelog", "summarize commits"
+- User wants to understand recent development activity
+
+## Procedure
+
+1. Examine git log (commits, dates, authors, messages)
+2. Group by time period: daily (last 7 days), weekly (older)
+3. Classify each commit: Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), Breaking (⚠️)
+4. Generate concise user-facing descriptions using project terminology
+
+## Constraints
+
+- Focus on user-facing changes
+- Merge related commits into coherent descriptions
+- Use project terminology from README
+- Highlight breaking changes prominently with migration notes
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/wiki-onboarding/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: wiki-onboarding
+description: "Generates two complementary onboarding guides \u2014 a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation fo..."
+risk: unknown
+source: community
+---
+
+# 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:onboard` command
+- 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# / .NET
+- `Cargo.toml` → Rust
+- `pyproject.toml` / `setup.py` / `requirements.txt` → Python
+- `go.mod` → Go
+- `pom.xml` / `build.gradle` → Java
+
+## Guide 1: Principal-Level Onboarding
+
+**Audience**: Senior/staff+ engineers who need the "why" behind decisions.
+
+### Required Sections
+
+1. **System Philosophy & Design Principles** — What invariants does the system maintain? What were the key design choices and why?
+2. **Architecture Overview** — Component map with Mermaid diagram. What owns what, communication patterns.
+3. **Key Abstractions & Interfaces** — The load-bearing abstractions everything depends on
+4. **Decision Log** — Major architectural decisions with context, alternatives considered, trade-offs
+5. **Dependency Rationale** — Why each major dependency was chosen, what it replaced
+6. **Data Flow & State** — How data moves through the system (traced from actual code, not guessed)
+7. **Failure Modes & Error Handling** — What breaks, how errors propagate, recovery patterns
+8. **Performance Characteristics** — Bottlenecks, scaling limits, hot paths
+9. **Security Model** — Auth, authorization, trust boundaries, data sensitivity
+10. **Testing Strategy** — What's tested, what isn't, testing philosophy
+11. **Operational Concerns** — Deployment, monitoring, feature flags, configuration
+12. **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
+
+1. **What This Project Does** — 2-3 sentence elevator pitch
+2. **Prerequisites** — Tools, versions, accounts needed
+3. **Environment Setup** — Step-by-step with exact commands, expected output at each step
+4. **Project Structure** — Annotated directory tree (what lives where and why)
+5. **Your First Task** — End-to-end walkthrough of adding a simple feature
+6. **Development Workflow** — Branch strategy, commit conventions, PR process
+7. **Running Tests** — How to run tests, what to test, how to add a test
+8. **Debugging Guide** — Common issues and how to diagnose them
+9. **Key Concepts** — Domain-specific terminology explained with code examples
+10. **Code Patterns** — "If you want to add X, follow this pattern" templates
+11. **Common Pitfalls** — Mistakes every new contributor makes and how to avoid them
+12. **Where to Get Help** — Communication channels, documentation, key contacts
+13. **Glossary** — Terms used in the codebase that aren't obvious
+14. **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)`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.