Use ZekTec with AI

Engineering Best Practices

Inspect a repository against customized engineering practices and propose or implement scoped improvements.

Example: Review this repository against our engineering practices and report the smallest useful changes.

Download skill · Documentation · Customize your skill

QA Testers Playbook

Prepare and execute evidence-backed testing using a customized QA playbook.

Example: Prepare a test plan for this change and report which checks you actually performed.

Download skill · Documentation · Customize your skill

Release & App Managers Playbook

Prepare release readiness checks, rollout plans, and rollback guidance using a customized release playbook.

Example: Prepare the staging release checklist and identify unresolved prerequisites.

Download skill · Documentation · Customize your skill

Advanced Actions Invoker

Generate and validate Composer JSON configuration and GitHub Actions workflow YAML for Advanced Actions Invoker.

Example: Create separate backend and frontend workflow forms with stage/prod selection and service checkboxes.

Download skill · Documentation

All The Versions

Diagnose runtimes, edit .tool-versions requirements, and install or remove versions using the local All The Versions MCP server.

Example: Explain which runtimes this repository needs and why my local setup differs.

Download skill · Documentation

Local MCP supports diagnosis, configuration edits, and runtime installation or removal. Write actions require explicit startup permissions.

Composer setup and compatibility

# Composer configuration and validation

Compatibility: Composer source version 0.1.1 with the configuration CLI introduced by the AI integration change. Older published packages may not include this CLI. Build from the tools repository after that change is merged.

Configuration has three objects: schema (JSON Schema), uischema (JSON Forms layout), and data (defaults). Workflow dispatch maps uischema to the input named layout. Do not use layout as the configuration key.

Use string enums for environment selection and boolean properties for service checkboxes. Use the project's existing environments; ZekTec uses dev, stage, and prod, usually stage and prod. Derive service names from the repository. For ZekTec deployment tasks, keep backend and frontend workflows separate and retain their existing deployment jobs.

Controls use JSON Pointer scopes such as #/properties/environment. Containers support VerticalLayout, HorizontalLayout, Group, Category, and Categorization. Every control must point to a schema property; defaults must satisfy constraints and required fields. UI formats such as toggle and color are renderer hints; the CLI validates JSON Schema constraints, not these visual formats.

In a checkout of https://github.com/zektec/zektec-tools, install the workspace dependencies and build the composer:

pnpm --filter @zektec/advanced-actions-invoker-composer build
node advanced-actions-invoker/composer/bin/composer.mjs validate /absolute/path/composer.json
node advanced-actions-invoker/composer/bin/composer.mjs generate /absolute/path/composer.json > /absolute/path/workflow.yml

The generated YAML is a dispatch scaffold that parses inputs. It does not deploy anything. Review and integrate existing deployment steps. Pass user inputs through environment variables or files; never interpolate them into executable shell text. Validate selected environments and services again before executing deployment operations. Native GitHub dispatch stays usable without the extension, but enhanced checkbox rendering requires Advanced Actions Invoker.

Connect All The Versions MCP

# Local runtime diagnosis and management

Build from the tools repository (https://github.com/zektec/zektec-tools):

cd all-the-versions
cargo build --release -p atv_core --bin atv-mcp

Configure your MCP client's stdio server using the absolute binary path and one or more explicit --root arguments. For example:

{ "mcpServers": { "all-the-versions": { "command": "/absolute/path/zektec-tools/all-the-versions/target/release/atv-mcp", "args": ["--root", "/absolute/path/repository", "--allow-file-writes", "--allow-runtime-writes"] } } }

This server is built from source; existing desktop downloads do not include it automatically. No remote endpoint, account, or token is required. MCP client configuration varies by client; copy the command and arguments into its supported format.

Operations: resolve_versions(path), diagnose(path, provider), list_installed_versions(provider, tool), export_report(path), read_configuration(path), set_version(path, tool, version, expected_content), remove_version(path, tool, expected_content), install_version(provider, tool, version), and uninstall_version(provider, tool, version). Provider is asdf, mise, nvm, fvm, or pyenv. Paths must be absolute and within an allowed root. The server reads .tool-versions files only within that root. To include inherited requirements from a parent folder, explicitly grant that parent as the root. Symbolic links to configuration outside the root are rejected. Provider inspection invokes the installed provider; only grant providers you trust on PATH.

Reports return JSON as tool content. Writes are optional: omit --allow-file-writes or --allow-runtime-writes to deny the respective actions. Read the directory's exact local configuration first; pass that content (or null for an absent file) as expected_content for edits. Edits preserve unrelated lines, reject symlinks and stale content, use an advisory lock and atomic replacement, and return a recovery backup path. External editors do not participate in the advisory lock. Inherited files are never edited automatically. Setting duplicate tool entries requires resolving them first.

Install/uninstall actions change the provider's global inventory, which can affect other repositories, and may execute trusted provider/plugin code. They do not change project requirements or install providers/plugins. Provider calls run synchronously and may take minutes; adjust client timeouts. Tool and runtime identifiers must start with an ASCII alphanumeric and contain only ASCII alphanumerics, dot, underscore, or hyphen (maximum 100 characters). Configuration versions may be several safe identifiers separated by single spaces; paths, shell expressions, and option flags are rejected. No arbitrary shell command or workflow-dispatch operation is exposed.