Frequently Asked Questions
Everything you need to know about prompt sharding, agent rules, and security profiles.
Auxo is a zero-auth, real-time collaborative workspace designed to translate raw developer brainstorming notes, stack lists, and requirements into a prompt-optimised context matrix.
Instead of manually writing structured system instructions for AI coding assistants, you outline your application details in our editor, compile the pack, and download a single ZIP containing formatted context files (`AGENTS.md`, `CLAUDE.md`, `.windsurfrules`, and `.cursor/rules/*.mdc`) ready to drop into your repository root.
Large Language Models (LLMs) suffer from attention degradation when prompt context windows grow too large. Instructions located in the middle of a massive configuration block (such as a bloated, single `.cursorrules` file) are frequently ignored or overridden—a phenomenon known as the "Lost-in-the-Middle" effect.
Auxo solves this by sharding your guidelines. Global architectures live in `AGENTS.md`, CLI scripts live in `CLAUDE.md`, and specific logical rules are partitioned into individual `.mdc` files scoped by file path globs. Editors like Cursor load these rules into memory only when you edit matching files, reducing input token overhead by up to 18.4% on average.
AGENTS.mdacts as the universal system constitution read by over 30 coding assistants. It serves as your project's structural source of truth.
It declares global technology stacks, architectural boundaries, coding philosophies (such as DRY, KISS, SOLID, YAGNI), and regulatory compliance directives (like HIPAA, SOC2, or PCI-DSS) without polluting individual rules with duplicate styling conventions.
CLAUDE.mdis a specialised runtime instructions file parsed directly by Anthropic's Claude Code CLI.
Because Claude Code loads this file at the start of every session, Auxo creates a condensed reference sheet registering the exact safe commands to run your development server, build pipeline, linters, and testing suites. It references @AGENTS.md to keep tokens small and prevent expensive session initialisation overhead.
Cursor rules use structured YAML frontmatter blocks containing path patterns (globs) to specify when they should be loaded.
For example, Auxo will isolate frontend styling constraints to ui-theme.mdc (bound to `src/components/**/*`), and database query schemas to a separate logic rule. This ensures the AI model only holds instructions relevant to the file it is actively modifying, avoiding rule contamination and token bloat.
Absolutely. We enforce a strict zero-retention security profile. When you use the Bring Your Own Key (BYOK) compile tier:
- Your OpenAI, Anthropic, or Gemini keys are obfuscated client-side in LocalStorage using symmetric XOR mask arrays combined with Base64 encoding.
- Keys are transmitted exclusively over TLS-encrypted HTTPS connections within transient request headers.
- Requests bypass our hosted databases entirely. Keys are processed strictly in Edge memory during compilation and are never logged, cached, or written to disk.
Yes. Auxo provides an unlimited Free BYOK (Bring Your Own Key) Tier. Supply your own Gemini, OpenAI, or Anthropic API key and run deep AI compilations completely for free — no account required.
For users who prefer keyless convenience, we offer hosted Cloud Credits (Tier 2 and Tier 3) that route through our internal Claude Sonnet 4.6 keys. These tiers are currently in preview — check the pricing page for availability.