Skip to content
Back to search

backoffice-skill

Agent skill: one sentence about a business in, a working multi-tenant management system out.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/tabishhassan5121472--backoffice-skill/badge.svg)](/listings/tabishhassan5121472--backoffice-skill)

HTML

<a href="/listings/tabishhassan5121472--backoffice-skill"><img src="/api/listings/tabishhassan5121472--backoffice-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Needs Node 22.13 or newer.

The skill is the `skills/backoffice` folder. Copy it to wherever your agent loads skills from.

**Claude Code**

git clone https://github.com/tabishhassan5121472/backoffice-skill
mkdir -p ~/.claude/skills && cp -R backoffice-skill/skills/backoffice ~/.claude/skills/

**Other agents** (Codex, Cursor, Gemini CLI and others that read `SKILL.md` folders): copy `skills/backoffice` into that agent's skills folder. The skill is plain Markdown plus Node scripts and uses nothing specific to one agent. It has been tested in Claude Code; reports from other agents are welcome.

Then ask for a system:

Use the backoffice skill: a system for my dental clinic.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 128 lines
  1. # backoffice
  2. **One sentence about a business in, a working management system out.**
  3. `backoffice` is an agent skill. Tell your coding agent "build me a system for my gym" (or clinic, car
  4. rental, guesthouse, agency, school) and it designs the business, generates a complete multi-tenant admin
  5. system, and proves it works with an automated check before it tells you it is done.
  6. ```text
  7. > Build me a system for a small car rental company: vehicles, bookings and damage reports.
  8. ```
  9. ![27-second demo: one sentence in, a working car rental system out](docs/demo.gif)
  10. *The terminal in the clip is recreated; every application screen is a real capture of the generated system.*
  11. The result of that one sentence, from a 256-line config the agent wrote, with no hand-written demo data:
  12. ![Dashboard of the generated car rental system](docs/dashboard.png)
  13. ![Fleet board: which car is out, reserved or free over the next two weeks](docs/fleet-board.png)
  14. What you get, running on your machine a few minutes later:
  15. - sign-in, with separate organisations that cannot see each other's data
  16. - roles that are really different: per-section permissions, hidden fields, steps only some roles may take
  17. - searchable, sortable, filterable tables with CSV export; forms with validation
  18. - status workflows ("Hand over keys", "Check in", "Mark paid") that update linked records
  19. - business rules: no double booking, capacity limits, calculated totals, automatic reference codes
  20. - a dashboard with date-aware tiles ("today", "overdue", "next 7 days"), charts and lists
  21. - team management and an activity log for the owner
  22. - demo data that holds together: past classes are completed, paid invoices have a payment date
  23. - one custom "signature" screen for the business (a timetable, a fleet calendar, a room board)
  24. ## How it works
  25. Agents are good at judgement and bad at writing the same CRUD code correctly forty times. So the skill
  26. splits the work:
  27. 1. **The agent designs the business** and writes one file, `system.config.ts`: the records, the roles, the
  28. lifecycle, the rules, the dashboard.
  29. 2. **A bundled template turns that file into the app**: database, API, every screen, demo data.
  30. 3. **`npm run verify` proves it**: it type-checks, builds, boots the server and exercises every section as
  31. every role (permissions, hidden fields, every status step and its side effects, business rules, tenant
  32. isolation, custom routes). The agent is told not to say "done" until every check passes.
  33. The generated app is plain, readable code you own: Node (built-in SQLite, no native modules), Express,
  34. React, Vite, Tailwind. One process, one port, no accounts, no API keys.
  35. ## Install
  36. Needs Node 22.13 or newer.
  37. The skill is the `skills/backoffice` folder. Copy it to wherever your agent loads skills from.
  38. **Claude Code**
  39. ```bash
  40. git clone https://github.com/tabishhassan5121472/backoffice-skill
  41. mkdir -p ~/.claude/skills && cp -R backoffice-skill/skills/backoffice ~/.claude/skills/
  42. ```
  43. **Other agents** (Codex, Cursor, Gemini CLI and others that read `SKILL.md` folders): copy
  44. `skills/backoffice` into that agent's skills folder. The skill is plain Markdown plus Node scripts and
  45. uses nothing specific to one agent. It has been tested in Claude Code; reports from other agents are welcome.
  46. Then ask for a system:
  47. ```text
  48. Use the backoffice skill: a system for my dental clinic.
  49. ```
  50. ## What is in the box
  51. ```text
  52. skills/backoffice/
  53. SKILL.md the workflow the agent follows
  54. references/domain-design.md how to model a business: core record, roles, rules, dashboard
  55. references/config-reference.md every option of system.config.ts
  56. references/blueprints/ ready designs: gym, clinic
  57. scripts/create.mjs copies the template into a new project
  58. assets/kernel/ the app template, including scripts/verify.mjs
  59. ```
  60. A taste of the config:
  61. ```ts
  62. {
  63. name: 'bookings', label: 'Bookings', singular: 'Booking', title: 'reference',
  64. fields: [
  65. { name: 'reference', type: 'text', auto: 'BK-{seq:5}' },
  66. { name: 'vehicle_id', type: 'ref', ref: 'vehicles', required: true },
  67. { name: 'pickup_on', type: 'date', required: true },
  68. { name: 'return_on', type: 'date', required: true },
  69. { name: 'total', type: 'money', compute: 'days(pickup_on, return_on) * vehicle_id.daily_rate' },
  70. ],
  71. status: {
  72. field: 'status', initial: 'reserved',
  73. states: [...],
  74. transitions: [
  75. { from: ['reserved'], to: 'on_rent', label: 'Hand over keys',
  76. then: [{ update: 'vehicle_id', set: { status: 'on_rent' } }] },
  77. { from: ['on_rent'], to: 'returned', label: 'Check in', set: { returned_on: 'today' },
  78. then: [{ update: 'vehicle_id', set: { status: 'available' } }] },
  79. ],
  80. },
  81. rules: [
  82. { check: 'return_on >= pickup_on', message: 'The return date cannot be before the pick-up date.' },
  83. { noOverlap: { per: 'vehicle_id', start: 'pickup_on', end: 'return_on' }, unless: { status: 'cancelled' },
  84. message: 'This vehicle is already booked for those dates.' },
  85. ],
  86. }
  87. ```
  88. ## What it is not
  89. A generated system is a strong starting point and a convincing demo, not a finished product. It does not
  90. include real payments, email or SMS, file uploads, or production hosting, and the demo data is rebuilt
  91. whenever the config changes. Anything handling real customer, health or payment data needs a proper
  92. review before it goes live.
  93. ## Contributing
  94. Blueprints are the most useful contribution: a one-page design for a business you know well (see
  95. `references/blueprints/gym.md`). Bug reports with the `system.config.ts` that triggered them are next.
  96. ## Licence
  97. MIT. Built by [Tabish Hassan](https://tabishapps.com).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.