Frequency Engineering Standards
Welcome to the single source of truth for how we build software at Frequency. These standards exist so every developer — new or veteran — can build with confidence, ship with consistency, and maintain the high bar our users expect.
Why Standards Matter
Standards aren’t bureaucracy — they’re multipliers. When everyone follows the same patterns:
- New developers onboard in days, not weeks
- Code reviews focus on logic, not style debates
- AI assistants generate correct code because they have clear rules
- Security and privacy are built-in, not bolted on
- Upgrades propagate cleanly because boundaries are respected
How This Site Is Organized
| Section | What You’ll Find |
|---|---|
| Architecture | Monorepo structure, shared packages, app patterns |
| Getting Started | Environment setup, first build, dev workflow |
| Tech Stack | Every technology we use and why |
| UI & Design | Mantine-first rules, theming, accessibility |
| API Standards | Security tiers, routes, error handling |
| Data & Schemas | LinkML → SQL → TypeScript pipeline |
| Security | PII classification, middleware, quality gates |
| AI Development | Agent system, specialist roles, slash commands |
| Deployment | Vercel, DNS, PR previews, environment vars |
| Runbooks | Step-by-step operational guides |
| ADRs | Architecture Decision Records |
Quick Start
If you’re new to Frequency, start here:
- Read Architecture to understand the monorepo and shared packages
- Follow Getting Started to set up your local environment
- Review UI & Design before writing your first component
- Check AI Development to see how
/freqagents accelerate your workflow
The Frequency Philosophy
Aesthetics are everything. Visual design, polish, and attention to detail are critical. Every pixel matters, every interaction should feel intentional, and every screen should look like it was designed by someone who cares.
This philosophy extends to our code. Clean architecture, clear boundaries, type-safe pipelines — our engineering standards are a reflection of the same care we put into our product.