matex-cli 1.2.82 → 1.2.87

package/package.json

@@ -1,13 +1,13 @@
 {
     "name": "matex-cli",
-    "version": "1.2.82",
+    "version": "1.2.87",
     "description": "MATEX CLI - The Agentic 'Bro-Swarm' for Engineering. Zero-Cost AI for Students and Pro-Grade Dev Power.",
     "main": "dist/index.js",
     "bin": {
         "matex": "bin/matex"
     },
     "scripts": {
-        "build": "tsc",
+        "build": "rm -rf dist && esbuild src/index.ts --bundle --platform=node --target=node16 --outfile=dist/index.js --minify",
         "dev": "tsc --watch",
         "test": "jest",
         "postinstall": "echo \"\n🚀 MATEX AI :: THE BRO-SWARM IS LIVE!\n👉 Run 'matex help' to meet your engineering brothers and enter the zero-cost student universe.\n\"",
@@ -22,6 +22,12 @@
         "coding-assistant",
         "mac-engineering"
     ],
+    "files": [
+        "dist/index.js",
+        "bin",
+        "README.md",
+        "USAGE_GUIDE.md"
+    ],
     "author": "Ajay Sharma <ajaypoudel47@gmail.com>",
     "license": "MIT",
     "dependencies": {
@@ -29,16 +35,17 @@
         "chalk": "^4.1.2",
         "commander": "^11.1.0",
         "conf": "^11.0.2",
+        "dotenv": "^16.3.1",
         "inquirer": "^8.2.5",
-        "ora": "^5.4.1",
-        "dotenv": "^16.3.1"
+        "ora": "^5.4.1"
     },
     "devDependencies": {
         "@types/inquirer": "^9.0.7",
+        "@types/jest": "^29.5.0",
         "@types/node": "^20.10.0",
-        "typescript": "^5.3.0",
+        "esbuild": "^0.27.3",
         "jest": "^29.7.0",
-        "@types/jest": "^29.5.0"
+        "typescript": "^5.3.0"
     },
     "engines": {
         "node": ">=16.0.0"

package/.agents/skills/mcp-server-dev/SKILL.md

@@ -1,60 +0,0 @@
----
-name: mcp-server-dev
-description: Comprehensive guide and workflow for creating high-quality Model Context Protocol (MCP) servers.
----
-
-# MCP Server Development Guide
-
-## Overview
-This skill enables the creation of robust MCP servers that allow LLMs to interact with external services through well-designed tools.
-
-## Phase 1: Deep Research and Planning
-
-### 1.1 Understand Modern MCP Design
-- **API Coverage vs. Workflow Tools**: Balance comprehensive API coverage with specialized workflow tools. When in doubt, prioritize comprehensive API coverage.
-- **Tool Naming**: Use clear, consistent, action-oriented names (e.g., `prefix_action_object`).
-- **Context Management**: Ensure tools return focused, relevant data with support for filtering and pagination.
-- **Error Handling**: Provide actionable error messages with specific suggestions.
-
-### 1.2 Protocol & SDK Research
-- **MCP Spec**: Review [modelcontextprotocol.io](https://modelcontextprotocol.io/sitemap.xml).
-- **TypeScript SDK (Recommended)**:
-    - Language: TypeScript
-    - Schema: Zod
-    - Transport: Streamable HTTP (remote/stateless) or stdio (local).
-- **Python SDK**:
-    - Language: Python
-    - Schema: Pydantic
-    - Setup: FastMCP.
-
-## Phase 2: Implementation
-
-### 2.1 Project Structure
-- **TypeScript**: `package.json`, `tsconfig.json`, `src/index.ts`.
-- **Python**: `pyproject.toml` or `requirements.txt`, `main.py`.
-
-### 2.2 Core Infrastructure
-- Implement API client with authentication.
-- Set up logging and error handling helpers.
-- Implement pagination support.
-
-### 2.3 Tool Implementation
-- **Input Schema**: Strict validation with descriptions and examples.
-- **Output Schema**: Structured data using `structuredContent`.
-- **Hints**: Use `readOnlyHint`, `destructiveHint`, `idempotentHint`.
-
-## Phase 3: Review and Test
-- **Code Quality**: No duplication, consistent error handling, full types.
-- **Testing**: Use **MCP Inspector** (`npx @modelcontextprotocol/inspector`).
-
-## Phase 4: Create Evaluations
-Create 10 complex, realistic, read-only questions in XML format to verify the server's effectiveness.
-
-```xml
-<evaluation>
-  <qa_pair>
-    <question>Complex user query requiring multiple tool calls...</question>
-    <answer>Verified string answer</answer>
-  </qa_pair>
-</evaluation>
-```

package/.agents/skills/mcp-server-dev/examples/basic-ts-server/package.json

@@ -1,20 +0,0 @@
-{
-    "name": "basic-mcp-server",
-    "version": "1.0.0",
-    "description": "A basic MCP server template",
-    "main": "dist/index.js",
-    "type": "module",
-    "scripts": {
-        "build": "tsc",
-        "start": "node dist/index.js",
-        "dev": "tsc -w"
-    },
-    "dependencies": {
-        "@modelcontextprotocol/sdk": "^1.0.1",
-        "zod": "^3.22.4"
-    },
-    "devDependencies": {
-        "@types/node": "^20.11.0",
-        "typescript": "^5.3.3"
-    }
-}

package/.agents/skills/mcp-server-dev/examples/basic-ts-server/src/index.ts

@@ -1,66 +0,0 @@
-import { Server } from "@modelcontextprotocol/sdk/server/index.js";
-import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
-import {
-    CallToolRequestSchema,
-    ListToolsRequestSchema,
-} from "@modelcontextprotocol/sdk/types.js";
-import { z } from "zod";
-
-const server = new Server(
-    {
-        name: "basic-mcp-server",
-        version: "1.0.0",
-    },
-    {
-        capabilities: {
-            tools: {},
-        },
-    }
-);
-
-/**
- * Define your tools here
- */
-server.setRequestHandler(ListToolsRequestSchema, async () => {
-    return {
-        tools: [
-            {
-                name: "echo",
-                description: "Echoes back the input string",
-                inputSchema: {
-                    type: "object",
-                    properties: {
-                        message: { type: "string", description: "The message to echo" },
-                    },
-                    required: ["message"],
-                },
-            },
-        ],
-    };
-});
-
-server.setRequestHandler(CallToolRequestSchema, async (request) => {
-    if (request.params.name === "echo") {
-        const args = z.object({ message: z.string() }).parse(request.params.arguments);
-        return {
-            content: [
-                {
-                    type: "text",
-                    text: `Echo: ${args.message}`,
-                },
-            ],
-        };
-    }
-    throw new Error("Tool not found");
-});
-
-async function main() {
-    const transport = new StdioServerTransport();
-    await server.connect(transport);
-    console.error("MCP Server running on stdio");
-}
-
-main().catch((error) => {
-    console.error("Fatal error:", error);
-    process.exit(1);
-});

package/.agents/skills/mcp-server-dev/resources/best_practices.md

@@ -1,20 +0,0 @@
-# MCP Server Development Best Practices
-
-## 1. Tool Design
-*   **Granularity**: Tools should be granular enough to be composed by the LLM, but high-level enough to provide value.
-*   **Naming**: Avoid generic names. Use `github_list_pull_requests` instead of `list_pr`.
-*   **Descriptions**: Treat tool descriptions as documentation for the LLM. Explain *why* and *when* to use it.
-
-## 2. Response Handling
-*   **Structured Data**: Use `structuredContent` whenever possible. It allows the LLM to access data programmatically without parsing strings.
-*   **Markdown for Humans**: Use text content for human-readable summaries inside response objects.
-*   **Pagination**: AI models can only handle so much text. Always paginate large lists (e.g., `cursor`, `limit`).
-
-## 3. Security
-*   **Input Sanitization**: Never trust inputs. Use Zod/Pydantic for strict schema validation.
-*   **Read-Only Safeties**: Mark read-only tools explicitly to prevent accidental mutations.
-*   **API Keys**: Never hardcode keys. Use environment variables or secret managers.
-
-## 4. Evaluation
-*   **String Comparison**: Ensure answers are stable and literal for automated testing.
-*   **Edge Cases**: Test your server with ambiguous or malformed queries to see how it handles errors.

package/.agents/skills/pptx-presentation-builder/SKILL.md

@@ -1,338 +0,0 @@
----
-name: pptx-presentation-builder
-description: Build professional PPTX presentations with brand-aligned layouts using structured deck briefs and validation steps for pitch, roadmap, and product decks.
-tags: [presentation, pptx, slides, storytelling, branding, pitch-deck]
-platforms: [Claude, ChatGPT, Gemini, Codex]
-allowed-tools:
-  - Write
-  - Read
-  - Task
----
-
-# PPTX Presentation Builder
-
-브랜드 가이드라인에 맞춘 전문 PPTX 프레젠테이션 빌더 스킬입니다. 피치덱, 로드맵, 제품 소개 등 다양한 프레젠테이션을 구조화된 브리프와 검증 단계로 생성합니다.
-
-## When to use this skill
-
-- **전문 슬라이드 덱 필요**: 프롬프트에서 프레젠테이션 생성
-- **브랜드 일관성 필요**: 가이드라인에 맞춘 일관된 슬라이드
-- **반복 가능한 템플릿**: 제품, 피치, 로드맵 덱 템플릿화
-
----
-
-## Instructions
-
-### Step 1: Gather Brand Constraints
-
-```yaml
-brand_kit:
-  colors:
-    primary: "#2563EB"
-    secondary: "#6366F1"
-    accent: "#F59E0B"
-    background: "#FFFFFF"
-    text: "#1F2937"
-  fonts:
-    heading: "Inter"
-    body: "Inter"
-    mono: "JetBrains Mono"
-  logo:
-    placement: "top-left" | "bottom-right"
-    size: "small" | "medium"
-  style:
-    tone: "minimal" | "bold" | "executive"
-    corners: "sharp" | "rounded"
-    shadows: true | false
-```
-
-### Step 2: Define Deck Structure
-
-```markdown
-## Deck Brief
-
-### Meta
-- **Title**: [덱 제목]
-- **Audience**: [청중]
-- **Goal**: [목표 - 투자 유치, 제품 소개, 보고]
-- **Duration**: [발표 시간]
-
-### Slides
-| # | Type | Title | Key Message |
-|---|------|-------|-------------|
-| 1 | Title | Company Name | Tagline |
-| 2 | Agenda | Today's Agenda | 3-5 bullet points |
-| 3 | Problem | The Challenge | Pain point statement |
-| 4 | Solution | Our Approach | Value proposition |
-| 5 | Features | Key Capabilities | 3 features with icons |
-| 6 | Demo | Product in Action | Screenshot/video |
-| 7 | Traction | Growth Numbers | Key metrics |
-| 8 | Team | Who We Are | Team photos + roles |
-| 9 | Ask | The Opportunity | Investment/partnership ask |
-| 10 | Contact | Get in Touch | Contact info + CTA |
-```
-
-### Step 3: Generate Slides
-
-슬라이드별 콘텐츠 생성:
-
-```markdown
-## Slide 1: Title Slide
-
-### Layout: Centered
-
-### Content
-- **Title**: [Company Name]
-- **Subtitle**: [Tagline - 10 words max]
-- **Visual**: Logo centered
-- **Background**: Gradient (#2563EB → #6366F1)
-
-### Speaker Notes
-Welcome the audience. Introduce yourself and the company.
-Set the context for why you're presenting today.
-```
-
-**슬라이드 타입별 템플릿**:
-
-| Type | Layout | Elements |
-|------|--------|----------|
-| Title | Centered | Logo, Title, Subtitle |
-| Agenda | Left-aligned | Numbered list (3-5 items) |
-| Problem | Split | Text left, Visual right |
-| Solution | Split | Visual left, Text right |
-| Features | 3-column | Icon + Title + Description |
-| Stats | Data cards | 3-4 key metrics |
-| Quote | Centered | Quote text + attribution |
-| Team | Grid | Photos + Names + Roles |
-| CTA | Centered | Headline + Button |
-
-### Step 4: Review and Refine
-
-```markdown
-## Review Checklist
-
-### Layout Balance
-- [ ] 시각적 균형 확인
-- [ ] 여백 충분히 확보
-- [ ] 정렬 일관성
-
-### Typography
-- [ ] 폰트 크기 계층 (H1 > H2 > Body)
-- [ ] 가독성 확보 (최소 18pt body)
-- [ ] 일관된 폰트 사용
-
-### Content
-- [ ] 슬라이드당 하나의 아이디어
-- [ ] 텍스트 과밀 방지
-- [ ] 데이터/주장의 출처 명시
-
-### Accessibility
-- [ ] 색상 대비 충분
-- [ ] 이미지에 alt text
-- [ ] 논리적 읽기 순서
-```
-
-### Step 5: Export and Handoff
-
-```markdown
-## Handoff Package
-
-### Files
-- presentation.pptx
-- presentation.pdf (backup)
-- assets/ (images, logos)
-
-### Summary
-- **Total Slides**: [count]
-- **Estimated Duration**: [minutes]
-- **Key Narrative Arc**: [brief description]
-
-### Editing Notes
-- Slide 5: [specific edit note]
-- Slide 8: [specific edit note]
-
-### Post-Export Checklist
-- [ ] Font embedding verified
-- [ ] Images high resolution
-- [ ] Animations functional
-- [ ] Links active
-```
-
----
-
-## Examples
-
-### Example 1: 5-Slide Roadmap
-
-**Prompt**:
-```
-Create a 5-slide roadmap deck for Q2–Q4
-with modern design and speaker notes.
-Target: Engineering leadership.
-```
-
-**Expected output**:
-```markdown
-## Roadmap Deck
-
-### Slide 1: Title
-- Q2-Q4 Product Roadmap
-- Engineering Review | [Date]
-
-### Slide 2: Executive Summary
-- 3 key themes for the period
-- Success metrics overview
-
-### Slide 3: Timeline
-- Gantt-style view
-- Q2: Foundation | Q3: Scale | Q4: Optimize
-- Key milestones marked
-
-### Slide 4: Dependencies & Risks
-- Cross-team dependencies
-- Risk matrix (Impact vs Likelihood)
-- Mitigation strategies
-
-### Slide 5: Next Steps
-- Immediate action items
-- Review cadence
-- Feedback channels
-```
-
-### Example 2: Investor Pitch Deck
-
-**Prompt**:
-```
-Build a 10-slide investor pitch deck for an AI SaaS.
-Include: problem, solution, market, traction, team, ask.
-Series A context, $5M target.
-```
-
-**Expected output**:
-- Slide-by-slide content with speaker notes
-- Consistent brand styling
-- Data visualization for traction
-- Clear ask slide with use of funds
-
-### Example 3: Product Demo Deck
-
-**Prompt**:
-```
-Create an 8-slide product demo deck.
-Audience: Potential enterprise customers.
-Focus: Features, integrations, security.
-```
-
-**Expected output**:
-- Feature showcase slides
-- Integration diagram
-- Security compliance overview
-- Customer success stories
-- Next steps / trial CTA
-
----
-
-## Best practices
-
-1. **One idea per slide**: 과밀 방지
-2. **Visual hierarchy**: Titles > Headings > Body
-3. **Use speaker notes**: 슬라이드 텍스트 최소화
-4. **Data clarity**: 차트 > 텍스트 단락
-5. **Consistent theming**: 색상, 폰트, 간격 통일
-
----
-
-## Common pitfalls
-
-- **테마 혼합**: 하나의 덱에 여러 스타일
-- **일관성 없는 간격/타이포**: 슬라이드마다 다름
-- **내러티브 흐름 없음**: 논리적 연결 부재
-
----
-
-## Troubleshooting
-
-### Issue: Slides feel inconsistent
-**Cause**: 브랜드 토큰 누락
-**Solution**: 템플릿 제공, 테마 강제 적용
-
-### Issue: Slides are too dense
-**Cause**: 슬라이드당 텍스트 과다
-**Solution**: 콘텐츠 분할, 비주얼 활용
-
-### Issue: Narrative unclear
-**Cause**: 슬라이드 순서 문제
-**Solution**: 스토리 아크 재구성
-
----
-
-## Output format
-
-```markdown
-## Presentation Report
-
-### Overview
-- **Title**: [deck title]
-- **Slides**: [count]
-- **Duration**: [minutes]
-- **Audience**: [target]
-
-### Slide-by-Slide
-
-#### Slide 1: [Title]
-**Type**: [slide type]
-**Layout**: [layout description]
-**Content**:
-- [content items]
-
-**Speaker Notes**:
-[notes]
-
----
-#### Slide 2: [Title]
-...
-
-### Brand Tokens Applied
-- Primary: [color]
-- Font: [font family]
-- Style: [tone]
-
-### Files Delivered
-- [ ] presentation.pptx
-- [ ] assets.zip
-```
-
----
-
-## Multi-Agent Workflow
-
-### Validation & Retrospectives
-
-- **Round 1 (Orchestrator)**: 내러티브 아크, 슬라이드 수 정합성
-- **Round 2 (Analyst)**: 레이아웃 일관성, 브랜드 준수
-- **Round 3 (Executor)**: 내보내기 준비 상태 체크
-
-### Agent Roles
-
-| Agent | Role |
-|-------|------|
-| Claude | 내러티브 구성, 콘텐츠 생성 |
-| Gemini | 데이터 시각화 제안, 레퍼런스 리서치 |
-| Codex | 템플릿 코드 생성, 자동화 |
-
----
-
-## Metadata
-
-### Version
-- **Current Version**: 1.0.0
-- **Last Updated**: 2026-01-21
-- **Compatible Platforms**: Claude, ChatGPT, Gemini, Codex
-
-### Related Skills
-- [technical-writing](../technical-writing/SKILL.md)
-- [image-generation](../../creative-media/image-generation/SKILL.md)
-- [marketing-automation](../../marketing/marketing-automation/SKILL.md)
-
-### Tags
-`#presentation` `#pptx` `#slides` `#storytelling` `#branding` `#pitch-deck`

package/.agents/workflows/deploy.md

@@ -1,27 +0,0 @@
----
-description: How to build and publish a new version of Matex CLI
----
-
-Follow these steps to safely build and publish a new version of the **MATEX AI CLI** to NPM.
-
-### 🚀 Deployment Workflow
-
-1. **Build the Project**
-   // turbo
-   `npm run build`
-   *Ensures all TypeScript files are compiled to JavaScript in the `dist` folder.*
-
-2. **Patch Version**
-   // turbo
-   `npm version patch`
-   *Automatically increments the version number in `package.json` (e.g., 1.2.26 -> 1.2.27).*
-
-3. **Publish to NPM**
-   // turbo
-   `npm publish`
-   *Uploads the latest build to the NPM registry.*
-
----
-
-**💡 Tip:** You can run all these commands at once by typing:
-`npm run build && npm version patch && npm publish`

package/dist/api/client.d.ts

@@ -1,40 +0,0 @@
-export interface ChatMessage {
-    role: 'user' | 'assistant' | 'system';
-    content: string;
-}
-export interface ChatRequest {
-    messages: ChatMessage[];
-    model: string;
-    temperature?: number;
-    max_tokens?: number;
-    stream?: boolean;
-}
-export declare class MatexAPIClient {
-    private client;
-    private apiKey;
-    private baseURL;
-    private sovereignKey;
-    constructor(apiKey: string, baseURL?: string);
-    setSovereignKey(key: string): void;
-    /**
-     * Send a streaming chat request to the API
-     */
-    chatStream(request: ChatRequest, onChunk: (chunk: string) => void, signal?: AbortSignal): Promise<string>;
-    /**
-     * Send a chat request to the API (non-streaming fallback)
-     */
-    chat(request: ChatRequest): Promise<string>;
-    /**
-     * Handle Server-Sent Events (SSE) streaming response
-     */
-    private handleStreamingResponse;
-    /**
-     * List available API keys (requires Firebase token, not for CLI use)
-     */
-    listAPIKeys(): Promise<any>;
-    /**
-     * Test API key validity
-     */
-    testConnection(): Promise<boolean>;
-}
-//# sourceMappingURL=client.d.ts.map

package/dist/api/client.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"client.d.ts","sourceRoot":"","sources":["../../src/api/client.ts"],"names":[],"mappings":"AAEA,MAAM,WAAW,WAAW;IACxB,IAAI,EAAE,MAAM,GAAG,WAAW,GAAG,QAAQ,CAAC;IACtC,OAAO,EAAE,MAAM,CAAC;CACnB;AAED,MAAM,WAAW,WAAW;IACxB,QAAQ,EAAE,WAAW,EAAE,CAAC;IACxB,KAAK,EAAE,MAAM,CAAC;IACd,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,MAAM,CAAC,EAAE,OAAO,CAAC;CACpB;AAED,qBAAa,cAAc;IACvB,OAAO,CAAC,MAAM,CAAgB;IAC9B,OAAO,CAAC,MAAM,CAAS;IACvB,OAAO,CAAC,OAAO,CAAS;IAExB,OAAO,CAAC,YAAY,CAAuB;gBAE/B,MAAM,EAAE,MAAM,EAAE,OAAO,GAAE,MAAmE;IAcxG,eAAe,CAAC,GAAG,EAAE,MAAM;IAI3B;;OAEG;IACG,UAAU,CAAC,OAAO,EAAE,WAAW,EAAE,OAAO,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,IAAI,EAAE,MAAM,CAAC,EAAE,WAAW,GAAG,OAAO,CAAC,MAAM,CAAC;IAyE/G;;OAEG;IACG,IAAI,CAAC,OAAO,EAAE,WAAW,GAAG,OAAO,CAAC,MAAM,CAAC;IAoBjD;;OAEG;YACW,uBAAuB;IA+BrC;;OAEG;IACG,WAAW,IAAI,OAAO,CAAC,GAAG,CAAC;IAKjC;;OAEG;IACG,cAAc,IAAI,OAAO,CAAC,OAAO,CAAC;CAY3C"}