[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-apache-cayenne-full-db-sync":3,"mdc-mydlxz-key":39,"related-org-apache-cayenne-full-db-sync":804,"related-repo-apache-cayenne-full-db-sync":946},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":22,"repoUrl":23,"updatedAt":24,"license":25,"forks":26,"topics":27,"repo":34,"sourceUrl":37,"mdContent":38},"cayenne-full-db-sync","synchronize Cayenne projects with database","Use this skill when the user wants to bring their WHOLE Cayenne project in line with the database in one shot — the mapping, the Object-layer names, and the generated Java classes together. This is the end-to-end 'sync with the DB' workflow, and it orchestrates three skills in order: `cayenne-db-import` (import schema metadata into the DataMap) → `cayenne-model-naming` (polish the just-imported names) → `cayenne-cgen` (regenerate Java classes). Trigger on holistic phrases like 'sync my project with the database', 'sync with the DB', 'my schema changed, update everything', 'update my entities\u002Fclasses from the database', 'reverse engineer and regenerate the classes', 'import the new tables and rebuild the entities', 'full DB sync', 'bring the model and classes up to date with the DB'. The distinguishing signal is scope: the user wants the whole project (mapping + names + Java code), not just one stage. For the *model\u002Fmapping only* (no name cleanup, no class generation) use `cayenne-db-import`; to (re)generate classes alone use `cayenne-cgen`; to clean names alone use `cayenne-model-naming`. Uses the `mcp__cayenne__dbimport_run` and `mcp__cayenne__cgen_run` MCP tools via the sub-skills; does NOT use Maven or Gradle goals.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"apache","Apache Software Foundation","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fapache.png",[12,16,19],{"name":13,"slug":14,"type":15},"Java","java","tag",{"name":17,"slug":18,"type":15},"Database","database",{"name":20,"slug":21,"type":15},"ORM","orm",343,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcayenne","2026-07-19T06:03:49.112969",null,137,[28,18,14,29,30,31,32,33],"cayenne","library","network-client","network-server","web-framework","xml",{"repoUrl":23,"stars":22,"forks":26,"topics":35,"description":36},[28,18,14,29,30,31,32,33],"Mirror of Apache Cayenne","https:\u002F\u002Fgithub.com\u002Fapache\u002Fcayenne\u002Ftree\u002FHEAD\u002Fai-plugin\u002Fskills\u002Fcayenne-full-db-sync","---\nname: cayenne-full-db-sync\ndescription: \"Use this skill when the user wants to bring their WHOLE Cayenne project in line with the database in one shot — the mapping, the Object-layer names, and the generated Java classes together. This is the end-to-end 'sync with the DB' workflow, and it orchestrates three skills in order: `cayenne-db-import` (import schema metadata into the DataMap) → `cayenne-model-naming` (polish the just-imported names) → `cayenne-cgen` (regenerate Java classes). Trigger on holistic phrases like 'sync my project with the database', 'sync with the DB', 'my schema changed, update everything', 'update my entities\u002Fclasses from the database', 'reverse engineer and regenerate the classes', 'import the new tables and rebuild the entities', 'full DB sync', 'bring the model and classes up to date with the DB'. The distinguishing signal is scope: the user wants the whole project (mapping + names + Java code), not just one stage. For the *model\u002Fmapping only* (no name cleanup, no class generation) use `cayenne-db-import`; to (re)generate classes alone use `cayenne-cgen`; to clean names alone use `cayenne-model-naming`. Uses the `mcp__cayenne__dbimport_run` and `mcp__cayenne__cgen_run` MCP tools via the sub-skills; does NOT use Maven or Gradle goals.\"\n---\n\n\u003C!--\n\tLicensed to the Apache Software Foundation (ASF) under one\n\tor more contributor license agreements.  See the NOTICE file\n\tdistributed with this work for additional information\n\tregarding copyright ownership.  The ASF licenses this file\n\tto you under the Apache License, Version 2.0 (the\n\t\"License\"); you may not use this file except in compliance\n\twith the License.  You may obtain a copy of the License at\n\t\n\thttps:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0\n\t\n\tUnless required by applicable law or agreed to in writing,\n\tsoftware distributed under the License is distributed on an\n\t\"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\n\tKIND, either express or implied.  See the License for the\n\tspecific language governing permissions and limitations\n\tunder the License.   \n-->\n# cayenne-full-db-sync\n\nBring an entire Cayenne project in line with the database in one pass. This skill is a **thin\norchestrator** — it runs three existing skills in sequence and does not re-implement any of their\nlogic:\n\n1. **`cayenne-db-import`** — import DB schema metadata into the DataMap (the mapping XML).\n2. **`cayenne-model-naming`** — polish the Object-layer names of what the import just added.\n3. **`cayenne-cgen`** — regenerate the Java entity classes so the code matches the model.\n\nEach sub-skill still runs within its own scope and carries its own required reading, MCP tool usage,\nfailure handling, and anti-patterns. Your job here is to drive them in order, pass the shared\nproject\u002FDataMap identity through, and short-circuit correctly when a stage has nothing to do.\n\n## When to use this vs. a single skill\n\n- **Whole project should reflect the DB** (mapping + names + Java) → this skill.\n- **Model\u002Fmapping only**, no name cleanup or class generation → `cayenne-db-import`.\n- **Java classes only**, model already correct → `cayenne-cgen`.\n- **Names only**, no import or regeneration → `cayenne-model-naming`.\n\nIf the request is ambiguous (\"update from the DB\"), default to this full sync — it is the common\nintent — but say what you're about to do (import → clean names → regenerate) before you start.\n\n## Required reading\n\nThis skill delegates, so read each sub-skill and let it pull its own references:\n\n- `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcayenne-db-import\u002FSKILL.md`\n- `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcayenne-model-naming\u002FSKILL.md`\n- `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcayenne-cgen\u002FSKILL.md`\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fproject-layout.md` — to resolve the project descriptor and DataMap once, up front.\n\n## Step 0 — Resolve the shared inputs once\n\nAll three stages operate on the same project. Resolve these before starting so you can pass them\nthrough:\n\n- **`projectPath`** — absolute path to the top-level project descriptor (`cayenne-*.xml`), via\n  `project-layout.md`. Not a DataMap file.\n- **`dataMap`** — the DataMap name from `\u003Cmap name=\"...\">` in the descriptor. If the project has\n  multiple DataMaps and the user wants \"everything\", run the whole pipeline once per DataMap. If\n  ambiguous, ask which DataMap; cache the answer.\n\nTell the user the plan in one line: \"I'll import from the DB, clean up the new names, then regenerate\nthe classes.\"\n\n## Step 1 — Import (`cayenne-db-import`)\n\nFollow the `cayenne-db-import` skill to run `dbimport_run` for the resolved project\u002FDataMap. Because\nyou are orchestrating, **you** drive the follow-up here — do not act on that skill's own Step 5\nhand-off prompts (it would suggest naming\u002Fcgen again); this skill sequences them instead.\n\nBranch on the result status:\n\n- **`imported` with a non-empty `summary`** (entities\u002Frelationships added\u002Fmodified) → the model\n  changed. Proceed to Step 2.\n- **`up_to_date`** (or `imported` with an all-zero summary) → the mapping already matches the DB.\n  **Skip Step 2** (nothing new to name). Go straight to Step 3 to guarantee the Java classes are in\n  sync — `cgen_run` is idempotent and simply reports everything skipped if the code is already\n  current. Tell the user the model was already up to date.\n- **`validation_failed`** → follow `cayenne-db-import`'s remediation table for the `error.code`. The\n  common first-run case is `dbconnector_not_configured`, which routes through the Modeler GUI to save\n  the connection; once resolved, re-run the import and continue the pipeline. If it can't be resolved,\n  stop and surface the problem — do **not** run naming or cgen on a failed import.\n- **`error`** (partial\u002Fmid-run failure) → surface `error.message` and the partial summary, then stop.\n  Don't proceed to naming or cgen.\n\n## Step 2 — Clean up names (`cayenne-model-naming`)\n\nOnly when Step 1 imported real changes. Follow the `cayenne-model-naming` skill in its **changed-only**\nmode — it scopes itself to the import's additions via `git diff`, so you don't tell it which entities\nchanged. Within this pipeline it runs **unattended**: apply the changed-scope renames and **report**\nwhat changed; do not pause for per-rename confirmation. (Naming must run *before* cgen so the classes\nare generated with the final names.)\n\nTwo carry-overs from that skill still hold: it only touches what the deterministic generator can't get\nright (run-together names, `team1`-style collisions, a table prefix leaking into relationships), and\nevery rename updates its cross-references per `model-naming-rename-safety.md`.\n\n## Step 3 — Regenerate classes (`cayenne-cgen`)\n\nFollow the `cayenne-cgen` skill to run `cgen_run` for the same project\u002FDataMap. This materializes the\nJava entity classes from the now-final model. Report the `summary` counts and the destination as that\nskill describes.\n\n## Step 4 — Summarize the whole run\n\nGive the user a single consolidated report of the three stages:\n\n- **Import** — entities\u002Frelationships added\u002Fremoved\u002Fmodified (from the `dbimport_run` summary).\n- **Names** — the renames applied (old → new), or \"none needed\".\n- **Classes** — files written \u002F skipped, and the destination directory.\n\nThen the usual follow-ups: remind them not to edit the `_\u003CEntity>.java` superclasses (regenerated),\nand to save the project in the Modeler if it's open.\n\n## Anti-patterns\n\n- **Don't use this for a single stage.** Model-only import → `cayenne-db-import`; classes-only →\n  `cayenne-cgen`; names-only → `cayenne-model-naming`. This skill is for the whole pipeline.\n- **Don't re-implement the sub-steps.** Delegate to each skill so its MCP tool usage, failure modes,\n  and anti-patterns all apply. This file only sequences and short-circuits.\n- **Don't run naming or cgen after a failed or empty import.** A `validation_failed`\u002F`error` stops the\n  pipeline; `up_to_date` skips naming (but cgen may still run as an idempotent guarantee).\n- **Don't reorder the stages.** Names must be finalized before cgen, or classes are generated with the\n  names you're about to change.\n- **Don't rewrite the whole model during a sync.** Naming stays in changed-only scope (import\n  additions), never an entire-model pass, unless the user explicitly asks for one.\n- **Don't suggest `mvn cayenne:cdbimport` \u002F `cayenne:cgen` or the Gradle tasks.** The sub-skills use\n  the MCP tools exclusively; if the server isn't connected, they point at `cayenne-mcp-server\u002FREADME.md`\n  and stop.\n",{"data":40,"body":41},{"name":4,"description":6},{"type":42,"children":43},"root",[44,51,65,113,118,125,188,193,199,204,245,251,256,311,316,329,356,361,488,500,549,569,581,605,611,616,656,669,675],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":4},[49],{"type":50,"value":4},"text",{"type":45,"tag":52,"props":53,"children":54},"p",{},[55,57,63],{"type":50,"value":56},"Bring an entire Cayenne project in line with the database in one pass. This skill is a ",{"type":45,"tag":58,"props":59,"children":60},"strong",{},[61],{"type":50,"value":62},"thin\norchestrator",{"type":50,"value":64}," — it runs three existing skills in sequence and does not re-implement any of their\nlogic:",{"type":45,"tag":66,"props":67,"children":68},"ol",{},[69,85,99],{"type":45,"tag":70,"props":71,"children":72},"li",{},[73,83],{"type":45,"tag":58,"props":74,"children":75},{},[76],{"type":45,"tag":77,"props":78,"children":80},"code",{"className":79},[],[81],{"type":50,"value":82},"cayenne-db-import",{"type":50,"value":84}," — import DB schema metadata into the DataMap (the mapping XML).",{"type":45,"tag":70,"props":86,"children":87},{},[88,97],{"type":45,"tag":58,"props":89,"children":90},{},[91],{"type":45,"tag":77,"props":92,"children":94},{"className":93},[],[95],{"type":50,"value":96},"cayenne-model-naming",{"type":50,"value":98}," — polish the Object-layer names of what the import just added.",{"type":45,"tag":70,"props":100,"children":101},{},[102,111],{"type":45,"tag":58,"props":103,"children":104},{},[105],{"type":45,"tag":77,"props":106,"children":108},{"className":107},[],[109],{"type":50,"value":110},"cayenne-cgen",{"type":50,"value":112}," — regenerate the Java entity classes so the code matches the model.",{"type":45,"tag":52,"props":114,"children":115},{},[116],{"type":50,"value":117},"Each sub-skill still runs within its own scope and carries its own required reading, MCP tool usage,\nfailure handling, and anti-patterns. Your job here is to drive them in order, pass the shared\nproject\u002FDataMap identity through, and short-circuit correctly when a stage has nothing to do.",{"type":45,"tag":119,"props":120,"children":122},"h2",{"id":121},"when-to-use-this-vs-a-single-skill",[123],{"type":50,"value":124},"When to use this vs. a single skill",{"type":45,"tag":126,"props":127,"children":128},"ul",{},[129,139,156,172],{"type":45,"tag":70,"props":130,"children":131},{},[132,137],{"type":45,"tag":58,"props":133,"children":134},{},[135],{"type":50,"value":136},"Whole project should reflect the DB",{"type":50,"value":138}," (mapping + names + Java) → this skill.",{"type":45,"tag":70,"props":140,"children":141},{},[142,147,149,154],{"type":45,"tag":58,"props":143,"children":144},{},[145],{"type":50,"value":146},"Model\u002Fmapping only",{"type":50,"value":148},", no name cleanup or class generation → ",{"type":45,"tag":77,"props":150,"children":152},{"className":151},[],[153],{"type":50,"value":82},{"type":50,"value":155},".",{"type":45,"tag":70,"props":157,"children":158},{},[159,164,166,171],{"type":45,"tag":58,"props":160,"children":161},{},[162],{"type":50,"value":163},"Java classes only",{"type":50,"value":165},", model already correct → ",{"type":45,"tag":77,"props":167,"children":169},{"className":168},[],[170],{"type":50,"value":110},{"type":50,"value":155},{"type":45,"tag":70,"props":173,"children":174},{},[175,180,182,187],{"type":45,"tag":58,"props":176,"children":177},{},[178],{"type":50,"value":179},"Names only",{"type":50,"value":181},", no import or regeneration → ",{"type":45,"tag":77,"props":183,"children":185},{"className":184},[],[186],{"type":50,"value":96},{"type":50,"value":155},{"type":45,"tag":52,"props":189,"children":190},{},[191],{"type":50,"value":192},"If the request is ambiguous (\"update from the DB\"), default to this full sync — it is the common\nintent — but say what you're about to do (import → clean names → regenerate) before you start.",{"type":45,"tag":119,"props":194,"children":196},{"id":195},"required-reading",[197],{"type":50,"value":198},"Required reading",{"type":45,"tag":52,"props":200,"children":201},{},[202],{"type":50,"value":203},"This skill delegates, so read each sub-skill and let it pull its own references:",{"type":45,"tag":126,"props":205,"children":206},{},[207,216,225,234],{"type":45,"tag":70,"props":208,"children":209},{},[210],{"type":45,"tag":77,"props":211,"children":213},{"className":212},[],[214],{"type":50,"value":215},"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcayenne-db-import\u002FSKILL.md",{"type":45,"tag":70,"props":217,"children":218},{},[219],{"type":45,"tag":77,"props":220,"children":222},{"className":221},[],[223],{"type":50,"value":224},"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcayenne-model-naming\u002FSKILL.md",{"type":45,"tag":70,"props":226,"children":227},{},[228],{"type":45,"tag":77,"props":229,"children":231},{"className":230},[],[232],{"type":50,"value":233},"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcayenne-cgen\u002FSKILL.md",{"type":45,"tag":70,"props":235,"children":236},{},[237,243],{"type":45,"tag":77,"props":238,"children":240},{"className":239},[],[241],{"type":50,"value":242},"${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fproject-layout.md",{"type":50,"value":244}," — to resolve the project descriptor and DataMap once, up front.",{"type":45,"tag":119,"props":246,"children":248},{"id":247},"step-0-resolve-the-shared-inputs-once",[249],{"type":50,"value":250},"Step 0 — Resolve the shared inputs once",{"type":45,"tag":52,"props":252,"children":253},{},[254],{"type":50,"value":255},"All three stages operate on the same project. Resolve these before starting so you can pass them\nthrough:",{"type":45,"tag":126,"props":257,"children":258},{},[259,289],{"type":45,"tag":70,"props":260,"children":261},{},[262,271,273,279,281,287],{"type":45,"tag":58,"props":263,"children":264},{},[265],{"type":45,"tag":77,"props":266,"children":268},{"className":267},[],[269],{"type":50,"value":270},"projectPath",{"type":50,"value":272}," — absolute path to the top-level project descriptor (",{"type":45,"tag":77,"props":274,"children":276},{"className":275},[],[277],{"type":50,"value":278},"cayenne-*.xml",{"type":50,"value":280},"), via\n",{"type":45,"tag":77,"props":282,"children":284},{"className":283},[],[285],{"type":50,"value":286},"project-layout.md",{"type":50,"value":288},". Not a DataMap file.",{"type":45,"tag":70,"props":290,"children":291},{},[292,301,303,309],{"type":45,"tag":58,"props":293,"children":294},{},[295],{"type":45,"tag":77,"props":296,"children":298},{"className":297},[],[299],{"type":50,"value":300},"dataMap",{"type":50,"value":302}," — the DataMap name from ",{"type":45,"tag":77,"props":304,"children":306},{"className":305},[],[307],{"type":50,"value":308},"\u003Cmap name=\"...\">",{"type":50,"value":310}," in the descriptor. If the project has\nmultiple DataMaps and the user wants \"everything\", run the whole pipeline once per DataMap. If\nambiguous, ask which DataMap; cache the answer.",{"type":45,"tag":52,"props":312,"children":313},{},[314],{"type":50,"value":315},"Tell the user the plan in one line: \"I'll import from the DB, clean up the new names, then regenerate\nthe classes.\"",{"type":45,"tag":119,"props":317,"children":319},{"id":318},"step-1-import-cayenne-db-import",[320,322,327],{"type":50,"value":321},"Step 1 — Import (",{"type":45,"tag":77,"props":323,"children":325},{"className":324},[],[326],{"type":50,"value":82},{"type":50,"value":328},")",{"type":45,"tag":52,"props":330,"children":331},{},[332,334,339,341,347,349,354],{"type":50,"value":333},"Follow the ",{"type":45,"tag":77,"props":335,"children":337},{"className":336},[],[338],{"type":50,"value":82},{"type":50,"value":340}," skill to run ",{"type":45,"tag":77,"props":342,"children":344},{"className":343},[],[345],{"type":50,"value":346},"dbimport_run",{"type":50,"value":348}," for the resolved project\u002FDataMap. Because\nyou are orchestrating, ",{"type":45,"tag":58,"props":350,"children":351},{},[352],{"type":50,"value":353},"you",{"type":50,"value":355}," drive the follow-up here — do not act on that skill's own Step 5\nhand-off prompts (it would suggest naming\u002Fcgen again); this skill sequences them instead.",{"type":45,"tag":52,"props":357,"children":358},{},[359],{"type":50,"value":360},"Branch on the result status:",{"type":45,"tag":126,"props":362,"children":363},{},[364,386,422,466],{"type":45,"tag":70,"props":365,"children":366},{},[367,384],{"type":45,"tag":58,"props":368,"children":369},{},[370,376,378],{"type":45,"tag":77,"props":371,"children":373},{"className":372},[],[374],{"type":50,"value":375},"imported",{"type":50,"value":377}," with a non-empty ",{"type":45,"tag":77,"props":379,"children":381},{"className":380},[],[382],{"type":50,"value":383},"summary",{"type":50,"value":385}," (entities\u002Frelationships added\u002Fmodified) → the model\nchanged. Proceed to Step 2.",{"type":45,"tag":70,"props":387,"children":388},{},[389,398,400,405,407,412,414,420],{"type":45,"tag":58,"props":390,"children":391},{},[392],{"type":45,"tag":77,"props":393,"children":395},{"className":394},[],[396],{"type":50,"value":397},"up_to_date",{"type":50,"value":399}," (or ",{"type":45,"tag":77,"props":401,"children":403},{"className":402},[],[404],{"type":50,"value":375},{"type":50,"value":406}," with an all-zero summary) → the mapping already matches the DB.\n",{"type":45,"tag":58,"props":408,"children":409},{},[410],{"type":50,"value":411},"Skip Step 2",{"type":50,"value":413}," (nothing new to name). Go straight to Step 3 to guarantee the Java classes are in\nsync — ",{"type":45,"tag":77,"props":415,"children":417},{"className":416},[],[418],{"type":50,"value":419},"cgen_run",{"type":50,"value":421}," is idempotent and simply reports everything skipped if the code is already\ncurrent. Tell the user the model was already up to date.",{"type":45,"tag":70,"props":423,"children":424},{},[425,434,436,441,443,449,451,457,459,464],{"type":45,"tag":58,"props":426,"children":427},{},[428],{"type":45,"tag":77,"props":429,"children":431},{"className":430},[],[432],{"type":50,"value":433},"validation_failed",{"type":50,"value":435}," → follow ",{"type":45,"tag":77,"props":437,"children":439},{"className":438},[],[440],{"type":50,"value":82},{"type":50,"value":442},"'s remediation table for the ",{"type":45,"tag":77,"props":444,"children":446},{"className":445},[],[447],{"type":50,"value":448},"error.code",{"type":50,"value":450},". The\ncommon first-run case is ",{"type":45,"tag":77,"props":452,"children":454},{"className":453},[],[455],{"type":50,"value":456},"dbconnector_not_configured",{"type":50,"value":458},", which routes through the Modeler GUI to save\nthe connection; once resolved, re-run the import and continue the pipeline. If it can't be resolved,\nstop and surface the problem — do ",{"type":45,"tag":58,"props":460,"children":461},{},[462],{"type":50,"value":463},"not",{"type":50,"value":465}," run naming or cgen on a failed import.",{"type":45,"tag":70,"props":467,"children":468},{},[469,478,480,486],{"type":45,"tag":58,"props":470,"children":471},{},[472],{"type":45,"tag":77,"props":473,"children":475},{"className":474},[],[476],{"type":50,"value":477},"error",{"type":50,"value":479}," (partial\u002Fmid-run failure) → surface ",{"type":45,"tag":77,"props":481,"children":483},{"className":482},[],[484],{"type":50,"value":485},"error.message",{"type":50,"value":487}," and the partial summary, then stop.\nDon't proceed to naming or cgen.",{"type":45,"tag":119,"props":489,"children":491},{"id":490},"step-2-clean-up-names-cayenne-model-naming",[492,494,499],{"type":50,"value":493},"Step 2 — Clean up names (",{"type":45,"tag":77,"props":495,"children":497},{"className":496},[],[498],{"type":50,"value":96},{"type":50,"value":328},{"type":45,"tag":52,"props":501,"children":502},{},[503,505,510,512,517,519,525,527,532,534,539,541,547],{"type":50,"value":504},"Only when Step 1 imported real changes. Follow the ",{"type":45,"tag":77,"props":506,"children":508},{"className":507},[],[509],{"type":50,"value":96},{"type":50,"value":511}," skill in its ",{"type":45,"tag":58,"props":513,"children":514},{},[515],{"type":50,"value":516},"changed-only",{"type":50,"value":518},"\nmode — it scopes itself to the import's additions via ",{"type":45,"tag":77,"props":520,"children":522},{"className":521},[],[523],{"type":50,"value":524},"git diff",{"type":50,"value":526},", so you don't tell it which entities\nchanged. Within this pipeline it runs ",{"type":45,"tag":58,"props":528,"children":529},{},[530],{"type":50,"value":531},"unattended",{"type":50,"value":533},": apply the changed-scope renames and ",{"type":45,"tag":58,"props":535,"children":536},{},[537],{"type":50,"value":538},"report",{"type":50,"value":540},"\nwhat changed; do not pause for per-rename confirmation. (Naming must run ",{"type":45,"tag":542,"props":543,"children":544},"em",{},[545],{"type":50,"value":546},"before",{"type":50,"value":548}," cgen so the classes\nare generated with the final names.)",{"type":45,"tag":52,"props":550,"children":551},{},[552,554,560,562,568],{"type":50,"value":553},"Two carry-overs from that skill still hold: it only touches what the deterministic generator can't get\nright (run-together names, ",{"type":45,"tag":77,"props":555,"children":557},{"className":556},[],[558],{"type":50,"value":559},"team1",{"type":50,"value":561},"-style collisions, a table prefix leaking into relationships), and\nevery rename updates its cross-references per ",{"type":45,"tag":77,"props":563,"children":565},{"className":564},[],[566],{"type":50,"value":567},"model-naming-rename-safety.md",{"type":50,"value":155},{"type":45,"tag":119,"props":570,"children":572},{"id":571},"step-3-regenerate-classes-cayenne-cgen",[573,575,580],{"type":50,"value":574},"Step 3 — Regenerate classes (",{"type":45,"tag":77,"props":576,"children":578},{"className":577},[],[579],{"type":50,"value":110},{"type":50,"value":328},{"type":45,"tag":52,"props":582,"children":583},{},[584,585,590,591,596,598,603],{"type":50,"value":333},{"type":45,"tag":77,"props":586,"children":588},{"className":587},[],[589],{"type":50,"value":110},{"type":50,"value":340},{"type":45,"tag":77,"props":592,"children":594},{"className":593},[],[595],{"type":50,"value":419},{"type":50,"value":597}," for the same project\u002FDataMap. This materializes the\nJava entity classes from the now-final model. Report the ",{"type":45,"tag":77,"props":599,"children":601},{"className":600},[],[602],{"type":50,"value":383},{"type":50,"value":604}," counts and the destination as that\nskill describes.",{"type":45,"tag":119,"props":606,"children":608},{"id":607},"step-4-summarize-the-whole-run",[609],{"type":50,"value":610},"Step 4 — Summarize the whole run",{"type":45,"tag":52,"props":612,"children":613},{},[614],{"type":50,"value":615},"Give the user a single consolidated report of the three stages:",{"type":45,"tag":126,"props":617,"children":618},{},[619,636,646],{"type":45,"tag":70,"props":620,"children":621},{},[622,627,629,634],{"type":45,"tag":58,"props":623,"children":624},{},[625],{"type":50,"value":626},"Import",{"type":50,"value":628}," — entities\u002Frelationships added\u002Fremoved\u002Fmodified (from the ",{"type":45,"tag":77,"props":630,"children":632},{"className":631},[],[633],{"type":50,"value":346},{"type":50,"value":635}," summary).",{"type":45,"tag":70,"props":637,"children":638},{},[639,644],{"type":45,"tag":58,"props":640,"children":641},{},[642],{"type":50,"value":643},"Names",{"type":50,"value":645}," — the renames applied (old → new), or \"none needed\".",{"type":45,"tag":70,"props":647,"children":648},{},[649,654],{"type":45,"tag":58,"props":650,"children":651},{},[652],{"type":50,"value":653},"Classes",{"type":50,"value":655}," — files written \u002F skipped, and the destination directory.",{"type":45,"tag":52,"props":657,"children":658},{},[659,661,667],{"type":50,"value":660},"Then the usual follow-ups: remind them not to edit the ",{"type":45,"tag":77,"props":662,"children":664},{"className":663},[],[665],{"type":50,"value":666},"_\u003CEntity>.java",{"type":50,"value":668}," superclasses (regenerated),\nand to save the project in the Modeler if it's open.",{"type":45,"tag":119,"props":670,"children":672},{"id":671},"anti-patterns",[673],{"type":50,"value":674},"Anti-patterns",{"type":45,"tag":126,"props":676,"children":677},{},[678,709,719,750,760,770],{"type":45,"tag":70,"props":679,"children":680},{},[681,686,688,693,695,700,702,707],{"type":45,"tag":58,"props":682,"children":683},{},[684],{"type":50,"value":685},"Don't use this for a single stage.",{"type":50,"value":687}," Model-only import → ",{"type":45,"tag":77,"props":689,"children":691},{"className":690},[],[692],{"type":50,"value":82},{"type":50,"value":694},"; classes-only →\n",{"type":45,"tag":77,"props":696,"children":698},{"className":697},[],[699],{"type":50,"value":110},{"type":50,"value":701},"; names-only → ",{"type":45,"tag":77,"props":703,"children":705},{"className":704},[],[706],{"type":50,"value":96},{"type":50,"value":708},". This skill is for the whole pipeline.",{"type":45,"tag":70,"props":710,"children":711},{},[712,717],{"type":45,"tag":58,"props":713,"children":714},{},[715],{"type":50,"value":716},"Don't re-implement the sub-steps.",{"type":50,"value":718}," Delegate to each skill so its MCP tool usage, failure modes,\nand anti-patterns all apply. This file only sequences and short-circuits.",{"type":45,"tag":70,"props":720,"children":721},{},[722,727,729,734,736,741,743,748],{"type":45,"tag":58,"props":723,"children":724},{},[725],{"type":50,"value":726},"Don't run naming or cgen after a failed or empty import.",{"type":50,"value":728}," A ",{"type":45,"tag":77,"props":730,"children":732},{"className":731},[],[733],{"type":50,"value":433},{"type":50,"value":735},"\u002F",{"type":45,"tag":77,"props":737,"children":739},{"className":738},[],[740],{"type":50,"value":477},{"type":50,"value":742}," stops the\npipeline; ",{"type":45,"tag":77,"props":744,"children":746},{"className":745},[],[747],{"type":50,"value":397},{"type":50,"value":749}," skips naming (but cgen may still run as an idempotent guarantee).",{"type":45,"tag":70,"props":751,"children":752},{},[753,758],{"type":45,"tag":58,"props":754,"children":755},{},[756],{"type":50,"value":757},"Don't reorder the stages.",{"type":50,"value":759}," Names must be finalized before cgen, or classes are generated with the\nnames you're about to change.",{"type":45,"tag":70,"props":761,"children":762},{},[763,768],{"type":45,"tag":58,"props":764,"children":765},{},[766],{"type":50,"value":767},"Don't rewrite the whole model during a sync.",{"type":50,"value":769}," Naming stays in changed-only scope (import\nadditions), never an entire-model pass, unless the user explicitly asks for one.",{"type":45,"tag":70,"props":771,"children":772},{},[773,794,796,802],{"type":45,"tag":58,"props":774,"children":775},{},[776,778,784,786,792],{"type":50,"value":777},"Don't suggest ",{"type":45,"tag":77,"props":779,"children":781},{"className":780},[],[782],{"type":50,"value":783},"mvn cayenne:cdbimport",{"type":50,"value":785}," \u002F ",{"type":45,"tag":77,"props":787,"children":789},{"className":788},[],[790],{"type":50,"value":791},"cayenne:cgen",{"type":50,"value":793}," or the Gradle tasks.",{"type":50,"value":795}," The sub-skills use\nthe MCP tools exclusively; if the server isn't connected, they point at ",{"type":45,"tag":77,"props":797,"children":799},{"className":798},[],[800],{"type":50,"value":801},"cayenne-mcp-server\u002FREADME.md",{"type":50,"value":803},"\nand stop.",{"items":805,"total":945},[806,824,838,851,864,877,888,898,904,914,924,934],{"slug":807,"name":807,"fn":808,"description":809,"org":810,"tags":811,"stars":821,"repoUrl":822,"updatedAt":823},"datafusion-python","write Apache DataFusion Python code","Use when the user is writing datafusion-python (Apache DataFusion Python bindings) DataFrame or SQL code. Covers imports, data loading, DataFrame operations, expression building, SQL-to-DataFrame mappings, idiomatic patterns, and common pitfalls.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[812,815,818],{"name":813,"slug":814,"type":15},"Data Analysis","data-analysis",{"name":816,"slug":817,"type":15},"Python","python",{"name":819,"slug":820,"type":15},"SQL","sql",593,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-python","2026-07-12T08:36:04.957626",{"slug":825,"name":825,"fn":826,"description":827,"org":828,"tags":829,"stars":835,"repoUrl":836,"updatedAt":837},"bydbql","generate and execute BanyanDB BydbQL queries","Generate, validate, and optionally execute read-only BanyanDB BydbQL for STREAM, MEASURE, TRACE, and PROPERTY resources. Use when the user asks to query BanyanDB, translate natural language to BydbQL, inspect BanyanDB schema or data, validate BydbQL, or fetch raw BanyanDB records.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[830,833,834],{"name":831,"slug":832,"type":15},"Analytics","analytics",{"name":17,"slug":18,"type":15},{"name":819,"slug":820,"type":15},344,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fskywalking-banyandb","2026-07-12T08:31:01.294423",{"slug":839,"name":839,"fn":840,"description":841,"org":842,"tags":843,"stars":835,"repoUrl":836,"updatedAt":850},"compiling","compile and build BanyanDB projects","Compile and build the SkyWalking BanyanDB project. Use when the user asks to compile, build, or generate code for this project.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[844,847],{"name":845,"slug":846,"type":15},"Build","build",{"name":848,"slug":849,"type":15},"Engineering","engineering","2026-07-12T08:31:06.373309",{"slug":852,"name":852,"fn":853,"description":854,"org":855,"tags":856,"stars":835,"repoUrl":836,"updatedAt":863},"gh-pull-request","create GitHub pull requests for BanyanDB","Create a GitHub pull request for SkyWalking BanyanDB. Use when the user asks to create a PR, submit changes, or open a pull request.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[857,860],{"name":858,"slug":859,"type":15},"GitHub","github",{"name":861,"slug":862,"type":15},"Pull Requests","pull-requests","2026-07-12T08:31:03.792415",{"slug":865,"name":865,"fn":866,"description":867,"org":868,"tags":869,"stars":835,"repoUrl":836,"updatedAt":876},"vendor-update","update Go and Node.js vendor dependencies","Upgrade Go\u002FNode.js vendor dependencies and sync tool versions. Use whenever the user says \"upgrade dependencies\", \"update vendors\", \"vendor update\", \"run vendor-upgrade\", \"bump dependencies\", \"update packages\", or asks to run the `vendor-update` Make target. This skill also checks `scripts\u002Fbuild\u002Fversion.mk` after upgrading to see if any tracked tool versions need updating too, and removes stale binaries from `bin\u002F` when versions change.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[870,873],{"name":871,"slug":872,"type":15},"Go","go",{"name":874,"slug":875,"type":15},"Node.js","node-js","2026-07-12T08:31:02.555555",{"slug":110,"name":110,"fn":878,"description":879,"org":880,"tags":881,"stars":22,"repoUrl":23,"updatedAt":887},"generate Cayenne entity Java classes","Use this skill whenever the user wants to (re)generate Cayenne entity Java classes from a DataMap. Trigger on phrases like 'generate Java classes', 'regenerate entities', 'run cgen', 'create the entity classes', 'why is the Artist class missing fields', 'where did the `_Abstract*` classes come from', 'sync the entity classes with the model', or any request to materialize Java from the DataMap. Also trigger as a follow-up after modeling changes (someone added an entity, attribute, or relationship and now the Java side is stale). This skill exclusively uses the `mcp__cayenne__cgen_run` MCP tool — it does NOT use `mvn cayenne:cgen` or the Gradle cgen task.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[882,885,886],{"name":883,"slug":884,"type":15},"Data Modeling","data-modeling",{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-07-12T08:32:33.575211",{"slug":82,"name":82,"fn":889,"description":890,"org":891,"tags":892,"stars":22,"repoUrl":23,"updatedAt":897},"import database schema into Cayenne DataMaps","Use this skill when the user wants to import database schema metadata into a Cayenne DataMap — the *model\u002Fmapping only*, not names or Java classes. Trigger on phrases like 'reverse engineer the database', 'import the schema', 'generate a DataMap from my DB', 'add the new tables from the DB into the model', 'import the customer table', 'create entities from these tables', or any request to read database metadata to populate or update a DataMap's XML. This is for *full schema* or *bulk table* import; one-off a-la-carte entity additions belong in the cayenne-modeling skill. IMPORTANT — scope: this imports the mapping ONLY; it does not clean up the Object-layer names or (re)generate Java classes. When the user wants their whole project brought in line with the DB ('sync my project with the database', 'my schema changed, update everything', 'update my entities\u002Fclasses from the DB'), that is the end-to-end `cayenne-full-db-sync` skill, which runs this import and then name cleanup and class generation. To regenerate classes alone use `cayenne-cgen`. The skill runs reverse engineering directly via the `mcp__cayenne__dbimport_run` MCP tool when a DBConnector is already configured; otherwise it opens the CayenneModeler GUI via `mcp__cayenne__open_project` to configure the connection first.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[893,894,895,896],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":819,"slug":820,"type":15},"2026-07-19T05:40:33.655062",{"slug":4,"name":4,"fn":5,"description":6,"org":899,"tags":900,"stars":22,"repoUrl":23,"updatedAt":24},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[901,902,903],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":96,"name":96,"fn":905,"description":906,"org":907,"tags":908,"stars":22,"repoUrl":23,"updatedAt":913},"clean up Cayenne object-layer names","Use this skill to clean up Object-layer names in a Cayenne DataMap — ObjEntity, ObjAttribute, and ObjRelationship names, plus DbRelationship names (the first-class unit of relationship cleanup — every FK has one whether or not an ObjRelationship was generated; the ObjRelationship name is synced to it when one exists) — so they read as descriptive, consistent Java. Trigger on phrases like 'clean up the model names', 'fix the entity names', 'these names look ugly', 'make the names descriptive', 'normalize the ObjEntity\u002Fattribute\u002Frelationship names', 'why is this relationship called team1', 'rename entities to be consistent', 'the import produced Gametype instead of GameType'. Invoke it on an explicit user request, or as a manual follow-up after a `cayenne-db-import` to polish the just-imported additions — it is never triggered automatically. IMPORTANT: this is a LIGHT polish pass — CayenneModeler's reverse-engineering already produces good names for the common case; only improve the specific things its deterministic algorithm cannot (run-together names with no separators like `gametype`, meaningless numbered names like `team1` from multiple relationships between two tables, and a common entity prefix that leaks into relationship names like `aaOrders`). Do NOT rewrite names that are already correct. This is Obj-layer naming polish; for structural model edits use `cayenne-modeling`, and for regenerating classes afterward use `cayenne-cgen`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[909,910,911,912],{"name":883,"slug":884,"type":15},{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-07-22T05:35:32.342548",{"slug":915,"name":915,"fn":916,"description":917,"org":918,"tags":919,"stars":22,"repoUrl":23,"updatedAt":923},"cayenne-modeler","manage Cayenne projects with CayenneModeler","Use this skill when the user explicitly wants to open CayenneModeler (the GUI) on a Cayenne project, or when the modeling task is inherently visual — reverse engineering (delegated to cayenne-db-import), bulk relationship layout, multi-entity visual refactoring. Trigger on phrases like 'open the Modeler', 'open in CayenneModeler', 'launch the GUI', 'edit visually', 'show me the project in the Modeler'. Do NOT trigger as a fallback for ordinary a-la-carte XML edits — those belong in the cayenne-modeling skill, which is faster and doesn't require the user to context-switch.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[920,921,922],{"name":883,"slug":884,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-07-12T08:32:37.199428",{"slug":925,"name":925,"fn":926,"description":927,"org":928,"tags":929,"stars":22,"repoUrl":23,"updatedAt":933},"cayenne-modeling","edit and extend Cayenne ORM models","Use this skill whenever the user wants to edit, inspect, or extend the Cayenne ORM model in a project — adding or modifying entities, attributes, relationships, embeddables, named queries, stored procedures, or DataNodes. Trigger on phrases like 'add an ObjEntity', 'add a DbEntity', 'add a relationship', 'expose this column as an attribute', 'create a new DataMap', 'add a named query', 'create an embeddable', 'add a stored procedure', 'change the attribute type', 'mark this column as nullable', 'rename this entity', or any mention of a Cayenne `*.map.xml` or `cayenne-*.xml` file. Also trigger when the user references modeling concepts (ObjEntity, DbEntity, ObjAttribute, DbAttribute, ObjRelationship, DbRelationship, Embeddable, dbEntityName, deleteRule, db-attribute-path, db-relationship-path, defaultPackage) in the context of a Cayenne-using app. This is the *primary* skill for a-la-carte ORM model manipulation — direct XML edits, not the Modeler GUI.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[930,931,932],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-07-19T05:40:32.6889",{"slug":935,"name":935,"fn":936,"description":937,"org":938,"tags":939,"stars":22,"repoUrl":23,"updatedAt":944},"cayenne-query","write and modify Cayenne database queries","Use this skill whenever the user wants to write or modify a Cayenne query — fetching entities by criteria, joining, prefetching to avoid N+1, ordering, paginating, aggregating, or running raw SQL through Cayenne. Trigger on phrases like 'query for X', 'fetch all artists where ...', 'write an ObjectSelect', 'use SQLSelect', 'use SelectById', 'add a prefetch', 'get distinct values', 'count rows', 'find by ID', 'load by primary key', 'build a Cayenne expression', 'why am I getting N+1', 'how do I paginate', 'select a single column', 'select columns into a DTO', 'named query in the DataMap'. Do NOT trigger for modeling changes (use cayenne-modeling) or runtime bootstrap (use cayenne-runtime).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[940,941,942,943],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":819,"slug":820,"type":15},"2026-07-12T08:32:35.072322",108,{"items":947,"total":993},[948,954,961,967,974,980,986],{"slug":110,"name":110,"fn":878,"description":879,"org":949,"tags":950,"stars":22,"repoUrl":23,"updatedAt":887},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[951,952,953],{"name":883,"slug":884,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":82,"name":82,"fn":889,"description":890,"org":955,"tags":956,"stars":22,"repoUrl":23,"updatedAt":897},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[957,958,959,960],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":819,"slug":820,"type":15},{"slug":4,"name":4,"fn":5,"description":6,"org":962,"tags":963,"stars":22,"repoUrl":23,"updatedAt":24},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[964,965,966],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":96,"name":96,"fn":905,"description":906,"org":968,"tags":969,"stars":22,"repoUrl":23,"updatedAt":913},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[970,971,972,973],{"name":883,"slug":884,"type":15},{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":915,"name":915,"fn":916,"description":917,"org":975,"tags":976,"stars":22,"repoUrl":23,"updatedAt":923},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[977,978,979],{"name":883,"slug":884,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":925,"name":925,"fn":926,"description":927,"org":981,"tags":982,"stars":22,"repoUrl":23,"updatedAt":933},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[983,984,985],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":935,"name":935,"fn":936,"description":937,"org":987,"tags":988,"stars":22,"repoUrl":23,"updatedAt":944},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[989,990,991,992],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":819,"slug":820,"type":15},8]