jell-utils 0.1.0 → 0.2.0

package/.taskmaster/tasks/tasks.json

@@ -0,0 +1,304 @@
+{
+  "master": {
+    "tasks": [
+      {
+        "id": "16",
+        "title": "Implement formatDateAdvanced function with token support",
+        "description": "Create formatDateAdvanced function that supports multiple date format tokens (YYYY, MM, DD, HH, mm, ss, ddd, dddd) for flexible date formatting",
+        "details": "Implementation details:\n- Create src/date/formatDateAdvanced.ts file\n- Support tokens: YYYY (4-digit year), MM (2-digit month), DD (2-digit day), HH (2-digit hour), mm (2-digit minute), ss (2-digit second), ddd (short weekday), dddd (full weekday)\n- Korean weekday mappings: ['일요일', '월요일', '화요일', '수요일', '목요일', '금요일', '토요일']\n- Short weekday: first character of full weekday (e.g., '월' from '월요일')\n- Use string replacement for each token\n- Pad numbers with leading zeros using String.padStart(2, '0')\n- Export function from src/date/index.ts and main src/index.ts\n\nPseudo-code:\n```typescript\nfunction formatDateAdvanced(date: Date | string, format: string): string {\n  const d = new Date(date)\n  const weekdays = ['일요일', '월요일', '화요일', '수요일', '목요일', '금요일', '토요일']\n  \n  const replacements = {\n    YYYY: d.getFullYear().toString(),\n    MM: (d.getMonth() + 1).toString().padStart(2, '0'),\n    DD: d.getDate().toString().padStart(2, '0'),\n    HH: d.getHours().toString().padStart(2, '0'),\n    mm: d.getMinutes().toString().padStart(2, '0'),\n    ss: d.getSeconds().toString().padStart(2, '0'),\n    dddd: weekdays[d.getDay()],\n    ddd: weekdays[d.getDay()].charAt(0)\n  }\n  \n  let result = format\n  for (const [token, value] of Object.entries(replacements)) {\n    result = result.replace(new RegExp(token, 'g'), value)\n  }\n  return result\n}\n```",
+        "testStrategy": "Tests already exist in __tests__/date.test.ts (lines 56-82). Verify:\n- YYYY-MM-DD format outputs correct date\n- Korean format (YYYY년 MM월 DD일) works\n- Time tokens (HH:mm:ss) work correctly\n- Weekday tokens (ddd, dddd) output Korean weekdays\n- Combined formats work properly\nRun: npm test -- date.test.ts",
+        "priority": "high",
+        "dependencies": [],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.194Z"
+      },
+      {
+        "id": "17",
+        "title": "Implement timeAgo function for relative time display",
+        "description": "Create timeAgo function that returns Korean relative time strings (방금 전, X분 전, X시간 전, 어제, X일 전, X주 전, X개월 전, X년 전)",
+        "details": "Implementation details:\n- Create src/date/timeAgo.ts file\n- Calculate time difference in milliseconds between input date and current time\n- Apply Korean relative time logic:\n  - < 1 minute: '방금 전'\n  - < 1 hour: 'X분 전'\n  - < 24 hours: 'X시간 전'\n  - < 48 hours: '어제'\n  - < 7 days: 'X일 전'\n  - < 30 days: 'X주 전'\n  - < 12 months: 'X개월 전'\n  - >= 12 months: 'X년 전'\n- Use Math.floor for calculating time units\n- Export from src/date/index.ts and main src/index.ts\n\nPseudo-code:\n```typescript\nfunction timeAgo(date: Date | string): string {\n  const now = Date.now()\n  const past = new Date(date).getTime()\n  const diff = now - past\n  \n  const minute = 60 * 1000\n  const hour = 60 * minute\n  const day = 24 * hour\n  const week = 7 * day\n  const month = 30 * day\n  const year = 365 * day\n  \n  if (diff < minute) return '방금 전'\n  if (diff < hour) return `${Math.floor(diff / minute)}분 전`\n  if (diff < day) return `${Math.floor(diff / hour)}시간 전`\n  if (diff < 2 * day) return '어제'\n  if (diff < week) return `${Math.floor(diff / day)}일 전`\n  if (diff < month) return `${Math.floor(diff / week)}주 전`\n  if (diff < year) return `${Math.floor(diff / month)}개월 전`\n  return `${Math.floor(diff / year)}년 전`\n}\n```",
+        "testStrategy": "Tests already exist in __tests__/date.test.ts (lines 84-124). Verify:\n- < 1 minute returns '방금 전'\n- Minutes, hours, days calculated correctly\n- '어제' for 24-48 hours\n- Weeks, months, years work correctly\nRun: npm test -- date.test.ts",
+        "priority": "high",
+        "dependencies": [],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.195Z"
+      },
+      {
+        "id": "18",
+        "title": "Implement getDaysInMonth function",
+        "description": "Create getDaysInMonth function that returns the number of days in a given month, accounting for leap years",
+        "details": "Implementation details:\n- Create src/date/getDaysInMonth.ts file\n- Accept year and month parameters (month 1-12)\n- Use Date object trick: create date for month+1 day 0, which gives last day of current month\n- Alternative: use array [31,28/29,31,30,31,30,31,31,30,31,30,31] with leap year check\n- Export from src/date/index.ts and main src/index.ts\n\nPseudo-code:\n```typescript\nfunction getDaysInMonth(year: number, month: number): number {\n  // Create date for next month's day 0 (last day of current month)\n  return new Date(year, month, 0).getDate()\n}\n```",
+        "testStrategy": "Tests already exist in __tests__/date.test.ts (lines 126-142). Verify:\n- February returns 28 in non-leap years (2025)\n- February returns 29 in leap years (2024)\n- December returns 31\n- April returns 30\nRun: npm test -- date.test.ts",
+        "priority": "medium",
+        "dependencies": [],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.197Z"
+      },
+      {
+        "id": "19",
+        "title": "Implement isLeapYear function",
+        "description": "Create isLeapYear function that determines if a given year is a leap year using standard leap year rules",
+        "details": "Implementation details:\n- Create src/date/isLeapYear.ts file\n- Apply leap year rules:\n  1. Divisible by 4: leap year candidate\n  2. Divisible by 100: NOT leap year (exception)\n  3. Divisible by 400: IS leap year (exception to exception)\n- Formula: (year % 4 === 0 && year % 100 !== 0) || (year % 400 === 0)\n- Export from src/date/index.ts and main src/index.ts\n\nPseudo-code:\n```typescript\nfunction isLeapYear(year: number): boolean {\n  return (year % 4 === 0 && year % 100 !== 0) || (year % 400 === 0)\n}\n```",
+        "testStrategy": "Tests already exist in __tests__/date.test.ts (lines 144-160). Verify:\n- 2024 (divisible by 4) returns true\n- 2025 (not divisible by 4) returns false\n- 2000 (divisible by 400) returns true\n- 1900 (divisible by 100 but not 400) returns false\nRun: npm test -- date.test.ts",
+        "priority": "medium",
+        "dependencies": [],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.198Z"
+      },
+      {
+        "id": "20",
+        "title": "Implement formatNumber function with thousand separators",
+        "description": "Create formatNumber function that formats numbers with thousand separators (commas)",
+        "details": "Implementation details:\n- Create src/number/formatNumber.ts file\n- Use Number.prototype.toLocaleString('en-US') for automatic thousand separators\n- Handle negative numbers correctly\n- Preserve decimal places if present\n- Export from src/number/index.ts and main src/index.ts\n\nPseudo-code:\n```typescript\nfunction formatNumber(num: number): string {\n  return num.toLocaleString('en-US')\n}\n```",
+        "testStrategy": "Tests already exist in __tests__/number.test.ts (lines 38-55). Verify:\n- 1000 returns '1,000'\n- 1234567 returns '1,234,567'\n- 1234.56 returns '1,234.56'\n- 0 returns '0'\n- Negative numbers formatted correctly\nRun: npm test -- number.test.ts",
+        "priority": "high",
+        "dependencies": [],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.199Z"
+      },
+      {
+        "id": "21",
+        "title": "Implement formatCurrency function with multi-currency support",
+        "description": "Create formatCurrency function that formats numbers as currency with support for KRW, USD, EUR, JPY, CNY",
+        "details": "Implementation details:\n- Create src/number/formatCurrency.ts file\n- Default currency: KRW (원)\n- Currency symbols: KRW='원' (suffix), USD='$' (prefix), EUR='€' (prefix), JPY='¥' (prefix), CNY='¥' (prefix)\n- Use formatNumber internally for thousand separators\n- Position symbol based on currency (prefix or suffix)\n- Export from src/number/index.ts and main src/index.ts\n\nPseudo-code:\n```typescript\ntype CurrencyCode = 'KRW' | 'USD' | 'EUR' | 'JPY' | 'CNY'\n\nfunction formatCurrency(amount: number, currency: CurrencyCode = 'KRW'): string {\n  const formatted = formatNumber(amount)\n  \n  const symbols = {\n    KRW: { symbol: '원', prefix: false },\n    USD: { symbol: '$', prefix: true },\n    EUR: { symbol: '€', prefix: true },\n    JPY: { symbol: '¥', prefix: true },\n    CNY: { symbol: '¥', prefix: true }\n  }\n  \n  const { symbol, prefix } = symbols[currency]\n  return prefix ? `${symbol}${formatted}` : `${formatted}${symbol}`\n}\n```",
+        "testStrategy": "Tests already exist in __tests__/number.test.ts (lines 57-74). Verify:\n- Default (KRW): 1000 returns '1,000원'\n- USD: 1000 returns '$1,000'\n- EUR: 1000 returns '€1,000'\n- JPY: 1000 returns '¥1,000'\nRun: npm test -- number.test.ts",
+        "priority": "high",
+        "dependencies": [
+          "20"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.200Z"
+      },
+      {
+        "id": "22",
+        "title": "Implement formatFileSize function",
+        "description": "Create formatFileSize function that converts bytes to human-readable file sizes (B, KB, MB, GB, TB) with optional precision",
+        "details": "Implementation details:\n- Create src/number/formatFileSize.ts file\n- Units: B (bytes), KB (1024 bytes), MB (1024 KB), GB (1024 MB), TB (1024 GB)\n- Default precision: 0 for B/KB, 2 for MB/GB/TB\n- Allow custom precision parameter\n- Use 1024 as base (binary, not decimal)\n- Export from src/number/index.ts and main src/index.ts\n\nPseudo-code:\n```typescript\nfunction formatFileSize(bytes: number, precision?: number): string {\n  const units = ['B', 'KB', 'MB', 'GB', 'TB']\n  let size = bytes\n  let unitIndex = 0\n  \n  while (size >= 1024 && unitIndex < units.length - 1) {\n    size /= 1024\n    unitIndex++\n  }\n  \n  const decimals = precision !== undefined ? precision : (unitIndex === 0 ? 0 : 2)\n  return `${size.toFixed(decimals)} ${units[unitIndex]}`\n}\n```",
+        "testStrategy": "Tests already exist in __tests__/number.test.ts (lines 76-96). Verify:\n- 500 returns '500 B'\n- 1024 returns '1 KB'\n- 1048576 returns '1 MB'\n- 1073741824 returns '1 GB'\n- Custom precision: 1536 with precision 2 returns '1.50 KB'\nRun: npm test -- number.test.ts",
+        "priority": "medium",
+        "dependencies": [],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.201Z"
+      },
+      {
+        "id": "23",
+        "title": "Implement numberToKorean function",
+        "description": "Create numberToKorean function that converts Arabic numerals to Korean number words (일, 이, 삼, ...)",
+        "details": "Implementation details:\n- Create src/number/numberToKorean.ts file\n- Digit names: ['영', '일', '이', '삼', '사', '오', '육', '칠', '팔', '구']\n- Unit names: ['', '십', '백', '천', '만', '억', '조']\n- Process number in groups of 4 digits (만 단위)\n- Handle special case: 0 returns '영'\n- Omit '일' before 십, 백, 천 in standard Korean\n- Export from src/number/index.ts and main src/index.ts\n\nPseudo-code:\n```typescript\nfunction numberToKorean(num: number): string {\n  if (num === 0) return '영'\n  \n  const digits = ['', '일', '이', '삼', '사', '오', '육', '칠', '팔', '구']\n  const units = ['', '십', '백', '천']\n  const bigUnits = ['', '만', '억', '조']\n  \n  const processGroup = (n: number): string => {\n    let result = ''\n    let temp = n\n    \n    for (let i = 3; i >= 0; i--) {\n      const digit = Math.floor(temp / Math.pow(10, i))\n      temp %= Math.pow(10, i)\n      \n      if (digit > 0) {\n        if (digit > 1 || i === 0) result += digits[digit]\n        result += units[i]\n      }\n    }\n    return result\n  }\n  \n  let result = ''\n  let groupIndex = 0\n  let remaining = num\n  \n  while (remaining > 0) {\n    const group = remaining % 10000\n    if (group > 0) {\n      const groupStr = processGroup(group)\n      result = groupStr + bigUnits[groupIndex] + result\n    }\n    remaining = Math.floor(remaining / 10000)\n    groupIndex++\n  }\n  \n  return result\n}\n```",
+        "testStrategy": "Tests already exist in __tests__/number.test.ts (lines 98-132). Verify:\n- Single digits: 1 returns '일', 5 returns '오'\n- Tens: 10 returns '십', 15 returns '십오'\n- Hundreds: 100 returns '백', 123 returns '백이십삼'\n- Thousands: 1000 returns '천', 1234 returns '천이백삼십사'\n- Ten thousands: 10000 returns '만', 12345 returns '만이천삼백사십오'\n- Hundred million: 100000000 returns '일억'\n- Zero: 0 returns '영'\nRun: npm test -- number.test.ts",
+        "priority": "medium",
+        "dependencies": [],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.201Z"
+      },
+      {
+        "id": "24",
+        "title": "Implement parseNumberFromString function",
+        "description": "Create parseNumberFromString function that extracts numeric value from formatted strings (with commas, currency symbols, etc.)",
+        "details": "Implementation details:\n- Create src/number/parseNumberFromString.ts file\n- Remove all non-numeric characters except decimal point and minus sign\n- Handle currency symbols ($, €, ¥, 원), thousand separators (,), etc.\n- Use parseFloat to convert cleaned string to number\n- Return NaN if no valid number found\n- Export from src/number/index.ts and main src/index.ts\n\nPseudo-code:\n```typescript\nfunction parseNumberFromString(str: string): number {\n  // Remove everything except digits, decimal point, and minus\n  const cleaned = str.replace(/[^0-9.-]/g, '')\n  return parseFloat(cleaned)\n}\n```",
+        "testStrategy": "Tests already exist in __tests__/number.test.ts (lines 134-148). Verify:\n- '1,234' returns 1234\n- '1,234.56' returns 1234.56\n- '$1,000' returns 1000\n- '1,000원' returns 1000\n- Plain numbers work: '12345' returns 12345\nRun: npm test -- number.test.ts",
+        "priority": "medium",
+        "dependencies": [],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.202Z"
+      },
+      {
+        "id": "25",
+        "title": "Create validation utilities module structure",
+        "description": "Set up validation utilities module with proper TypeScript structure and exports",
+        "details": "Implementation details:\n- Create src/validation/ directory\n- Create src/validation/index.ts as module entry point\n- Export all validation functions from index.ts\n- Update main src/index.ts to export validation utilities\n- Follow existing module pattern from date/, number/ modules\n\nFile structure:\n```\nsrc/validation/\n├── index.ts (exports)\n├── isEmail.ts\n├── isPhoneNumber.ts\n├── isUrl.ts\n├── formatPhoneNumber.ts\n└── formatBusinessNumber.ts\n```",
+        "testStrategy": "Verification:\n- Directory structure created correctly\n- Module exports configured\n- TypeScript compilation succeeds\n- No import errors in main index.ts\nRun: npm run build",
+        "priority": "high",
+        "dependencies": [],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.202Z"
+      },
+      {
+        "id": "26",
+        "title": "Implement isEmail validation function",
+        "description": "Create isEmail function to validate email addresses using RFC 5322 compliant regex pattern",
+        "details": "Implementation details:\n- Create src/validation/isEmail.ts file\n- Use comprehensive email regex pattern\n- Pattern should match: local-part@domain with proper character restrictions\n- Handle edge cases: dots, hyphens, special characters\n- Use regex test method for validation\n- Export from src/validation/index.ts\n\nRecommended regex (RFC 5322 simplified):\n```typescript\nfunction isEmail(email: string): boolean {\n  const emailRegex = /^[a-zA-Z0-9.!#$%&'*+\\/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$/\n  return emailRegex.test(email)\n}\n```",
+        "testStrategy": "Create __tests__/validation/isEmail.test.ts:\n- Valid emails: 'test@example.com', 'user.name@domain.co.kr', 'name+tag@mail.com'\n- Invalid emails: 'invalid-email', 'test@', '@example.com', 'test@test'\n- Edge cases: empty string, no @ symbol, multiple @ symbols\nTarget coverage: 100%\nRun: npm test -- validation/isEmail.test.ts",
+        "priority": "high",
+        "dependencies": [
+          "25"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.203Z"
+      },
+      {
+        "id": "27",
+        "title": "Implement isPhoneNumber validation function",
+        "description": "Create isPhoneNumber function to validate Korean phone numbers (mobile and landline)",
+        "details": "Implementation details:\n- Create src/validation/isPhoneNumber.ts file\n- Support mobile numbers: 010, 011, 016, 017, 018, 019\n- Support landline: area codes 02, 031-044, 051-055, 061-064\n- Accept formats: with/without hyphens\n- Mobile pattern: 01[016789]-?\\d{3,4}-?\\d{4}\n- Landline pattern: 0[2-6][1-5]?-?\\d{3,4}-?\\d{4}\n- Export from src/validation/index.ts\n\nPseudo-code:\n```typescript\nfunction isPhoneNumber(phone: string): boolean {\n  const mobileRegex = /^01[016789]-?\\d{3,4}-?\\d{4}$/\n  const landlineRegex = /^0[2-6][1-5]?-?\\d{3,4}-?\\d{4}$/\n  \n  return mobileRegex.test(phone) || landlineRegex.test(phone)\n}\n```",
+        "testStrategy": "Create __tests__/validation/isPhoneNumber.test.ts:\n- Valid mobile: '010-1234-5678', '01012345678', '011-123-4567'\n- Valid landline: '02-123-4567', '031-1234-5678'\n- Invalid: '1234-5678', '020-1234-5678', '010-12-34'\n- Edge cases: too short, too long, wrong prefixes\nTarget coverage: 100%\nRun: npm test -- validation/isPhoneNumber.test.ts",
+        "priority": "high",
+        "dependencies": [
+          "25"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.204Z"
+      },
+      {
+        "id": "28",
+        "title": "Implement isUrl validation function",
+        "description": "Create isUrl function to validate URLs with support for http, https, ftp protocols",
+        "details": "Implementation details:\n- Create src/validation/isUrl.ts file\n- Support protocols: http, https, ftp\n- Validate domain structure\n- Allow localhost and IP addresses\n- Allow port numbers and paths\n- Use URL constructor for validation (try-catch approach)\n- Export from src/validation/index.ts\n\nPseudo-code:\n```typescript\nfunction isUrl(url: string): boolean {\n  try {\n    const parsed = new URL(url)\n    return ['http:', 'https:', 'ftp:'].includes(parsed.protocol)\n  } catch {\n    return false\n  }\n}\n```",
+        "testStrategy": "Create __tests__/validation/isUrl.test.ts:\n- Valid URLs: 'https://example.com', 'http://localhost:3000', 'ftp://files.example.com'\n- Valid with paths: 'https://example.com/path/to/page'\n- Invalid: 'not-a-url', 'htp://wrong.com', 'example.com' (no protocol)\n- Edge cases: empty string, malformed URLs\nTarget coverage: 100%\nRun: npm test -- validation/isUrl.test.ts",
+        "priority": "medium",
+        "dependencies": [
+          "25"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.204Z"
+      },
+      {
+        "id": "29",
+        "title": "Implement formatPhoneNumber function",
+        "description": "Create formatPhoneNumber function to format Korean phone numbers with proper hyphen placement",
+        "details": "Implementation details:\n- Create src/validation/formatPhoneNumber.ts file\n- Remove all non-digit characters first\n- Detect number type: mobile (starts with 01) or landline (starts with 02-064)\n- Mobile format: 010-1234-5678 or 011-123-4567 (3-4-4 or 3-3-4)\n- Landline formats: 02-1234-5678 (2-4-4), 031-1234-5678 (3-4-4)\n- Return original if invalid length\n- Export from src/validation/index.ts\n\nPseudo-code:\n```typescript\nfunction formatPhoneNumber(phone: string): string {\n  const digits = phone.replace(/[^0-9]/g, '')\n  \n  if (digits.startsWith('02')) {\n    // Seoul: 02-XXXX-XXXX\n    if (digits.length === 10) {\n      return `${digits.slice(0, 2)}-${digits.slice(2, 6)}-${digits.slice(6)}`\n    }\n  } else if (digits.startsWith('01')) {\n    // Mobile: 01X-XXXX-XXXX or 01X-XXX-XXXX\n    if (digits.length === 11) {\n      return `${digits.slice(0, 3)}-${digits.slice(3, 7)}-${digits.slice(7)}`\n    } else if (digits.length === 10) {\n      return `${digits.slice(0, 3)}-${digits.slice(3, 6)}-${digits.slice(6)}`\n    }\n  } else if (/^0[3-6]/.test(digits)) {\n    // Area code: 0XX-XXXX-XXXX\n    if (digits.length === 11) {\n      return `${digits.slice(0, 3)}-${digits.slice(3, 7)}-${digits.slice(7)}`\n    } else if (digits.length === 10) {\n      return `${digits.slice(0, 3)}-${digits.slice(3, 6)}-${digits.slice(6)}`\n    }\n  }\n  \n  return phone // Return original if format not recognized\n}\n```",
+        "testStrategy": "Create __tests__/validation/formatPhoneNumber.test.ts:\n- Mobile: '01012345678' returns '010-1234-5678'\n- Seoul: '0212345678' returns '02-1234-5678'\n- Area code: '03112345678' returns '031-1234-5678'\n- Already formatted: '010-1234-5678' returns '010-1234-5678'\n- Invalid lengths handled gracefully\nTarget coverage: 100%\nRun: npm test -- validation/formatPhoneNumber.test.ts",
+        "priority": "medium",
+        "dependencies": [
+          "25"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.205Z"
+      },
+      {
+        "id": "30",
+        "title": "Implement formatBusinessNumber function",
+        "description": "Create formatBusinessNumber function to format Korean business registration numbers (사업자등록번호) in XXX-XX-XXXXX format",
+        "details": "Implementation details:\n- Create src/validation/formatBusinessNumber.ts file\n- Remove all non-digit characters\n- Validate length is exactly 10 digits\n- Format as XXX-XX-XXXXX\n- Return original string if invalid\n- Note: isBusinessNumber already exists in main util, consider using it for validation\n- Export from src/validation/index.ts\n\nPseudo-code:\n```typescript\nfunction formatBusinessNumber(brn: string): string {\n  const digits = brn.replace(/[^0-9]/g, '')\n  \n  if (digits.length !== 10) {\n    return brn // Return original if invalid length\n  }\n  \n  return `${digits.slice(0, 3)}-${digits.slice(3, 5)}-${digits.slice(5)}`\n}\n```",
+        "testStrategy": "Create __tests__/validation/formatBusinessNumber.test.ts:\n- '1234567890' returns '123-45-67890'\n- '123-45-67890' returns '123-45-67890' (already formatted)\n- Invalid lengths: '12345' returns '12345' (unchanged)\n- Non-digit characters removed before formatting\nTarget coverage: 100%\nRun: npm test -- validation/formatBusinessNumber.test.ts",
+        "priority": "low",
+        "dependencies": [
+          "25"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:23:03.205Z"
+      },
+      {
+        "id": "31",
+        "title": "Update package.json version to 0.2.0",
+        "description": "Update package version from 0.1.0 to 0.2.0 and add new keywords for improved npm discoverability",
+        "details": "Implementation details:\n- Update version field from \"0.1.0\" to \"0.2.0\"\n- Add new keywords to keywords array:\n  - \"date-utils\"\n  - \"number-formatting\"\n  - \"validation\"\n  - \"korean-utils\"\n  - \"file-size\"\n  - \"currency-formatting\"\n- Ensure description is clear and concise\n- No other package.json changes needed at this point",
+        "testStrategy": "Verification:\n- package.json version shows 0.2.0\n- Keywords array includes new entries\n- npm run build succeeds\n- All tests pass before publishing\nRun: npm test && npm run build",
+        "priority": "low",
+        "dependencies": [
+          "16",
+          "17",
+          "18",
+          "19",
+          "20",
+          "21",
+          "22",
+          "23",
+          "24",
+          "26",
+          "27",
+          "28",
+          "29",
+          "30"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:24:49.336Z"
+      },
+      {
+        "id": "32",
+        "title": "Create comprehensive README documentation for v0.2.0",
+        "description": "Update README.md with complete documentation for all new date, number, and validation utilities with Korean and English examples",
+        "details": "Implementation details:\n- Add \"📅 날짜/시간 유틸리티\" section with formatDateAdvanced, timeAgo, getDaysInMonth, isLeapYear\n- Add \"💰 숫자 포맷 유틸리티\" section with formatNumber, formatCurrency, formatFileSize, numberToKorean, parseNumberFromString\n- Add \"✅ 검증 유틸리티\" section with isEmail, isPhoneNumber, isUrl, formatPhoneNumber, formatBusinessNumber\n- Include code examples for each function\n- Update table of contents\n- Add usage examples showing real-world scenarios\n- Update installation instructions if needed\n- Maintain Korean language primary documentation (Korean-focused library)\n- Follow existing README.md structure and style",
+        "testStrategy": "Verification:\n- All new functions documented with examples\n- Code examples are syntactically correct\n- Links in table of contents work\n- Markdown renders properly on GitHub\n- No broken links or formatting issues\nManual review of rendered README on GitHub",
+        "priority": "medium",
+        "dependencies": [
+          "31"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:26:24.939Z"
+      },
+      {
+        "id": "33",
+        "title": "Achieve 90%+ test coverage for all modules",
+        "description": "Write additional tests and improve existing test suites to achieve minimum 90% coverage across all modules (statements, branches, functions, lines)",
+        "details": "Implementation details:\n- Run coverage report: npm run test:coverage\n- Identify uncovered lines, branches, and functions\n- Add missing test cases for edge cases:\n  - Null/undefined inputs\n  - Empty strings\n  - Invalid data types\n  - Boundary conditions\n  - Error handling paths\n- Focus on new modules (date, number, validation)\n- Ensure existing modules maintain coverage\n- Add tests for error scenarios and edge cases\n- Document any intentionally untested code\n\nTarget metrics (from PRD):\n- Statements: ≥90% (current 79.67%)\n- Branches: ≥85% (current 75.32%)\n- Functions: ≥95% (current 85.14%)\n- Lines: ≥90% (current 79.67%)",
+        "testStrategy": "Verification:\n- Run npm run test:coverage\n- Check coverage report meets all targets:\n  - Statements ≥90%\n  - Branches ≥85%\n  - Functions ≥95%\n  - Lines ≥90%\n- Review coverage report HTML for any gaps\n- All tests pass: npm test",
+        "priority": "high",
+        "dependencies": [
+          "16",
+          "17",
+          "18",
+          "19",
+          "20",
+          "21",
+          "22",
+          "23",
+          "24",
+          "26",
+          "27",
+          "28",
+          "29",
+          "30"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:24:49.337Z"
+      },
+      {
+        "id": "34",
+        "title": "Verify build and prepare for npm publication",
+        "description": "Final verification that all code builds correctly, passes linting, and is ready for npm publish",
+        "details": "Implementation details:\n- Run full build: npm run build\n- Verify lib/ directory contains all compiled files\n- Run linter: npm run lint\n- Fix any linting errors: npm run lint:fix\n- Run all tests: npm test\n- Run coverage check: npm run test:coverage\n- Verify package.json exports are correct\n- Test import statements in lib/ output\n- Ensure no TypeScript errors\n- Check that all new functions are exported from main index.ts\n\nPre-publish checklist:\n- [ ] Build succeeds (npm run build)\n- [ ] All tests pass (npm test)\n- [ ] Coverage ≥90% (npm run test:coverage)\n- [ ] Linting passes (npm run lint)\n- [ ] README updated\n- [ ] Version updated to 0.2.0",
+        "testStrategy": "Verification:\n- npm run build completes without errors\n- npm run lint passes\n- npm test shows all tests passing\n- npm run test:coverage shows ≥90% coverage\n- lib/ directory structure correct\n- TypeScript definitions (.d.ts files) generated\n- All exports accessible from main package\nRun all npm scripts in sequence",
+        "priority": "high",
+        "dependencies": [
+          "31",
+          "32",
+          "33"
+        ],
+        "status": "done",
+        "subtasks": [],
+        "updatedAt": "2025-12-26T02:26:24.941Z"
+      },
+      {
+        "id": "35",
+        "title": "Publish v0.2.0 to npm registry",
+        "description": "Publish the updated jell-utils package to npm registry as version 0.2.0",
+        "details": "Implementation details:\n- Ensure logged into npm: npm whoami\n- Login if needed: npm login\n- Run prepublishOnly script (automatically runs tests and lint)\n- Publish to npm: npm publish\n- Verify package published: npm view jell-utils@0.2.0\n- Check package page on npmjs.com\n- Create GitHub release tag: git tag v0.2.0\n- Push tag: git push origin v0.2.0\n\nPost-publish verification:\n- Package visible on npmjs.com/package/jell-utils\n- Version 0.2.0 listed\n- README displays correctly\n- Installation works: npm install jell-utils@0.2.0",
+        "testStrategy": "Verification:\n- npm view jell-utils shows version 0.2.0\n- Package page on npmjs.com displays correctly\n- README renders properly on npm\n- Test installation in clean directory:\n  - mkdir test-install && cd test-install\n  - npm init -y\n  - npm install jell-utils@0.2.0\n  - Verify node_modules/jell-utils contains expected files\n- GitHub tag v0.2.0 created",
+        "priority": "high",
+        "dependencies": [
+          "34"
+        ],
+        "status": "pending",
+        "subtasks": []
+      }
+    ],
+    "metadata": {
+      "version": "1.0.0",
+      "lastModified": "2025-12-26T02:26:24.941Z",
+      "taskCount": 20,
+      "completedCount": 19,
+      "tags": [
+        "master"
+      ]
+    }
+  }
+}

package/.taskmaster/templates/example_prd.txt

@@ -0,0 +1,47 @@
+<context>
+# Overview  
+[Provide a high-level overview of your product here. Explain what problem it solves, who it's for, and why it's valuable.]
+
+# Core Features  
+[List and describe the main features of your product. For each feature, include:
+- What it does
+- Why it's important
+- How it works at a high level]
+
+# User Experience  
+[Describe the user journey and experience. Include:
+- User personas
+- Key user flows
+- UI/UX considerations]
+</context>
+<PRD>
+# Technical Architecture  
+[Outline the technical implementation details:
+- System components
+- Data models
+- APIs and integrations
+- Infrastructure requirements]
+
+# Development Roadmap  
+[Break down the development process into phases:
+- MVP requirements
+- Future enhancements
+- Do not think about timelines whatsoever -- all that matters is scope and detailing exactly what needs to be build in each phase so it can later be cut up into tasks]
+
+# Logical Dependency Chain
+[Define the logical order of development:
+- Which features need to be built first (foundation)
+- Getting as quickly as possible to something usable/visible front end that works
+- Properly pacing and scoping each feature so it is atomic but can also be built upon and improved as development approaches]
+
+# Risks and Mitigations  
+[Identify potential risks and how they'll be addressed:
+- Technical challenges
+- Figuring out the MVP that we can build upon
+- Resource constraints]
+
+# Appendix  
+[Include any additional information:
+- Research findings
+- Technical specifications]
+</PRD>