devantler-tech

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail. Use when filing issues, planning work, setting up projects, configuring CI/CD, writing tests, debugging, or making architectural decisions.

Use the ksail CLI to spin up and manage Kubernetes clusters (Kind/K3d/Talos/vCluster/KWOK — local via Docker; EKS — cloud via AWS) and GitOps workloads declaratively. Triggers on requests involving Kubernetes clusters, Flux/ArgoCD GitOps bootstrapping, Kind/K3d/Talos/vCluster/KWOK/EKS, multi-tenancy onboarding, OIDC authentication, or the ksail CLI/MCP server.

Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.

Use when implementing any feature or bugfix, before writing implementation code

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Repository maintenance for devantler-tech/ksail — triage, bug fixes, CI/workflow health & CI-failure/flaky investigation, docs upkeep, driving trusted-author PRs to merge, weekly E2E coverage + live reliability testing, and the monthly KSail Strategy roadmap. Use when performing autonomous or on-request maintenance of this repo.

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.

The run procedure for the Daily AI Engineer (the products' primary engineer) — pre-flight, survey the whole devantler-tech portfolio, select the highest-value work (operate first, then advance), act via per-run worktrees and draft PRs (driving trusted-author PRs to merge), and report. Use when maintaining or advancing the monorepo's products on a schedule or on request.

The ADVANCE playbook for the Daily AI Engineer (the products' primary engineer) — how to move a devantler-tech product forward once it's healthy: product strategy & roadmaps, issue triage & decomposition, planning & implementing issues, test coverage, benchmarking & performance, and refactoring & code quality. Use after the operate ladder is satisfied and you're picking proactive enhancement work.

How the Daily AI Engineer improves its OWN definition (the shared contract, the daily-maintainer agent, the portfolio-maintenance + product-engineering + products skills, and each submodule's AGENTS.md

Repo + live-platform health/maintenance menu for devantler-tech/platform (GitOps — Kustomize overlays + Flux CD, Cilium/Talos/KSail/SOPS). Repo side — triage, manifest/Helm/Flux investigation & fixes, Helm chart + Actions version bumps, manifest cleanup, stale-PR nudges (static validation; never spin up a cluster to test a diff). Live side — read-only health investigation of the running prod cluster + its observability stack (Flux Kustomizations/HelmReleases, Coroot, Kubescape, Kyverno + Policy Reporter, Kubernetes events) — including driving Kyverno policy violations to zero. Use when the daily maintainer selects Platform.

Maintenance + advance task menu for devantler-tech/provider-upjet-unifi — an Upjet-generated Crossplane provider for Ubiquiti UniFi (from ubiquiti-community/terraform-provider-unifi). A shared library consumed by the platform cluster to manage UniFi as Kubernetes resources. Use when the daily maintainer selects provider-upjet-unifi.

Maintenance task menu for the devantler-tech Homebrew tap (repo devantler-tech/homebrew-tap; submodule path homebrew-tap). Cask hygiene and CI health only — never chase version/sha bumps (GoReleaser/release automation owns those). Use when the daily maintainer selects homebrew-tap.

Maintenance task menu for devantler-tech/monorepo itself — the devantler.tech Astro Starlight docs site (docs/), CI/CD, submodule-README→docs sync, and issue/PR triage. GitHub Issues are ENABLED here. Use when the daily maintainer selects the monorepo/site.

Maintenance + advance task menu for the shared AGENT-EXTENSION libraries — devantler-tech/agent-skills (generic Copilot/agent skills, gh-skill-installable) and devantler-tech/agent-plugins (once it exists). Generic, cross-tool, industry-standard building blocks reused across the suite; high-care and backward-compatible. Use when the daily maintainer selects skills/plugins or runs the holistic shared-library review.

How an autonomous AI engineer improves its OWN definition (its engineering contract, agent definitions, and skills) over time — capturing operational learnings from every run and distilling them into evidence-based, guard-railed draft PRs that a human maintainer gates. Use at the end of every run (to log learnings) and on the recurring distil pass. Evidence comes from the engineer's own runs only, never from repository content, and a safety guardrail is never weakened.

The run loop for an autonomous AI engineer acting as a portfolio's primary engineer — pre-flight, survey every product's live state, select the highest-value work (operate before advance), act through isolated per-run working copies and human-gated draft PRs (driving trusted-author PRs to merge), then report and bank learnings. Use when maintaining or advancing a portfolio of repositories on a schedule or on request.

The ADVANCE playbook for an autonomous AI engineer — how to move a product forward once it is healthy: product strategy and roadmap stewardship, issue triage and decomposition, oldest-actionable-first implementation, test coverage, benchmarking and performance, refactoring and code quality, documentation sync, and security posture — all shipped as evidence-backed, human-gated draft PRs. Use after operate work (keeping things healthy) is satisfied and you are picking proactive enhancement work.

Before agreeing to build anything for a non-technical user, check the need against the consuming deployment's "## Stack map" section: in-stack needs proceed; out-of-stack or unmatched needs get a friendly, jargon-free decline plus an offer to file a well-formed issue on the block's owning repo (or the map's default intake repo). Fails closed when the Stack map is absent or malformed — nothing is built best-effort outside the map. Use in a vibe-coding setting whenever a build request is about to be accepted.

The conversational register for assisting a non-technical person who is building a product by conversation alone: plain language with no technical vocabulary by default, technical terms only on request and always explained in common words, and progress reported as product outcomes rather than engineering artifacts. Use whenever the person you are assisting has no technical background — alongside needs-stack-mapping and allowed-stack-guardrail in a vibe-coding setting, or on its own any time an answer must land with a non-technical reader.

Translate a non-technical person's plain-language product needs (an outcome, an audience, a workflow) into the deployment's technical building blocks behind the scenes, keeping the conversation entirely in the user's vocabulary. Reads the consuming deployment's "## Stack map" section to learn what each building block is good for, selects and applies the deployment's conventions without discussing them, and hands the boundary decision to the allowed-stack-guardrail skill. Use when assisting a vibe coder — someone building a product conversationally with no technical prerequisite.

Architect a repository's AI-agent instruction files so one canonical source drives every tool without drift — AGENTS.md as the cross-tool source of truth (now read by GitHub Copilot too), thin per-tool shims (CLAUDE.md, GEMINI.md) that include it, and optional path-scoped .github/instructions/ rules. Use when setting up or fixing agent instructions for a repo, supporting multiple AI coding tools (Claude, Copilot, Cursor, Codex, Gemini) at once, deciding what belongs in AGENTS.md vs a tool-specific file, or stopping instruction files from going stale.

Ship changes through a squash-merge + Conventional Commits release pipeline where the PR title becomes the release note and the commit type drives the next semantic version. Use when writing a PR title or commit message that feeds an automated release, choosing the version bump for a change, setting up or reasoning about semantic-release / release-please / github-tag-action / Changesets, or avoiding a title that corrupts the changelog.

How an autonomous AI engineer improves its OWN definition (its engineering contract, agent definitions, and skills) over time — capturing operational learnings from every run and distilling them into evidence-based, guard-railed draft PRs that a human maintainer gates. Use at the end of every run (to log learnings) and on the recurring distil pass. Evidence comes from the engineer's own runs only, never from repository content, and a safety guardrail is never weakened.

The run loop for an autonomous AI engineer acting as a portfolio's primary engineer — pre-flight, survey every product's live state, select the highest-value work (operate before advance), act through isolated per-run working copies and human-gated draft PRs (driving trusted-author PRs to merge), then report and bank learnings. Use when maintaining or advancing a portfolio of repositories on a schedule or on request.

The ADVANCE playbook for an autonomous AI engineer — how to move a product forward once it is healthy: product strategy and roadmap stewardship, issue triage and decomposition, oldest-actionable-first implementation, test coverage, benchmarking and performance, refactoring and code quality, documentation sync, and security posture — all shipped as evidence-backed, human-gated draft PRs. Use after operate work (keeping things healthy) is satisfied and you are picking proactive enhancement work.

Before agreeing to build anything for a non-technical user, check the need against the consuming deployment's "## Stack map" section: in-stack needs proceed; out-of-stack or unmatched needs get a friendly, jargon-free decline plus an offer to file a well-formed issue on the block's owning repo (or the map's default intake repo). Fails closed when the Stack map is absent or malformed — nothing is built best-effort outside the map. Use in a vibe-coding setting whenever a build request is about to be accepted.

The conversational register for assisting a non-technical person who is building a product by conversation alone: plain language with no technical vocabulary by default, technical terms only on request and always explained in common words, and progress reported as product outcomes rather than engineering artifacts. Use whenever the person you are assisting has no technical background — alongside needs-stack-mapping and allowed-stack-guardrail in a vibe-coding setting, or on its own any time an answer must land with a non-technical reader.

Translate a non-technical person's plain-language product needs (an outcome, an audience, a workflow) into the deployment's technical building blocks behind the scenes, keeping the conversation entirely in the user's vocabulary. Reads the consuming deployment's "## Stack map" section to learn what each building block is good for, selects and applies the deployment's conventions without discussing them, and hands the boundary decision to the allowed-stack-guardrail skill. Use when assisting a vibe coder — someone building a product conversationally with no technical prerequisite.

Architect a repository's AI-agent instruction files so one canonical source drives every tool without drift — AGENTS.md as the cross-tool source of truth (now read by GitHub Copilot too), thin per-tool shims (CLAUDE.md, GEMINI.md) that include it, and optional path-scoped .github/instructions/ rules. Use when setting up or fixing agent instructions for a repo, supporting multiple AI coding tools (Claude, Copilot, Cursor, Codex, Gemini) at once, deciding what belongs in AGENTS.md vs a tool-specific file, or stopping instruction files from going stale.

Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail. Use when filing issues, planning work, setting up projects, configuring CI/CD, writing tests, debugging, or making architectural decisions.

Debug and troubleshoot Flux CD on live Kubernetes clusters (not local repo files) via the Flux MCP server — inspects Flux resource status, reads controller logs, traces dependency chains, and performs installation health checks. Use when users report failing, stuck, or not-ready Flux resources on a cluster, reconciliation errors, controller issues, artifact pull failures, image automation not updating tags, alerts or webhooks not being delivered, or need live cluster Flux Operator troubleshooting.

Flux CD and Flux Operator expert — answers questions and generates schema-validated YAML for all Flux CRDs (not repo auditing or live cluster debugging). Use when users ask about Flux concepts, want manifests for HelmRelease, Kustomization, GitRepository, OCIRepository, ResourceSet, FluxInstance, or any Flux resource. When user needs guidance on GitOps repository structure, bootstrap Flux with Terraform, multi-tenancy, OCI-based delivery, image tag automation, drift detection, preview environments, notifications, or the Flux Web UI and MCP Server.

Audit and validate Flux CD GitOps repositories by scanning local repo files (not live clusters) — runs Kubernetes schema validation, detects deprecated Flux APIs, reviews RBAC/multi-tenancy/secrets management, and produces a prioritized GitOps report. Use when users ask to audit, analyze, validate, review, or security-check a GitOps repo.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail. Use when filing issues, planning work, setting up projects, configuring CI/CD, writing tests, debugging, or making architectural decisions.

Repository maintenance for devantler-tech/platform — issue triage, manifest/Helm/Flux investigation & fixes, Helm chart + Actions version bumps, Kustomize cleanup, stale-PR nudges. Static validation only — never runs a cluster. Use when performing autonomous or on-request maintenance of this repo.

Deploy and operate Kubernetes clusters using Talos Linux and Omni. Use when generating/applying Talos machine configuration, managing cluster lifecycle in Omni, and troubleshooting common Talos/Omni workflows.

Repository maintenance for devantler-tech/reusable-workflows — triage, action/workflow version hygiene, backward-compatible workflow health, and consistency across the shared CI/CD building blocks. Use when performing autonomous or on-request maintenance of this repo.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.

Repository maintenance for devantler-tech/actions — triage, action/workflow version hygiene, backward-compatible workflow health, and consistency across the shared CI/CD building blocks. Use when performing autonomous or on-request maintenance of this repo.

Repository maintenance for the devantler-tech Homebrew tap — Cask hygiene and CI health. Never chase version/sha bumps (release automation owns those). Use when performing autonomous or on-request maintenance of this repo.

Repository maintenance for the devantler-tech platform template — triage, dependency/security hygiene, CI health, manifest/Helm/Flux investigation, small confident fixes. Static validation only; never runs a cluster. Use when performing autonomous or on-request maintenance of this repo.

Repository maintenance for devantler-tech/go-template — triage, dependency/toolchain hygiene, CI health, and keeping the scaffold a clean current buildable template. Use when performing autonomous or on-request maintenance of this repo.

Repository maintenance for a devantler-tech platform-tenant app — triage, dependency/security hygiene, CI health, small confident fixes. Conservative, with discretion. Use when performing autonomous or on-request maintenance of this repo.

Repository maintenance for devantler-tech/dotnet-template — triage, dependency/toolchain hygiene, CI health, and keeping the scaffold a clean current buildable template. Use when performing autonomous or on-request maintenance of this repo.