Merge pull request #282 from YAPP-Github/develop

[RELEASE] 1.5.0

Author: rbgksqkr

.coderabbit.yaml

@@ -0,0 +1,79 @@
+language: ko-KR
+
+tone_instructions: '왜 개선이 필요한지 먼저 설명. 리뷰 순서: 1) 문제 상황 2) 해결 방향 제안 3) 추천과 이유 4) 개선 효과. 선택지를 주되 경험 기반 추천도 함께. 부드럽고 건설적으로!'
+
+reviews:
+  profile: assertive
+  request_changes_workflow: false
+  poem: false
+  auto_review:
+    enabled: true
+    auto_incremental_review: true
+    ignore_title_keywords: ['RELEASE']
+
+  path_instructions:
+    - path: 'src/**/*.{ts,tsx}'
+      instructions: |
+        다음 항목들을 우선적으로 검사해주세요:
+
+        **Readability (가독성)**
+        - 매직 넘버는 명명된 상수로 변경했는가? (예: 300ms → ANIMATION_DELAY_MS)
+        - 복잡한 삼항연산자는 if문 또는 switch문으로 처리하거나 컴포넌트를 분리했는가?
+        - 복잡한 조건은 의미 있는 변수명을 가지는가? (예: isValidEmail, hasRequiredRole)
+        - 구현 디테일이 추상화되어 있는가? (복잡한 로직 → 별도 컴포넌트/훅)
+
+        **Predictability (예측 가능성)**
+        - 유사한 함수/훅들의 반환 타입이 일관적인가?
+        - 함수명이 실제 동작을 명확히 나타내는가?
+        - 숨겨진 사이드 이펙트가 있는가? (SRP 위반)
+
+        **Coupling (결합도)**
+        - Props drilling이 과도하지 않은가? (5개 이상 props는 컴포지션 검토)
+        - 상태 관리 범위가 너무 넓지 않은가? (필요한 상태만 선택)
+
+        **Cohesion (응집도)**
+        - 파일이 도메인/기능별로 잘 구성되어 있는가?
+
+        **프로젝트 규칙**
+        - 'let' 사용을 최소화했는가? (const/메서드 체이닝 선호)
+        - React Query 사용했는가? (데이터 페칭)
+        - 에러 핸들링이 고려되었는가?
+
+    - path: 'src/**/*.tsx'
+      instructions: |
+        - Props가 5개 이상인가? (컴포지션 고려)
+        - 조건부 렌더링이 복잡한가? (별도 컴포넌트로 분리 제안)
+        - useEffect를 최소화했는가? (파생 상태 사용)
+        - 컴포넌트가 단일 책임을 가지는가?
+
+    - path: 'src/**/*.ts'
+      instructions: |
+        **Query 함수 (`*Query`, `useXXXQuery`)**
+        - queryKey가 명확하고 캐싱 전략이 적절한가?
+        - staleTime, gcTime 설정이 필요한가?
+        - 데이터 변환 로직이 필요한가?
+        - 의존성 배열이 정확한가?
+
+        **Mutation 함수 (`*Mutation`, `useXXXMutation`)**
+        - onSuccess, onError 핸들러가 제대로 정의되었는가?
+        - 낙관적 업데이트(optimisticData)가 필요한가?
+        - invalidateQueries로 관련 쿼리를 무효화하는가?
+        - 에러 발생 시 롤백 로직이 있는가?
+        - 로딩/성공/에러 상태를 어떻게 처리하는가?
+
+        **주의 사항**
+        - useQuery/useMutation을 직접 컴포넌트에서 사용하지 않았는가? (커스텀 훅으로 래핑했는가?)
+        - 토큰/인증 헤더가 올바르게 설정되었는가?
+
+    - path: 'src/schema/**/*.ts'
+      instructions: |
+        - Zod 스키마 메시지는 사용자 친화적인가?
+        - 모든 필드에 적절한 검증이 있는가?
+        - 에러 메시지가 명확한가?
+
+# 지식 기반 설정
+knowledge_base:
+  code_guidelines:
+    filePatterns:
+      - '.cursor/rules/**/*.mdc'
+      - 'README.md'

.cursor/rules/nextjs-sentry.mdc

@@ -1,5 +1,5 @@
 ---
-alwaysApply: true
+alwaysApply: false
 ---
 
 These examples should be used as guidance when configuring Sentry functionality within a project.

.cursor/rules/zod.mdc

@@ -0,0 +1,124 @@
+---
+alwaysApply: true
+---
+
+You are an expert developer proficient in TypeScript, React and Next.js, Zod, TanStack React Query
+
+Code Style and Structure
+
+- Write concise, technical TypeScript code with accurate examples.
+- Use functional and declarative programming patterns; avoid classes.
+- Prefer iteration and modularization over code duplication.
+- Use descriptive variable names with auxiliary verbs (e.g., `isLoading`, `hasError`).
+- Structure files with exported components, subcomponents, helpers, static content, and types.
+- Favor named exports for components and functions.
+- Use lowercase with dashes for directory names (e.g., `components/auth-wizard`).
+
+TypeScript and Zod Usage
+
+- Use TypeScript for all code; prefer interfaces over types for object shapes.
+- Utilize Zod for schema validation and type inference.
+- Avoid enums; use literal types or maps instead.
+- Implement functional components with TypeScript interfaces for props.
+
+Syntax and Formatting
+
+- Use the `function` keyword for pure functions.
+- Write declarative JSX with clear and readable structure.
+- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
+
+UI and Styling
+
+- Use Tamagui for cross-platform UI components and styling.
+- Implement responsive design with a mobile-first approach.
+- Ensure styling consistency between web and native applications.
+- Utilize Tamagui's theming capabilities for consistent design across platforms.
+
+State Management and Data Fetching
+
+- Use Zustand for state management.
+- Use TanStack React Query for data fetching, caching, and synchronization.
+- Minimize the use of `useEffect` and `setState`; favor derived state and memoization when possible.
+
+Internationalization
+
+- Use i18next and react-i18next for web applications.
+- Use expo-localization for React Native apps.
+- Ensure all user-facing text is internationalized and supports localization.
+
+Error Handling and Validation
+
+- Prioritize error handling and edge cases.
+- Handle errors and edge cases at the beginning of functions.
+- Use early returns for error conditions to avoid deep nesting.
+- Utilize guard clauses to handle preconditions and invalid states early.
+- Implement proper error logging and user-friendly error messages.
+- Use custom error types or factories for consistent error handling.
+
+Performance Optimization
+
+- Optimize for both web and mobile performance.
+- Use dynamic imports for code splitting in Next.js.
+- Implement lazy loading for non-critical components.
+- Optimize images use appropriate formats, include size data, and implement lazy loading.
+
+Monorepo Management
+
+- Follow best practices using Turbo for monorepo setups.
+- Ensure packages are properly isolated and dependencies are correctly managed.
+- Use shared configurations and scripts where appropriate.
+- Utilize the workspace structure as defined in the root `package.json`.
+
+Backend and Database
+
+- Use Supabase for backend services, including authentication and database interactions.
+- Follow Supabase guidelines for security and performance.
+- Use Zod schemas to validate data exchanged with the backend.
+
+Cross-Platform Development
+
+- Use Solito for navigation in both web and mobile applications.
+- Implement platform-specific code when necessary, using `.native.tsx` files for React Native-specific components.
+- Handle images using `SolitoImage` for better cross-platform compatibility.
+
+Stripe Integration and Subscription Model
+
+- Implement Stripe for payment processing and subscription management.
+- Use Stripe's Customer Portal for subscription management.
+- Implement webhook handlers for Stripe events (e.g., subscription created, updated, or cancelled).
+- Ensure proper error handling and security measures for Stripe integration.
+- Sync subscription status with user data in Supabase.
+
+Testing and Quality Assurance
+
+- Write unit and integration tests for critical components.
+- Use testing libraries compatible with React and React Native.
+- Ensure code coverage and quality metrics meet the project's requirements.
+
+Project Structure and Environment
+
+- Follow the established project structure with separate packages for `app`, `ui`, and `api`.
+- Use the `apps` directory for Next.js and Expo applications.
+- Utilize the `packages` directory for shared code and components.
+- Use `dotenv` for environment variable management.
+- Follow patterns for environment-specific configurations in `eas.json` and `next.config.js`.
+- Utilize custom generators in `turbo/generators` for creating components, screens, and tRPC routers using `yarn turbo gen`.
+
+Key Conventions
+
+- Use descriptive and meaningful commit messages.
+- Ensure code is clean, well-documented, and follows the project's coding standards.
+- Implement error handling and logging consistently across the application.
+
+Follow Official Documentation
+
+- Adhere to the official documentation for each technology used.
+- For Next.js, focus on data fetching methods and routing conventions.
+- Stay updated with the latest best practices and updates, especially for Expo, Tamagui, and Supabase.
+
+Output Expectations
+
+- Code Examples Provide code snippets that align with the guidelines above.
+- Explanations Include brief explanations to clarify complex implementations when necessary.
+- Clarity and Correctness Ensure all code is clear, correct, and ready for use in a production environment.
+- Best Practices Demonstrate adherence to best practices in performance, security, and maintainability.

src/apis/post.ts

@@ -46,6 +46,13 @@ export interface ExperimentPostListFilters {
   count?: number;
 }
 
+export interface ExtractKeywordsLimitResponse {
+  count: number;
+  limit: number;
+  remainingCount: number;
+  resetsAt: string;
+}
+
 export const fetchPostList = async (params: ExperimentPostListFilters) => {
   const queryParams = getQueryParamsToString({ ...params });
   return await fetchClient.get<ExperimentPostResponse>(API_URL.postList(queryParams), {
@@ -56,3 +63,7 @@ export const fetchPostList = async (params: ExperimentPostListFilters) => {
 export const fetchPostCount = async <T>(region?: string | null) => {
   return await fetchClient.get<T>(API_URL.postArea(region), { requireAuth: false });
 };
+
+export const fetchExtractKeywordsLimit = async () => {
+  return await fetchClient.get<ExtractKeywordsLimitResponse>(API_URL.extractKeywordsLimit);
+};