Fullstack Engineering Standards
Documentation
The reference both frontend and backend teams in Product Engineer team are held to. Written to remove ambiguity, not just document tradeoffs: every section ends with a rule you can act on. Written and maintained by Real Human on the Product Engineering team.
What this document is not
This is not a Next.js-specific guide, and it does not cover deployment or CI/CD, which a separate department owns. Outside of Section 2, it is written at the level of principles and decision criteria, so it keeps working if the stack changes. See the introduction for the full scope.
New here? Start with these
Purpose, scope, and how to propose a change to this standard.
1. IntroductionSelection criteria, the current approved stack, and the polyglot policy.
2. Technology Selection & Current StackMonorepo vs multi-repo criteria and structure by layer responsibility.
3. Repository & Project StructurePR checklist, linting principles, and the commit and branching convention.
4. Code Quality & CollaborationFrontend path
Backend path
Service boundaries, persistence standards, and data modeling.
6. Backend & Data ArchitectureWhen to use internal RPC, REST, GraphQL, and event-driven messaging.
7. System Architecture & Service CommunicationDesign for failure, SOLID, design patterns, YAGNI, and feature flagging.
8. Engineering Principles & Design PatternsEveryone’s responsibility
Consistent error shapes, UI error states, retries, and background jobs.
10. Error Handling & ResilienceEnv var rules, auth, input validation, secrets, and middleware standards.
11. SecurityAsset optimization, bundle budgets, code splitting, and query performance.
12. Performance GuidelinesTest scope by layer, mocking convention, smoke tests, and coverage.
13. Testing StrategyReference
Too lazy to read?
We. got. your. back! We at product engineering team are believe in work-life balance and mental health and wellness.
Pass the page URL when you ask. Example:
Read https://swe.ardhiraka.com/swe/2-technology-selection
and walk me through setting up the current stack for a new project.Copy Page sits next to the table of contents on every docs page. The main button copies markdown to your clipboard; the menu opens the same page in Claude or ChatGPT with one click.
This standard is agent-readable, not just human-readable. Every section
lives at /swe/{slug}.md and is indexed in /swe/llms.txt, so a coding
agent can read the current rules instead of guessing from training data.
Want the agent to enforce standards on its own? Install the Agent Plugin: skills that review PRs, diffs, and design calls against these rules using live content from this site. Install docs live here; the plugin source is in a private org repo.