Demo

Use Prompt Engineering

Write workflow-first Agent Plans — not CRUD checklists. Use the HR pre-build prompt as the reference shape, then adapt it to your plugin.

Prompt tips

  • Start from Pre-build Prompts → HR Plugins (copy structure, then change domain)
  • Require “read .agents/skills/quan-erp and quan-erp-plugins first” in every task
  • Demand workflow outcomes (approve/post/transfer/payroll) — forbid list/create/edit-only delivery
  • Every DB entity class must end with Entity and extend BaseEntity; list full detail props per entity
  • Reuse builtin services/entities (Partner, User, Branch, Currency, File, Notification…) — no local copies
  • Spell services as domain logic, APIs as actions, pages as ops UI (inbox, timeline, reports)
  • Name plugin id/folder and whether backend, frontend, or both; end with a demo path + checklist

Recommended plan shape (from HR)

Mirror the HR Agent Plan sections so the agent gets a complete build contract.

  • 0. Intro & detail — skills, reuse builtins, naming rules, mandatory non-CRUD outcomes
  • 1. Features — workflow-first numbered capabilities
  • 2. Entity — *Entity classes + full detail props (and per-record differences when needed)
  • 3. Service — domain services, not CRUD wrappers
  • 4. Apis — action endpoints (approve, change-salary, generate payroll…)
  • 5. Dto — action DTOs + validation rules
  • 6. Pages — detail views + ops screens
  • 7. Goal — demo path + register/roles checklist + README assumptions

Example prompt (HR-shaped starter)

Short starter you can paste, then replace with the full HR pre-build prompt or your own domain plan.

TSexample prompt
1Read .agents/skills/quan-erp/SKILL.md and quan-erp-plugins first. 2Use the Pre-build Prompts → HR Plugins plan as the reference format. 3 4Build plugins/hr/ as a full people-ops plugin — NOT CRUD only. 5Mandatory: EmployeeDetailEntity dossier; per-employee EmployeeSalaryHistoryEntity 6(different current amount/currency/frequency allowed); LeaveTypeEntity + LeavePolicyEntity 7+ optional EmployeeLeaveEntitlementEntity overrides; AttendanceRecordEntity; 8PayrollRunEntity → PayslipEntity/PayslipLineEntity from each employee's own current salary. 9 10Naming: every DB entity class must end with Entity and extend BaseEntity. 11List full detail props for every entity. Reuse User/Branch/Currency/File/Notification builtins. 12Deliver workflow services + action APIs + ops pages (leave inbox, salary timeline, payroll run). 13Demo: hire two employees with different salaries → leave + attendance → payroll finalize. 14End with registration checklist and README assumptions (leave-day rules, payroll deductions).

Use Pre-build Prompts

For a ready-made full Agent Plan, open Build with AI Agent → Pre-build Prompts → HR Plugins, copy the prompt, and paste it into Cursor Agent. Adapt the same section layout for CRM, Inventory, Accounting, and other domains.

  • HR is the richest reference (detail, salary history, leave rules, attendance, payroll)
  • Keep the 0–7 section order when you invent a new domain prompt
  • Prefer copying Pre-build Prompts over writing a thin “add CRUD page” ask