Agent skill
arch-decisions-vuralserhat86-antigravity-agentic-
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/arch-decisions-vuralserhat86-antigravity-agentic-
SKILL.md
📋 Architecture Decisions
ADR, database selection ve capacity planning.
📝 ADR Template
# ADR-001: Database Selection
## Status: Accepted
## Context
[Problem açıklaması]
## Decision
PostgreSQL kullanacağız.
## Consequences
### Positive
- ACID compliance
### Negative
- Horizontal scaling zor
## Alternatives
- MongoDB: Rejected - JOINs için uygun değil
🗄️ Database Selection
| SQL | NoSQL |
|---|---|
| Complex JOINs | Flexible schema |
| ACID | High throughput |
| Transactions | Horizontal scale |
📊 Capacity Planning
DAU: 1M users
Requests: 20/user/day = 20M/day
RPS: 20M / 86400 = ~230 RPS
Peak: 230 × 3 = ~700 RPS
Architecture Decisions v1.0
🔄 Workflow
Kaynak: AWS Architecture Blog
Aşama 1: Problem Identification
- Context: Problemi ve etkilerini net tanımla.
- Constraints: Kısıtlamaları (Bütçe, Zaman, Teknoloji) belirle.
- Options: En az 2 alternatif çözüm yolu belirle.
Aşama 2: Proposal (Status: Proposed)
- Draft: ADR şablonunu doldur.
- RFC: Takımdan yorum iste (Pull Request veya Toplantı).
- Evaluation: Alternatifleri kriterlere göre puanla (Pros/Cons).
Aşama 3: Decision (Status: Accepted/Rejected)
- Consensus: Kararı netleştir ve statüyü güncelle.
- Implications: Kararın uzun vadeli etkilerini (Consequences) yaz.
- Commit: ADR dosyasını repoya ekle.
Kontrol Noktaları
| Aşama | Doğrulama |
|---|---|
| 1 | Problem ve alternatifler net mi? |
| 2 | Takım görüşü alındı mı? |
| 3 | Kararın "Consequences" bölümü dürüstçe yazıldı mı? |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?