writing-client-code

Konvensi kode klien Bitwarden untuk Angular dan TypeScript. Gunakan saat membuat komponen, layanan, atau memodifikasi aplikasi web/browser/desktop.

npx skills add https://github.com/bitwarden/clients --skill writing-client-code

Why libs/common cannot import Angular

CLI is a first-class client. Any code in libs/common must work without Angular's dependency injection, decorators, or lifecycle hooks. This is why cross-client services use abstract classes as interfaces — the concrete implementations (Default*, Web*, Browser*, Desktop*, Cli*) live in their respective apps.

Architectural Rationale

Thin components

Components contain only view logic. Business logic belongs in services. This keeps components testable, reusable, and prevents Angular lifecycle coupling from leaking into domain logic.

Composition over inheritance

Avoid extending components across clients. Compose using shared child components instead. Inheritance creates tight coupling between client-specific UI and shared behavior — when one client's needs diverge, inherited components become hard to change safely.

Don't modernize existing code unless asked

The codebase contains both legacy and modern Angular patterns. When modifying an existing file, follow the patterns already in that file. Don't migrate any of these unless explicitly asked:

  • *ngIf → @if, *ngFor → @for
  • @Input() / @Output() → input() / output() signals
  • Constructor injection → inject()
  • Default change detection → OnPush
  • NgModule declarations → standalone components

If asked to modernize, follow this order (per the Angular migration guide): standalone → control flow → input/output signals → view queries → signals → computed → OnPush (last, only after full signal migration).

State management: Signals vs RxJS

  • Component local state and Angular-only services: Use Signals
  • Cross-client services (libs/common): Use RxJS (because CLI has no Angular Signals support)

Avoid manual subscriptions. Prefer | async pipe. When subscriptions are necessary, pipe through takeUntilDestroyed() — enforced by the prefer-takeUntil lint rule.

No TypeScript enums (ADR-0025)

Use frozen const objects with Object.freeze() and as const, plus a companion type alias. Enums have runtime behavior that creates subtle bugs with tree-shaking.

Critical Rules for New Code

These rules apply strictly to new files and components. For existing code, follow the patterns already in the file.

  • New components must use ChangeDetectionStrategy.OnPush and be standalone: true. NgModules are permitted only for grouping related standalone components
  • Prefer inject() function for DI in Angular primitives (components, pipes, directives). Use constructor injection for code shared with non-Angular clients (CLI)
  • New templates must use control flow syntax (@if, @for, @switch), not structural directives
  • Use host property in component decorators, not @HostBinding / @HostListener
  • Use Reactive Forms exclusively — not template-driven forms
  • File naming: kebab-case.component.ts, .service.ts, .pipe.ts, .directive.ts. Also: .request.ts, .response.ts, .view.ts, .data.ts for models (ADR-0012)
  • All Tailwind classes require tw- prefix — tw-flex, tw-mt-2, not flex, mt-2
  • Testing with Jest — use jest-mock-extended for mocking services. describe/it blocks, not test()
  • Imports from @bitwarden/common must not pull in Angular-specific code (breaks CLI)

Examples

Dependency injection (new Angular code)

// CORRECT — inject() for Angular primitives
export class VaultComponent {
  private vaultService = inject(VaultService);
}

// ALSO CORRECT — constructor injection for code shared with CLI
export class CryptoService {
  constructor(private stateService: StateService) {}
}

Tailwind prefix

<!-- CORRECT -->
<div class="tw-flex tw-gap-2 tw-mt-4">
  <!-- WRONG — missing tw- prefix, will be stripped -->
  <div class="flex gap-2 mt-4"></div>
</div>

Const objects over enums (ADR-0025)

// CORRECT — with companion type alias
export const CipherType = Object.freeze({
  Login: 1,
  SecureNote: 2,
} as const);
export type CipherType = (typeof CipherType)[keyof typeof CipherType];

// WRONG — TypeScript enums have runtime side effects
export enum CipherType {
  Login = 1,
  SecureNote = 2,
}

Further Reading

Lebih banyak skill dari bitwarden

figma-to-angular
bitwarden
Skill ini mengubah spesifikasi desain Figma menjadi komponen Angular yang sudah diimplementasikan sepenuhnya dengan cerita Storybook di dalam monorepo Bitwarden Clients. Outputnya harus sesuai secara visual dengan desain sambil mengikuti semua konvensi basis kode.
force-multiplier
bitwarden
Terapkan satu maksud ke banyak target sekaligus — sekumpulan repositori di seluruh ekosistem Bitwarden, atau banyak proyek di dalam monorepo — sebagai N yang konsisten,…
analyzing-git-sessions
bitwarden
Menganalisis komit git dan perubahan dalam rentang waktu atau rentang komit, memberikan ringkasan terstruktur untuk tinjauan kode, retrospektif, catatan kerja, atau sesi…
coordinating-cross-team-breakdown
bitwarden
Mengkoordinasikan tinjauan dan persetujuan lintas tim untuk Bitwarden Tech Breakdown. Gunakan saat mengidentifikasi tim yang terdampak, membangun tabel persetujuan Bagian 3, menindaklanjuti…
assessing-jira-issue-relevance
bitwarden
Gunakan ketika pengguna memberikan satu kunci masalah Jira dan bertanya apakah masalah tersebut masih relevan, masih berlaku, masih tertunda, masih merupakan bug, telah diperbaiki, atau dapat…
assessing-test-coverage
bitwarden
Gunakan saat menentukan cakupan pengujian yang SUDAH ada untuk perubahan tertentu (PR, kunci Jira, dokumen Tech Breakdown, CSV Testmo, jalur yang diubah, atau yang disebut…
retrospecting
bitwarden
Melakukan analisis komprehensif terhadap sesi Claude Code, memeriksa riwayat git, log percakapan, perubahan kode, dan mengumpulkan umpan balik pengguna untuk menghasilkan…
reviewing-incremental-changes
bitwarden
Gunakan keterampilan ini saat meninjau ulang PR yang sudah memiliki komentar atau saat menanggapi perubahan pengembang setelah tinjauan awal. Terapkan saat utas PR ada atau…