Quickstart
Get your first Figentra project running in minutes
Installation
Install packages and configure your monorepo workspace
Packages
Browse all available packages and their APIs
Standards
Explore coding standards for consistent, maintainable code
Why Figentra?
Building large TypeScript applications across multiple teams introduces friction: conflicting conventions, duplicated utilities, inconsistent error handling, and fragmented testing strategies. Figentra solves this by providing a unified platform where every package, standard, and pattern is designed to work together.Typed Packages
Every package ships with full TypeScript types and contracts — no guessing at API shapes
Shared Standards
File naming, folder structure, linting, and testing conventions enforced across all teams
Operational Runbooks
Deployment, incident response, and security runbooks baked in from day one
How It Works
1
Install the packages you need
Add
@figentra/* packages to your monorepo workspace packages using your preferred package manager.2
Apply the standards
Follow the file naming, folder structure, and linting standards to keep your codebase consistent.
3
Use the architecture patterns
Reference the Architecture Decision Records and monorepo structure guide to make informed design choices.
4
Operate with confidence
Use the runbooks for deployment, incident response, and security when things go wrong.
Explore the Documentation
Architecture Overview
Understand the monorepo structure and key architectural decisions
Core Packages
Start with contracts, health checks, and the DI container
Testing Standards
Learn how Figentra projects structure and run tests
Operations
Review deployment and incident response runbooks