القائمة
Guidance and best practices for architectural decision records (adr).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Accessibility testing for web applications using Playwright (@playwright/test) with TypeScript and axe-core. Use when asked to write, run, or debug automated accessibility checks, keyboard navigation tests, focus management, ARIA/semantic validations, screen reader compatibility, or WCAG 2.1 Level AA compliance testing. Covers axe-core integration, POUR principles (perceivable, operable, understandable, robust), color contrast, form labels, landmarks, and accessible names.
To ensure the application is usable by people with disabilities, complying with WCAG standards and improving SEO/UX. Use when: During development of UI components; Before major releases.
Accessibility testing toolkit using Selenium WebDriver 4+ with Java 21+ and axe-core engine. Use when asked to validate WCAG 2.1/2.2 compliance, scan pages or components for a11y violations, test keyboard navigation, audit color contrast, check ARIA semantics, generate accessibility reports, filter axe rules, debug screen reader issues, or implement POUR principles (perceivable, operable, understandable, robust).
To allow incompatible interfaces to work together by wrapping an object in an adapter that translates its interface into one that a client expects. Use when: When integrating a third-party library whose interface doesn't match your application's internal requirements; When you want to standardize multiple different implementations of a service (e.g., different payment gateways); When you need to provide a stable interface while the underlying dependency is subject to change.
To implement a scalable permission system where users have roles, and roles have granular permissions. Use when: B2B SaaS applications (Admin, Editor, Viewer); Systems with complex access requirements.
Browser automation CLI for AI agents. Use for website interaction, form automation, screenshots, scraping, and web app verification. Prefer snapshot refs (@e1, @e2) for deterministic actions.
| name | architectural-decision-records-adr |
| description | Guidance and best practices for architectural decision records (adr). |
Use ADRs for decisions that are:
Store records in /docs/adr/ using a sequential naming convention: XXXX-title.md.
# ADR 0005: Use PostgreSQL instead of MongoDB
**Date**: 2024-02-09
**Status**: Accepted
**Deciders**: @team-leads
## Context
Our application requires complex relational queries and ACID compliance for financial transactions. While MongoDB is easier to scale horizontally, the current data model is highly relational.
## Decision
We will use PostgreSQL as our primary database.
## Consequences
- **Positive**: Native support for relational joins, strong consistency, and JSONB for semi-structured data.
- **Negative**: Requires schema migrations; horizontal scaling is more complex than MongoDB.
Treat ADRs like code. Submit a PR, discuss the decision, and once accepted, merge it into the main branch.
Superseded.A chronological history of the project's architecture that allows new team members to understand why certain choices were made.