backend-integration

Guides backend API modifications in a Laravel backend from a frontend development context.

3|1|Updated Jan 12, 2026

Search Tags:#php #laravel #rest api #backend integration #code conventions #pint #api endpoints

Ready to run

npx skills add https://github.com/nghyane/VSTEP --skill backend-integration-nghyane

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-integration
Source: https://github.com/nghyane/VSTEP/tree/main/apps/frontend-v3/.agents/skills/backend-integration
Command: npx skills add https://github.com/nghyane/VSTEP --skill backend-integration-nghyane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend developers often need to add or change backend API endpoints but lack knowledge of the backend codebase conventions, risking inconsistent code placement and style violations. ## Core Features & Use Cases - Convention Enforcement: Directs the agent to read the backend's AGENTS.md before writing any code. - Endpoint Discovery: Instructs grepping routes/api.php for existing endpoints to avoid duplication. - Service Layer Placement: Ensures business logic goes into app/Services/ rather than controllers. - Code Style Compliance: Runs Laravel Pint (./vendor/bin/pint --dirty) after changes. - Use Case: When adding a new API endpoint for a frontend feature, the agent checks existing routes, places logic in the correct service class, and formats the code automatically. ## Quick Start Add a new API endpoint to the backend for the learner dashboard feature following the backend integration rules.

Frequently Asked Questions about backend-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add a new API endpoint to a Laravel backend from a frontend project?▼

First read the backend's AGENTS.md for conventions, then grep routes/api.php to check for existing endpoints. Add your route, place the business logic in a service class under app/Services/, and run ./vendor/bin/pint --dirty to format the changes.

Where should business logic go in a Laravel application?▼

Business logic belongs in service classes under app/Services/, not in controllers. Controllers should stay thin and delegate work to services, keeping the codebase maintainable and testable.

How do I check if an API endpoint already exists in Laravel?▼

Grep the routes/api.php file for the endpoint path or related keywords. This prevents creating duplicate routes and helps you follow existing naming patterns.

What is Laravel Pint and when should I run it?▼

Laravel Pint is a code style fixer for PHP that enforces consistent formatting. Run ./vendor/bin/pint --dirty after making backend changes to format only the files you modified.

When should I not modify the backend directly from frontend work?▼

Avoid backend changes when the frontend can consume existing endpoints found in routes/api.php. Only modify the backend when a genuinely new endpoint or changed behavior is required, and always follow the documented conventions first.