@vyuhlabs/dxkit 2.4.8 → 2.5.1

package/templates/.claude/skills/deploy/SKILL.md.template

@@ -1,131 +0,0 @@
----
-name: deploy
-description: Deploy services, release to production, push to cloud. Use when asked about deployment, releases, shipping to production, or CI/CD.
----
-
-# Deployment
-
-## Commands
-- `make deploy` - Deploy services (configure deployment target first)
-- `make build` - Build before deploying
-- `make check` - Run full validation before deploying
-
-## Pre-Deployment Checklist
-- [ ] `make check` passes (quality + tests + validation)
-- [ ] All changes committed and pushed
-- [ ] PR reviewed and approved
-{{#IF_INFISICAL}}
-- [ ] Secrets pulled: `make secrets-pull`
-{{/IF_INFISICAL}}
-- [ ] No hardcoded secrets in code or config
-
-## Deployment Safety
-
-**CRITICAL: Never auto-approve destructive deployment operations.**
-
-- Always preview/dry-run before applying changes
-- Require explicit user confirmation for production deployments
-- Never force-push or skip CI checks before deploying
-{{#IF_INFISICAL}}
-
-## Secrets for Deployment
-
-Pull secrets before deploying:
-```bash
-make secrets-pull     # fetch from Infisical to .env
-make secrets-show     # verify configuration (masked values)
-```
-
-**Never pass secrets as CLI arguments** — use environment variables or secret managers.
-{{/IF_INFISICAL}}
-
-{{#IF_GCLOUD}}
-## Google Cloud Deployment
-
-### Cloud Run
-```bash
-# Build and push container
-gcloud builds submit --tag gcr.io/$PROJECT_ID/<service-name>
-
-# Deploy (ALWAYS review before confirming)
-gcloud run deploy <service-name> \
-  --image gcr.io/$PROJECT_ID/<service-name> \
-  --region <region> \
-  --platform managed
-```
-
-### GKE
-```bash
-# Build image
-docker build -t gcr.io/$PROJECT_ID/<service-name> .
-docker push gcr.io/$PROJECT_ID/<service-name>
-
-# Apply manifests (review first)
-kubectl apply -f k8s/ --dry-run=client  # preview
-kubectl apply -f k8s/                    # apply
-```
-
-**Security:** Use Workload Identity for GCP auth in production — never embed service account keys.
-{{/IF_GCLOUD}}
-
-{{#IF_PULUMI}}
-## Pulumi Deployment
-
-```bash
-# ALWAYS preview first
-pulumi preview
-
-# Review the diff carefully, then apply
-pulumi up
-
-# Check outputs
-pulumi stack output
-```
-
-**Security:** Use `pulumi config set --secret` for sensitive config — never plain-text.
-
-**Never run `pulumi destroy` without explicit confirmation** — it deletes all resources.
-{{/IF_PULUMI}}
-
-{{#IF_DOCKER}}
-## Docker Deployment
-
-```bash
-# Build images
-docker-compose build
-
-# Push to registry
-docker-compose push
-
-# Deploy (depends on orchestration platform)
-docker-compose -f docker-compose.prod.yml up -d
-```
-
-**Security:** Never copy `.env` files into Docker images. Use runtime environment variables.
-{{/IF_DOCKER}}
-
-{{#IF_CSHARP}}
-## C# Deployment
-
-```bash
-# Framework-dependent (requires .NET runtime on target)
-dotnet publish -c Release -o out/ --self-contained false
-
-# Self-contained (no runtime needed on target)
-dotnet publish -c Release -r linux-x64 --self-contained true
-```
-
-For Docker, use multi-stage builds:
-- Build stage: `mcr.microsoft.com/dotnet/sdk:{{CSHARP_VERSION}}`
-- Runtime stage: `mcr.microsoft.com/dotnet/aspnet:{{CSHARP_VERSION}}`
-{{/IF_CSHARP}}
-
-## CI/CD
-
-CI pipeline (`.github/workflows/ci.yml`) runs automatically on PR:
-- Validation, quality checks, tests per enabled language
-- Coverage enforcement at {{COVERAGE_THRESHOLD}}%
-
-## Gotchas
-
-See [references/gotchas.md](references/gotchas.md) for known deployment issues.

package/templates/.claude/skills/deploy/references/gotchas.md

@@ -1,5 +0,0 @@
-# Deployment Gotchas
-
-<!-- This file grows over time. Each entry is added during session-end. -->
-<!-- Format: date, category, description, resolution -->
-<!-- NEVER include secret values, tokens, or credentials here -->

package/templates/.claude/skills/doctor/SKILL.md

@@ -1,54 +0,0 @@
----
-name: doctor
-description: Diagnose and fix development environment issues. Use when setup fails, tools are missing, the environment is broken, or something is misconfigured.
----
-
-# Doctor & Setup
-
-## Commands
-- `make doctor` - Diagnose common setup issues (checks files, toolchains, config)
-- `make setup` - Interactive setup for new developers
-- `make info` - Show project configuration dashboard
-- `make config` - Interactive configuration editor
-
-## What Doctor Checks
-1. Core files (`.project.yaml`, `Makefile`, `.project/`)
-2. YAML syntax validation
-3. Language toolchain versions (Python, Go, Node, Rust)
-4. Quality tools installation (linters, formatters)
-5. Pre-commit hook configuration
-6. Git configuration
-7. Docker/Docker Compose availability
-8. Service health (if infrastructure enabled)
-
-## Common Issues & Fixes
-
-### Missing tools
-```bash
-make doctor    # identify what's missing
-make setup     # re-run interactive setup
-```
-
-### Config out of sync
-```bash
-make sync          # re-sync .project.yaml to language files
-make sync-preview  # preview changes first (dry run)
-```
-
-### Pre-commit failures
-```bash
-make fix       # auto-fix all issues
-make check     # verify everything passes
-```
-
-### Build failures after config change
-```bash
-make sync      # sync config
-make clean     # clean artifacts
-make build     # rebuild
-```
-
-## Environment
-- DevContainer-based (see `.devcontainer/`)
-- `post-create.sh` runs automatically on container creation
-- All tools installed via devcontainer features or post-create script

package/templates/.claude/skills/gcloud/SKILL.md

@@ -1,66 +0,0 @@
----
-name: gcloud
-description: Google Cloud Platform operations — gcloud CLI, Cloud Run, GKE, BigQuery, IAM, GCS. Use when asked about GCP, Google Cloud, gcloud commands, or cloud infrastructure.
-paths:
-  - '**/cloudbuild.yaml'
-  - '**/cloudbuild.yml'
-  - '**/.gcloudignore'
-  - '**/app.yaml'
----
-
-# Google Cloud (gcloud)
-
-## Setup
-- **Auth:** `gcloud auth login` (configured during `make setup`)
-- **Project:** Set in `.env` as `GOOGLE_CLOUD_PROJECT`
-- **SDK:** Installed via devcontainer post-create script
-
-## Common Commands
-
-### Authentication & Project
-```bash
-gcloud auth list                              # check auth status
-gcloud config get-value project               # current project
-gcloud config set project <PROJECT_ID>        # switch project
-gcloud projects list                          # list accessible projects
-```
-
-### Services & Resources
-```bash
-gcloud services list --enabled                # enabled APIs
-gcloud run services list                      # Cloud Run services
-gcloud container clusters list                # GKE clusters
-gcloud sql instances list                     # Cloud SQL instances
-gcloud storage ls                             # GCS buckets
-```
-
-### Logs & Monitoring
-```bash
-gcloud logging read "resource.type=cloud_run_revision" --limit=50
-gcloud logging read "severity>=ERROR" --limit=20 --format=json
-```
-
-## Integration with Secrets
-
-GCP project ID is stored in `.env`:
-```
-GOOGLE_CLOUD_PROJECT=my-project-id
-```
-
-Use `make secrets-pull` to fetch GCP-related secrets from Infisical.
-
-## Security — CRITICAL
-
-1. **NEVER output `gcloud auth print-access-token`** — it exposes bearer tokens
-2. **NEVER output or log service account JSON keys**
-3. **NEVER embed credentials in code** — use Workload Identity or Application Default Credentials
-4. Use `gcloud auth application-default login` for local development
-5. In production, use Workload Identity Federation (not service account keys)
-
-## Deployment
-
-See the `deploy` skill for GCP deployment patterns (Cloud Run, GKE).
-
-## Gotchas
-
-See [references/gotchas.md](references/gotchas.md) for GCP-specific issues.

package/templates/.claude/skills/gcloud/references/gotchas.md

@@ -1,5 +0,0 @@
-# Google Cloud Gotchas
-
-<!-- This file grows over time. Each entry is added during session-end. -->
-<!-- Format: date, category, description, resolution -->
-<!-- NEVER include secret values, tokens, credentials, or project IDs here -->

package/templates/.claude/skills/learned/SKILL.md

@@ -1,55 +0,0 @@
----
-name: learned
-description: Project-specific learnings, gotchas, and conventions discovered during development. Check this before starting any task for accumulated team knowledge.
----
-
-# Learned Patterns & Gotchas
-
-This skill accumulates project-specific knowledge over time.
-It is updated during session-end checkpoints.
-
-## How This Works
-
-1. During `make session-end`, the checkpoint process reviews the session
-2. Any new gotchas, patterns, or conventions are appended to the reference files
-3. Over time, this becomes the most valuable skill — real failure points and patterns
-
-## Files
-
-- [references/gotchas.md](references/gotchas.md) - Accumulated gotchas and edge cases (append-only)
-- [references/conventions.md](references/conventions.md) - Team conventions discovered during development
-- [references/deny-recommendations.md](references/deny-recommendations.md) - Commands that should be added to `.claude/settings.json` deny list (requires human review)
-
-## When to Update
-
-Update these files when you encounter:
-- Unexpected behaviors or edge cases
-- Workarounds for tool/framework bugs
-- Team conventions or patterns that aren't obvious from the code
-- Configuration pitfalls
-- Deployment or environment-specific issues
-
-## When to Create a New Skill
-
-If a learning is significant enough to warrant its own skill (e.g., a specific API integration, a migration workflow, a caching pattern), create a new directory under `.claude/skills/<name>/` with a `SKILL.md` instead of appending here. This skill (`learned`) is for general cross-cutting knowledge; domain-specific knowledge deserves its own skill.
-
-## Format
-
-### Gotchas
-```markdown
-## YYYY-MM-DD - Category / Short Title
-Description of the issue.
-**Resolution:** How it was resolved.
-```
-
-### Conventions
-```markdown
-## Category - Convention Name
-Description of the convention.
-**Rationale:** Why this convention was adopted.
-```
-
-## Security
-
-**NEVER include secret values, tokens, passwords, or API keys in any file under this skill.**
-If a gotcha involves credentials, describe the issue generically without exposing actual values.

package/templates/.claude/skills/learned/references/conventions.md

@@ -1,11 +0,0 @@
-# Team Conventions
-
-<!-- Discovered conventions are added here during session-end. -->
-<!-- Format: category, convention, rationale -->
-<!-- NEVER include secret values, tokens, or credentials here -->
-
-<!-- Example:
-## Python - Use App Factory Pattern
-All FastAPI applications should use the app factory pattern (create_app function) rather than module-level app instantiation.
-**Rationale:** Enables test isolation and configuration flexibility. Adopted after test pollution issues in the auth service.
--->

package/templates/.claude/skills/learned/references/deny-recommendations.md

@@ -1,18 +0,0 @@
-# Deny Rule Recommendations
-
-<!--
-  This file tracks commands/actions that SHOULD be added to .claude/settings.json deny list.
-  Claude cannot modify settings.json directly (security boundary).
-  A developer should periodically review this file and promote entries to settings.json.
-
-  Format:
-  ## YYYY-MM-DD - Rule
-  `DenyPattern` — reason this should be blocked
-  **Context:** what happened that surfaced this need
--->
-
-<!-- Example:
-## 2025-12-15 - Block database drop
-`Bash(dropdb:*)` — accidentally dropped staging database during cleanup
-**Context:** Claude ran dropdb instead of truncating tables during test cleanup
--->

package/templates/.claude/skills/learned/references/gotchas.md

@@ -1,11 +0,0 @@
-# Project Gotchas
-
-<!-- This file grows over time. Each entry is added during session-end. -->
-<!-- Format: date, category, description, resolution -->
-<!-- NEVER include secret values, tokens, or credentials here -->
-
-<!-- Example:
-## 2025-12-15 - Python / Import Order
-ruff's isort rules conflict with local imports when using relative paths in the src/ directory.
-**Resolution:** Use absolute imports from package root (e.g., `from mypackage.module import X`).
--->

package/templates/.claude/skills/pulumi/SKILL.md

@@ -1,73 +0,0 @@
----
-name: pulumi
-description: Pulumi infrastructure as code — stacks, previews, deployments, config. Use when asked about IaC, Pulumi, cloud resources, infrastructure provisioning, or stack management.
-paths:
-  - 'Pulumi.yaml'
-  - 'Pulumi.yml'
-  - 'Pulumi.*.yaml'
-  - '**/Pulumi.yaml'
-  - '**/Pulumi.*.yaml'
----
-
-# Pulumi (Infrastructure as Code)
-
-## Setup
-- **Auth:** `pulumi login` (configured during `make setup`)
-- **SDK:** Installed via devcontainer post-create script
-- **Path:** `~/.pulumi/bin/pulumi`
-
-## Core Workflow
-
-**ALWAYS preview before applying changes:**
-
-```bash
-# 1. Preview changes (safe, read-only)
-pulumi preview
-
-# 2. Review the diff carefully
-
-# 3. Apply changes (REQUIRES explicit user confirmation)
-pulumi up
-
-# 4. Check outputs
-pulumi stack output
-```
-
-## Common Commands
-
-### Stack Management
-```bash
-pulumi stack ls                    # list stacks
-pulumi stack select <name>         # switch stack
-pulumi stack output                # view outputs
-pulumi stack export                # export state
-```
-
-### Configuration
-```bash
-pulumi config                     # view config
-pulumi config set key value       # set plain config
-pulumi config set --secret key value  # set encrypted secret
-pulumi config get key             # get value
-```
-
-### State & History
-```bash
-pulumi stack history              # deployment history
-pulumi state                      # inspect state
-pulumi refresh                    # sync state with cloud
-```
-
-## Security — CRITICAL
-
-1. **ALWAYS `pulumi preview` before `pulumi up`** — review the diff
-2. **NEVER run `pulumi destroy` without explicit user confirmation** — it deletes all resources
-3. **Use `pulumi config set --secret`** for sensitive values — never plain-text
-4. **NEVER output `pulumi config get --secret`** values in responses
-5. **State files may contain secrets** — ensure backend is secure (encrypted)
-6. Pulumi passphrase (if using local backend) should be in `.env`, never hardcoded
-
-## Integration
-
-- Secrets from Infisical can be used as Pulumi config values
-- GCP project from `.env` (`GOOGLE_CLOUD_PROJECT`) can configure Pulumi GCP provider

package/templates/.claude/skills/quality/SKILL.md.template

@@ -1,108 +0,0 @@
----
-name: quality
-description: Run code quality checks, linting, formatting, and auto-fixing. Use when asked to check code quality, fix lint errors, format code, or run pre-commit checks.
----
-
-# Code Quality
-
-## Commands
-- `make quality` - Run all quality checks (report: `tmp/reports/quality-report.md`)
-- `make quality-fix` - Auto-fix all fixable issues
-- `make lint` - Lint only
-- `make format` - Format all code
-- `make fix` - Fix + format (shorthand)
-- `make check` - Full pre-commit check (validate + quality + test)
-- `make format-check` - Check formatting without modifying
-
-## Quality Presets
-- `make quality-strict` - 90% coverage, all checks
-- `make quality-standard` - 80% coverage (default)
-- `make quality-relaxed` - 50% coverage
-- `make quality-off` - Disable checks
-- `make quality-config` - Show current settings
-
-{{#IF_PYTHON}}
-## Python
-
-**Tools:** ruff (lint + format), mypy (types)
-**Config:** `ruff.toml`, `pyproject.toml`
-**Script:** `.project/scripts/quality/lint-python.sh`
-
-Common fixes:
-```bash
-ruff check --fix .
-ruff format .
-mypy src/
-```
-
-Key ruff rules: pycodestyle (E), pyflakes (F), isort (I), mccabe (C90), bugbear (B).
-Per-file ignores configured in `ruff.toml` for tests (assertions, fixtures).
-{{/IF_PYTHON}}
-
-{{#IF_GO}}
-## Go
-
-**Tools:** golangci-lint (27 linters), gofmt, goimports
-**Config:** `.golangci.yml`
-**Script:** `.project/scripts/quality/lint-go.sh`
-
-Common fixes:
-```bash
-gofmt -w .
-goimports -w .
-golangci-lint run --fix
-```
-{{/IF_GO}}
-
-{{#IF_NODE}}
-## Node.js
-
-**Tools:** ESLint, Prettier
-Common fixes:
-```bash
-npx prettier --write .
-npx eslint --fix .
-```
-{{/IF_NODE}}
-
-{{#IF_NEXTJS}}
-## Next.js
-
-**Directory:** `frontend/`
-```bash
-cd frontend && npm run lint
-cd frontend && npx prettier --write .
-cd frontend && npx tsc --noEmit  # type check
-```
-{{/IF_NEXTJS}}
-
-{{#IF_RUST}}
-## Rust
-
-**Tools:** clippy, rustfmt
-```bash
-cargo fmt
-cargo clippy --fix --allow-dirty
-```
-{{/IF_RUST}}
-
-{{#IF_CSHARP}}
-## C#
-
-**Tools:** dotnet format, Roslyn Analyzers, StyleCop Analyzers
-**Config:** `.editorconfig`, `Directory.Build.props`
-
-Common fixes:
-```bash
-dotnet format                          # auto-fix formatting
-dotnet format --verify-no-changes      # CI check (no modifications)
-```
-{{/IF_CSHARP}}
-
-## Gotchas
-
-See [references/gotchas.md](references/gotchas.md) for known quality issues.
-
-## Security
-
-Never disable security-related lint rules. If a rule seems wrong, investigate before suppressing.

package/templates/.claude/skills/quality/references/gotchas.md

@@ -1,5 +0,0 @@
-# Quality Gotchas
-
-<!-- This file grows over time. Each entry is added during session-end. -->
-<!-- Format: date, category, description, resolution -->
-<!-- NEVER include secret values, tokens, or credentials here -->

package/templates/.claude/skills/review/SKILL.md.template

@@ -1,73 +0,0 @@
----
-name: review
-description: Review code for quality, security, and patterns. Use when asked to review code, a PR, check for problems, or audit for security issues.
----
-
-# Code Review
-
-## Quick Check
-Run `make check` first — it validates, lints, tests, and checks docs in one command.
-
-## Review Checklist
-
-### 1. Quality
-- [ ] `make quality` passes
-- [ ] Coverage meets threshold ({{COVERAGE_THRESHOLD}}%)
-- [ ] No suppressed lint rules without justification
-
-### 2. Security
-- [ ] No hardcoded secrets, API keys, tokens, or passwords
-- [ ] No secrets in commit messages, comments, or logs
-- [ ] User input is validated/sanitized at system boundaries
-- [ ] No SQL injection, XSS, or command injection vectors
-- [ ] Sensitive files are gitignored (`.env`, credentials)
-
-### 3. Testing
-- [ ] New features have tests
-- [ ] Edge cases and error paths tested
-- [ ] Tests are deterministic (no timing/order dependencies)
-
-### 4. Architecture
-- [ ] Follows existing patterns in the codebase
-- [ ] Dependencies injected (not imported directly in business logic)
-- [ ] Error handling is consistent
-
-{{#IF_PYTHON}}
-### Python-Specific
-- [ ] Type hints on public functions
-- [ ] Pydantic models for data validation
-- [ ] No bare `except:` — catch specific exceptions
-- [ ] Async/await used correctly (no blocking in async context)
-{{/IF_PYTHON}}
-
-{{#IF_GO}}
-### Go-Specific
-- [ ] Errors checked and handled (no `_` for errors)
-- [ ] Context propagated through call chains
-- [ ] Proper resource cleanup (defer for Close/Unlock)
-- [ ] Table-driven tests used where appropriate
-{{/IF_GO}}
-
-{{#IF_NEXTJS}}
-### Next.js-Specific
-- [ ] Server vs client components used correctly
-- [ ] No sensitive data in client components
-- [ ] TypeScript strict mode compliance
-{{/IF_NEXTJS}}
-
-{{#IF_CSHARP}}
-### C#-Specific
-- [ ] Nullable reference types enabled (`#nullable enable`)
-- [ ] Async/await used correctly (no blocking on async with `.Result` or `.Wait()`)
-- [ ] IDisposable resources properly disposed (`using` statements)
-- [ ] LINQ used appropriately (not in hot paths without reason)
-- [ ] Dependency injection used (no `new` for services)
-- [ ] No hardcoded connection strings
-{{/IF_CSHARP}}
-
-## Common Issues
-- Missing error handling
-- Hardcoded configuration (should use `.env` or config)
-- Missing tests for edge cases
-- Inconsistent naming conventions
-- Overly broad error catching