cursorrules

A repository rules file that gives AI assistants context and contribution requirements for SignalTree, a reactive JSON library for Angular.

In plain words
What is it for?
Explaining SignalTree’s state model and enforcing rules about numbers, documentation, and code generation.
Why use it?
It keeps generated code and documentation aligned with the project’s design and prevents unsupported measured figures from being published.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/jborgia/signaltree/cursorrules
Clone the repo
git clone --depth 1 https://github.com/JBorgia/signaltree

Made for: Cursor.

Per session 4,991 This file is loaded in full into every session.
When invoked 4,991 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
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 $0.04991 $0.04991
Opus 5 $0.02495 $0.02495
Sonnet 5 $0.00998 $0.00998
Haiku 4.5 $0.00499 $0.00499

Measured 2d ago against content hash 766f23ebcbb1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

cursorrules scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

1. ✅ Clean install: `rm -rf node_modules pnpm-lock.yaml && pnpm install`
.cursorrules · 711 lines

How it starts

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

SignalTree Repository Rules & Context

This file provides comprehensive context for AI assistants working on the SignalTree codebase.

Numbers in this file

Every measured figure here names the tool that regenerates it. If you are about to state a size or a timing that is not in this file, run the generator — do not recall it, and do not read it from artifacts/*.json, which is gitignored local scratch that has already put stale figures into published docs. See AGENTS.md.

This file primes code generation, so a wrong number here becomes wrong numbers in other people's repositories.

Repository Overview

SignalTree: Reactive JSON for Angular. JSON branches, reactive leaves.

No actions. No reducers. No selectors. Type-safe, dot-addressable state where data stays plain and reactivity stays invisible.

Core Philosophy:

  • JSON Branches — Your state paths look like JSON. $.user.profile.settings

  • Reactive Leaves — Leaf nodes are signals you read and write. tree.$.name()

  • No Mechanics — No actions, reducers, or selectors. Just data that reacts.

  • Lazy by Design — Signals created only where accessed. Minimal runtime footprint.

  • Language: TypeScript

  • Framework: Angular (for ng-forms, demo)

  • Package Manager: pnpm

  • Monorepo Tool: Nx

  • Build Tools: Rollup (packages & guardrails), Angular CLI (demo)

  • Testing: Vitest

  • Linting: ESLint

  • License: Apache-2.0

Architecture

Monorepo Structure

signaltree/
├── packages/              # All npm packages
│   ├── core/             # Main package with recursive typing
│   ├── ng-forms/         # Angular forms integration
│   ├── guardrails/       # Dev-only performance monitoring (Rollup build)
│   ├── shared/           # Internal shared utilities (PRIVATE - not published)
│   ├── types/            # Internal TypeScript types (PRIVATE)
│   └── utils/            # Internal utilities (PRIVATE)
├── apps/
│   └── demo/             # Demo application (Angular 19+)
├── scripts/              # Build, release, and validation scripts
├── dist/                 # Build output (gitignored)
└── docs/                 # Documentation

Read the full file on GitHub · 711 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 · 711 lines · 4,991 tokens per session scan C 766f23ebcbb1

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository JBorgia/signaltree (22 stars, last pushed 11d ago), licensed Apache-2.0. It adds 4,991 tokens to every session, about $0.0250 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.