apcore-skills

Part of aipartnerup/apcore-skills

Apcore ecosystem management skill for Claude Code. Handles cross-language SDK synchronization, framework integration scaffolding, multi-repo audits, spec-driven test generation, coordinated releases, and documentation alignment.

Commands

Command	Usage	Description
/apcore-skills		Ecosystem dashboard — versions, git status, health, all commands
/apcore-skills:sync	[repos...] [--phase a|b|all] [--fix] [--scope core|mcp|all] [--lang python,typescript,...] [--internal-check none|contract|skeleton|behavior] [--deep-chain on|off] [--save]	Cross-language API + contract/intent + call-chain (deep-chain) + documentation consistency check & fix
/apcore-skills:sdk	<language> [--type core|mcp] [--ref <existing-sdk>]	Bootstrap a new language SDK from reference
/apcore-skills:integration	<framework> [--lang python|typescript|go] [--ref <existing-integration>]	Bootstrap a new framework integration
/apcore-skills:audit	[--scope core|mcp|integrations|all] [--fix] [--no-deep-chain] [--save report.md]	Deep cross-repo consistency audit — 11 dimensions including D10 Contract Parity (shape-level intent) and D11 Deep-Chain Parity (chain-level intent — cross-language call-graph diff). Emits review-compatible output consumable by /code-forge:fix --review.
/apcore-skills:tester	[<repos...>] [--spec <feature>] [--mode generate|run|full] [--category unit|integration|boundary|protocol|contract|conformance|all] [--save report.md]	Spec-driven test generation & cross-language behavioral verification (incl. Contract-derived tests and shared conformance fixtures)
/apcore-skills:release	<version> [--scope core|mcp|integrations|all] [--dry-run]	Coordinated multi-repo release pipeline

Ecosystem

The apcore ecosystem consists of:

Core Protocol:

• apcore — Protocol specification and documentation

Core SDKs (must stay in sync):

• apcore-python — Python SDK
• apcore-typescript — TypeScript SDK (npm: apcore-js)
• apcore-rust — Rust SDK

MCP Bridges (must stay in sync):

• apcore-mcp-python — Python MCP server
• apcore-mcp-typescript — TypeScript MCP server (npm: apcore-mcp)
• apcore-mcp-rust — Rust MCP server

A2A Bridges:

• apcore-a2a-python — Python A2A bridge
• apcore-a2a-typescript — TypeScript A2A bridge

Toolkit:

• apcore-toolkit-python — Python toolkit
• apcore-toolkit-typescript — TypeScript toolkit

CLI:

• apcore-cli — Command-line interface

Framework Integrations:

• django-apcore — Django integration
• flask-apcore — Flask integration
• nestjs-apcore — NestJS integration
• tiptap-apcore — TipTap editor integration

Shared Libraries:

• apcore-discovery-python — Shared discovery utilities

Prerequisites

1. All apcore ecosystem repos should be in a common parent directory (e.g., ~/WorkSpace/aipartnerup/)
2. The apcore/ protocol repo with PROTOCOL_SPEC.md is required for sync, sdk, and tester (core-sdk target) commands
3. Spec repos per project type: apcore-mcp/ (MCP bridges), apcore-a2a/ (A2A bridges), apcore-cli/ (CLI), apcore-toolkit/ (toolkit)
4. No config file needed — ecosystem discovery is automatic based on directory naming conventions
5. Optional: .apcore-skills.json in the ecosystem root to customize discovery and version groups
6. code-forge skill required for sdk and integration commands (generates .code-forge.json and uses code-forge:port, code-forge:plan, code-forge:impl)

Breaking Changes (v0.10+)

• sync --internal-check default changed from none to contract. Every /apcore-skills:sync invocation without an explicit flag now runs Phase A signatures plus the contract-tier comparison (Step 4B). This is a stricter default than v0.9 and may surface pre-existing L2 intent divergences in repos that had never opted into contract checking.
• To preserve v0.9 behavior (Phase A signatures only), pass --internal-check=none explicitly: /apcore-skills:sync --internal-check=none.
• audit D4 now warns when a feature spec's public symbol has no ## Contract: block. Existing specs without Contract blocks will produce new warnings until filled in.
• release Step 2.5 consistency gate is mandatory before version bump. Critical audit/sync findings block release unless explicitly overridden with rationale (logged).

Consistency Layers

The ecosystem enforces consistency at three distinct layers — each layer has a different goal and a different skill responsible for it:

Layer	What must be identical	What may differ	Enforced by
L1 Implementation	— nothing required —	Helper names, function decomposition, control-flow shape, line count, idiom usage	Not enforced. Each language follows its own grain.
L2 Intent / Contract (SHAPE)	Inputs validation rules, errors raised (and codes), side-effect order, return shape, behavioral properties (async, thread_safe, pure, idempotent, reentrant)	Implementation details, helper structure	sync Step 4B (contract tier — default on) + audit D10 (Contract Parity)
L2.5 Intent / Call-Chain (CHAIN)	Which internal calls each public method makes, in what order, producing which state mutations. Catches "signatures match + declared contract matches, but internal call graph diverges" — e.g., one language's public method silently skips a validation call peers perform, or lacks a null-guard peers have	Helper decomposition, exact control-flow shape	sync Step 4C (deep-chain — default on) + audit D11 (Deep-Chain Parity)
L3 Public Signature	Class/function names (with language convention), parameter names/types, return types, trait/interface contracts, multi-constructor coverage	Internal type choices, private helpers	sync Step 4 (Phase A checklist) + audit D1 (API Surface)

Feature specs in doc repos (apcore/, apcore-mcp/) declare L2 contracts in ## Contract: ClassName.method blocks. See skills/shared/contract-spec.md for the authoritative format. audit D4 flags any public symbol whose feature spec lacks a Contract block.

When sync or audit detects an L2 divergence, its review-compatible output (# Project Review:) can be piped directly to /code-forge:fix --review for automated patching.

Integration with Other Skills

• spec-forge — Generate specifications for new features before implementing; specs should include ## Contract: blocks for every public method (see skills/shared/contract-spec.md)
• code-forge:plan / code-forge:impl — Plan and implement features within individual repos
• code-forge:port — Port features from one language SDK to another
• code-forge:fix --review — Directly consumes audit (Step 3.1) and sync (Step 9.1) review-compatible output to patch L2/L3 divergences across repos
• code-forge:tdd / code-forge:fix — Fix failures surfaced by tester via TDD red-green cycle
• code-forge:verify — Verify test results before claiming fixes are complete
• apcore-skills — Ecosystem-level operations that span multiple repos