jfrog-reference-architecture
Guides JFrog Platform topology, sizing (RPM, t-shirt templates), deployment, multi-site use cases, SaaS vs self-managed, HA, air-gapped, and disaster recovery using the official Reference Architecture site as the sole source of facts. Use this skill when the user asks how to size Artifactory or Xray, which deployment pattern to choose, single vs multi site, active-active, active-passive, CI/CD separation, Helm/Kubernetes install planning, or reference architecture (live WebFetch from jfrog.com/reference-architecture). Do NOT use for artifact search or download, repository or permission admin, CVE or vulnerability lookups, live jf CLI operations against their instance, or package curation — use the jfrog base skill or jfrog-package-curation instead.
jfrog · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add jfrog/jfrog-skills --skill jfrog-reference-architecture技能说明
name: jfrog-reference-architecture description: >- Guides JFrog Platform topology, sizing (RPM, t-shirt templates), deployment, multi-site use cases, SaaS vs self-managed, HA, air-gapped, and disaster recovery using the official Reference Architecture site as the sole source of facts. Use this skill when the user asks how to size Artifactory or Xray, which deployment pattern to choose, single vs multi site, active-active, active-passive, CI/CD separation, Helm/Kubernetes install planning, or reference architecture (live WebFetch from jfrog.com/reference-architecture). Do NOT use for artifact search or download, repository or permission admin, CVE or vulnerability lookups, live jf CLI operations against their instance, or package curation — use the jfrog base skill or jfrog-package-curation instead. compatibility: >- Requires outbound HTTPS (WebFetch or equivalent). Request full_network when the runtime blocks fetches. No jf CLI or configured JFrog instance required for planning-only questions. metadata: role: workflow
JFrog Reference Architecture
Planning skill for topology, sizing, and deployment. Answers must come from live fetches of the JFrog Platform Reference Architecture — not from training data or duplicated tables in this repo.
Prerequisites
- Read
../jfrog/SKILL.mdfor JFrog Platform concepts, product vocabulary, and routing to other workflows. - No
jfCLI required for planning-only questions (no live instance needed).
Source of truth
| Allowed in this skill | Not allowed |
|---|---|
| Fetch procedures, workflows, output templates | Sizing RPM tables, use-case narratives, deployment checklists copied from the site |
| Helm chart preference (jfrog-platform on Kubernetes) | Hardcoded slug lists or criteria |
Every factual claim (numbers, template names, limitations, infrastructure guidance) must come from a WebFetch in the current session. If fetch fails, retry or ask the user to open the URL — do not guess from memory.
Citations: Use the URL: line from the relevant section in the fetched content (public HTML URL). You may note content was read from llms-full.txt.
For fetch URLs, size thresholds, and the fallback ladder, see references/doc-access.md.
Gotchas
| Symptom | Mitigation |
|---|---|
| Sizing numbers or use-case names not on the official site | WebFetch ref-arch first; cite URL: from the fetch — not training data |
small template recommended for production | Re-read production warnings in the fetched Artifactory/Xray sizing sections |
| SaaS section missing or 404 | SaaS paths use prefix jfrog-saas, not saas |
| HA storage guidance wrong | Per ref arch: cluster-file-system or object storage — not file-system for HA |
WebFetch blocked, truncated, or over size limits | Request full_network; downgrade per references/doc-access.md |
Session bootstrap
Before answering a reference-architecture question:
WebFetchhttps://jfrog.com/reference-architecture/llms-full.txt(primary).- Keep the response in context for follow-ups in the same thread.
- Note approximate response size. If over 1 MB, or truncated, follow the downgrade path in
references/doc-access.md(sitemap + targetedindex.md). - Re-bootstrap when uncertain after long unrelated conversation.
Request full_network (or the runtime equivalent) when WebFetch is blocked.
Parsing llms-full.txt
Sections are separated by --- and typically include:
# <Title>URL: https://jfrog.com/reference-architecture/...- Optional
> <summary> - Body text (may be condensed vs the HTML page)
Use only text from the fetch. For recommendations, cite the section’s URL: line.
Intent routing
| User intent | Where to look in llms-full | Fallback |
|---|---|---|
| Sizing | # Sizing, # AWS Sizing, Azure, GCP sections | .../self-managed/deployment/sizing/index.md |
| Topology / use case | Matching title + URL: for SaaS (jfrog-saas) or self-managed | That path’s index.md |
| List use cases | All URL: lines containing /use-cases/ | sitemap.xml |
| Deployment / install | Deployment and considerations sections | .../deployment/index.md |
| Disaster recovery | DR playbook / tiers sections | Matching index.md |
SaaS paths use prefix jfrog-saas, not saas.
Workflow: Sizing
- Bootstrap
llms-full.txt(unless downgraded to single-page fetch). - Find the Sizing section. Build follow-up questions from Artifactory Sizing Templates Criteria in the fetch (peak Requests Per Minute and Concurrent Connections per template).
- Use
AskQuestionwhen available; otherwise numbered options using labels from the fetched table only. - If the user mentions Xray or production, use Xray Sizing Templates Criteria and production warnings from the same fetch (e.g. small is not for production).
- If the user names a cloud, use AWS Sizing / Azure / GCP sections from the fetch.
- Recommend a template (
smallthrough2xlarge) and cite the sizing pageURL:from the dump. - Helm: Recommend the jfrog-platform chart with
-f sizing/platform-<template>.yaml.WebFetchthe chart README if the user wants exact install commands.
Sizing output template
## Recommended sizing
- **Template**: <from fetched table>
- **Artifactory**: <RPM and concurrent connections from fetched table>
- **Xray** (if applicable): <from fetched Xray table>
- **Source**: <URL: line from Sizing section>
- **Helm**: `helm upgrade --install` with `-f sizing/platform-<template>.yaml` on chart `jfrog/jfrog-platform`
- **Caveats**: <Notes / additional factors from fetched Sizing sec
阅读完整来源 ↗