intent-and-structure

A guide to the layout and coding conventions of a PNPM monorepo, a repository containing multiple related packages.

In plain words
What is it for?
It supports work across package source code, documentation, tests, scripts, shared dependencies, and release configuration.
Why use it?
It helps an agent place changes correctly and follow the project's rules for imports, errors, testing, builds, and releases.

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/logosdx/monorepo/intent-and-structure
Clone the repo
git clone --depth 1 https://github.com/logosdx/monorepo

Made for: Cursor.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 622 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00013 $0.00622
Opus 5 $0.00006 $0.00311
Sonnet 5 $0.00003 $0.00124
Haiku 4.5 $0.00001 $0.00062

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

Security

Grade A, and why

intent-and-structure 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.

.cursor/rules/intent-and-structure.mdc · 74 lines

What it actually says

Intent & Structure

PNPM monorepo structure and organizational patterns for the @logosdx ecosystem.

Repository Structure

  • Source code: packages/*/src/ - Each package has its own source directory
  • Documentation: docs/ - Centralized documentation for all packages
  • Tests: tests/src/ - Mirrors source structure for validation
  • Scripts: scripts/ - Build, release, and utility scripts
  • Configuration: Root-level configs for TypeScript, build tools, etc.

Package Organization

  • Independent packages: Each package builds and publishes separately
  • Shared dependencies: Internal packages depend on each other via published interfaces
  • Cross-package imports: Use package names (@logosdx/utils) not relative paths
  • Test imports: Use relative paths (../../packages/utils/src/index.ts) to validate actual implementation

Error Handling Philosophy

  • Fail-prone operations (I/O, network, async) → Use Go-style error tuple [result, error]
  • Business logic functions → Return actual results directly
  • Composition → Combine error tuple for I/O with direct returns for business logic

Build & Release

  • Individual builds: Each package builds independently with its own config
  • Coordinated releases: Use changeset for version management and releases
  • Type generation: Shared TypeScript configs for consistent type generation
  • Documentation: TypeDoc generation for each package

Development Workflow

  • Package creation: Use pnpm run new script for new packages
  • Testing: pnpm run test runs all tests, pnpm run tdd for development
  • Building: pnpm run build builds all packages
  • Documentation: pnpm run build:docs generates TypeDoc

Quick Examples

# Create new package
pnpm run new

# Run tests
pnpm run test
pnpm run tdd

# Build everything
pnpm run build

# Generate docs
pnpm run build:docs
// ✅ Cross-package imports (production code)
import { attempt } from '@logosdx/utils';
import { ObserverEngine } from '@logosdx/observer';

// ✅ Test imports (relative paths)
import { attempt } from '../../../../packages/utils/src/index.ts';
import { ObserverEngine } from '../../../../packages/observer/src/engine.ts';

// ❌ Wrong import pattern in tests
import { attempt } from '@logosdx/utils'; // Won't validate actual implementation

// ✅ Error handling patterns
// Fail-prone operation (I/O)
const [user, err] = await attempt(() => fetchUser(userId));
if (err) throw err;

// Business logic (direct return)
const modifiedUser = modifyUserEmail(user, newEmail);
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 · 74 lines · 13 tokens per session scan A 336d190ac0b3

Subscribe to this mod's changes

intent-and-structure is a cursor rule published in the GitHub repository logosdx/monorepo (7 stars, last pushed 17d ago), licensed BSD-3-Clause. It adds 13 tokens to every session and 622 once invoked, about $0.0001 per session on Opus 5. 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-08-31.