Yavaren™ user guideVersion 1.0.0Printable guide · PDF

Stack conventions

Stack conventions

The languages and frameworks Yavaren works in, and the conventions each one follows.

Each repository in a project has a stack. For every stack, the engineer follows a stack profile: principles, naming and structure conventions, patterns to use and to avoid, a review checklist, and the quality checks it runs when your repository has them. Your repository's own conventions and tool configuration always come first.

Stack Used for Conventions
Android (Kotlin, Jetpack, Compose) android Read
Angular angular Read
Bicep (Azure) added by file type Read
C (CMake) c-cmake Read
C++ (CMake) cpp-cmake Read
Databricks (PySpark, Delta Lake, Asset Bundles) databricks Read
dbt Core dbt Read
Django django Read
.NET (C# / ASP.NET Core) dotnet Read
Elixir (and Phoenix) elixir Read
Embedded firmware (C/C++, PlatformIO) embedded Read
Flutter (Dart) flutter Read
Go go Read
Java (Maven / Gradle) java-maven, java-gradle Read
Kotlin kotlin Read
Laravel laravel Read
Next.js (App Router) nextjs Read
Node.js (server-side JavaScript) node Read
PHP php Read
Playwright end-to-end tests (TypeScript) playwright Read
Playwright end-to-end tests (.NET, NUnit) playwright-dotnet Read
Python python Read
Ruby on Rails rails Read
React react Read
ROS 2 (robotics) ros2 Read
Ruby ruby Read
Rust rust Read
Salesforce (Apex, LWC, metadata) salesforce, salesforce-prod Read
Scala scala Read
Snowflake (SQL, Snowpark, schemachange) snowflake Read
SQL databases (migrations, procedures, views) sql Read
Swift swift Read
Terraform and OpenTofu added by file type Read
TypeScript typescript Read
Vue 3 vue Read