Skip to content

docs: add AI tools configuration (Claude, Codex)#205

Merged
froggy1014 merged 6 commits intomainfrom
docs/ai-tools-setup
Apr 8, 2026
Merged

docs: add AI tools configuration (Claude, Codex)#205
froggy1014 merged 6 commits intomainfrom
docs/ai-tools-setup

Conversation

@froggy1014
Copy link
Copy Markdown
Contributor

@froggy1014 froggy1014 commented Apr 7, 2026

Changes

  1. Figma MCP 프로젝트 레벨에서의 MCP 추가

  2. CLAUDE, AGENTS 초기화

요즘 모델 능력치나, 토큰은 다들 100달러는 기본으로 쓰실 것 같아서 편한 유지보수를 위해 한국어로 작성했어요.

  1. 생각나는 세팅 값 추가 ( settings.json, config.toml, post hook.. )

To Reviewers

일단 먼저 초기화해두고, 작업하시는거 보면서 스킬 추가하거나 컨텍스트 깍아나가려고 합니다.

codex나 claude 세팅 값이나 연동을 우아하게 하는 방법아신다면 공유부탁드립니다. ㅎㅎ ...

cursor는 필요하면 추후에 추가해보겠습니다. ^^7

Summary by CodeRabbit

  • Documentation

    • 기여자 가이드라인, 개발 워크플로우 및 컴포넌트 작성·스타일 규칙 문서 추가
  • Chores

    • 개발용 에이전트/도구 설정 파일 추가 및 로컬 설정 제외 규칙 업데이트
    • 변경 시 자동 포맷/검사 실행을 위한 후크 추가(포맷터 실행 상태 메시지 포함)
    • 코드 포맷터/린트 도구 버전 업그레이드 및 관련 설정 정리

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 7, 2026

⚠️ No Changeset found

Latest commit: 8fff34d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 7, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 4748cfdc-f551-4a06-a515-8e6ae678b138

📥 Commits

Reviewing files that changed from the base of the PR and between 6a29b4d and 8fff34d.

📒 Files selected for processing (2)
  • .codex/config.toml
  • .mcp.json
✅ Files skipped from review due to trivial changes (1)
  • .codex/config.toml
🚧 Files skipped from review as they are similar to previous changes (1)
  • .mcp.json

Walkthrough

리포지터리에 Claude Code·Codex·MCP 설정과 개발자 문서가 추가되었습니다. Biome 자동 포맷 후크와 샌드박스·플러그인·모델 제한, Codex 기본 모델·승인 정책, Figma MCP 엔드포인트, Biome 스키마/설정 변경 및 devDependency 업그레이드가 포함됩니다.

Changes

Cohort / File(s) Summary
Claude Code 설정
​.claude/settings.json, ​.gitignore
Claude 권한·플러그인·모델 제한, 네트워크 샌드박스 규칙, Edit/Write 후 Biome 검사 PostToolUse 훅(한글 상태 메시지) 추가; 로컬 설정 파일(.claude/settings.local.json)을 .gitignore에 추가.
Codex 설정 및 훅
​.codex/config.toml, ​.codex/hooks.json
Codex 기본 모델(gpt-5.4)·추론/웹검색/승인 정책 설정, sandbox_mode/workspace-write 활성화; PostToolUse(Bash) 훅으로 pnpm biome check --write --unsafe --changed 실행 설정.
MCP 서버 설정
​.mcp.json
figmaplaywright MCP 서버 엔드포인트/런너 등록 추가.
개발자 문서
AGENTS.md, CLAUDE.md
모노레포 구조·패키지 규약, 개발 워크플로(설치, Storybook, 테스트, 포맷 등), 컴포넌트/테스트/커밋 규칙 문서 추가.
Biome 및 패키지 업데이트
biome.json, package.json
Biome 스키마 참조를 로컬 경로로 변경, files 인클루드/ignoreUnknown 재구성, @biomejs/biome devDependency 버전 업그레이드 및 lint-staged 명령 배열 포맷 조정.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested labels

documentation

Suggested reviewers

  • kimdaeyeob
  • hy57in
  • developerjhp
  • bae-sh
  • SEMIN-97
  • heeji289

Poem

🐰✨ 새 설정들이 깡총깡총 왔어요,
코드와 포맷터가 손잡고 춤추고,
훅이 지나가며 파일을 예쁘게 다듬고,
문서들이 길을 밝히니 개발자도 웃어요,
토끼가 축하해요 — 당근 한 입! 🥕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed 제목은 변경 사항의 주요 내용을 명확하게 반영하고 있습니다. Claude와 Codex AI 도구 설정 추가라는 핵심 변경 사항을 간결하게 요약했습니다.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/ai-tools-setup

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 7, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/settings.json:
- Around line 43-44: The JSON in .claude/settings.json is invalid due to a
trailing comma after the "PostToolUse" array in the "hooks" object; remove the
comma following the closing bracket of the "PostToolUse" array so the array ends
with ] (no comma), then validate the file (e.g., with a JSON linter) to ensure
"hooks" contains only that single property and the JSON parses correctly.

In @.codex/config.toml:
- Around line 14-18: The file is missing the [permissions.network] section so
the current sandbox configuration (sandbox_mode and [sandbox_workspace_write]
with network_access = true) permits unrestricted outbound access; add a new
[permissions.network] block named exactly "permissions.network" and set enabled
to true, mode to "limited", and provide an allowed_domains array containing
"registry.npmjs.org" and "npm.pkg.github.com" so network access is restricted to
those domains instead of being globally allowed.

In @.codex/hooks.json:
- Around line 5-10: The global Bash trigger ("matcher": "Bash") combined with
the command "pnpm biome check --write --unsafe --changed" is too broad and
applies destructive auto-fixes; change the hook to a narrower matcher (e.g.,
target only shell scripts or changed files instead of "Bash") and remove the
"--unsafe" flag from the command so it no longer applies potentially destructive
fixes; also consider invoking the repository-standard script (e.g., package.json
"format:biome" or "lint:biome") instead of calling biome with unsafe options to
align behavior with existing project scripts.

In `@CLAUDE.md`:
- Line 65: The MD037 lint warning is caused by unescaped asterisk patterns in
the list item "import 순서 강제: node → react → `@sipe-team/`* → `@vanilla-extract/`* →
`@radix-ui/`* → 외부 패키지 → 상대 경로 (그룹 사이 빈 줄)"; fix it by wrapping each glob-like
token containing '*' in inline code (e.g. change `@sipe-team/`*,
`@vanilla-extract/`*, `@radix-ui/`* to `@sipe-team/*`, `@vanilla-extract/*`,
`@radix-ui/*`) so the markdown linter no longer treats the asterisks as emphasis
(MD037).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: c0a01e0f-c08d-4974-98c6-f24487ab2cc7

📥 Commits

Reviewing files that changed from the base of the PR and between 14ef05c and d29c64c.

📒 Files selected for processing (7)
  • .claude/settings.json
  • .codex/config.toml
  • .codex/hooks.json
  • .gitignore
  • .mcp.json
  • AGENTS.md
  • CLAUDE.md

## 린팅 및 포맷팅

- **Biome** (ESLint/Prettier가 아님) — 싱글 쿼트, 스페이스, 줄 너비 120자
- import 순서 강제: node → react → @sipe-team/* → @vanilla-extract/* → @radix-ui/* → 외부 패키지 → 상대 경로 (그룹 사이 빈 줄)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

마크다운 lint(MD037) 경고를 해소해 주세요.

Line [65]의 * 패턴이 강조 마커로 해석될 수 있습니다. 토큰을 코드 표기로 감싸면 경고를 없앨 수 있습니다.

수정 예시
-- import 순서 강제: node → react → `@sipe-team/`* → `@vanilla-extract/`* → `@radix-ui/`* → 외부 패키지 → 상대 경로 (그룹 사이 빈 줄)
+- import 순서 강제: `node` → `react` → `@sipe-team/*` → `@vanilla-extract/*` → `@radix-ui/*` → 외부 패키지 → 상대 경로 (그룹 사이 빈 줄)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- import 순서 강제: node → react → @sipe-team/*@vanilla-extract/*@radix-ui/* → 외부 패키지 → 상대 경로 (그룹 사이 빈 줄)
- import 순서 강제: `node``react``@sipe-team/*``@vanilla-extract/*``@radix-ui/*` → 외부 패키지 → 상대 경로 (그룹 사이 빈 줄)
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)

[warning] 65-65: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CLAUDE.md` at line 65, The MD037 lint warning is caused by unescaped asterisk
patterns in the list item "import 순서 강제: node → react → `@sipe-team/`* →
`@vanilla-extract/`* → `@radix-ui/`* → 외부 패키지 → 상대 경로 (그룹 사이 빈 줄)"; fix it by
wrapping each glob-like token containing '*' in inline code (e.g. change
`@sipe-team/`*, `@vanilla-extract/`*, `@radix-ui/`* to `@sipe-team/*`,
`@vanilla-extract/*`, `@radix-ui/*`) so the markdown linter no longer treats the
asterisks as emphasis (MD037).

Copy link
Copy Markdown
Member

@Yeom-JinHo Yeom-JinHo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎭 Playwright MCP도 opt-in 문서 형태로 추가하면 좋을 것 같아요~!


- **`packages/*`** — 개별 컴포넌트 패키지 (button, input, card, chip, skeleton 등)
- **`packages/tokens`** — 디자인 토큰 (색상, 간격, 타이포그래피, 라운딩, 그림자, z-index)을 vanilla-extract contract vars로 export
- **`packages/theme`** — vanilla-extract `assignInlineVars`를 사용한 ThemeProvider, 런타임 테마 전환 (4개 테마, 라이트 모드 기본)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

요건 release-v1 기준으로 작성된건가용?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Yeom-JinHo

투표를 보니까 release/v1이 main으로 머지할거같아서 release/v1 에서 /init을 했어요.

언제 release/v1을 합치실지 몰라서 어차피 다 새로운 파일들이기도하구, main을 target branch로 잡았습니다.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

좋아요~~ 👍🏽

@froggy1014 froggy1014 merged commit a02ee4e into main Apr 8, 2026
4 checks passed
@froggy1014 froggy1014 deleted the docs/ai-tools-setup branch April 8, 2026 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants