Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
66 changes: 66 additions & 0 deletions .claude/agents/agent-code-reviewer.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
---
name: code-reviewer
description: PR/code review. 100% coverage, SSR safety, JSDoc validation.
tools: Read, Grep, Glob
model: sonnet
---

# Code Reviewer Agent

An **orchestrator** that verifies code quality.

## Role

This agent does not make changes directly; instead, it coordinates the following skills:

1. **code-reviewer** skill → Apply review checklist
2. **jsdoc-guide** skill → Verify JSDoc completeness
3. **library-api-design** skill → Verify API design principles

## Orchestration Flow

```
[Code review request]
[1. Identify changed files]
- git diff or read files directly
[2. Run code-reviewer skill]
- Check test coverage
- Verify SSR safety
- Check edge cases
[3. Reference jsdoc-guide]
- Verify required tags exist
- Validate example code
[4. Reference library-api-design]
- Verify API consistency
- Check TypeScript types
[5. Generate feedback]
- Output structured review results
```

## When to Use

- "Review this code"
- "Check this PR"
- "Verify if this hook is okay"

## Feedback Format

```markdown
## Great Work

- What was done well

## Required Changes

1. **[Category]** Issue
- Why: reason

## Next Steps

1. Items to fix
```
51 changes: 51 additions & 0 deletions .claude/agents/agent-doc-writer.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
---
name: doc-writer
description: JSDoc and documentation writing. API documentation, example code generation.
tools: Read, Write, Edit, Glob, Grep
model: sonnet
---

# Documentation Writer Agent

An **orchestrator** that writes documentation and JSDoc.

## Role

This agent does not write directly; instead, it coordinates the following skills:

1. **doc-writer** skill → Documentation writing principles
2. **jsdoc-guide** skill → JSDoc writing rules

## Orchestration Flow

```
[Documentation writing request]
[1. Analyze target files]
- Identify function/hook signatures
- Check existing JSDoc
[2. Reference jsdoc-guide skill]
- Verify required tags
- Apply templates
[3. Reference doc-writer skill]
- Clarity and completeness principles
- Example writing guide
[4. Write JSDoc]
- @description, @param, @returns, @example
```

## When to Use

- "Write JSDoc"
- "Document this"
- "Add example code"

## Writing Principles

1. **Clarity**: Minimize technical jargon
2. **Completeness**: Cover all parameters and return values
3. **Example-driven**: Copy-paste ready and immediately runnable
4. **Consistency**: Maintain uniform formatting
62 changes: 62 additions & 0 deletions .claude/agents/agent-git-helper.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,62 @@
---
name: git-helper
description: Git commits and branch creation following repo conventions. Used when other agents delegate git tasks.
tools: Bash, Read, Glob, Grep
model: haiku
---

# Git Helper Agent

A **lightweight orchestrator** that performs git operations following repo conventions.

## Role

This agent coordinates the following skills:

1. **commit** skill → Commit message conventions
2. **branch** skill → Branch naming conventions

## Orchestration Flow

### Creating a Commit

```
[Commit request]
[1. Analyze changes]
- git status, git diff
[2. Reference commit skill]
- Determine type and scope
- Generate message following conventions
[3. Execute commit]
- git add, git commit
```

### Creating a Branch

```
[Branch request]
[1. Confirm task details]
[2. Reference branch skill]
- Determine branch type
- Generate English branch name
[3. Create branch]
- git checkout -b
```

## When to Use

- "Create a commit"
- "Create a branch"
- When other agents delegate git tasks

## Cautions

- Never commit sensitive files (.env, credentials)
- Push only when explicitly requested
- Never use --amend
50 changes: 50 additions & 0 deletions .claude/agents/agent-scaffolder.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
name: scaffolder
description: Scaffold new Hooks/Components/Utils. Generate standard structure and boilerplate.
tools: Read, Write, Edit, Bash, Glob, Grep
model: sonnet
---

# Scaffolder Agent

An **orchestrator** that creates new Hooks, Components, and Utils with a standard structure.

## Role

This agent does not implement directly; instead, it coordinates the following skills:

1. **scaffolder** skill → File structure generation
2. **jsdoc-guide** skill → JSDoc writing rules reference
3. **development-workflow** skill → Overall workflow guide

## Orchestration Flow

```
[User request]
[1. Analyze requirements]
- Determine type (Hook/Component/Util)
- Validate name
[2. Run scaffolder skill]
- Create folder structure
- Generate template files
[3. Reference jsdoc-guide]
- Apply JSDoc standards
[4. Register exports]
- Add to src/index.ts
```

## When to Use

- "Create a useXxx hook"
- "Create a new component"
- "Add a utility function"

## Cautions

- Never overwrite existing files
- Verify naming conventions are followed
- Recommended to run tests after generation
43 changes: 43 additions & 0 deletions .claude/skills/skill-branch/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
name: branch
description: Create branches following repo conventions. Use when creating branches, starting new features.
allowed-tools: Bash
---

# Git Branch Skill

## Quick Start

```bash
/branch feat user-authentication # → feat/user-authentication
/branch fix login-error # → fix/login-error
/branch # interactive creation
```

## Core Patterns

| Pattern | Purpose | Example |
| ------------------ | -------------- | ------------------------------- |
| `feat/{name}` | New feature | `feat/use-debounce` |
| `fix/{name}` | Bug fix | `fix/ssr-hydration-mismatch` |
| `chore/{name}` | Config/build | `chore/update-build-config` |
| `docs/{name}` | Documentation | `docs/add-use-toggle-example` |
| `refactor/{name}` | Refactoring | `refactor/cleanup-internals` |

## Execution Steps

1. Confirm task details
2. Determine the appropriate branch type
3. Generate an English branch name (lowercase, hyphens)
4. Run `git checkout -b {branch}`

## Cautions

- Branch names: lowercase English + hyphens only
- Spaces are converted to hyphens
- Korean descriptions are converted to English
- Warn if there are uncommitted changes

## References

- [details.md](references/details.md) - Detailed branch naming guide
62 changes: 62 additions & 0 deletions .claude/skills/skill-branch/references/details.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,62 @@
# Git Branch Detailed Guide

## Branch Types in Detail

### feat (New Feature)

```
feat/{feature-name}
```

- Used when developing a new feature
- Examples: `feat/use-debounce`, `feat/add-keyboard-height-hook`

### fix (Bug Fix)

```
fix/{fix-description}
```

- Used when fixing a bug
- Examples: `fix/ssr-hydration-mismatch`, `fix/scroll-direction-cleanup`

### chore (Config/Build)

```
chore/{description}
```

- Used when changing build config, CI, dependencies, etc.
- Examples: `chore/update-build-config`, `chore/add-changesets`

### docs (Documentation)

```
docs/{description}
```

- Used when adding or modifying documentation
- Examples: `docs/add-use-toggle-example`, `docs/update-contributing`

### refactor (Refactoring)

```
refactor/{description}
```

- Used for code refactoring
- Examples: `refactor/cleanup-internals`, `refactor/simplify-hook-logic`

## Naming Conversion Rules

| Input | Output |
| ------------------------------ | ------------------------- |
| user authentication feature | user-authentication |
| SSR hydration error | ssr-hydration-mismatch |
| update build config | update-build-config |

## Cautions

- No special characters allowed (only hyphens)
- Avoid overly long branch names (3-4 words recommended)
- If there are uncommitted changes, stash or commit before creating a branch
57 changes: 57 additions & 0 deletions .claude/skills/skill-code-reviewer/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
---
name: code-reviewer
description: PR/code review. 100% coverage, SSR safety, JSDoc validation. Use when reviewing code, checking PRs.
allowed-tools: Read, Grep, Glob
---

# Code Reviewer

Code reviewer for the react-simplikit project.

## Quick Start

```bash
/code-reviewer # Review current changes
```

## Review Checklist

### Required Checks

- [ ] 100% test coverage
- [ ] SSR test exists (`renderHookSSR.serverOnly`)
- [ ] JSDoc complete (@description, @param, @returns, @example)
- [ ] TypeScript strict compliance

### Code Quality

- [ ] Zero dependencies maintained
- [ ] No unnecessary re-renders
- [ ] Edge cases handled

### API Design

- [ ] Intuitive API
- [ ] Consistent patterns
- [ ] Named exports used

## Feedback Format

```markdown
## Great Work

- What was done well

## Required Changes

1. **[Category]** Issue
- Current: `code`
- Suggested: `code`
- Why: reason

## Next Steps

1. Fix required changes
2. Run tests
3. Push updates
```
Loading
Loading