agentleFS
UfukCetinkaya57UfukCetinkaya57/backend-governance/.claude/skills/brainstorming/SKILL.md

brainstorming

Skill0 starsChanged 5 months agoMITView on GitHub

Yeni feature, mimari karar veya tasarim oncesi kullan. Alternatifleri kesfeder, trade-off analizi yapar, tasarimi netlestirir.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +2 more from Leodorareluctant259
  • +6 more from ryanportfolio

The file

Files
SKILL.md

Brainstorming — Fikirden Tasarima

Temel Kural

TASARIM ONAYLANMADAN KOD YAZILMAZ. ISTISNASI YOK.
"Basit gorunuyor" gecerli degil. Basit projeler, incelenmemis varsayimlarin en cok zarara verdigi yerdir. Tasarim kisa olabilir (birkaç cumle) ama OLMALI.

## Kontrol Listesi

Sirayla tamamla:

**Proje context'ini incele** — dosyalar, yapilar, son degisiklikler
**Aciklayici sorular sor** — seferde TEK soru, amac/kisitlar/basari kriterlerini anla
**2-3 yaklasim oner** — trade-off'larla, kendi onerinle
**Tasarimi sun** — karmasikliga gore olcekle, her bolumden sonra kullaniciya sor
**Onay al** — kullanici tasarimi onaylayana kadar ilerle
## Surec

### Fikri Anlama

Detayli sorulardan once kapsami degerlendir
Cok buyuk bir istekse (birden fazla bagimsiz alt sistem) → once parcala, hangi sirayla yapilacagini belirle
Uygun kapsamli projeler icin seferde TEK soru sor
Mumkunse coktan secmeli sorular tercih et
Odak: amac, kisitlar, basari kriterleri
### Alternatifleri Kesfet

2-3 farkli yaklasim oner
Her birinin artilari/eksileri
Kendi onerin ve gerekce
Onerini onde sun, neden sectigini acikla
### Tasarimi Sun

Ne yapilacagini anladiginda tasarimi sun
Her bolumu karmasikligina gore olcekle (basit = birkaç cumle, karmasik = detayli aciklama)
Her bolumden sonra sor: "Burasi dogru mu?"
Kapsam: mimari, bilesenler, veri akisi, hata yonetimi, test
Bir sey netlesmediyse geri don, sor
### Tasarim Ilkeleri

**Izolasyon:** Her birim tek bir amaca hizmet etsin, iyi tanimlanmis arayuzlerle iletisim kursun
**Anlasilabilirlik:** Birinin ic detaylari okumadan ne yaptigini anlayabilmesi gerekir
**YAGNI acimadan uygula:** Gereksiz ozellikleri tasarimdan cikar
**Mevcut codebase'e uy:** Yeni pattern onerme, mevcut patternleri takip et. Mevcut kodda sorun varsa ve isi etkiliyorsa, hedefli iyilestirme oner. Alakasiz refactoring YASAK.
## Anti-Pattern: "Buna Tasarim Gerekmez"

Her proje bu surecten gecer. Tek fonksiyonluk utility, config degisikligi, basit CRUD — hepsi. Tasarim belgeniz birkaç cumlede olabilir ama YOKSA = incelenmemis varsayimlar = israf.

## Sonuc

Tasarim onaylandiktan sonra:
- ADR gerekiyorsa yaz (mimari kararlar icin)
- Implementasyon adimlarini belirle
- Uygulama baslasin

---

Kaynak: obra/superpowers (uyarlanmis versiyon)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.