project-structure

A set of rules for organizing the PoolAI repository and choosing languages for each part. It defines the roles of Rust, JavaScript, TypeScript, and Bash, and distinguishes folders such as source code, tests, scripts, and Rust binaries.

In plain words
What is it for?
Use it when adding files, choosing a location for code or tests, creating command-line binaries, writing scripts, or checking that repository changes follow PoolAI’s layout.
Why use it?
It reduces confusion about where files belong and prevents accidental use of prohibited languages or incorrect folder conventions.

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/platinoff/poolai/project-structure
Clone the repo
git clone --depth 1 https://github.com/platinoff/poolAI

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,214 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.01214
Opus 5 $0.00000 $0.00607
Sonnet 5 $0.00000 $0.00243
Haiku 4.5 $0.00000 $0.00121

Measured yesterday against content hash d04356db6a6b, 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.

.cursor/rules/project-structure.mdc · 97 lines

How it starts

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

Project Structure Rules

Runtime stack (канон)

  • Primary: Rust — src/, tests/, crates/ (див. .cursor/rules/runtime-stack-policy.mdc, alwaysApply).
  • UI: JavaScript у src/ui/; E2E — e2e/ (TypeScript).
  • Python: заборонено в репозиторії (0× .py); OpenAPI audit — cargo run --bin poolai-openapi-gap-audit.
  • Java: у репо немає; не додавати без явного запиту.
  • Архівні docs з Python — ігнорувати для імплементації.

Repository layout (люди vs Cargo)

Повний опис: docs/development/REPOSITORY_LAYOUT.md.

Шлях Призначення
src/ Rust product code (library + main)
src/bin/ Cargo binaries onlycargo run --bin NAME
bin/ Dev/ops launchers.sh / .ps1 (run, LAN, verify, e2e)
scripts/ Toolchain / deploy — MSYS PATH, gcc, build verify, git helpers
tests/ Integration tests (Rust convention)
crates/*/src/ Workspace members (e.g. poolai-solana-adapter)

Не плутати: кореневий bin/src/bin/. Rust .rs binaries тільки в src/bin/.

Directory Organization

  • src/ - Source code (all Rust modules)
  • tests/ - Integration tests (all test files)
  • docs/ - Documentation (all markdown files)
    • docs/troubleshooting/ - Troubleshooting guides (QUICK_FIX_MSYS2.md, etc.)
  • bin/ - Dev/ops shell scripts (launch, LAN stand, verify, cargo helpers)
  • scripts/ - Toolchain, MSYS setup, deployment helpers
  • docker/ - Docker files (Dockerfile, docker-compose.yml)
  • .agents/skills/ - Canon Agent Skills (Cursor + OpenCode): marketplace copies + abracadabra, poolai-documentation
  • .cursor/ - Cursor agent configuration (rules, commands, plans, native skill mirrors)
    • .cursor/rules/ - All Cursor rules (including .cursorrules moved here)
    • .cursor/skills/ - Cursor-native mirrors of project skills (keep identical to .agents/skills/)
  • .opencode/skills/ - OpenCode-native mirrors of project skills (keep identical to .agents/skills/)
  • AGENTS.md - OpenCode always-on canon (same VDT as alwaysApply Cursor rules)

Read the full file on GitHub · 97 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 · 97 lines · 1,214 tokens per session scan A d04356db6a6b

Subscribe to this mod's changes

project-structure is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,214 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-31.