@ngxtm/devkit 3.15.0 → 3.17.0

package/merged-commands/discord-bot-architect.md

@@ -2,6 +2,7 @@
 name: discord-bot-architect
 description: "Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Discord Bot Architect
@@ -275,3 +276,6 @@ cause missed heartbeats and disconnections.
 | Issue | medium | ## Development: Use guild commands |
 | Issue | medium | ## Never block the event loop |
 | Issue | medium | ## Show modal immediately |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/dispatching-parallel-agents.md

@@ -1,6 +1,8 @@
 ---
 name: dispatching-parallel-agents
-description: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
+description: "Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies"
+risk: unknown
+source: community
 ---
 
 # Dispatching Parallel Agents

package/merged-commands/distributed-debugging-debug-trace.md

@@ -1,6 +1,8 @@
 ---
 name: distributed-debugging-debug-trace
-description: "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments."
+description: "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, an..."
+risk: unknown
+source: community
 ---
 
 # Debug and Trace Configuration

package/merged-commands/distributed-tracing.md

@@ -1,6 +1,8 @@
 ---
 name: distributed-tracing
-description: Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
+description: "Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implem..."
+risk: unknown
+source: community
 ---
 
 # Distributed Tracing

package/merged-commands/django-pro.md

@@ -1,11 +1,13 @@
 ---
 name: django-pro
-description: Master Django 5.x with async views, DRF, Celery, and Django
+description: "Master Django 5.x with async views, DRF, Celery, and Django"
   Channels. Build scalable web applications with proper architecture, testing,
   and deployment. Use PROACTIVELY for Django development, ORM optimization, or
   complex Django patterns.
 metadata:
   model: opus
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/merged-commands/doc-coauthoring.md

@@ -1,6 +1,8 @@
 ---
 name: doc-coauthoring
-description: Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
+description: "Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This ..."
+risk: unknown
+source: community
 ---
 
 # Doc Co-Authoring Workflow
@@ -373,3 +375,6 @@ Announce document completion. Provide a few final tips:
 - Don't rush through stages
 - Each iteration should make meaningful improvements
 - The goal is a document that actually works for readers
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/docker-expert.md

@@ -1,9 +1,11 @@
 ---
 name: docker-expert
-description: Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY for Dockerfile optimization, container issues, image size problems, security hardening, networking, and orchestration challenges.
+description: "Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY f..."
 category: devops
 color: blue
 displayName: Docker Expert
+risk: unknown
+source: community
 ---
 
 # Docker Expert
@@ -406,4 +408,7 @@ When reviewing Docker configurations, focus on:
 - Establish container standards for CI/CD integration
 - Define security baselines for production orchestration
 
-I provide comprehensive Docker containerization expertise with focus on practical optimization, security hardening, and production-ready patterns. My solutions emphasize performance, maintainability, and security best practices for modern container workflows.
+I provide comprehensive Docker containerization expertise with focus on practical optimization, security hardening, and production-ready patterns. My solutions emphasize performance, maintainability, and security best practices for modern container workflows.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/docs-architect.md

@@ -1,11 +1,13 @@
 ---
 name: docs-architect
-description: Creates comprehensive technical documentation from existing
+description: "Creates comprehensive technical documentation from existing"
   codebases. Analyzes architecture, design patterns, and implementation details
   to produce long-form technical manuals and ebooks. Use PROACTIVELY for system
   documentation, architecture guides, or technical deep-dives.
 metadata:
   model: sonnet
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/merged-commands/documentation-generation-doc-generate.md

@@ -1,6 +1,8 @@
 ---
 name: documentation-generation-doc-generate
-description: "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices."
+description: "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI..."
+risk: unknown
+source: community
 ---
 
 # Automated Documentation Generation

package/merged-commands/documentation-templates.md

@@ -1,7 +1,9 @@
 ---
 name: documentation-templates
-description: Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
+description: "Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation."
 allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
 ---
 
 # Documentation Templates
@@ -48,8 +50,8 @@ Brief one-line description.
 
 ## Documentation
 
-- [API Reference](./docs/api.md)
-- [Architecture](./docs/architecture.md)
+- API Reference
+- Architecture
 
 ## License
 
@@ -192,3 +194,6 @@ For RAG indexing:
 ---
 
 > **Remember:** Templates are starting points. Adapt to your project's needs.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/documentation.md

@@ -0,0 +1,261 @@
+---
+name: documentation
+description: "Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing."
+source: personal
+risk: safe
+domain: documentation
+category: workflow-bundle
+version: 1.0.0
+---
+
+# Documentation Workflow Bundle
+
+## Overview
+
+Comprehensive documentation workflow for generating API documentation, architecture documentation, README files, code comments, and technical content from codebases.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Creating project documentation
+- Generating API documentation
+- Writing architecture docs
+- Documenting code
+- Creating user guides
+- Maintaining wikis
+
+## Workflow Phases
+
+### Phase 1: Documentation Planning
+
+#### Skills to Invoke
+- `docs-architect` - Documentation architecture
+- `documentation-templates` - Documentation templates
+
+#### Actions
+1. Identify documentation needs
+2. Choose documentation tools
+3. Plan documentation structure
+4. Define style guidelines
+5. Set up documentation site
+
+#### Copy-Paste Prompts
+```
+Use @docs-architect to plan documentation structure
+```
+
+```
+Use @documentation-templates to set up documentation
+```
+
+### Phase 2: API Documentation
+
+#### Skills to Invoke
+- `api-documenter` - API documentation
+- `api-documentation-generator` - Auto-generation
+- `openapi-spec-generation` - OpenAPI specs
+
+#### Actions
+1. Extract API endpoints
+2. Generate OpenAPI specs
+3. Create API reference
+4. Add usage examples
+5. Set up auto-generation
+
+#### Copy-Paste Prompts
+```
+Use @api-documenter to generate API documentation
+```
+
+```
+Use @openapi-spec-generation to create OpenAPI specs
+```
+
+### Phase 3: Architecture Documentation
+
+#### Skills to Invoke
+- `c4-architecture-c4-architecture` - C4 architecture
+- `c4-context` - Context diagrams
+- `c4-container` - Container diagrams
+- `c4-component` - Component diagrams
+- `c4-code` - Code diagrams
+- `mermaid-expert` - Mermaid diagrams
+
+#### Actions
+1. Create C4 diagrams
+2. Document architecture
+3. Generate sequence diagrams
+4. Document data flows
+5. Create deployment docs
+
+#### Copy-Paste Prompts
+```
+Use @c4-architecture-c4-architecture to create C4 diagrams
+```
+
+```
+Use @mermaid-expert to create architecture diagrams
+```
+
+### Phase 4: Code Documentation
+
+#### Skills to Invoke
+- `code-documentation-code-explain` - Code explanation
+- `code-documentation-doc-generate` - Doc generation
+- `documentation-generation-doc-generate` - Auto-generation
+
+#### Actions
+1. Extract code comments
+2. Generate JSDoc/TSDoc
+3. Create type documentation
+4. Document functions
+5. Add usage examples
+
+#### Copy-Paste Prompts
+```
+Use @code-documentation-code-explain to explain code
+```
+
+```
+Use @code-documentation-doc-generate to generate docs
+```
+
+### Phase 5: README and Getting Started
+
+#### Skills to Invoke
+- `readme` - README generation
+- `environment-setup-guide` - Setup guides
+- `tutorial-engineer` - Tutorial creation
+
+#### Actions
+1. Create README
+2. Write getting started guide
+3. Document installation
+4. Add usage examples
+5. Create troubleshooting guide
+
+#### Copy-Paste Prompts
+```
+Use @readme to create project README
+```
+
+```
+Use @tutorial-engineer to create tutorials
+```
+
+### Phase 6: Wiki and Knowledge Base
+
+#### Skills to Invoke
+- `wiki-architect` - Wiki architecture
+- `wiki-page-writer` - Wiki pages
+- `wiki-onboarding` - Onboarding docs
+- `wiki-qa` - Wiki Q&A
+- `wiki-researcher` - Wiki research
+- `wiki-vitepress` - VitePress wiki
+
+#### Actions
+1. Design wiki structure
+2. Create wiki pages
+3. Write onboarding guides
+4. Document processes
+5. Set up wiki site
+
+#### Copy-Paste Prompts
+```
+Use @wiki-architect to design wiki structure
+```
+
+```
+Use @wiki-page-writer to create wiki pages
+```
+
+```
+Use @wiki-onboarding to create onboarding docs
+```
+
+### Phase 7: Changelog and Release Notes
+
+#### Skills to Invoke
+- `changelog-automation` - Changelog generation
+- `wiki-changelog` - Changelog from git
+
+#### Actions
+1. Extract commit history
+2. Categorize changes
+3. Generate changelog
+4. Create release notes
+5. Publish updates
+
+#### Copy-Paste Prompts
+```
+Use @changelog-automation to generate changelog
+```
+
+```
+Use @wiki-changelog to create release notes
+```
+
+### Phase 8: Documentation Maintenance
+
+#### Skills to Invoke
+- `doc-coauthoring` - Collaborative writing
+- `reference-builder` - Reference docs
+
+#### Actions
+1. Review documentation
+2. Update outdated content
+3. Fix broken links
+4. Add new features
+5. Gather feedback
+
+#### Copy-Paste Prompts
+```
+Use @doc-coauthoring to collaborate on docs
+```
+
+## Documentation Types
+
+### Code-Level
+- JSDoc/TSDoc comments
+- Function documentation
+- Type definitions
+- Example code
+
+### API Documentation
+- Endpoint reference
+- Request/response schemas
+- Authentication guides
+- SDK documentation
+
+### Architecture Documentation
+- System overview
+- Component diagrams
+- Data flow diagrams
+- Deployment architecture
+
+### User Documentation
+- Getting started guides
+- User manuals
+- Tutorials
+- FAQs
+
+### Process Documentation
+- Runbooks
+- Onboarding guides
+- SOPs
+- Decision records
+
+## Quality Gates
+
+- [ ] All APIs documented
+- [ ] Architecture diagrams current
+- [ ] README up to date
+- [ ] Code comments helpful
+- [ ] Examples working
+- [ ] Links valid
+
+## Related Workflow Bundles
+
+- `development` - Development workflow
+- `testing-qa` - Documentation testing
+- `ai-ml` - AI documentation

package/merged-commands/docusign-automation.md

@@ -0,0 +1,213 @@
+---
+name: docusign-automation
+description: "Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# DocuSign Automation via Rube MCP
+
+Automate DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active DocuSign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docusign`
+- 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 `docusign`
+3. If connection is not ACTIVE, follow the returned auth link to complete DocuSign OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Browse and Select Templates
+
+**When to use**: User wants to find available document templates for sending
+
+**Tool sequence**:
+1. `DOCUSIGN_LIST_ALL_TEMPLATES` - List all available templates [Required]
+2. `DOCUSIGN_GET_TEMPLATE` - Get detailed template information [Optional]
+
+**Key parameters**:
+- For listing: Optional search/filter parameters
+- For details: `templateId` (from list results)
+- Response includes template `templateId`, `name`, `description`, roles, and fields
+
+**Pitfalls**:
+- Template IDs are GUIDs (e.g., '12345678-abcd-1234-efgh-123456789012')
+- Templates define recipient roles with signing tabs; understand roles before creating envelopes
+- Large template libraries require pagination; check for continuation tokens
+- Template access depends on account permissions
+
+### 2. Create and Send Envelopes from Templates
+
+**When to use**: User wants to send documents for signature using a pre-built template
+
+**Tool sequence**:
+1. `DOCUSIGN_LIST_ALL_TEMPLATES` - Find the template to use [Prerequisite]
+2. `DOCUSIGN_GET_TEMPLATE` - Review template roles and fields [Optional]
+3. `DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE` - Create the envelope [Required]
+4. `DOCUSIGN_SEND_ENVELOPE` - Send the envelope for signing [Required]
+
+**Key parameters**:
+- For CREATE_ENVELOPE_FROM_TEMPLATE:
+  - `templateId`: Template to use
+  - `templateRoles`: Array of role assignments with `roleName`, `name`, `email`
+  - `status`: 'created' (draft) or 'sent' (send immediately)
+  - `emailSubject`: Custom subject line for the signing email
+  - `emailBlurb`: Custom message in the signing email
+- For SEND_ENVELOPE:
+  - `envelopeId`: Envelope ID from creation response
+
+**Pitfalls**:
+- `templateRoles` must match the role names defined in the template exactly (case-sensitive)
+- Setting `status` to 'sent' during creation sends immediately; use 'created' for drafts
+- If status is 'sent' at creation, no need to call SEND_ENVELOPE separately
+- Each role requires at minimum `roleName`, `name`, and `email`
+- `emailSubject` overrides the template's default email subject
+
+### 3. Monitor Envelope Status
+
+**When to use**: User wants to check the status of sent envelopes or track signing progress
+
+**Tool sequence**:
+1. `DOCUSIGN_GET_ENVELOPE` - Get envelope details and status [Required]
+
+**Key parameters**:
+- `envelopeId`: Envelope identifier (GUID)
+- Response includes `status`, `recipients`, `sentDateTime`, `completedDateTime`
+
+**Pitfalls**:
+- Envelope statuses: 'created', 'sent', 'delivered', 'signed', 'completed', 'declined', 'voided'
+- 'delivered' means the email was opened, not that the document was signed
+- 'completed' means all recipients have signed
+- Recipients array shows individual signing status per recipient
+- Envelope IDs are GUIDs; always resolve from creation or search results
+
+### 4. Add Templates to Existing Envelopes
+
+**When to use**: User wants to add additional documents or templates to an existing envelope
+
+**Tool sequence**:
+1. `DOCUSIGN_GET_ENVELOPE` - Verify envelope exists and is in draft state [Prerequisite]
+2. `DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE` - Add template to envelope [Required]
+
+**Key parameters**:
+- `envelopeId`: Target envelope ID
+- `documentId`: Document ID within the envelope
+- `templateId`: Template to add
+
+**Pitfalls**:
+- Envelope must be in 'created' (draft) status to add templates
+- Cannot add templates to already-sent envelopes
+- Document IDs are sequential within an envelope (starting from '1')
+- Adding a template merges its fields and roles into the existing envelope
+
+### 5. Manage Envelope Lifecycle
+
+**When to use**: User wants to send, void, or manage draft envelopes
+
+**Tool sequence**:
+1. `DOCUSIGN_GET_ENVELOPE` - Check current envelope status [Prerequisite]
+2. `DOCUSIGN_SEND_ENVELOPE` - Send a draft envelope [Optional]
+
+**Key parameters**:
+- `envelopeId`: Envelope to manage
+- For sending: envelope must be in 'created' status with all required recipients
+
+**Pitfalls**:
+- Only 'created' (draft) envelopes can be sent
+- Sent envelopes cannot be unsent; they can only be voided
+- Voiding an envelope notifies all recipients
+- All required recipients must have valid email addresses before sending
+
+## Common Patterns
+
+### ID Resolution
+
+**Template name -> Template ID**:
+```
+1. Call DOCUSIGN_LIST_ALL_TEMPLATES
+2. Find template by name in results
+3. Extract templateId (GUID format)
+```
+
+**Envelope tracking**:
+```
+1. Store envelopeId from CREATE_ENVELOPE_FROM_TEMPLATE response
+2. Call DOCUSIGN_GET_ENVELOPE periodically to check status
+3. Check recipient-level status for individual signing progress
+```
+
+### Template Role Mapping
+
+When creating an envelope from a template:
+```
+1. Call DOCUSIGN_GET_TEMPLATE to see defined roles
+2. Map each role to actual recipients:
+   {
+     "roleName": "Signer 1",     // Must match template role name exactly
+     "name": "John Smith",
+     "email": "john@example.com"
+   }
+3. Include ALL required roles in templateRoles array
+```
+
+### Envelope Status Flow
+
+```
+created (draft) -> sent -> delivered -> signed -> completed
+                       \-> declined
+                       \-> voided (by sender)
+```
+
+## Known Pitfalls
+
+**Template Roles**:
+- Role names are case-sensitive; must match template definition exactly
+- All required roles must be assigned when creating an envelope
+- Missing role assignments cause envelope creation to fail
+
+**Envelope Status**:
+- 'delivered' means email opened, NOT document signed
+- 'completed' is the final successful state (all parties signed)
+- Status transitions are one-way; cannot revert to previous states
+
+**GUIDs**:
+- All DocuSign IDs (templates, envelopes) are GUID format
+- Always resolve names to GUIDs via list/search endpoints
+- Do not hardcode GUIDs; they are unique per account
+
+**Rate Limits**:
+- DocuSign API has per-account rate limits
+- Bulk envelope creation should be throttled
+- Polling envelope status should use reasonable intervals (30-60 seconds)
+
+**Response Parsing**:
+- Response data may be nested under `data` key
+- Recipient information is nested within envelope response
+- Date fields use ISO 8601 format
+- Parse defensively with fallbacks for optional fields
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List templates | DOCUSIGN_LIST_ALL_TEMPLATES | (optional filters) |
+| Get template | DOCUSIGN_GET_TEMPLATE | templateId |
+| Create envelope | DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE | templateId, templateRoles, status |
+| Send envelope | DOCUSIGN_SEND_ENVELOPE | envelopeId |
+| Get envelope status | DOCUSIGN_GET_ENVELOPE | envelopeId |
+| Add template to envelope | DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE | envelopeId, documentId, templateId |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/docx-official.md

@@ -1,7 +1,9 @@
 ---
-name: docx
-description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
+name: docx-official
+description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional document..."
 license: Proprietary. LICENSE.txt has complete terms
+risk: unknown
+source: community
 ---
 
 # DOCX creation, editing, and analysis
@@ -194,4 +196,7 @@ Required dependencies (install if not available):
 - **docx**: `npm install -g docx` (for creating new documents)
 - **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
 - **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
-- **defusedxml**: `pip install defusedxml` (for secure XML parsing)
+- **defusedxml**: `pip install defusedxml` (for secure XML parsing)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.