From default-setup
팀 공용 Claude Code 기본 환경을 셋업한다. CLAUDE.md에 마커 태그로 코딩 가이드라인을 삽입/업데이트하고, settings.json을 적용한다. "/default-setup", "기본 세팅", "팀 셋업", "초기 설정" 등으로 호출.
npx claudepluginhub hoyuo/hoyuo-cc-plugin --plugin default-setupThis skill is limited to using the following tools:
프로젝트 CLAUDE.md에 마커 태그(`<!-- default-setup:start/end -->`)로 팀 표준 가이드라인을 삽입/업데이트하고, .claude/settings.json을 적용하는 스킬.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
프로젝트 CLAUDE.md에 마커 태그(<!-- default-setup:start/end -->)로 팀 표준 가이드라인을 삽입/업데이트하고, .claude/settings.json을 적용하는 스킬.
/default-setup 실행 시:
CLAUDE.md를 Read<!-- default-setup:start --> ~ <!-- default-setup:end --> 마커를 검색
.claude/settings.json을 Read
.claude/ 디렉토리 생성 후 템플릿으로 새로 생성적용 결과 요약 출력.
CLAUDE.md에 삽입할 내용 (마커 태그 포함):
<!-- default-setup:start -->
## Coding Guidelines
### 1. Think Before Coding
**Don't assume. Don't hide confusion. Surface tradeoffs.**
Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them - don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
### 2. Simplicity First
**Minimum code that solves the problem. Nothing speculative.**
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
### 3. Surgical Changes
**Touch only what you must. Clean up only your own mess.**
When editing existing code:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it - don't delete it.
When your changes create orphans:
- Remove imports/variables/functions that YOUR changes made unused.
- Don't remove pre-existing dead code unless asked.
The test: Every changed line should trace directly to the user's request.
### 4. Goal-Driven Execution
**Define success criteria. Loop until verified.**
Transform tasks into verifiable goals:
- "Add validation" → "Write tests for invalid inputs, then make them pass"
- "Fix the bug" → "Write a test that reproduces it, then make it pass"
- "Refactor X" → "Ensure tests pass before and after"
For multi-step tasks, state a brief plan:
1. [Step] → verify: [check]
2. [Step] → verify: [check]
3. [Step] → verify: [check]
Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
### 5. Verify Before You Use
**Don't trust memory for external APIs. Check first.**
- Don't guess API signatures, parameters, or return types. Read the source or docs.
- Don't assume an import path exists. Verify the module exports what you expect.
- If a library version matters, check which version is installed before using new APIs.
- If you're unsure whether a method exists, say so. Don't silently fabricate it.
Common mistakes to avoid:
- Inventing helper functions that don't exist in the library.
- Using v3 API syntax when the project has v2 installed.
- Assuming default parameter values without checking.
The test: Every external call in your code should be traceable to real documentation or source code.
**These guidelines are working if:** fewer unnecessary changes in diffs, fewer rewrites due to overcomplication, and clarifying questions come before implementation rather than after mistakes.
<!-- default-setup:end -->
.claude/settings.json에 적용할 설정:
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"permissions": {
"allow": [
"Bash(*)",
"Edit(*)",
"Write(*)",
"Read(*)",
"Glob(*)",
"Grep(*)",
"WebFetch",
"WebSearch",
"NotebookEdit(*)",
"Task:*"
],
"ask": [
"Bash(git push:*)",
"Bash(git reset:*)",
"Bash(rm -rf:*)"
]
},
"env": {
"ENABLE_TOOL_SEARCH": "1",
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1",
"CLAUDE_CODE_MAX_OUTPUT_TOKENS": "64000"
},
"cleanupPeriodDays": 365,
"enableAllProjectMcpServers": true,
"language": "korean",
"alwaysThinkingEnabled": true,
"teammateMode": "auto"
}