5462 Verified Industrial Rules/Deterministic Behavioral Specifications

Industrial Guardrails for AI Coding Agents

Establish strict architectural baselines for your engineering team. Fully compatible with Cursor (.mdc), Claude Code (CLAUDE.md), Windsurf, Codex / Cline, and GitHub Copilot.

Popular Stacks:
Auto-Detect Stack from Manifest
Showing 24 of 5462 industrial specifications
fastify-5-schema-compilers-encapsulation-production-standard
backendcritical

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

Blocks:Mutating global AJV/fast-json-stringify compilers or exposing route-level decorators and hooks across sibling plugin contexts without encapsulation boundaries.
Targets:Cursor•Claude•Windsurf•Codex
solidstart-1-0-server-functions-async-boundaries-production-standard
frontendcritical

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

Blocks:Closing over reactive client signals inside server$ RPCs or calling unvalidated server functions directly in reactive effects.
Targets:Cursor•Claude•Windsurf•Codex
astro-5-actions-content-layer-production-standard
frontendcritical

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

Blocks:Writing legacy Astro v4 content collection configurations and unvalidated server actions that throw generic Errors instead of ActionError.
Targets:Cursor•Claude•Windsurf•Codex
nuxt-4-nitro-server-engine-shared-directory-production-standard
frontendcritical

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

Blocks:Placing mutable module-level state in Nitro event handlers and importing server-only dependencies into client or shared directories.
Targets:Cursor•Claude•Windsurf•Codex
svelte-5-runes-reactivity
frontendcritical

Svelte 5 Runes ($state, $derived, $effect) & Legacy Reactivity Elimination

Production standard for Svelte 5. Mandates using modern Runes ($state, $derived, $effect) and strictly eliminates deprecated Svelte 3/4 reactive declarations ($: variable = ...) and mutable let bindings.

Blocks:AI writes deprecated $: reactive declarations or let count = 0 inside Svelte 5 components, failing to trigger the new signals-based reactivity engine.
Targets:Cursor•Claude•Windsurf•Codex
bun-sqlite-wal-concurrency
backendcritical

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

Blocks:AI opens bun:sqlite with default rollback journals and un-isolated batch inserts, triggering SQLITE_BUSY crashes under concurrent requests.
Targets:Cursor•Claude•Windsurf•Codex
drizzle-orm-batch-transactions
backendcritical

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

Blocks:AI loops single insert queries over serverless HTTP DB drivers (Neon / PlanetScale), creating 20x network latency waterfalls and partial failure states.
Targets:Cursor•Claude•Windsurf•Codex
temporal-io-deterministic-workflow
backendcritical

Temporal.io Workflow Code Determinism & Side Effect Isolation Standard

Production standard for Temporal.io distributed orchestrations. Mandates strict determinism inside workflow functions, strictly prohibiting Math.random(), Date.now(), mutable global variables, or direct network/database calls outside Temporal Activities.

Blocks:AI calls Date.now() or fetch() directly inside a Temporal workflow function, causing non-deterministic replay crashes during worker upgrades.
Targets:Cursor•Claude•Windsurf•Codex
tanstack-start-router-ssr-production-standard
frontendcritical

TanStack Start SSR: Type-Safe Search Validation, Granular Loader Dependencies, and Deferred Data Streaming

Enforces strict type safety for URL search parameters via schema validators, prevents SSR render blocking through deferred streaming promises, and ensures loaders trigger re-executions only when declared dependencies mutate. Failing to adhere leads to TTFB degradation, hydration mismatch exceptions, and silent cache invalidation bugs in fullstack TanStack applications.

Blocks:Blocking SSR on non-critical queries and relying on untyped search params without loaderDeps
Targets:Cursor•Claude•Windsurf•Codex
react-19-action-hooks-useactionstate-production-standard
frontendcritical

React 19 Action Hooks & useActionState Production Standard & Concurrency Guardrail

React 19 introduces native async Action transitions that manage pending states, concurrent updates, and optimistic rollbacks natively within the framework lifecycle. Reverting to legacy manual useState booleans for submission states introduces race conditions, breaks concurrent rendering boundaries, and bypasses automatic error boundaries. Modern production frontends must leverage useActionState, useOptimistic, and useFormStatus to ensure resilient, race-condition-free form lifecycles.

Blocks:Wrapping async form handlers in manual useState loading and error states instead of leveraging native React 19 Actions.
Targets:Cursor•Claude•Windsurf•Codex
next-js-15-server-actions-boundary-csrf-production-standard
frontendcritical

Next.js 15 Server Actions Boundary CSRF & Origin Validation Standard

Next.js 15 Server Actions enforce built-in origin checks against the Host header, but multi-domain setups, reverse proxy misconfigurations, or unauthenticated action endpoints create severe CSRF and unauthorized state mutation vectors. Production actions must assert authenticated session identity, validate strict schemas, and configure experimental.serverActions.allowedOrigins to protect critical boundaries.

Blocks:Treating Server Actions as private client-only functions while omitting boundary session checks and reverse-proxy origin configurations.
Targets:Cursor•Claude•Windsurf•Codex
valkey-8-0-threaded-io-cluster-failover-production-standard
backendcritical

Valkey 8.0 Threaded I/O & Cluster Failover Production Standard & Concurrency Guardrail

Valkey 8.0 introduces dual-channel multi-threaded I/O to scale network throughput while preserving single-threaded execution atomicity. Clustered deployments must strictly handle MOVED/ASK redirects and slot hashing constraints during node failovers and shard migration. Failure to enforce slot co-locality via hash tags in multi-key operations and Lua scripts causes CROSSSLOT errors and catastrophic transactional rollback failures during cluster rebalancing.

Blocks:Executing un-hashed multi-key commands and Lua scripts across disparate nodes while failing to handle cluster redirects and transient failover states.
Targets:Cursor•Claude•Windsurf•Codex
qwik-city-resumability-containerization-production-standard
frontendcritical

Qwik City Resumability & Containerization Production Standard

Enforces Qwik's zero-hydration resumability model by strictly isolating lexical boundaries across Optimizer-split chunk closures. Prevents accidental closure captures, serialization bottlenecks, and eager code evaluation that degrade instant-on performance. Failure to maintain clean serializable boundaries introduces runtime de-opt failures, memory leaks, and massive client bundle bloat.

Blocks:Capturing non-serializable runtime instances inside '$' closures or eagerly importing heavy client modules without QRL boundaries.
Targets:Cursor•Claude•Windsurf•Codex
vite-6-environment-api-multi-runtimes-production-standard
frontendcritical

Vite 6 Environment API & Multi-Runtimes Architecture Standard

Vite 6 deprecates monolithic SSR transforms in favor of the Environment API, isolating module graphs and module runners across distinct runtimes (Node.js, Edge, workerd, and Client). Conflating environment module graphs or invoking deprecated APIs like `ssrLoadModule` causes cross-runtime state leakage, broken HMR transport boundaries, and unhandled execution crashes. Strict boundary isolation across `server.environments` MUST be enforced to guarantee deterministic compilation and Hot Module Replacement.

Blocks:Defaulting to legacy `ssrLoadModule` and accessing shared server transform caches across multi-runtime targets instead of scoped `DevEnvironment` instances.
Targets:Cursor•Claude•Windsurf•Codex
tanstack-start-router-ssr-streaming-standard
frontendcritical

TanStack Start & Router SSR: Type-Safe Search Validation, Loaders, and Deferred Streaming

Enforces strict type safety and streaming invariants in TanStack Start and TanStack Router SSR applications. Mandates route-level search param schema validation via Zod/Valibot, prevents waterfall SSR blocking by requiring deferred streaming for non-critical dependencies, and enforces execution-boundary safety between loaders and server functions.

Blocks:Unvalidated search params with blocking SSR loaders that serialize entire component trees before initial stream flush.
Targets:Cursor•Claude•Windsurf•Codex
surrealdb-2-0-live-queries-record-links-production-standard
backendcritical

SurrealDB 2.0 Live Queries & Record Links Production Standard

SurrealDB 2.0 introduces strict RecordId types, an overhauled Rust engine, and push-based LIVE QUERY streaming over WebSockets. In production, unmanaged live queries cause persistent socket leaks and cluster memory exhaustion, while handling record links as arbitrary strings breaks transactional graph traversal and schema validation.

Blocks:Treating record IDs as raw interpolated strings and abandoning live query UUID subscriptions without deterministic teardown.
Targets:Cursor•Claude•Windsurf•Codex
duckdb-node-js-zero-copy-apache-arrow-ingest-production-standard
backendcritical

DuckDB Node.js Zero-Copy Apache Arrow Ingest & Concurrency Standard

DuckDB in Node.js requires strict adherence to zero-copy memory boundaries when streaming Arrow IPC records and executing parallel analytical queries across connection pools. Naive JSON serialization, raw ArrayBuffer copies, or concurrent queries sharing a single un-pooled Connection instance trigger V8 heap exhaustion, memory leaks, or native segfaults. Production architectures must enforce worker-safe connection pooling, explicit Arrow RecordBatch streaming via C++ IPC bindings, and strictly bounded memory limits.

Blocks:Deserializing analytical query results into native V8 JavaScript objects or executing concurrent queries on a single un-pooled DuckDB Connection handle.
Targets:Cursor•Claude•Windsurf•Codex
valkey-8-0-threaded-io-cluster-failover-guardrails
backendcritical

Valkey 8.0 Threaded I/O & Cluster Failover Production Standards

Valkey 8.0 leverages asynchronous multi-threaded I/O for socket read/write operations while preserving single-threaded execution for command mutations. In distributed cluster deployments, unhandled MOVED and ASK redirections during automatic master failovers cause cascading connection pool exhaustion and silent command drops. Furthermore, multi-key operations and Lua scripts execute atomically only when all involved keys map to the identical cluster hash slot via explicit hash tags.

Blocks:Executing cross-slot multi-key commands without hash tags while ignoring cluster failover redirects and socket pool saturation.
Targets:Cursor•Claude•Windsurf•Codex
langgraph-2026-stateful-checkpointers-human-in-the-loop-production-standard
backendcritical

LangGraph Stateful Checkpointers & Resilient Human-in-the-Loop Concurrency Guardrail

LangGraph production systems require durable checkpointers, deterministic thread scoping, and atomic human-in-the-loop (HITL) interrupt semantics to preserve workflow states across restarts and horizontal scaling. Relying on transient in-memory checkpointers or blocking asynchronous loops destroys state continuity and causes workflow deadlocks during deployments. Teams must mandate transactional state backends, native interrupt triggers, and schema-validated resumes within immutable channel reducers.

Blocks:Deploying ephemeral in-memory checkpointers in distributed environments and hijacking graph control with unpersisted manual prompts instead of native interrupt primitives.
Targets:Cursor•Claude•Windsurf•Codex
litellm-proxy-load-balancing-fallback-routing-production-standard
backendcritical

LiteLLM Proxy Load Balancing & Fallback Routing Production Standard

Production LiteLLM proxy deployments must maintain deterministic fallback topologies, bounded semantic cache lifecycles, and tenant-isolated token quota budgets across heterogeneous model providers. Without explicit circuit breaking and tier-aware load balancing, transient provider rate limits escalate into catastrophic cascading failures across upstream microservices. Reliable gateway architectures decouple client call-sites from provider-specific error formats by enforcing uniform retry budgets and distributed cache invalidation.

Blocks:Naive direct model invocations lacking circuit breakers, fallback groups, and budget bounds that crash downstream services on provider HTTP 429 bursts.
Targets:Cursor•Claude•Windsurf•Codex
tauri-2-0-mobile-ipc-permissions-scope-production-standard
mobilecritical

Tauri 2.0 Mobile IPC & Capabilities Permissions Matrix Standard

Tauri v2 introduces a capability-driven permissions system replacing legacy v1 allowlists across iOS and Android runtimes. Failure to constrain IPC command handlers with typed schemas and explicit mobile capability definitions exposes native mobile OS surfaces to arbitrary code execution, permission leakage, and silent serialization failures. Production mobile deployments require strictly typed IPC boundary validation, granular capability scopes, and graceful permission degradation.

Blocks:Hallucinating deprecated Tauri v1 allowlists or executing unsanitized IPC commands across mobile webviews without capability scoping.
Targets:Cursor•Claude•Windsurf•Codex
capacitor-7-native-bridge-biometric-auth-production-standard
mobilecritical

Capacitor 7 Native Bridge, Biometric Auth & Android 15 Lifecycle Production Standard

Capacitor 7 enforces strict bridge lifecycle contracts, asynchronous native plugin interop, and mandatory Android 15 edge-to-edge window inset handling. Storing sensitive authentication tokens in unencrypted web storage or failing to bind biometric authentication directly to hardware-backed Keystore or Secure Enclave mechanisms compromises app integrity and causes fatal crash or viewport occlusion issues on modern mobile operating systems.

Blocks:Persisting biometrically gated tokens in plaintext Web Storage or CapacitorPreferences while ignoring Android 15 edge-to-edge safe area occlusion.
Targets:Cursor•Claude•Windsurf•Codex
tanstack-start-ssr-streaming-search-params
frontendcritical

TanStack Start SSR Loader Invariants: Type-Safe Search Params & Deferred Streaming

Enforces type-safe search parameter validation via explicit schemas, prevents SSR TTFB stalls by delegating non-critical data to deferred streaming promises, and guarantees server-only boundaries using TanStack Start server functions.

Blocks:Awaiting slow secondary data in SSR loaders and accessing raw, unvalidated search parameters.
Targets:Cursor•Claude•Windsurf•Codex
tailwind-v4-css-first-theme-directives
frontendcritical

Tailwind CSS v4 CSS-First Theme Directives and Dynamic Interpolation Guardrail

Enforces modern Tailwind CSS v4 CSS-first configuration via pure @theme and @theme inline blocks, deprecating legacy tailwind.config.js/ts abstractions. Mandates native CSS custom properties with color-mix() runtime opacity interpolation instead of legacy RGB channel workarounds. Ensures token declarations follow v4 standard namespace conventions and CSS variable resolution across the build pipeline.

Blocks:Persisting legacy tailwind.config.js architecture and RGB-tuple opacity hacks in Tailwind CSS v4 environments
Targets:Cursor•Claude•Windsurf•Codex
Architectural Philosophy

The Industrial Behavioral Standard for AI Coding Assistants

Modern software engineering teams increasingly rely on autonomous coding assistants like Cursor, Claude Code, Windsurf, Codex, and Cline. However, raw foundational LLMs lack repository-specific context, memory of breaking framework versions, and corporate security guidelines. AgentRules.org establishes an industrial-grade behavioral matrix that transforms erratic AI code generation into deterministic, verified engineering output.

Deterministic Guardrails

Preemptively restrict AI agents from generating deprecated APIs, unauthenticated Server Actions, or sync blocking calls before code ever touches your repository.

Deprecation Immunity

Hardened against training cutoff biases. Automatically steer agents away from Next.js 14 pages/ router, React 18 manual useMemo sprays, and Tailwind v3 configurations.

Zero-Friction Sync

Export seamlessly to Cursor Modern (.cursor/rules/*.mdc), Claude Code (CLAUDE.md), Windsurf, Codex/Cline (AGENTS.md), and GitHub Copilot in one click or via CLI.

Root-Cause Analysis

Why Autonomous AI Models Hallucinate Deprecated Code

When an LLM generates software, it does not possess runtime introspection or an active compiler. Instead, it predicts the next token based on statistical probabilities learned during pre-training. This creates three critical failure modes in modern software projects:

1. Training Distribution Bias (Legacy Repositories Outnumber Modern Ones 100:1)

Because Next.js 12-14, React 16-18, and Tailwind v2-v3 existed for years before Next.js 15, React 19, and Tailwind v4 were released, the model has seen orders of magnitude more legacy code. Without negative constraints, statistical averaging will almost always output legacy patterns.

2. Asynchronous Boundary Blindness

In Python (FastAPI/SQLAlchemy) and Node.js (Next.js 15 cookies/params), APIs shifted from synchronous values to asynchronous Promises. LLMs frequently omit await or invoke blocking synchronous calls inside async event loops, paralyzing high-throughput servers.

3. Silent Concurrency & Security Leakage

AI assistants optimize for making code compile in a sandbox. They routinely omit authorization checks in Server Actions, spin up unbounded goroutines in Go without context cancellation, or run Docker containers as root UID 0.

Ecosystem Architecture

The AI Agent Golden Iron Triangle

An effective autonomous AI developer requires three coordinated layers working in unison: Behavioral Constraints, Procedural Skills, and System Tools.

Layer 1: RulesAgentRules.org

Behavioral Guardrails

Defines architectural invariants, forbidden anti-patterns, and technology conventions (.cursorrules, CLAUDE.md, AGENTS.md).

Layer 2: Skillsaskills.dev

Execution Functions

Powers the agent with executable recipes for refactoring, test scaffolding, database schema migrations, and design tokens.

Layer 3: Toolsmcp-serverlist.com

System Capabilities (MCP)

Discovers and connects standardized Model Context Protocol servers for secure filesystem access, database querying, and live git operations.

Multi-Client Format Matrix

Universal Compatibility Across AI Development Clients

Every rule in AgentRules.org is engineered with a multi-target AST transformer that emits valid configuration files formatted specifically for your IDE or CLI environment:

Cursor Modern (.mdc)
.cursor/rules/*.mdc

Scoped YAML frontmatter with file globs (e.g. app/**/*.{ts,tsx}). Automatically activates rules only when relevant files are edited.

Anthropic Claude Code
CLAUDE.md

Root-level markdown guidelines read by Claude Code CLI. Formatted with strict section headings, build commands, and architectural invariants.

Codeium Windsurf
.windsurfrules

Project-wide behavioral instructions optimized for Windsurf Cascades and contextual multi-file code modifications.

OpenAI Codex / Cline
AGENTS.md

Universal agent system prompts compliant with OpenAI Codex, Cline, and Roo Code agent instruction frameworks.

Cursor Legacy (.cursorrules)
.cursorrules

Traditional root-level cursorrules format supported across all versions of Cursor IDE.

GitHub Copilot
.github/copilot-instructions.md

Official repository-level custom instructions format read by GitHub Copilot Chat in VS Code and JetBrains.

Curated Fullstack Blueprints

Pre-Assembled Industrial Stacks

Field-tested rule combinations with AST conflict resolution for the world's most demanding production stacks:

fullstack7 Rules

Next.js 15 + React 19 + Tailwind v4 + Prisma + Docker

Production-grade behavioral constraints for modern Next.js 15 App Router applications. Enforces asynchronous cookies, pure CSS variables in Tailwind v4, React 19 compiler hooks, anti-N+1 Prisma queries, and non-root Docker builds.

View Stack Blueprint
backend5 Rules

FastAPI + Pydantic v2 + SQLAlchemy 2.0 + Docker Security

Enforces async I/O integrity in FastAPI, Pydantic v2 model_validate patterns, SQLAlchemy 2.0 select syntax, and zero-privilege Docker containerization.

View Stack Blueprint
backend4 Rules

Go Gin + GORM Concurrency + Clean Architecture + Docker

Enforces explicit Go error handling, goroutine context cancellation, GORM thread-safe session branching, and minimal scratch Docker containers.

View Stack Blueprint
backend3 Rules

Rust Axum + Tokio + Cloud-Native Systems

Production behavioral rules for Rust backend engineering. Guards against blocking the Tokio executor, enforces Send + Sync state, and mandates zero unwrap() in production paths.

View Stack Blueprint
mobile4 Rules

React Native + Expo SDK 52 + Expo Router + Zod

Architectural rules for React Native and Expo SDK 52. Guards native bridge performance, enforces Expo Router typed routes, and prevents plain-text storage of API keys on mobile clients.

View Stack Blueprint
web33 Rules

Solidity 0.8+ + Reentrancy Guard + Gas Optimization

Zero-tolerance security guardrails for EVM smart contracts. Enforces Checks-Effects-Interactions, custom errors over string reverts, and strictly audited OpenZeppelin contracts.

View Stack Blueprint
backend6 Rules

Autonomous AI Agents + MCP Protocol + LangGraph 2026 + pgvector

Ironclad behavioral invariants for autonomous AI agents, Model Context Protocol (MCP) tool servers, durable LangGraph state machines, and high-recall PostgreSQL pgvector HNSW indexing.

View Stack Blueprint
devops5 Rules

ArgoCD + Helm 3 + OpenTelemetry + Caddy 2 + Docker

Enterprise Kubernetes continuous delivery and distributed observability stack. Enforces Git as the single source of truth via ArgoCD self-healing, type-safe Helm schema validation, W3C distributed trace propagation, and automatic ACME edge TLS termination.

View Stack Blueprint
backend5 Rules

Stripe Webhooks + RS256 JWT + Redis Rate Limiter + PII Masking

Financial-grade payment webhook ingestion and identity authentication architecture. Mandates raw-buffer HMAC verification, RS256 JWT rotation in HttpOnly cookies, atomic Redis sliding-window DDoS protection, and recursive PII log sanitization.

View Stack Blueprint
backend5 Rules

ClickHouse + RabbitMQ + DuckDB + OpenSearch + pgvector

Industrial high-throughput data streaming, vectorized in-situ analytics, and hybrid lexical/vector search. Enforces ClickHouse ReplacingMergeTree append-only tables, RabbitMQ Dead Letter Exchange (DLX) resilience, DuckDB zero-copy Parquet queries, and cached Lucene BitSet filters.

View Stack Blueprint
backend6 Rules

OpenAI Structured Outputs + vLLM + LangChain LCEL + OWASP Guardrails

Enterprise generative AI serving architecture. Enforces CFG grammar-constrained JSON generation with zodResponseFormat, vLLM continuous batching with PagedAttention, async streaming LCEL chains, and indirect prompt injection boundaries.

View Stack Blueprint
devops5 Rules

Tailscale WireGuard + AWS CDK v2 + KEDA Autoscaling + Istio mTLS

Defense-in-depth cloud platform architecture. Replaces open public IP ports with Tailscale WireGuard mesh tunnels, synthesizes least-privilege AWS CDK v2 infrastructure, autoscales worker pods on message queue lag via KEDA, and enforces strict Istio SPIFFE mTLS.

View Stack Blueprint
backend6 Rules

Semantic RAG + DeepEval CI + OpenAI Structured Outputs + pgvector + MCP Sandboxing

Enterprise architecture for hallucination-resistant RAG systems. Combines structural markdown chunking, Cross-Encoder reranking, automated DeepEval regression test suites in CI/CD, strictly typed Zod JSON outputs, and sandboxed Model Context Protocol execution.

View Stack Blueprint
fullstack6 Rules

IETF Idempotency-Key + Casbin ABAC + Redis Locks + Stripe Webhooks + SOPS Secrets

Financial-grade transaction processing architecture. Mandates IETF Idempotency-Key header enforcement with atomic Redis distributed locks, declarative Casbin PERM authorization, cryptographic Stripe webhook verification, and SOPS secret encryption in GitOps.

View Stack Blueprint
backend5 Rules

Kafka Consumer Commit + Redis Streams PEL + ClickHouse Deduplication + Go errgroup

Production event streaming and analytics ingestion architecture. Mandates asynchronous batch commits with rebalance listeners in Kafka, explicit Pending Entries List (PEL) recovery in Redis Streams, argMax version deduplication in ClickHouse, and context-aware error propagation with Go errgroup.

View Stack Blueprint
frontend5 Rules

Next.js 15 PPR + Server Actions CSRF + React 19 useTransition + TypeScript satisfies

Modern frontend performance and security standard. Mandates Next.js 15 Partial Prerendering (PPR) with experimental dynamicIO, cryptographic Origin/CSRF verification on Server Actions, non-urgent state slicing via useTransition, and strict satisfies type narrowing.

View Stack Blueprint
Anti-Hallucination Error Catalog

Common AI Coding Hallucination Traps & Verified Fixes

Exact error signatures generated by Cursor, Claude Code, and Copilot due to LLM training cutoff biases, diagnosed with verified root cause fixes:

Developer FAQ

Frequently Asked Questions About Agent Rules

Everything you need to know about implementing industrial AI coding guardrails across your engineering organization:

Q:How do agent rules prevent AI coding hallucinations?

Agent rules inject deterministic constraints into the system instruction layer of your AI editor. By pairing explicit negative constraints (e.g. "never use synchronous cookies() in Next.js 15") with positive production examples, the LLM's token generation is bounded before it produces code.

Q:What is the token budget impact of stacking multiple rules?

A typical single rule consumes ~250 tokens (0.1% of Claude 3.5 Sonnet's 200k context window). When combining 5-8 rules into a Fullstack Agent Pack, our AST deduplication merger strips redundant instructions, keeping the entire pack under 1,800 tokens. We also provide a Compact Mode that compresses instructions by 64%.

Q:How does AgentRules resolve conflicting guidelines across multiple stacks?

Our synthesis engine groups rules into distinct namespaces (Frontend, Backend, DevOps, Security) and assigns precedence hierarchies. When rules share overlapping concerns (e.g. TypeScript strictness in Next.js vs Vite), higher-severity constraints override looser defaults.

Q:Can our engineering team enforce rule compliance in CI/CD pipelines?

Yes. We provide automated GitHub Actions workflow generators (.github/workflows/agent-rules-check.yml) and pre-commit hooks that audit your .cursorrules or CLAUDE.md against our REST API (/api/audit) to prevent accidental drift.

3 Rules in Stack

Next.js, Tailwind, TypeScript