How does this skill help with monorepo management?

It provides a standardized step-by-step procedure to update multiple packages (contracts, api, bot) in the correct order, followed by a global verification check.

Why is direct database access prohibited for the bot?

To maintain a clean separation of concerns, the skill enforces that consumers like bots must use the API layer, ensuring all data access follows the defined business logic and contracts.

What does a contract-first approach mean in this skill?

It means the API schema (the 'contract') must be defined and updated in the shared contracts package before any implementation logic is written in the API or consumer services.

Which verification commands are executed?

The skill runs pnpm build commands for the contracts, api, and bot filters, along with a general check command to ensure the entire system is valid after changes.

Contract-First API Workflow

Name: Contract-First API Workflow
Author: Hakuya5247

byHakuya5247

API 개발

Enforces a contract-first development cycle for API changes to ensure consistency across schemas, services, and documentation.

소개

The Contract-First API Workflow skill is designed to standardize the way API changes are implemented within a monorepo environment. It mandates a strict sequence of operations: defining the schema in a shared contracts package, implementing the API, updating consumer services (like bots) without direct database access, and finally updating documentation. This approach minimizes integration errors, ensures type safety across the stack, and maintains a single source of truth for your API specifications, making it ideal for teams prioritizing architectural integrity and automated verification.

주요 기능

Synchronized documentation updates for structural changes
Dependency enforcement preventing direct DB access from consumer layers
0 GitHub stars
Strict contract-first schema definition in shared packages
Standardized workflow for API additions and modifications
Automated multi-package build verification with pnpm

사용 사례

Enforcing architectural boundaries between backend services and UI/bot consumers
Adding new endpoints to a TypeScript monorepo with type-safe contracts
Refactoring existing API structures while ensuring consumer compatibility

소개

주요 기능

Synchronized documentation updates for structural changes
Dependency enforcement preventing direct DB access from consumer layers
0 GitHub stars
Strict contract-first schema definition in shared packages
Standardized workflow for API additions and modifications
Automated multi-package build verification with pnpm

사용 사례

Enforcing architectural boundaries between backend services and UI/bot consumers
Adding new endpoints to a TypeScript monorepo with type-safe contracts
Refactoring existing API structures while ensuring consumer compatibility