메뉴
Project coding conventions extracted from chat history. Load when writing new code, naming things, designing APIs, or reviewing PRs. Topics: Cursor pagination is mandatory for all paged GraphQL endpoints.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Technical decisions made for this project, with reasoning and rejected alternatives. Load when proposing architectural changes, evaluating alternatives, or asked why a choice was made. Topics: Adopt OAuth 2.0 authorization code flow with PKCE for the customer portal SPA.
System architecture facts: components, data flow, integration boundaries. Load when implementing cross-component features, debugging integration issues, or onboarding to the codebase. Topics: Event sourcing for the billing audit log.
| name | ai-memory-coding-conventions |
| description | Project coding conventions extracted from chat history. Load when writing new code, naming things, designing APIs, or reviewing PRs. Topics: Cursor pagination is mandatory for all paged GraphQL endpoints. |
Auto-generated by ai-memory from AI chat history. Edit memories via
ai-memory list/extract/resolverather than this file — it is fully regenerated on everyai-memory rules --target skills.
Every paged GraphQL endpoint MUST use Relay-style cursor pagination (edges / node / cursor + pageInfo.hasNextPage). Choose first + after as the canonical pair; reject last + before unless explicitly justified per endpoint. CI lint rule will enforce on new schema.
Why: Cursor pagination is stable across mutations and aligns with the Apollo/Relay tooling already in use. Migration of existing offset endpoints exposes both shapes for one minor version so consumers can switch over without breakage.
Rejected: Offset/limit (rejected, see Context). Page-token-only (rejected — no cursor opacity guarantee, leaks server state). Custom cursor scheme (rejected — no benefit over Relay spec).
