OpenParable
Skip to content
← Back to skills

Crm Package Development

Development
crm-package-development

Crm Package Development is an Agent Skill for development published in the krayin/laravel-crm repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when creating a new Krayin CRM package or module, extending CRM functionality via a package, or adding custom business logic without modifying core files. Covers Laravel package structure, service providers, migrations, models, repositories, routes, controllers, views, config, ACL, and menus.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/krayin/laravel-crm/blob/HEAD/.github/skills/crm-package-development/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/crm-package-development, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Skill: CRM Package Development (Krayin CRM)

Purpose

This skill guides the AI agent to design and develop a new CRM package (module) for Krayin CRM in a clean, upgrade-safe, and maintainable way.


When to Activate

Activate this skill when the user wants to:

  • Create a new CRM package/module
  • Extend CRM functionality via a package
  • Add custom business logic without modifying core files

Project Context

  • Framework: Laravel
  • Product: Krayin CRM
  • Krayin CRM is already installed and running
  • The package must integrate seamlessly with existing CRM modules

Development Rules

  • Follow Krayin CRM architecture and conventions
  • Do NOT modify core Krayin files unless explicitly required
  • Use Laravel package-based structure
  • All database changes must be done using migrations
  • Ensure backward compatibility and safe upgrades

Package Structure Guidelines

A CRM package should follow this structure:

packages/
└── Webkul/
    └── PackageName/
        ├── src/
        │   ├── Providers/
        │   │   └── PackageServiceProvider.php
        │   ├── Models/
        │   ├── Contracts/
        │   ├── Repositories/
        │   ├── Http/
        │   │   ├── Controllers/
        │   │   └── Requests/
        │   ├── Routes/
        │   │   ├── admin.php
        │   │   └── api.php
        │   ├── Database/
        │   │   └── Migrations/
        │   ├── Resources/
        │   │   └── views/
        │   └── Config/
        │       └── package.php
        │       ├── menu.php
        │       ├── core_config.php
        │       └── acl.php
        └── composer.json