1. Proper naming of functions and variables

// avoid repetition in hierarchies and namespacessealed class AuthorizedLogin {    ❌ data object AuthorizedLoginSucceded    ✅ data object Succeded    ❌ data object AuthorizedLoginFailed    ✅ data object Failed    ❌ data object AuthorizedLoginInProgress    ✅ data object InProgress}// so later in the code you get this:return AuthorizedLogin.Succeded // instead of this:return AuthorizedLogin.AuthorizedLoginSucceded// Acronyms and abbreviations can confuse developers,very descriptive names, however, do not.❌ fun getData() { ... }✅ fun getAccountData { ... }❌ fun updAccount(account: Account) { ... }✅ fun updateAccount(account: Account) { ... }❌ fun updateAccount(newAccountName: String) { ... }✅ fun updateAccountName(newAccountName: String) { ... }

2. Order of public and private functions in Classes:

class AccountViewModel : SomeInterface {  init {    sendLogEvent()  }  override fun functionFromInterface() { ... }  fun onAccountClick() {    ...    updateAccount()  }  private fun updateAccount() { ... }  private fun sendLogEvent() { ... }}

3. Wrap chained calls

❌ val anchor = owner?.firstChild!!.siblings(forward = true).dropWhile { it is PsiComment || it is PsiWhiteSpace } ✅ val anchor = owner    ?.firstChild!!    .siblings(forward = true)    .dropWhile { request->        request is PsiComment || request is PsiWhiteSpace     }

4. Named arguments and parameter list wrapping

// named arguments & parameter list wrapingdrawSquare(x = 10,y = 10,width = 100,height = 100,fill = true)

5. Avoid all usage of the implicit argument nameit inside multi-line expressions or multi-line lambdas

6. Read Kotlin and Android conventions

7. Define rules for naming composables

@Composablefun AccountScreen() {    val state by viewModel.state    AccountContent() { ... }}@Composableprivate fun AccountContent() {    Column {Text(text = "AccountName")        Image(src = "AccountPhoto")        AccountDetailsView()    }     }@Composableprivate fun AccountDetailsView() { ... }

8. Last but not least. You do not have to blindly follow these conventions. But as long as you have defined a set of rules/conventions, you should follow them without many deviations.