AICodingKit Dev Tooling

@aicodingkit/dev provides the aicodingkit-dev and create-aicodingkit global npm commands. It is authored in TypeScript and compiled to dist/ before packaging.

For complete installation, Capability Pack authoring, command, Catalog publication, CI, and source development instructions, see the Chinese usage and development guide.

New Capability Packs default to every supported Agent: opencode, claude-code, cursor, codebuddy, and trae. The generated aicodingkit.yaml therefore omits spec.compatibility.agents; omit it from an existing Pack as well when all Agents are supported. A Skill, MCP, or Profile can explicitly narrow or change that default through spec.overrides.<coordinate>.compatibility.agents. Catalog publication writes the resolved declaration into each immutable entry. Existing historical Catalog entries are validated as-is and are never backfilled.

The published npm artifact uses bundleDependencies for yaml. Build a local artifact with npm ci, npm run build, and npm pack --pack-destination releases; install it on an offline machine with npm install --global --offline <artifact.tgz>.

npm Release And Offline Artifact

Install the published author tooling with npm install --global @aicodingkit/dev. A protected GitLab release tag named v<package.json version> validates the source, stores an offline .tgz under the releases/ job artifact, and publishes the package to npmjs. Configure NPM_TOKEN as a masked, protected, ordinary GitLab CI/CD variable in this project. It must be an npm access token allowed to publish the @aicodingkit scope; do not configure it as a File variable.

npm versions are immutable. Increase package.json, commit and push the change, then create and push the matching protected v<version> tag. The release job fails rather than attempting to overwrite an existing npm version.

Generated Capability Pack pipelines pin AICODINGKIT_TOOLING_VERSION to the generator's current version. A group or project CI/CD variable with the same name can centrally override that YAML default after a newer Tooling version has been published. This permits a controlled fleet upgrade; otherwise, regenerate the pipeline and review the explicit version change in each Pack repository.

Central Artifact Registry

Generated Capability Pack pipelines publish every new immutable Pack artifact to the GitLab Generic Package Registry of AICODINGKIT_CATALOG_PROJECT_ID. The resulting Catalog Entry uses the same central Artifact URL, while source.repository and source.commit continue to identify the original Pack source project.

The protected AICODINGKIT_CATALOG_TOKEN is the Catalog release bot credential. It must be able to push the generated Catalog release branch, create its merge request, and upload Generic Packages in the Catalog project. Pack pipelines no longer upload release artifacts to their own CI_PROJECT_ID, so new Pack versions do not require individual Artifact read access for every developer. Existing Catalog entries and their historic Artifact URLs are not migrated.