project-structure

A directory map for a pnpm workspace monorepo, which is one repository containing multiple related packages and applications. It shows where the Next.js frontend, backend packages, shared code, configuration, and assets belong.

In plain words
What is it for?
It guides developers when adding pages, API routes, UI components, shared packages, configuration, public files, and other project code.
Why use it?
It prevents new code from being placed in the wrong package or directory and helps keep shared and browser-only code separated.

Cursor rule for Claude Code

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/robinfaraj/one-context/project-structure
Clone the repo
git clone --depth 1 https://github.com/robinfaraj/one-context

Made for: Claude Code.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 782 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.00000 $0.00782
Opus 5 $0.00000 $0.00391
Sonnet 5 $0.00000 $0.00156
Haiku 4.5 $0.00000 $0.00078

Measured yesterday against content hash cbf78f0d4df7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

project-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 yesterday.

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.

.claude/skills/coding-style/references/project-structure.mdc · 73 lines

How it starts

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

Project Structure

pnpm workspace monorepo with a Next.js App Router app and shared backend packages.

Root

  • pnpm-workspace.yaml, turbo.json, package.json — workspace and build orchestration
  • tsconfig.json, tooling/typescript/*.json — TypeScript bases
  • biome.json — lint and format (Biome, not ESLint/Prettier)
  • config/ — shared runtime config and types
  • tooling/ — scripts, Tailwind preset, TypeScript presets
  • prompts/ — brand guide and prompt references

App (frontend)

apps/web/ — Next.js App Router application (SSR-first)

  • Pages and routing: apps/web/app/**
    • app/api/**/route.ts — API routes (edge/server)
    • app/layout.tsx, app/page.tsx, app/global-error.tsx — global files
  • Feature modules: apps/web/modules/**
    • modules/ui/ — UI components (shadcn/ui, Radix, Tailwind)
    • modules/shared/ — cross-domain shared code (keep minimal)
  • Public assets: apps/web/public/**
  • Config: apps/web/next.config.ts, apps/web/postcss.config.cjs

Place all browser/UI-only code in apps/web. Prefer Server Components; limit use client to interactive UI concerns.

Backend and Shared Packages

Package Purpose Status
packages/api/ HonoJS API server — routes, middleware, shared utils Active (health, auth routes)
packages/auth/ better-auth config, helpers, plugins Active
packages/database/ Prisma schema, migrations, client Active
packages/integrations/ Third-party integrations Scaffolded
packages/logs/ Logging config and helper Active
packages/mail/ Email providers and templates Scaffolded
packages/storage/ File storage providers Scaffolded
packages/tasks/ Background tasks / Trigger.dev Scaffolded
packages/utils/ Shared utilities (dates, html, links, errors, types) Active

Key Paths

  • API entry: packages/api/src/app.ts
  • API routes: packages/api/src/routes/**
  • Database schema: packages/database/prisma/schema.prisma
  • Migrations: packages/database/prisma/migrations/**

Read the full file on GitHub · 73 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. yesterday First seen · 73 lines · 0 tokens per session scan A cbf78f0d4df7

Subscribe to this mod's changes

project-structure is a cursor rule published in the GitHub repository robinfaraj/one-context (43 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 782 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-08-30.