Menu
SkillsMP has collected 20 skills from xberg-io/agent-conventions. Open a skill to review its source and details.
Showing 20 of 20 collected skills.
Canonical xberg.io brand, product catalog, docs-site (Astro Starlight + @xberg-io/docs-theme), alef badge, docs task commands, prose style, Google Analytics IDs, brand assets, and README-template policy. Load when writing READMEs or docs, editing docs-site…
The shared Cargo feature-flag naming and semantics contract across xberg-io Rust libraries — the same flag names mean the same thing everywhere (otel, mcp/mcp-http, mimalloc/jemalloc, acceleration). Load when adding, renaming, or reviewing a crate's…
The canonical contract for tracing as a first-class product observability surface across xberg-io Rust libraries and services — level semantics, span/field naming, instrumentation patterns, and how xberg-enterprise consumes library spans over OTLP. Load when…
Standard shape of the CI/CD pipeline across xberg-io repos — per-domain GitHub Actions workflows, linters, OS matrix, quality gates and coverage thresholds, task-only invocation, and the Validate→Build→Test→Deploy stages. Load when adding or editing CI…
Conventions for using the gh CLI to manage PRs, issues, CI runs, and releases — squash merges, issue linking, monitoring and reruns, generated release notes. Load when creating or merging PRs, filing issues, monitoring/rerunning CI, or cutting a GitHub…
How to work with Alef-generated binding files and the task commands that regenerate, build, format, and verify them. Load when editing bindings, running task alef:*, or regenerating generated packages/e2e suites.
How to use basemind's MCP tools and CLI for structural and historical code questions instead of grep, file reads, and naked git. Load when navigating the codebase, finding definitions or call sites, exploring git history, or coordinating with other agents in…
Architecture rules for the polyglot binding layer and the C FFI boundary — crate naming, distribution paths, ownership and null-safety invariants, error-context propagation, and async patterns. Load when designing or editing language bindings, the C ABI,…
Common Taskfile commands across xberg-io repos — setup, build, test, lint, format, coverage, and bench. Load when running or discovering task commands, or unsure which task drives a build/test/lint step.
Reference for poly, the single-binary multi-language linter and formatter — per-language engines, the lint/fmt commands, poly.toml configuration, severity behavior, and the shared CI validation workflow. Load when linting or formatting code, configuring…
Developer quick-start for xberg-io repos — prerequisites, initial setup, and the core build/test/lint workflow. Load when onboarding to a repo or setting up a local dev environment for the first time.
Release/publish a Rust core crate or CLI in an xberg-io polyglot repo (crawlberg, html-to-markdown, xberg, tree-sitter-language-pack, liter-llm). Load when releasing or publishing a Rust crate or CLI — cutting a new version, tagging, running `gh release…
Standard Taskfile conventions across xberg-io repos — task discovery, common and language-scoped tasks, build profiles, the alef and e2e task families, lock-file discipline. Load when running or adding tasks, choosing between task commands, or deciding how to…
How to add a new target language to Alef-based e2e test generation — generator wiring, output layout, and registration. Load when extending e2e generation to a new language binding.
How to author a new e2e test fixture for cross-language test generation — fixture fields, assertion types, and id conventions. Load when adding or editing e2e fixtures consumed by the generator.
How Alef-based e2e generation works — the alef.toml [e2e] config, JSON fixtures under fixtures/, per-language output layout, fixture id/loading/sorting rules, and the regenerate/verify task commands. Load when configuring e2e generation, adding fixtures, or…
Schema for e2e test fixtures — required fields, the supported assertion types, skip conditions, id uniqueness rules, and how fixture files are organized by category. Load when authoring or editing e2e fixtures, choosing assertion types, or structuring fixture…
Docker image conventions for xberg-io services — multi-stage builds, layer caching, security hardening (non-root, vulnerability scanning, no baked secrets), signal handling and healthchecks, and tagging. Load when writing or editing Dockerfiles, container…
Google Cloud conventions for xberg-io — project and region, the standard service set, resource naming, workload identity federation over service account keys, least-privilege IAM, and gcloud-CLI-only operations. Load when provisioning or configuring GCP…
Observability conventions for xberg-io services — structured JSON logging, tracing spans and context fields, log-level semantics, Prometheus metric types and cardinality rules, and health endpoints wired to K8s probes. Load when adding logging, tracing,…