@wooojin/forgen 0.1.0

package/starter-pack/solutions/starter-secret-management.md

@@ -0,0 +1,37 @@
+---
+name: starter-secret-management
+version: 1
+status: verified
+confidence: 0.70
+type: pattern
+scope: me
+tags:
+  - security
+  - secret
+  - env
+  - api-key
+  - credential
+  - 보안
+  - 시크릿
+identifiers: []
+evidence:
+  injected: 0
+  reflected: 0
+  negative: 0
+  sessions: 0
+  reExtracted: 0
+created: "2026-04-03"
+updated: "2026-04-03"
+supersedes: null
+extractedBy: manual
+---
+
+## Context
+Hardcoded secrets in source code are the top cause of credential leaks. Once in git history, a secret is compromised — deleting it later doesn't remove it from history.
+
+## Content
+**Never put secrets in source code.** Use env vars as baseline. Validate required vars at startup — fail fast if missing. Commit `.env.example` with placeholder values, gitignore all real `.env` files.
+
+**Escalation**: Local dev uses `.env`. Production uses a secret manager (AWS Secrets Manager, Vault, Doppler) with IAM access.
+
+**If leaked**: (1) Rotate immediately. (2) Audit access logs. (3) Remove from history with `git filter-repo`. (4) Assume compromised from moment of commit.

package/starter-pack/solutions/starter-separation-of-concerns.md

@@ -0,0 +1,36 @@
+---
+name: starter-separation-of-concerns
+version: 1
+status: verified
+confidence: 0.70
+type: pattern
+scope: me
+tags:
+  - architecture
+  - separation
+  - pure
+  - function
+  - 관심사분리
+  - 아키텍처
+identifiers: []
+evidence:
+  injected: 0
+  reflected: 0
+  negative: 0
+  sessions: 0
+  reExtracted: 0
+created: "2026-04-03"
+updated: "2026-04-03"
+supersedes: null
+extractedBy: manual
+---
+
+## Context
+When business logic is entangled with HTTP, database, and logging, testing requires the entire stack and changes to one concern break others.
+
+## Content
+Separate by dependency: **Pure logic** (no I/O, trivially testable) / **I/O adapters** (thin DB/HTTP wrappers) / **Orchestration** (glues pure + I/O with async/await and error handling).
+
+Pure functions take data in, return data out — no mocks needed for testing. Adapters convert external formats to domain types. Orchestration is thin glue that's already tested through its components.
+
+**Test strategy**: Unit test pure logic exhaustively (fast). Integration test adapters. Orchestration needs minimal tests.

package/starter-pack/solutions/starter-tdd-red-green-refactor.md

@@ -0,0 +1,40 @@
+---
+name: starter-tdd-red-green-refactor
+version: 1
+status: verified
+confidence: 0.70
+type: pattern
+scope: me
+tags:
+  - tdd
+  - test
+  - workflow
+  - red-green-refactor
+  - 테스트
+  - 테스트주도개발
+identifiers: []
+evidence:
+  injected: 0
+  reflected: 0
+  negative: 0
+  sessions: 0
+  reExtracted: 0
+created: "2026-04-03"
+updated: "2026-04-03"
+supersedes: null
+extractedBy: manual
+---
+
+## Context
+Writing code first and testing later creates coverage gaps. TDD inverts this: prove the requirement as a failing test before writing production code.
+
+## Content
+**Red**: Write the smallest failing test. **Green**: Write minimum code to pass. **Refactor**: Clean up while tests stay green.
+
+```typescript
+// RED: it('returns 0 for empty cart', () => expect(calculateTotal([])).toBe(0));
+// GREEN: const calculateTotal = (items: CartItem[]) => items.reduce((s,i) => s+i.price*i.qty, 0);
+// REFACTOR: improve naming, extract helpers — re-run tests after each change
+```
+
+Rules: (1) No production code without a failing test. (2) Only enough to fail. (3) Only enough to pass. (4) Refactor only when green.

package/starter-pack/solutions/starter-typescript-strict-types.md

@@ -0,0 +1,39 @@
+---
+name: starter-typescript-strict-types
+version: 1
+status: verified
+confidence: 0.70
+type: pattern
+scope: me
+tags:
+  - typescript
+  - type
+  - strict
+  - any
+  - union
+  - 타입
+  - 타입스크립트
+identifiers: []
+evidence:
+  injected: 0
+  reflected: 0
+  negative: 0
+  sessions: 0
+  reExtracted: 0
+created: "2026-04-03"
+updated: "2026-04-03"
+supersedes: null
+extractedBy: manual
+---
+
+## Context
+Using `any` silences the compiler at the cost of runtime errors. Discriminated unions make complex state type-safe and self-documenting.
+
+## Content
+**Eliminate `any`** — use `unknown` + type guards when type is genuinely unknown.
+
+**Discriminated unions** for mutually exclusive states:
+```typescript
+type State<T> = { status:'idle' } | { status:'loading' } | { status:'ok'; data:T } | { status:'error'; error:Error };
+```
+Compiler enforces `data` only exists on `ok`, `error` only on `error`. Prefer `satisfies` over type assertions — validates shape without widening.