@ngxtm/devkit 3.0.2 → 3.1.0

package/skills/deployment-validation-config-validate/SKILL.md

@@ -0,0 +1,496 @@
+---
+name: deployment-validation-config-validate
+description: "You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat"
+---
+
+# Configuration Validation
+
+You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configuration testing strategies, and ensure configurations are secure, consistent, and error-free across all environments.
+
+## Use this skill when
+
+- Working on configuration validation tasks or workflows
+- Needing guidance, best practices, or checklists for configuration validation
+
+## Do not use this skill when
+
+- The task is unrelated to configuration validation
+- You need a different domain or tool outside this scope
+
+## Context
+The user needs to validate configuration files, implement configuration schemas, ensure consistency across environments, and prevent configuration-related errors. Focus on creating robust validation rules, type safety, security checks, and automated validation processes.
+
+## Requirements
+$ARGUMENTS
+
+## Instructions
+
+### 1. Configuration Analysis
+
+Analyze existing configuration structure and identify validation needs:
+
+```python
+import os
+import yaml
+import json
+from pathlib import Path
+from typing import Dict, List, Any
+
+class ConfigurationAnalyzer:
+    def analyze_project(self, project_path: str) -> Dict[str, Any]:
+        analysis = {
+            'config_files': self._find_config_files(project_path),
+            'security_issues': self._check_security_issues(project_path),
+            'consistency_issues': self._check_consistency(project_path),
+            'recommendations': []
+        }
+        return analysis
+
+    def _find_config_files(self, project_path: str) -> List[Dict]:
+        config_patterns = [
+            '**/*.json', '**/*.yaml', '**/*.yml', '**/*.toml',
+            '**/*.ini', '**/*.env*', '**/config.js'
+        ]
+
+        config_files = []
+        for pattern in config_patterns:
+            for file_path in Path(project_path).glob(pattern):
+                if not self._should_ignore(file_path):
+                    config_files.append({
+                        'path': str(file_path),
+                        'type': self._detect_config_type(file_path),
+                        'environment': self._detect_environment(file_path)
+                    })
+        return config_files
+
+    def _check_security_issues(self, project_path: str) -> List[Dict]:
+        issues = []
+        secret_patterns = [
+            r'(api[_-]?key|apikey)',
+            r'(secret|password|passwd)',
+            r'(token|auth)',
+            r'(aws[_-]?access)'
+        ]
+
+        for config_file in self._find_config_files(project_path):
+            content = Path(config_file['path']).read_text()
+            for pattern in secret_patterns:
+                if re.search(pattern, content, re.IGNORECASE):
+                    if self._looks_like_real_secret(content, pattern):
+                        issues.append({
+                            'file': config_file['path'],
+                            'type': 'potential_secret',
+                            'severity': 'high'
+                        })
+        return issues
+```
+
+### 2. Schema Validation
+
+Implement configuration schema validation with JSON Schema:
+
+```typescript
+import Ajv from 'ajv';
+import ajvFormats from 'ajv-formats';
+import { JSONSchema7 } from 'json-schema';
+
+interface ValidationResult {
+  valid: boolean;
+  errors?: Array<{
+    path: string;
+    message: string;
+    keyword: string;
+  }>;
+}
+
+export class ConfigValidator {
+  private ajv: Ajv;
+
+  constructor() {
+    this.ajv = new Ajv({
+      allErrors: true,
+      strict: false,
+      coerceTypes: true
+    });
+    ajvFormats(this.ajv);
+    this.addCustomFormats();
+  }
+
+  private addCustomFormats() {
+    this.ajv.addFormat('url-https', {
+      type: 'string',
+      validate: (data: string) => {
+        try {
+          return new URL(data).protocol === 'https:';
+        } catch { return false; }
+      }
+    });
+
+    this.ajv.addFormat('port', {
+      type: 'number',
+      validate: (data: number) => data >= 1 && data <= 65535
+    });
+
+    this.ajv.addFormat('duration', {
+      type: 'string',
+      validate: /^\d+[smhd]$/
+    });
+  }
+
+  validate(configData: any, schemaName: string): ValidationResult {
+    const validate = this.ajv.getSchema(schemaName);
+    if (!validate) throw new Error(`Schema '${schemaName}' not found`);
+
+    const valid = validate(configData);
+
+    if (!valid && validate.errors) {
+      return {
+        valid: false,
+        errors: validate.errors.map(error => ({
+          path: error.instancePath || '/',
+          message: error.message || 'Validation error',
+          keyword: error.keyword
+        }))
+      };
+    }
+    return { valid: true };
+  }
+}
+
+// Example schema
+export const schemas = {
+  database: {
+    type: 'object',
+    properties: {
+      host: { type: 'string', format: 'hostname' },
+      port: { type: 'integer', format: 'port' },
+      database: { type: 'string', minLength: 1 },
+      user: { type: 'string', minLength: 1 },
+      password: { type: 'string', minLength: 8 },
+      ssl: {
+        type: 'object',
+        properties: {
+          enabled: { type: 'boolean' }
+        },
+        required: ['enabled']
+      }
+    },
+    required: ['host', 'port', 'database', 'user', 'password']
+  }
+};
+```
+
+### 3. Environment-Specific Validation
+
+```python
+from typing import Dict, List, Any
+
+class EnvironmentValidator:
+    def __init__(self):
+        self.environments = ['development', 'staging', 'production']
+        self.environment_rules = {
+            'development': {
+                'allow_debug': True,
+                'require_https': False,
+                'min_password_length': 8
+            },
+            'production': {
+                'allow_debug': False,
+                'require_https': True,
+                'min_password_length': 16,
+                'require_encryption': True
+            }
+        }
+
+    def validate_config(self, config: Dict, environment: str) -> List[Dict]:
+        if environment not in self.environment_rules:
+            raise ValueError(f"Unknown environment: {environment}")
+
+        rules = self.environment_rules[environment]
+        violations = []
+
+        if not rules['allow_debug'] and config.get('debug', False):
+            violations.append({
+                'rule': 'no_debug_in_production',
+                'message': 'Debug mode not allowed in production',
+                'severity': 'critical'
+            })
+
+        if rules['require_https']:
+            urls = self._extract_urls(config)
+            for url_path, url in urls:
+                if url.startswith('http://') and 'localhost' not in url:
+                    violations.append({
+                        'rule': 'require_https',
+                        'message': f'HTTPS required for {url_path}',
+                        'severity': 'high'
+                    })
+
+        return violations
+```
+
+### 4. Configuration Testing
+
+```typescript
+import { describe, it, expect } from '@jest/globals';
+import { ConfigValidator } from './config-validator';
+
+describe('Configuration Validation', () => {
+  let validator: ConfigValidator;
+
+  beforeEach(() => {
+    validator = new ConfigValidator();
+  });
+
+  it('should validate database config', () => {
+    const config = {
+      host: 'localhost',
+      port: 5432,
+      database: 'myapp',
+      user: 'dbuser',
+      password: 'securepass123'
+    };
+
+    const result = validator.validate(config, 'database');
+    expect(result.valid).toBe(true);
+  });
+
+  it('should reject invalid port', () => {
+    const config = {
+      host: 'localhost',
+      port: 70000,
+      database: 'myapp',
+      user: 'dbuser',
+      password: 'securepass123'
+    };
+
+    const result = validator.validate(config, 'database');
+    expect(result.valid).toBe(false);
+  });
+});
+```
+
+### 5. Runtime Validation
+
+```typescript
+import { EventEmitter } from 'events';
+import * as chokidar from 'chokidar';
+
+export class RuntimeConfigValidator extends EventEmitter {
+  private validator: ConfigValidator;
+  private currentConfig: any;
+
+  async initialize(configPath: string): Promise<void> {
+    this.currentConfig = await this.loadAndValidate(configPath);
+    this.watchConfig(configPath);
+  }
+
+  private async loadAndValidate(configPath: string): Promise<any> {
+    const config = await this.loadConfig(configPath);
+
+    const validationResult = this.validator.validate(
+      config,
+      this.detectEnvironment()
+    );
+
+    if (!validationResult.valid) {
+      this.emit('validation:error', {
+        path: configPath,
+        errors: validationResult.errors
+      });
+
+      if (!this.isDevelopment()) {
+        throw new Error('Configuration validation failed');
+      }
+    }
+
+    return config;
+  }
+
+  private watchConfig(configPath: string): void {
+    const watcher = chokidar.watch(configPath, {
+      persistent: true,
+      ignoreInitial: true
+    });
+
+    watcher.on('change', async () => {
+      try {
+        const newConfig = await this.loadAndValidate(configPath);
+
+        if (JSON.stringify(newConfig) !== JSON.stringify(this.currentConfig)) {
+          this.emit('config:changed', {
+            oldConfig: this.currentConfig,
+            newConfig
+          });
+          this.currentConfig = newConfig;
+        }
+      } catch (error) {
+        this.emit('config:error', { error });
+      }
+    });
+  }
+}
+```
+
+### 6. Configuration Migration
+
+```python
+from typing import Dict
+from abc import ABC, abstractmethod
+import semver
+
+class ConfigMigration(ABC):
+    @property
+    @abstractmethod
+    def version(self) -> str:
+        pass
+
+    @abstractmethod
+    def up(self, config: Dict) -> Dict:
+        pass
+
+    @abstractmethod
+    def down(self, config: Dict) -> Dict:
+        pass
+
+class ConfigMigrator:
+    def __init__(self):
+        self.migrations: List[ConfigMigration] = []
+
+    def migrate(self, config: Dict, target_version: str) -> Dict:
+        current_version = config.get('_version', '0.0.0')
+
+        if semver.compare(current_version, target_version) == 0:
+            return config
+
+        result = config.copy()
+        for migration in self.migrations:
+            if (semver.compare(migration.version, current_version) > 0 and
+                semver.compare(migration.version, target_version) <= 0):
+                result = migration.up(result)
+                result['_version'] = migration.version
+
+        return result
+```
+
+### 7. Secure Configuration
+
+```typescript
+import * as crypto from 'crypto';
+
+interface EncryptedValue {
+  encrypted: true;
+  value: string;
+  algorithm: string;
+  iv: string;
+  authTag?: string;
+}
+
+export class SecureConfigManager {
+  private encryptionKey: Buffer;
+
+  constructor(masterKey: string) {
+    this.encryptionKey = crypto.pbkdf2Sync(masterKey, 'config-salt', 100000, 32, 'sha256');
+  }
+
+  encrypt(value: any): EncryptedValue {
+    const algorithm = 'aes-256-gcm';
+    const iv = crypto.randomBytes(16);
+    const cipher = crypto.createCipheriv(algorithm, this.encryptionKey, iv);
+
+    let encrypted = cipher.update(JSON.stringify(value), 'utf8', 'hex');
+    encrypted += cipher.final('hex');
+
+    return {
+      encrypted: true,
+      value: encrypted,
+      algorithm,
+      iv: iv.toString('hex'),
+      authTag: cipher.getAuthTag().toString('hex')
+    };
+  }
+
+  decrypt(encryptedValue: EncryptedValue): any {
+    const decipher = crypto.createDecipheriv(
+      encryptedValue.algorithm,
+      this.encryptionKey,
+      Buffer.from(encryptedValue.iv, 'hex')
+    );
+
+    if (encryptedValue.authTag) {
+      decipher.setAuthTag(Buffer.from(encryptedValue.authTag, 'hex'));
+    }
+
+    let decrypted = decipher.update(encryptedValue.value, 'hex', 'utf8');
+    decrypted += decipher.final('utf8');
+
+    return JSON.parse(decrypted);
+  }
+
+  async processConfig(config: any): Promise<any> {
+    const processed = {};
+
+    for (const [key, value] of Object.entries(config)) {
+      if (this.isEncryptedValue(value)) {
+        processed[key] = this.decrypt(value as EncryptedValue);
+      } else if (typeof value === 'object' && value !== null) {
+        processed[key] = await this.processConfig(value);
+      } else {
+        processed[key] = value;
+      }
+    }
+
+    return processed;
+  }
+}
+```
+
+### 8. Documentation Generation
+
+```python
+from typing import Dict, List
+import yaml
+
+class ConfigDocGenerator:
+    def generate_docs(self, schema: Dict, examples: Dict) -> str:
+        docs = ["# Configuration Reference\n"]
+
+        docs.append("## Configuration Options\n")
+        sections = self._generate_sections(schema.get('properties', {}), examples)
+        docs.extend(sections)
+
+        return '\n'.join(docs)
+
+    def _generate_sections(self, properties: Dict, examples: Dict, level: int = 3) -> List[str]:
+        sections = []
+
+        for prop_name, prop_schema in properties.items():
+            sections.append(f"{'#' * level} {prop_name}\n")
+
+            if 'description' in prop_schema:
+                sections.append(f"{prop_schema['description']}\n")
+
+            sections.append(f"**Type:** `{prop_schema.get('type', 'any')}`\n")
+
+            if 'default' in prop_schema:
+                sections.append(f"**Default:** `{prop_schema['default']}`\n")
+
+            if prop_name in examples:
+                sections.append("**Example:**\n```yaml")
+                sections.append(yaml.dump({prop_name: examples[prop_name]}))
+                sections.append("```\n")
+
+        return sections
+```
+
+## Output Format
+
+1. **Configuration Analysis**: Current configuration assessment
+2. **Validation Schemas**: JSON Schema definitions
+3. **Environment Rules**: Environment-specific validation
+4. **Test Suite**: Configuration tests
+5. **Migration Scripts**: Version migrations
+6. **Security Report**: Issues and recommendations
+7. **Documentation**: Auto-generated reference
+
+Focus on preventing configuration errors, ensuring consistency, and maintaining security best practices.

package/skills/design-md/SKILL.md

@@ -0,0 +1,178 @@
+---
+name: design-md
+description: "Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files"
+source: "https://github.com/google-labs-code/stitch-skills/tree/main/skills/design-md"
+risk: safe
+---
+
+# Stitch DESIGN.md Skill
+
+You are an expert Design Systems Lead. Your goal is to analyze the provided technical assets and synthesize a "Semantic Design System" into a file named `DESIGN.md`.
+
+## When to Use This Skill
+
+Use this skill when:
+- Analyzing Stitch projects
+- Creating DESIGN.md files
+- Synthesizing semantic design systems
+- Working with Stitch design language
+- Generating design documentation for Stitch projects
+
+## Overview
+
+This skill helps you create `DESIGN.md` files that serve as the "source of truth" for prompting Stitch to generate new screens that align perfectly with existing design language. Stitch interprets design through "Visual Descriptions" supported by specific color values.
+
+## Prerequisites
+
+- Access to the Stitch MCP Server
+- A Stitch project with at least one designed screen
+- Access to the Stitch Effective Prompting Guide: https://stitch.withgoogle.com/docs/learn/prompting/
+
+## The Goal
+
+The `DESIGN.md` file will serve as the "source of truth" for prompting Stitch to generate new screens that align perfectly with the existing design language. Stitch interprets design through "Visual Descriptions" supported by specific color values.
+
+## Retrieval and Networking
+
+To analyze a Stitch project, you must retrieve screen metadata and design assets using the Stitch MCP Server tools:
+
+1. **Namespace discovery**: Run `list_tools` to find the Stitch MCP prefix. Use this prefix (e.g., `mcp_stitch:`) for all subsequent calls.
+
+2. **Project lookup** (if Project ID is not provided):
+   - Call `[prefix]:list_projects` with `filter: "view=owned"` to retrieve all user projects
+   - Identify the target project by title or URL pattern
+   - Extract the Project ID from the `name` field (e.g., `projects/13534454087919359824`)
+
+3. **Screen lookup** (if Screen ID is not provided):
+   - Call `[prefix]:list_screens` with the `projectId` (just the numeric ID, not the full path)
+   - Review screen titles to identify the target screen (e.g., "Home", "Landing Page")
+   - Extract the Screen ID from the screen's `name` field
+
+4. **Metadata fetch**: 
+   - Call `[prefix]:get_screen` with both `projectId` and `screenId` (both as numeric IDs only)
+   - This returns the complete screen object including:
+     - `screenshot.downloadUrl` - Visual reference of the design
+     - `htmlCode.downloadUrl` - Full HTML/CSS source code
+     - `width`, `height`, `deviceType` - Screen dimensions and target platform
+     - Project metadata including `designTheme` with color and style information
+
+5. **Asset download**:
+   - Use `web_fetch` or `read_url_content` to download the HTML code from `htmlCode.downloadUrl`
+   - Optionally download the screenshot from `screenshot.downloadUrl` for visual reference
+   - Parse the HTML to extract Tailwind classes, custom CSS, and component patterns
+
+6. **Project metadata extraction**:
+   - Call `[prefix]:get_project` with the project `name` (full path: `projects/{id}`) to get:
+     - `designTheme` object with color mode, fonts, roundness, custom colors
+     - Project-level design guidelines and descriptions
+     - Device type preferences and layout principles
+
+## Analysis & Synthesis Instructions
+
+### 1. Extract Project Identity (JSON)
+- Locate the Project Title
+- Locate the specific Project ID (e.g., from the `name` field in the JSON)
+
+### 2. Define the Atmosphere (Image/HTML)
+Evaluate the screenshot and HTML structure to capture the overall "vibe." Use evocative adjectives to describe the mood (e.g., "Airy," "Dense," "Minimalist," "Utilitarian").
+
+### 3. Map the Color Palette (Tailwind Config/JSON)
+Identify the key colors in the system. For each color, provide:
+- A descriptive, natural language name that conveys its character (e.g., "Deep Muted Teal-Navy")
+- The specific hex code in parentheses for precision (e.g., "#294056")
+- Its specific functional role (e.g., "Used for primary actions")
+
+### 4. Translate Geometry & Shape (CSS/Tailwind)
+Convert technical `border-radius` and layout values into physical descriptions:
+- Describe `rounded-full` as "Pill-shaped"
+- Describe `rounded-lg` as "Subtly rounded corners"
+- Describe `rounded-none` as "Sharp, squared-off edges"
+
+### 5. Describe Depth & Elevation
+Explain how the UI handles layers. Describe the presence and quality of shadows (e.g., "Flat," "Whisper-soft diffused shadows," or "Heavy, high-contrast drop shadows").
+
+## Output Guidelines
+
+- **Language:** Use descriptive design terminology and natural language exclusively
+- **Format:** Generate a clean Markdown file following the structure below
+- **Precision:** Include exact hex codes for colors while using descriptive names
+- **Context:** Explain the "why" behind design decisions, not just the "what"
+
+## Output Format (DESIGN.md Structure)
+
+```markdown
+# Design System: [Project Title]
+**Project ID:** [Insert Project ID Here]
+
+## 1. Visual Theme & Atmosphere
+(Description of the mood, density, and aesthetic philosophy.)
+
+## 2. Color Palette & Roles
+(List colors by Descriptive Name + Hex Code + Functional Role.)
+
+## 3. Typography Rules
+(Description of font family, weight usage for headers vs. body, and letter-spacing character.)
+
+## 4. Component Stylings
+* **Buttons:** (Shape description, color assignment, behavior).
+* **Cards/Containers:** (Corner roundness description, background color, shadow depth).
+* **Inputs/Forms:** (Stroke style, background).
+
+## 5. Layout Principles
+(Description of whitespace strategy, margins, and grid alignment.)
+```
+
+## Usage Example
+
+To use this skill for the Furniture Collection project:
+
+1. **Retrieve project information:**
+   ```
+   Use the Stitch MCP Server to get the Furniture Collection project
+   ```
+
+2. **Get the Home page screen details:**
+   ```
+   Retrieve the Home page screen's code, image, and screen object information
+   ```
+
+3. **Reference best practices:**
+   ```
+   Review the Stitch Effective Prompting Guide at:
+   https://stitch.withgoogle.com/docs/learn/prompting/
+   ```
+
+4. **Analyze and synthesize:**
+   - Extract all relevant design tokens from the screen
+   - Translate technical values into descriptive language
+   - Organize information according to the DESIGN.md structure
+
+5. **Generate the file:**
+   - Create `DESIGN.md` in the project directory
+   - Follow the prescribed format exactly
+   - Ensure all color codes are accurate
+   - Use evocative, designer-friendly language
+
+## Best Practices
+
+- **Be Descriptive:** Avoid generic terms like "blue" or "rounded." Use "Ocean-deep Cerulean (#0077B6)" or "Gently curved edges"
+- **Be Functional:** Always explain what each design element is used for
+- **Be Consistent:** Use the same terminology throughout the document
+- **Be Visual:** Help readers visualize the design through your descriptions
+- **Be Precise:** Include exact values (hex codes, pixel values) in parentheses after natural language descriptions
+
+## Tips for Success
+
+1. **Start with the big picture:** Understand the overall aesthetic before diving into details
+2. **Look for patterns:** Identify consistent spacing, sizing, and styling patterns
+3. **Think semantically:** Name colors by their purpose, not just their appearance
+4. **Consider hierarchy:** Document how visual weight and importance are communicated
+5. **Reference the guide:** Use language and patterns from the Stitch Effective Prompting Guide
+
+## Common Pitfalls to Avoid
+
+- ❌ Using technical jargon without translation (e.g., "rounded-xl" instead of "generously rounded corners")
+- ❌ Omitting color codes or using only descriptive names
+- ❌ Forgetting to explain functional roles of design elements
+- ❌ Being too vague in atmosphere descriptions
+- ❌ Ignoring subtle design details like shadows or spacing patterns