campusway-api-contract-regression
Keeps backend API responses and frontend expectations aligned with regression checks.
Install
mkdir -p .claude/skills/campusway-api-contract-regression && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15164" && unzip -o skill.zip -d .claude/skills/campusway-api-contract-regression && rm skill.zipInstalls to .claude/skills/campusway-api-contract-regression
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
CampusWay API contract and regression workflow for Express TypeScript endpoints. Use when: API response changed, field mismatch, frontend integration broke, schema drift, endpoint refactor, release regression checks.Key capabilities
- →Define contract scope including endpoint path, method, request, response fields, and status codes
- →Confirm current backend implementation for a specific endpoint
- →Compare frontend usage path and required fields with backend contract
- →Apply minimal compatibility changes, such as preserving old fields or adding new ones
- →Run backend and frontend builds and targeted tests for verification
- →Record explicit contract deltas including added, removed fields, and status code changes
How it works
This skill outlines a procedure for verifying API contracts by comparing backend implementations with frontend expectations, applying compatibility changes, and running verification tests.
Inputs & outputs
When to use campusway-api-contract-regression
- →Verify api contract
- →Refactor endpoint
- →Regression test check
About this skill
CampusWay API Contract Regression
Outcome
Keep backend responses and frontend expectations aligned while reducing endpoint regressions.
When To Use
- API payload shape changes.
- Frontend breaks after backend refactor.
- New fields are added or renamed.
- Release candidate needs API safety validation.
Procedure
- Define contract scope:
- endpoint path and method
- request fields
- response fields and status codes
- Confirm current backend implementation for that endpoint.
- Compare frontend usage path and required fields.
- Apply minimal compatibility changes:
- preserve old fields when safe
- add additive fields before removing legacy fields
- Run verification:
cd backend && npm run build- targeted backend tests for affected module
cd frontend && npm run buildcd frontend && npm run e2e:smoke -- e2e/public-smoke.spec.ts
- Record explicit contract delta:
- added fields
- removed fields
- status code changes
Decision Points
- If breaking change is unavoidable, require staged rollout note and frontend update in same PR.
- If contract is used by multiple clients, keep backward-compatible fallback window.
Quality Checks
- No runtime undefined-field errors in frontend.
- Backend returns stable status codes and validation errors.
- Contract changes are documented in related API docs.
References In Workspace
API_CONTRACT_SUBSCRIPTION.mdHOME_API_CONTRACT.mdNEWS_API_CONTRACT.mdbackend/API_DOCUMENTATION.md
When not to use it
- →When the API is not an Express TypeScript endpoint
- →When the changes do not involve API response changes or schema drift
- →When the frontend integration is not broken due to API changes
Limitations
- →If a breaking change is unavoidable, a staged rollout note and frontend update in the same PR are required
- →If a contract is used by multiple clients, a backward-compatible fallback window should be maintained
- →The skill does not automatically fix runtime undefined-field errors in the frontend
How it compares
This workflow systematically aligns backend API contracts with frontend expectations through a defined procedure and verification steps, reducing regressions more effectively than ad-hoc checks.
Compared to similar skills
campusway-api-contract-regression side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| campusway-api-contract-regression (this skill) | 0 | 4mo | No flags | Intermediate |
| mqtt-kmp | 0 | 4mo | Review | Advanced |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
| telegram-mini-app | 62 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by md-muntasir-shihab
View all by md-muntasir-shihab →You might also like
mqtt-kmp
meshtastic
MQTTastic Client KMP — Kotlin Multiplatform MQTT 5.0 client library project knowledge
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
telegram-mini-app
davila7
Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and building viral mini apps that monetize. Use when: telegram mini app, TWA, telegram web app, TON app, mini app.
stripe-integration
wshobson
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.
nestjs-expert
davila7
Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js authentication. Use PROACTIVELY for any Nest.js application issues including architecture decisions, testing strategies, performance optimization, or debugging complex dependency injection problems. If a specialized expert is a better fit, I will recommend switching and stop.
nodejs-backend-patterns
wshobson
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.