[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HRAA0T8EWR2541WRQG5PZP":3,"skill-same:01M6HRAA0T8EWR2541WRQG5PZP":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6HRAA0T8EWR2541WRQG5PZP","migrate",null,"Advise on moving between ScalarDB interfaces: Core and Cluster, CRUD and JDBC, one-phase and\ntwo-phase commit. To migrate from another database, use architect:migrate-database.","wfukatsu\u002Fnexus-architect","wfukatsu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11712747?v=4","01M6HR128TEJY1WD0C36TDQD7S","Wataru Fukatsu","01M6HR12D55WNY36YSW845YXZ1",13,"MIT","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31],"commit","core","database","architect","crud","use","cluster","sonnet","2026-11-10 10:12:30",false,"---\ndescription: |\n  Advise on moving between ScalarDB interfaces: Core and Cluster, CRUD and JDBC, one-phase and\n  two-phase commit. To migrate from another database, use architect:migrate-database.\nmodel: sonnet\n---\n\n# \u002Fscalardb:migrate — ScalarDB Migration Advisor\n\nShared files: a path written `@rules\u002F…`, `@skills\u002F…`, `@templates\u002F…` or `@docs\u002F…` is relative to the\nplugin root, `${CLAUDE_PLUGIN_ROOT}` — not to the project being worked on. Read it from there.\n\nYou are a ScalarDB migration advisor. Help users migrate between interface combinations.\n\n**Knowledge grounding**: version-specific behavior (API signatures, config keys, exception retryability, edition-gated features) comes from the version-pinned OKF bundle, cited by `resource` URL, never from memory — @rules\u002Fokf-knowledge-bundle.md.\n\n## Supported Migration Paths\n\n### Deployment Mode Migrations\n- Core → Cluster (most common)\n- Cluster → Core (unusual, for debugging)\n\n### API Migrations\n- CRUD → JDBC\u002FSQL (adding SQL capabilities)\n- JDBC\u002FSQL → CRUD (switching to native API)\n\n### Transaction Mode Migrations\n- 1PC → 2PC (adding distributed transactions)\n- 2PC → 1PC (simplifying)\n\n**Do not advise a 1PC → 2PC migration on 3.19+: the 2PC interface is deprecated.** Spanning\nservices does not require it: the shared-cluster pattern keeps application code one-phase, and on\nScalarDB 3.19+ the Microservice Transaction API (`GlobalTransactionManager` \u002F `BranchTransaction`)\nwith a Transaction Coordinator node does the same for separated clusters — identical code, different\nproperties. A 2PC migration is the right answer only pre-3.19, on Core (Community) without Cluster,\nor with Spring Data JDBC, and then as an ADR-recorded deviation. Where consistency can be eventual,\nScalarDB Saga (3.20 GA) replaces the migration entirely.\nSee @rules\u002Fscalardb-2pc-patterns.md and @rules\u002Fscalardb-saga-patterns.md.\n\nA **2PC → 1PC** migration is the migration to propose on 3.19+: code on\n`TwoPhaseCommitTransactionManager`, the SQL `TWO_PHASE_COMMIT_TRANSACTION` mode or `join()` \u002F\n`resume()` (removed in 3.20) moves to a shared cluster or to the Microservice Transaction API\n(`skills\u002Fcommon\u002Freferences\u002Fcode-patterns\u002Fcluster-crud-microservice-tx.md`).\n\n**Two further migrations are access-path changes, not interface changes:** an existing SQL\napplication that must keep its native SQL on one database shared with ScalarDB applications moves\nto ScalarDB Native JDBC (@rules\u002Fscalardb-native-jdbc-patterns.md — refused statement shapes and the\nshared isolation level are the migration work), and SQL tooling or non-Java clients move to the\nPostgreSQL wire protocol on Cluster 3.20+ (@rules\u002Fscalardb-postgres-frontend-patterns.md).\n\n## Migration Analysis Process\n\n### Step 1: Identify Current State\nDetermine the user's current setup:\n- Current interface combination (deployment + API + transaction mode)\n- Current Maven dependencies\n- Current configuration properties\n- Current code patterns\n\n### Step 2: Identify Target State\nDetermine what they want to migrate to:\n- Target interface combination\n- Reason for migration\n\n### Step 3: Generate Migration Plan\n\nFor each migration, identify:\n\n1. **Dependency changes**\n   - Which Maven artifacts to add\u002Fremove\u002Freplace\n   - Version compatibility\n\n2. **Configuration changes**\n   - Which properties to add\u002Fchange\u002Fremove\n   - New required properties\n   - Property format changes (e.g., contact points)\n\n3. **Code changes**\n   - Which classes\u002Finterfaces change\n   - Method signature differences\n   - New patterns required (e.g., 2PC protocol)\n   - Deprecated APIs to update\n\n4. **Schema changes**\n   - Any schema format changes needed\n   - Schema loading tool changes\n\n5. **Infrastructure changes**\n   - Docker Compose updates\n   - ScalarDB Cluster deployment (if migrating to Cluster)\n\n## Dependency Versions\n\nThe diffs below write `:\u003Cversion>` on purpose: a migration is exactly the moment to move onto a\ncurrent **stable** ScalarDB release, and every ScalarDB artifact must land on the *same* version.\nResolve it per `rules\u002Fdependency-versions.md`\n(`https:\u002F\u002Frepo1.maven.org\u002Fmaven2\u002Fcom\u002Fscalar-labs\u002F\u003Cartifact>\u002Fmaven-metadata.xml`, or\n`gh release list -R scalar-labs\u002Fscalardb`), check it against the target edition and Java version, and\nconfirm with the user unless the project opted out (`options.confirm_versions` \u002F\n`--no-confirm-versions`). Do not carry the version the project is migrating *from* forward by default.\n\n## Common Migrations\n\n### Core CRUD 1PC → Cluster CRUD 1PC\n\n**Dependencies:**\n```diff\n- implementation 'com.scalar-labs:scalardb:\u003Ccurrent>'      # whatever the project pins today\n+ implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:\u003Cversion>'  # resolved stable\n```\n\n**Configuration:**\n```diff\n- scalar.db.storage=jdbc\n- scalar.db.contact_points=jdbc:mysql:\u002F\u002Flocalhost:3306\u002F\n- scalar.db.username=root\n- scalar.db.password=mysql\n+ scalar.db.transaction_manager=cluster\n+ scalar.db.contact_points=indirect:\u003CCLUSTER_HOST>\n```\n\n**Code changes:** None — the API is identical.\n\n**Schema loading:**\n```diff\n- java -jar scalardb-schema-loader-*.jar --config ...\n+ java -jar scalardb-cluster-schema-loader-*-all.jar --config ...\n```\n\n### Core CRUD 1PC → Core CRUD 2PC\n\n**Dependencies:** No changes.\n\n**Configuration:** No changes (same storage config).\n\n**Code changes:**\n```diff\n- DistributedTransactionManager manager = factory.getTransactionManager();\n- DistributedTransaction tx = manager.begin();\n+ TwoPhaseCommitTransactionManager manager = factory.getTwoPhaseCommitTransactionManager();\n+ TwoPhaseCommitTransaction tx = manager.begin();\n\n  \u002F\u002F CRUD operations (unchanged)\n\n- tx.commit();\n+ tx.prepare();\n+ tx.validate();\n+ tx.commit();\n```\n\n**New exception handling:** Add catches for `PreparationConflictException`, `PreparationException`, `ValidationConflictException`, `ValidationException`.\n\n### CRUD → JDBC\u002FSQL\n\n**Dependencies:**\n```diff\n- implementation 'com.scalar-labs:scalardb:\u003Ccurrent>'      # whatever the project pins today\n+ implementation 'com.scalar-labs:scalardb-sql-jdbc:\u003Cversion>'                 # resolved stable\n+ implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:\u003Cversion>'  # resolved stable\n```\n\n**Configuration:**\n```diff\n- scalar.db.storage=jdbc\n- scalar.db.contact_points=jdbc:mysql:\u002F\u002Flocalhost:3306\u002F\n- scalar.db.username=root\n- scalar.db.password=mysql\n+ scalar.db.sql.connection_mode=cluster\n+ scalar.db.sql.cluster_mode.contact_points=indirect:\u003CCLUSTER_HOST>\n```\n\n**Code changes:** Complete rewrite from CRUD builder pattern to JDBC PreparedStatement pattern.\n\n**Schema:** Convert `schema.json` to `schema.sql`.\n\n## Output Format\n\nPresent the migration plan as:\n\n```\n## Migration: [Source] → [Target]\n\n### 1. Dependency Changes\n[diff of build.gradle]\n\n### 2. Configuration Changes\n[diff of properties file]\n\n### 3. Code Changes\n[detailed description with before\u002Fafter examples]\n\n### 4. Schema Changes\n[any schema format or loading changes]\n\n### 5. Migration Steps\n1. Update build.gradle\n2. Update configuration\n3. Update code\n4. Test\n```\n\n## Reference Files\n\nConsult these reference documents:\n- `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcommon\u002Freferences\u002Finterface-matrix.md` — Interface combinations overview\n- `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcommon\u002Freferences\u002Fconfiguration-reference.md` — Configuration for all modes\n- `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcommon\u002Freferences\u002Fcode-patterns\u002F` — Complete code examples for each combination\n- `${CLAUDE_PLUGIN_ROOT}\u002Frules\u002Fscalardb-2pc-patterns.md` — Two-phase commit protocol rules (for 1PC -> 2PC migration)\n\n## How to Use\n\nThis agent should be invoked with a Agent tool call like:\n\n```\nAdvise on migrating from [current combination] to [target combination].\nAnalyze the code in [path] and generate a detailed migration plan\nwith dependency, configuration, and code changes.\n```\n","# \u002Fscalardb:migrate — ScalarDB Migration Advisor\n\nShared files: a path written `@rules\u002F…`, `@skills\u002F…`, `@templates\u002F…` or `@docs\u002F…` is relative to the\nplugin root, `${CLAUDE_PLUGIN_ROOT}` — not to the project being worked on. Read it from there.\n\nYou are a ScalarDB migration advisor. Help users migrate between interface combinations.\n\n**Knowledge grounding**: version-specific behavior (API signatures, config keys, exception retryability, edition-gated features) comes from the version-pinned OKF bundle, cited by `resource` URL, never from memory — @rules\u002Fokf-knowledge-bundle.md.\n\n## Supported Migration Paths\n\n### Deployment Mode Migrations\n- Core → Cluster (most common)\n- Cluster → Core (unusual, for debugging)\n\n### API Migrations\n- CRUD → JDBC\u002FSQL (adding SQL capabilities)\n- JDBC\u002FSQL → CRUD (switching to native API)\n\n### Transaction Mode Migrations\n- 1PC → 2PC (adding distributed transactions)\n- 2PC → 1PC (simplifying)\n\n**Do not advise a 1PC → 2PC migration on 3.19+: the 2PC interface is deprecated.** Spanning\nservices does not require it: the shared-cluster pattern keeps application code one-phase, and on\nScalarDB 3.19+ the Microservice Transaction API (`GlobalTransactionManager` \u002F `BranchTransaction`)\nwith a Transaction Coordinator node does the same for separated clusters — identical code, different\nproperties. A 2PC migration is the right answer only pre-3.19, on Core (Community) without Cluster,\nor with Spring Data JDBC, and then as an ADR-recorded deviation. Where consistency can be eventual,\nScalarDB Saga (3.20 GA) replaces the migration entirely.\nSee @rules\u002Fscalardb-2pc-patterns.md and @rules\u002Fscalardb-saga-patterns.md.\n\nA **2PC → 1PC** migration is the migration to propose on 3.19+: code on\n`TwoPhaseCommitTransactionManager`, the SQL `TWO_PHASE_COMMIT_TRANSACTION` mode or `join()` \u002F\n`resume()` (removed in 3.20) moves to a shared cluster or to the Microservice Transaction API\n(`skills\u002Fcommon\u002Freferences\u002Fcode-patterns\u002Fcluster-crud-microservice-tx.md`).\n\n**Two further migrations are access-path changes, not interface changes:** an existing SQL\napplication that must keep its native SQL on one database shared with ScalarDB applications moves\nto ScalarDB Native JDBC (@rules\u002Fscalardb-native-jdbc-patterns.md — refused statement shapes and the\nshared isolation level are the migration work), and SQL tooling or non-Java clients move to the\nPostgreSQL wire protocol on Cluster 3.20+ (@rules\u002Fscalardb-postgres-frontend-patterns.md).\n\n## Migration Analysis Process\n\n### Step 1: Identify Current State\nDetermine the user's current setup:\n- Current interface combination (deployment + API + transaction mode)\n- Current Maven dependencies\n- Current configuration properties\n- Current code patterns\n\n### Step 2: Identify Target State\nDetermine what they want to migrate to:\n- Target interface combination\n- Reason for migration\n\n### Step 3: Generate Migration Plan\n\nFor each migration, identify:\n\n1. **Dependency changes**\n   - Which Maven artifacts to add\u002Fremove\u002Freplace\n   - Version compatibility\n\n2. **Configuration changes**\n   - Which properties to add\u002Fchange\u002Fremove\n   - New required properties\n   - Property format changes (e.g., contact points)\n\n3. **Code changes**\n   - Which classes\u002Finterfaces change\n   - Method signature differences\n   - New patterns required (e.g., 2PC protocol)\n   - Deprecated APIs to update\n\n4. **Schema changes**\n   - Any schema format changes needed\n   - Schema loading tool changes\n\n5. **Infrastructure changes**\n   - Docker Compose updates\n   - ScalarDB Cluster deployment (if migrating to Cluster)\n\n## Dependency Versions\n\nThe diffs below write `:\u003Cversion>` on purpose: a migration is exactly the moment to move onto a\ncurrent **stable** ScalarDB release, and every ScalarDB artifact must land on the *same* version.\nResolve it per `rules\u002Fdependency-versions.md`\n(`https:\u002F\u002Frepo1.maven.org\u002Fmaven2\u002Fcom\u002Fscalar-labs\u002F\u003Cartifact>\u002Fmaven-metadata.xml`, or\n`gh release list -R scalar-labs\u002Fscalardb`), check it against the target edition and Java version, and\nconfirm with the user unless the project opted out (`options.confirm_versions` \u002F\n`--no-confirm-versions`). Do not carry the version the project is migrating *from* forward by default.\n\n## Common Migrations\n\n### Core CRUD 1PC → Cluster CRUD 1PC\n\n**Dependencies:**\n```diff\n- implementation 'com.scalar-labs:scalardb:\u003Ccurrent>'      # whatever the project pins today\n+ implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:\u003Cversion>'  # resolved stable\n```\n\n**Configuration:**\n```diff\n- scalar.db.storage=jdbc\n- scalar.db.contact_points=jdbc:mysql:\u002F\u002Flocalhost:3306\u002F\n- scalar.db.username=root\n- scalar.db.password=mysql\n+ scalar.db.transaction_manager=cluster\n+ scalar.db.contact_points=indirect:\u003CCLUSTER_HOST>\n```\n\n**Code changes:** None — the API is identical.\n\n**Schema loading:**\n```diff\n- java -jar scalardb-schema-loader-*.jar --config ...\n+ java -jar scalardb-cluster-schema-loader-*-all.jar --config ...\n```\n\n### Core CRUD 1PC → Core CRUD 2PC\n\n**Dependencies:** No changes.\n\n**Configuration:** No changes (same storage config).\n\n**Code changes:**\n```diff\n- DistributedTransactionManager manager = factory.getTransactionManager();\n- DistributedTransaction tx = manager.begin();\n+ TwoPhaseCommitTransactionManager manager = factory.getTwoPhaseCommitTransactionManager();\n+ TwoPhaseCommitTransaction tx = manager.begin();\n\n  \u002F\u002F CRUD operations (unchanged)\n\n- tx.commit();\n+ tx.prepare();\n+ tx.validate();\n+ tx.commit();\n```\n\n**New exception handling:** Add catches for `PreparationConflictException`, `PreparationException`, `ValidationConflictException`, `ValidationException`.\n\n### CRUD → JDBC\u002FSQL\n\n**Dependencies:**\n```diff\n- implementation 'com.scalar-labs:scalardb:\u003Ccurrent>'      # whatever the project pins today\n+ implementation 'com.scalar-labs:scalardb-sql-jdbc:\u003Cversion>'                 # resolved stable\n+ implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:\u003Cversion>'  # resolved stable\n```\n\n**Configuration:**\n```diff\n- scalar.db.storage=jdbc\n- scalar.db.contact_points=jdbc:mysql:\u002F\u002Flocalhost:3306\u002F\n- scalar.db.username=root\n- scalar.db.password=mysql\n+ scalar.db.sql.connection_mode=cluster\n+ scalar.db.sql.cluster_mode.contact_points=indirect:\u003CCLUSTER_HOST>\n```\n\n**Code changes:** Complete rewrite from CRUD builder pattern to JDBC PreparedStatement pattern.\n\n**Schema:** Convert `schema.json` to `schema.sql`.\n\n## Output Format\n\nPresent the migration plan as:\n\n```\n## Migration: [Source] → [Target]\n\n### 1. Dependency Changes\n[diff of build.gradle]\n\n### 2. Configuration Changes\n[diff of properties file]\n\n### 3. Code Changes\n[detailed description with before\u002Fafter examples]\n\n### 4. Schema Changes\n[any schema format or loading changes]\n\n### 5. Migration Steps\n1. Update build.gradle\n2. Update configuration\n3. Update code\n4. Test\n```\n\n## Reference Files\n\nConsult these reference documents:\n- `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcommon\u002Freferences\u002Finterface-matrix.md` — Interface combinations overview\n- `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcommon\u002Freferences\u002Fconfiguration-reference.md` — Configuration for all modes\n- `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fcommon\u002Freferences\u002Fcode-patterns\u002F` — Complete code examples for each combination\n- `${CLAUDE_PLUGIN_ROOT}\u002Frules\u002Fscalardb-2pc-patterns.md` — Two-phase commit protocol rules (for 1PC -> 2PC migration)\n\n## How to Use\n\nThis agent should be invoked with a Agent tool call like:\n\n```\nAdvise on migrating from [current combination] to [target combination].\nAnalyze the code in [path] and generate a detailed migration plan\nwith dependency, configuration, and code changes.\n```\n",{"model":31,"description":37},"Advise on moving between ScalarDB interfaces: Core and Cluster, CRUD and JDBC, one-phase and\ntwo-phase commit. To migrate from another database, use architect:migrate-database.\n","main","fed4c7ebb79ed82ce5c961f944a1ab0ab21bae26","skills\u002Fmigrate",1,"https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect","https:\u002F\u002Fnexus-architect-docs-070772.gitlab.io\u002F","https:\u002F\u002Fgithub.com\u002Fwfukatsu","https:\u002F\u002Fwww.scalar-labs.com\u002F","Wataru Fukatsu | Co-Founder and CEO, Scalar, Inc.","2026-11-14 22:03:27",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add wfukatsu\u002Fnexus-architect --skill migrate",{"tool":54,"command":55},"bunx","bunx skills add wfukatsu\u002Fnexus-architect --skill migrate",{"tool":57,"command":58},"pnpm","pnpm dlx skills add wfukatsu\u002Fnexus-architect --skill migrate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate\u002FSKILL.md",true,[],[63,93,125,154,178,195],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":75,"publishedAt":32},"01M6HRH10GPAVTZ8W90WD9HJK1","verify-sql-migration","Prove a SQL migration on data: golden checks against an authorized source database and\ndifferential tests against ScalarDB. Never touches production.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fverify-sql-migration\u002FSKILL.md",[69,70],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[76,77,78,79,80,25,81,82,83,84,85,26,86,87,88,89,90,91,92,31],"verify sql migration","verify","sql","migration","never","en","mode","true","tests","auto","id","properties","data","fetcher","Production","source","golden",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":108,"publishedAt":32},"01M6HRGWK643YKN0QVRQSNSDCR","verify-implementation","Check code against the design (API contract, transactions, security, requirements, the example\nchain) and report every divergence; optionally runs the eight-stage quality gate.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fverify-implementation\u002FSKILL.md",[99,102,105],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":103,"categoryName":104,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":106,"categoryName":107,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000037","律师与法务",[109,77,110,111,112,113,114,115,116,81,117,83,118,119,85,120,121,122,123,124],"verify implementation","implementation","chain","scope","quality gate","example","repo","backlog","api contract","design","contract","stage","requirements","code","api","check",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":137,"publishedAt":32},"01M6HRGS929NK1B5WG1ZANSXQ1","update-knowledge","Fetch or update an OKF knowledge bundle: ScalarDB\u002FScalarDL, or the vendored Kubernetes\u002FTerraform\nbundle.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fupdate-knowledge\u002FSKILL.md",[131,134],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153],"update knowledge","update","knowledge","fetch","plugin","haiku","name","kubernetes","latest","okf","status","terraform","Bash","bundle","Tools","root",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":164,"publishedAt":32},"01M6HRGNMYSK70R8Y9BY41E74D","start","Interactive entry point for system architecture work: refactor a legacy application into services,\nor design a new system from requirements; picks the path from the project's state. To move a\ndatabase to ScalarDB, use migrate-database.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fstart\u002FSKILL.md",[160,161],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":162,"categoryName":163,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000032","设计师",[156,165,166,167,168,118,29,169,26,121,5,170,171,172,173,174,175,176,177],"for","project","move","system","Legacy","interactive","architecture","state","work","services","refactor","application","path",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":32},"01M6HRGHZXK0NXF6W62MMNS46H","select-scalardb-edition","Choose the ScalarDB edition (Community, Enterprise Standard or Premium, plus Enterprise Options),\ndeployment mode and cluster topology through a short interview.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fselect-scalardb-edition\u002FSKILL.md",[],[185,186,187,188,30,189,190,191,192,82,193,194,31],"select","select scalardb edition","community","interview","options","deployment","choose","Enterprise","short","topology",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":32},"01M6HRGESF0BH6KCT70BP70B2J","scaffold","Generate a runnable ScalarDB starter project for any of the six interface combinations: build,\nconfig, schema, service class, docker-compose and README.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fscaffold\u002FSKILL.md",[201],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[197,203,165,166,204,205,206,207,208,209,210,211,212,213,214,31],"compose","docker-compose","README","docker","interface","schema","combinations","starter","generate","build","config","service"]