agentmods.dev

back-office-architecture

back-office-architecture is a cursor rule for Cursor from Scopeo/draftnrun. It costs 0 tokens per session (1,001 once invoked), scanned A, original, Apache-2.0.

A frontend architecture guide for a Vue application, covering folders, reusable components, pages, API modules, data-fetching hooks, navigation, and plugins. It also describes areas such as knowledge bases, workflows, agents, and monitoring.

In plain words
What is it for?
Use it when adding Vue pages, components, API modules, data queries, dialogs, charts, navigation items, or screens for workflows, agents, and monitoring.
Why use it?
It gives a shared structure for placing new code and connecting the interface to APIs. This reduces inconsistent folder layouts and duplicated patterns as the application grows.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

not rated 30repo 4d ago A scan 0 tokens original Apache-2.0

Good fit Use it when adding Vue pages, components, API modules, data queries, dialogs, charts, navigation items, or screens for workflows, agents, and monitoring.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/scopeo/draftnrun/back-office-architecture
View source ↗ Scopeo/draftnrun draftnrun.vercel.app
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/Scopeo/draftnrun

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for back-office-architecture

README.md
[![agentmods](https://agentmods.dev/badge/rules/scopeo/draftnrun/back-office-architecture.svg)](https://agentmods.dev/rules/scopeo/draftnrun/back-office-architecture)
Your own site
<a href="https://agentmods.dev/rules/scopeo/draftnrun/back-office-architecture"><img src="https://agentmods.dev/badge/rules/scopeo/draftnrun/back-office-architecture.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,001 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01001
Opus 5 $0.00000 $0.00500
Sonnet 5 $0.00000 $0.00200
Haiku 4.5 $0.00000 $0.00100

Measured 2d ago against content hash bc94eba33c25, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

back-office-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

frontend/.cursor/rules/back-office-architecture.mdc · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Back-office architecture

Directory structure

src/
  api/              # Domain-specific API modules (one file per domain)
  assets/           # Images, styles (auth.scss, misc.scss)
  components/       # Reusable components
    charts/         #   Chart.js wrappers (BarChart, LineChart, etc.)
    dialogs/        #   GenericConfirmDialog, HelpRequestDialog
    shared/         #   EmptyState, ErrorState, skeletons, VersionSelector, etc.
    studio/         #   Studio/flow builder (Vue Flow nodes, edges, panels)
    knowledge/      #   Knowledge base CRUD & editor
    monitoring/     #   Monitoring/observability dashboards
    qa/             #   QA testing & evaluation
    workflows/      #   Workflow-specific UI
    agents/         #   Agent-specific UI
    observability/  #   Observability detail views
  composables/      # Vue composables
    queries/        #   TanStack Query hooks (one per domain)
  layouts/          # default.vue (sidebar + main), blank.vue (auth pages)
  navigation/       # Sidebar nav item config (vertical/)
  pages/            # File-based routing (unplugin-vue-router)
  plugins/          # App plugins (vuetify, casl, router, gtm, hotjar)
  services/         # Backend integration (auth, Google Drive, scopeoApi barrel)
  stores/           # Pinia stores — auth, org, config (only these three)
  types/            # TypeScript type definitions
  utils/            # Helpers (logger, colorConverter, validators, formatters, etc.)

Component conventions

  • Naming: PascalCase file names (AgentChatHistory.vue).
  • Max size: ~400 lines per .vue file. Extract sub-components or composables when approaching the limit.
  • Script: Always <script setup lang="ts">.
  • Props/Emits: Use generic type parameter syntax (defineProps<T>(), defineEmits<T>()).

API modules (src/api/)

One file per domain — e.g. agents.ts, workflows.ts, knowledge.ts. Each exports named API objects (e.g. export const agentsApi = { ... }).

Read the full file on GitHub · 99 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 99 lines · 0 tokens per session scan A bc94eba33c25

Subscribe to this mod's changes

back-office-architecture is a cursor rule published in the GitHub repository Scopeo/draftnrun (30 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,001 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

FrontendVue and Svelte
Related

Other cursor rules, from other repositories

svelte-5-vs-svelte-4-cursorrules-prompt-file

Cursor rules for comparing Svelte 5 and Svelte 4 development.

PatrickJS/awesome-cursorrules · 653 tokens

sveltekit-typescript-guide-cursorrules-prompt-file

Cursor rules for SvelteKit development with TypeScript integration.

PatrickJS/awesome-cursorrules · 189 tokens

vue-typescript-patterns

A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.

soaring-xiongkulu/easyaiot · 381 tokens

svelte-mcp-tools

Instructions for using the Svelte MCP server tools for documentation lookup, code analysis, and validation.

sveltejs/ai-tools · 297 tokens

frontend-component

Vue component structure, styling, derived state, modals, icons, DaisyUI/Tailwind frontend component conventions.

nerds-odd-e/doughnut · 0 tokens

frontend

Vue frontend — components, Vitest, generated API client, apiCallWithLoading, DaisyUI. Read this first for any frontend work.

nerds-odd-e/doughnut · 28 tokens