solmate-skills 2.0.10 → 2.0.12

package/AGENTS.md

@@ -73,8 +73,14 @@
 - **사용자 커뮤니케이션 필수**: 구현 전 HTML Preview를 사용자에게 보여주고 피드백을 받아야 하며, 확인 결과와 보완 사항을 UI 문서 또는 `docs/04_Logic_Progress/00_BACKLOG.md`에 기록한다.
 - **구현 차단 조건**: HTML Preview가 없거나 문서에 링크되지 않았거나 사용자의 화면 확인 기록이 없으면 UI-First Gate를 통과할 수 없고, 구현을 시작할 수 없다.
 
+### 2.9. Component & Library Planning Gate (필수)
+- **컴포넌트·라이브러리 계획 필수화**: React 구현 전 사용할 shadcn/ui 컴포넌트, 직접 만들 커스텀 컴포넌트, 재사용할 기존 컴포넌트, 새로 설치할 라이브러리, 설치하지 않을 라이브러리를 정리한다.
+- **shadcn 적용 방식 기록**: 신규 Next.js 모노레포는 `init --preset`, 기존 프로젝트는 `apply --preset` 또는 `apply --only theme` 적용 여부를 기록한다. 해당 없으면 `N/A - 사유`를 적는다.
+- **저장 위치**: Component & Library Plan은 `docs/03_Technical_Specs/` 문서, `docs/04_Logic_Progress/00_BACKLOG.md`, 또는 Pre-Code Technical Brief에 기록한다.
+- **구현 차단 조건**: Component & Library Plan이 없으면 React 컴포넌트 구현을 시작할 수 없다.
+
 ## 3. 개발 표준 및 품질
-- **UI 중심 개발 전략 (UI-First)**: Concept_Design -> UI_Screens -> Technical_Specs -> Logic_Progress 순서를 따른다.
+- **UI 중심 개발 전략 (UI-First)**: Concept_Design -> UI_Screens -> HTML Preview -> Pre-Code Technical Brief -> Component & Library Plan -> React 구현 -> Technical_Specs/Logic_Progress 순서를 따른다.
 - **git commit 필수**: 중요 작업 전 반드시 git commit을 수행한다.
 - **커밋 메시지 형식**: `type(scope): subject` 포맷을 따른다.
   - **Type**: `feat`(기능), `fix`(버그), `docs`(문서), `style`(포맷), `refactor`(리팩토링), `test`(테스트), `chore`(기타)
@@ -110,7 +116,7 @@ AI 에이전트는 본 프로젝트에 설치된 다음 **26개 스킬**을 활
 | | `docs-pitch` | 피치덱 작성 (Markdown / Reveal.js HTML) |
 | | `docs-business` | 사업계획서 작성 (정부 지원, 투자 심사, 파트너십 목적별 구성) |
 | **품질 검증 (QA)** | `verify-implementation` | 모든 `verify-*` 스킬의 통합 순차 실행 및 YAGNI/KISS/DRY Gate 보고 |
-| | `verify-docs` | 문서 레이어 정합성 및 네이밍/메타데이터, UI-First Gate 검증 |
+| | `verify-docs` | 문서 레이어 정합성 및 네이밍/메타데이터, UI-First Gate, Component & Library Planning Gate 검증 |
 | | `verify-ui` | 구현 UI와 화면 문서·HTML Preview·사용자 동선·상태별 UI 정합성 검증 |
 | | `verify-code` | PR 전 코드 품질 종합 리뷰 (로직, 타입, 중복, 과잉 구현, 사이드 이펙트) |
 | | `verify-security` | OWASP Top 10 기준 보안 취약점 점검 (인증, 인젝션, 시크릿 노출 등) |
@@ -119,8 +125,8 @@ AI 에이전트는 본 프로젝트에 설치된 다음 **26개 스킬**을 활
 | | `verify-skills` | 스킬 패키지 메타데이터·CLI·README/AGENTS·패키징 검증 |
 | **개발 및 설계** | `rules-dev` | 코딩 표준, 프로젝트 컨벤션, YAGNI/KISS/DRY Gate 준수 여부 확인 |
 | | `rules-react` | UI 컴포넌트 설계 및 구현 표준 가이드 |
-| | `rules-product` | 기획→UI→React→개발문서 전체 파이프라인 오케스트레이션 |
-| **특수 도구(Tools)** | `tools-shadcn` | shadcn/ui 라이브러리 활용 및 커스텀 가이드 |
+| | `rules-product` | 기획→UI→컴포넌트·라이브러리 계획→React→개발문서 전체 파이프라인 오케스트레이션 |
+| **특수 도구(Tools)** | `tools-shadcn` | shadcn/ui 컴포넌트·프리셋·라이브러리 활용 및 커스텀 가이드 |
 | | `tools-obsidian` | 지식 베이스(Obsidian)와의 동기화 및 관리 |
 | **외부 확장(External)** | `ext-awesome-design` | 프리미엄 디자인 시스템 및 마크다운 템플릿 라이브러리 |
 | | `ext-k-skill` | 한국 특화 전문 스킬 모음 (법률, 배송, 교통 등) |
@@ -154,3 +160,5 @@ AI 에이전트는 사용자가 스킬을 호출하지 않아도, 아래 상황
 
 ## 6. 최종 약속
 AI 에이전트는 본 **AGENTS.md**를 모든 판단의 최우선 근거로 삼는다. 문서에 정의되지 않은 작업을 수행할 경우 반드시 사용자에게 구현 전 문서 업데이트 필요성을 먼저 확인한다.
+
+**사람용 스킬 사용법** (상황별 선택, 26개 카탈로그, Gate 상세): 프로젝트 루트 `USAGE.md` — 영문 기본, 하단 한국어 (`npx solmate-skills install` 시 복사).

package/CLAUDE.md

@@ -23,7 +23,7 @@ There are no build, test, or lint scripts in this repo (`"test": "echo \"Error:
 
 ## Installing Skills via Symlink (Dev)
 
-`init-skills.sh` creates symlinks from a target project's `.agent/skills/` to this repo, and links `AGENTS.md` to the project root. Run it from inside the target project:
+`init-skills.sh` creates symlinks from a target project's `.agent/skills/` to this repo, and links `AGENTS.md` and `USAGE.md` to the project root. Run it from inside the target project:
 
 ```bash
 bash /Users/namhyeongseog/Documents/solmate-skills/init-skills.sh

package/README.md

@@ -2,7 +2,7 @@
 
 Reusable AI-agent skills for disciplined product work.
 
-`solmate-skills` packages the Solmate workflow as installable skills: plan the product, create browser-viewable UI previews, lock backlog tasks to their source documents, implement with YAGNI/KISS/DRY approval gates, and verify the result before release.
+`solmate-skills` packages the Solmate workflow as installable skills: plan the product, create browser-viewable UI previews, lock backlog tasks to their source documents, plan components and libraries before coding, implement with YAGNI/KISS/DRY approval gates, and verify the result before release.
 
 Use it when you want an AI coding agent to follow a shared workflow instead of improvising project structure, documentation, implementation order, and QA.
 
@@ -24,7 +24,9 @@ npx solmate-skills@latest install rules-product
 npx solmate-skills@latest install hooks
 ```
 
-The installer copies each selected skill folder into `.agent/skills/<skill-name>` in your current project.
+The installer copies each selected skill folder into `.agent/skills/<skill-name>` in your current project and copies [USAGE.md](./USAGE.md) to the project root.
+
+**Detailed usage:** see `USAGE.md` at the project root (English default, Korean below) for the situation-to-skill cheat sheet, orchestrator map, full skill catalog (26 skills), gate details, and recommended prompts.
 
 ## What You Get
 
@@ -32,10 +34,30 @@ The installer copies each selected skill folder into `.agent/skills/<skill-name>
 - **UI-first planning**: `/docs-plan` creates concept and screen documents before implementation starts.
 - **HTML UI Preview Gate**: major screens and flows must have browser-viewable HTML previews under `docs/02_UI_Screens/previews/`.
 - **Backlog Context Lock**: every backlog item must link the Concept, UI, HTML Preview, Technical Spec, and QA documents needed for implementation.
+- **Component & Library Planning Gate**: React work must name the shadcn/ui components, custom components, reused components, libraries to add, libraries to avoid, and preset action before coding.
 - **YAGNI/KISS/DRY Gate**: `rules-dev` is the canonical source for avoiding future-only features, preferring the simplest existing/native path, and removing only true duplicate knowledge.
 - **Implementation workflow**: `/rules-workflow` keeps coding work tied to approved documents, preconditions, and acceptance criteria.
 - **Release verification**: `/verify-implementation` runs the verification family for docs, UI, code, security, performance, DB schema, and skill package readiness.
 
+## What's New in 2.0.12
+
+`solmate-skills@2.0.12` adds a bilingual usage guide and copies it into every target project on install.
+
+- [USAGE.md](./USAGE.md) documents all 26 skills in English (default) with Korean below: cheat sheet, orchestrator map, gates, and prompts.
+- `npx solmate-skills install` (single skill, `all`, or `hooks`) now copies `USAGE.md` to the project root.
+- [README.md](./README.md) is trimmed to a 5-minute start; detailed usage lives in `USAGE.md`.
+- `init-skills.sh` symlinks `USAGE.md` alongside `AGENTS.md` for local development.
+
+## What's New in 2.0.11
+
+`solmate-skills@2.0.11` adds a Component & Library Planning Gate so React implementation starts from approved UI context and an explicit component/library plan.
+
+- `/rules-product` and `/rules-workflow` now connect concept docs, HTML UI preview, component planning, and implementation in a clearer sequence.
+- `/rules-react` requires agents to name shadcn/ui components, custom components, reused components, libraries to add, libraries to avoid, and preset action before coding.
+- `/tools-shadcn` documents the default new-project preset command and existing-project apply command.
+- `/verify-docs` and `/verify-implementation` now check that UI docs, backlog references, and implementation plans preserve the UI-first flow.
+- `README.md` and `AGENTS.md` surface the planning gate as part of the recommended Solmate workflow.
+
 ## What's New in 2.0.10
 
 `solmate-skills@2.0.10` fixes Claude Code hook false positives so read-only tool use no longer triggers edit-oriented skill suggestions.
@@ -70,24 +92,33 @@ Recent workflow guardrails:
 
 ## Quick Start
 
-설치 후 상황에 맞는 스킬을 하나 실행하는 것으로 시작합니다.
+Install skills, then invoke one command based on your situation.
 
-| 상황 | 시작 명령 | 설명 |
+| Situation | Start with | Notes |
 |:---|:---|:---|
-| 신규 프로젝트 — 아무것도 없을 때 | `/rules-product` | 현재 단계를 자동 진단하고 Phase 1부터 순서대로 안내 |
-| 기획은 있고 코드를 작성하려 할 때 | `/rules-dev` | 커밋 형식, 환경변수, TypeScript 기준 등 컨벤션 먼저 정립 |
-| 기능 하나를 구현하려 할 때 | `/rules-product` → `/rules-workflow` | 현재 Phase를 먼저 진단한 뒤 계획 수립부터 PR까지 진행 |
-| PR 전 최종 점검 | `/verify-implementation` | 모든 `verify-*` 스킬을 순차 실행하여 통합 보고 |
+| New project or "where do I start?" | `/rules-product` | Diagnoses phase and delegates to the right skill |
+| Implement one feature | `/rules-product` then `/rules-workflow` | Gates must pass before coding |
+| Pre-PR / pre-release check | `/verify-implementation` | Runs the verify-* family in order |
 
-**가장 권장하는 시작 한 줄:**
+**Recommended first line:**
 
-```
+```text
 /rules-product
 ```
 
-`rules-product`는 프로젝트 상태를 스스로 진단해 현재 어느 단계인지 파악하고, 해당 단계의 올바른 스킬로 위임하는 오케스트레이터입니다. 새 프로젝트든 재개 중인 프로젝트든 동일하게 사용할 수 있습니다.
+### Orchestrator map
+
+```text
+rules-product  →  diagnose phase, check gates, delegate
+rules-workflow →  plan → implement → verify → PR (18 steps)
+verify-implementation →  run verify-* skills and report
+```
+
+Full pipeline, gates, backlog template, and all 26 skill entries: **[USAGE.md](./USAGE.md)**
+
+### Flow Status Block
 
-`rules-product` and `rules-workflow` should show a short Flow Status Block at the start of work, before implementation, before verification, and at handoff:
+`rules-product` and `rules-workflow` report progress in this format:
 
 ```text
 [Flow]
@@ -99,288 +130,44 @@ Gate: UI-First Gate 진행 중
 권장 스킬: /docs-plan
 ```
 
-### Using Skills in an Existing Project
+### Existing projects
 
-이미 진행 중인 프로젝트에도 최신 `solmate-skills`를 다시 설치해서 사용할 수 있습니다. 사용 방식은 신규 프로젝트와 같지만, 시작점은 항상 현재 프로젝트 상태를 먼저 진단하는 것입니다.
-
-**Update or reinstall skills from the project root:**
+Reinstall from the project root, then diagnose — do not restart from Phase 1 by default.
 
 ```bash
 npx solmate-skills@latest install all
 npx solmate-skills@latest install hooks
 ```
 
-**Recommended first prompt:**
-
-```text
-/rules-product를 사용해서 이 프로젝트의 현재 진행 상태를 진단하고, 다음 작업을 Flow Status Block 기준으로 안내해줘.
-```
-
-**When starting implementation work:**
-
-```text
-/rules-workflow를 사용해서 현재 기능 작업을 진행해줘. 먼저 Flow Status Block으로 현재 위치를 알려주고, UI-First 흐름에 맞춰 진행해줘.
-```
-
-**When verifying finished work:**
-
-```text
-/verify-implementation으로 현재 변경사항을 전체 검증해줘. Flow Status Block을 포함해서 보고해줘.
-```
-
-진행 중인 프로젝트에서는 Phase 1부터 강제로 다시 시작하지 않습니다. `/rules-product`가 기존 문서, 코드, 백로그, 변경사항을 보고 현재 위치를 진단한 뒤, 이어서 진행할 Phase와 필요한 Gate를 제안해야 합니다.
+Example prompts: [USAGE.md §9 Recommended Prompts](./USAGE.md#9-recommended-prompts) (EN) · [§9 권장 프롬프트](./USAGE.md#9-권장-프롬프트-모음) (KO)
 
 ---
 
-## Available Skills
-
-Skills are organized into five categories.
+## Skills at a Glance
 
-### Governance
+26 installable skills plus `hooks`. Category summary:
 
-| Skill | Description |
+| Category | Skills |
 |:---|:---|
-| `role-team-lead` | Team lead protocols: branch protection, PR review, DB migration, deployment. |
-| `role-team-member` | Team member protocols: branching, Conventional Commits (Korean), PR creation. |
+| Orchestration | `rules-product`, `rules-workflow` |
+| Rules | `rules-docs`, `rules-dev`, `rules-react`, `manage-collaboration`, `manage-decisions`, `manage-skills` |
+| Documentation | `docs-plan`, `docs-dev`, `docs-pitch`, `docs-business` |
+| Verification | `verify-implementation`, `verify-docs`, `verify-ui`, `verify-code`, `verify-security`, `verify-performance`, `verify-drizzle-schema`, `verify-skills` |
+| Roles | `role-team-lead`, `role-team-member` |
+| Tools | `tools-shadcn`, `tools-obsidian` |
+| External | `ext-awesome-design`, `ext-k-skill` |
 
-### Rules
-
-| Skill | Description |
-|:---|:---|
-| `rules-docs` | Master documentation rules and 365 Principle governance. |
-| `rules-dev` | Enforce development setup, coding conventions, and quality rules. |
-| `rules-react` | Create modular, premium React components and pages. |
-| `rules-workflow` | Full 18-step implementation and execution lifecycle. |
-| `rules-product` | Orchestrate the full product development pipeline. |
-| `manage-collaboration` | Enforce AI-Human collaboration standards. |
-| `manage-decisions` | Question-driven decision making for tech, DB, API, UX, and architecture choices. |
-| `manage-skills` | Detect and fix drift between verify skills and changed code. |
-
-### Documentation
-
-| Skill | Description |
-|:---|:---|
-| `docs-plan` | Create and manage **planning documents** (Layer 1-2: vision, UI screens). |
-| `docs-dev` | Create and manage **development documents** (Layer 3-5: specs, logic, QA). |
-| `docs-pitch` | Create pitch decks for investors, hackathons, and demo days. |
-| `docs-business` | Generate professional business plans for funding or partnerships. |
-| `verify-docs` | Audit documentation structure and metadata standards. |
-
-### Special Tools
-
-| Skill | Description |
-|:---|:---|
-| `tools-shadcn` | Expert guidance for shadcn/ui components. |
-| `tools-obsidian` | Sync documentation with an Obsidian vault. |
-
-### External Extensions
-
-| Skill | Description |
-|:---|:---|
-| `ext-awesome-design` | Premium design system and markdown templates. |
-| `ext-k-skill` | Collection of specialized Korean tools and services. |
-
-### Quality & Automation
-
-| Skill | Description |
-|:---|:---|
-| `verify-implementation` | Dynamically discover and run all `verify-*` skills. |
-| `verify-drizzle-schema` | Verify Drizzle ORM schema matches architecture specs. |
-| `verify-security` | Check for security vulnerabilities based on OWASP Top 10. |
-| `verify-performance` | Lighthouse & Core Web Vitals check. |
-| `verify-code` | Comprehensive pre-PR code quality review. |
-| `verify-ui` | Verify implemented UI against screen docs, HTML previews, and user flows. |
-| `verify-skills` | Verify skill package metadata, CLI output, and release readiness. |
+**Situation cheat sheet, per-skill when/prerequisites/outputs/next:** [USAGE.md](./USAGE.md)
 
 ---
 
-## Usage Guide
-
-### Documentation System
-
-The documentation system follows the **365 Principle** (3 Investor Lenses, 6 Rubrics, 5 Documentation Layers) and is split across two skills based on the type of document.
-
-**Which skill to use:**
-
-```
-Product vision, Lean Canvas, UI design  →  docs-plan
-DB schema, API specs, roadmap, QA       →  docs-dev
-Unsure which layer?                     →  rules-docs
-```
-
-**5-Layer structure:**
-
-```
-docs/
-├── 01_Concept_Design/   ← docs-plan
-├── 02_UI_Screens/       ← docs-plan
-├── 03_Technical_Specs/  ← docs-dev
-├── 04_Logic_Progress/   ← docs-dev
-└── 05_QA_Validation/    ← docs-dev
-```
-
-**Typical workflow:**
-
-```
-1. /docs-plan    → Write VISION_CORE.md, LEAN_CANVAS.md, PRODUCT_SPECS.md
-2. /docs-plan    → Write SCREEN_FLOW.md, UI_DESIGN.md, and HTML UI previews
-3. HTML UI Preview Gate → Show browser-viewable HTML screens and capture user feedback
-4. UI-First Gate → Confirm screens, user paths, data flow, and UI states before coding
-5. Pre-Code Technical Brief → Confirm data sources, API shape, state strategy, and acceptance criteria
-6. /docs-dev     → Write DEVELOPMENT_PRINCIPLES.md, DB_SCHEMA.md, API_SPECS.md
-7. /docs-dev     → Write ROADMAP.md, BACKLOG.md with mandatory related document links
-8. /rules-workflow → Implement each backlog item only after reading linked docs and passing UI-First Gate
-9. /verify-implementation  → Audit docs, UI, code, security, performance, DB, and skill package changes
-```
-
-Backlog items are intentionally document-linked. Each task in `docs/04_Logic_Progress/00_BACKLOG.md` must include related Concept, UI, Technical Spec, and QA documents, plus implementation preconditions, acceptance criteria, and a document sync check. If a related document does not exist, the item must say `N/A - 사유`; implementation should pause when the missing document is required for a safe decision.
+## Hooks (optional)
 
-### Backlog Context Lock
-
-Backlog Context Lock makes `docs/04_Logic_Progress/00_BACKLOG.md` act as a bridge between planning documents and implementation. A backlog item is not considered ready for coding until it names the documents that define why the task exists, how the UI should behave, what technical constraints apply, and how the work will be verified.
-
-### UI-First Gate
-
-UI-First Gate prevents implementation from starting before the team has reviewed the actual screens and the user's path through them. Before coding, confirm the core screen structure, user entry and exit paths, CTAs, screen-by-screen data flow, loading states, empty states, and error states. If these are missing, update `docs/02_UI_Screens/`, its HTML previews, or the backlog first.
-
-### HTML UI Preview Gate
-
-UI planning documents are not complete with Markdown alone. For every major screen or user flow, create a browser-viewable HTML preview and store it under:
-
-```text
-docs/02_UI_Screens/previews/
-```
-
-Recommended naming:
-
-```text
-docs/02_UI_Screens/previews/01_main_flow_preview.html
-docs/02_UI_Screens/previews/02_dashboard_preview.html
-```
-
-Each related UI document must link to the HTML file with a relative path. The preview must be shown to the user before implementation, and feedback must be captured in `XX_PROTOTYPE_REVIEW.md`, `00_SCREEN_FLOW.md`, `01_UI_DESIGN.md`, or the related backlog item.
-
-Required fields for every backlog item:
-
-- `Related Concept Docs`
-- `Related UI Docs`
-- `Related HTML Preview`
-- `Related Technical Docs`
-- `Related QA Docs`
-- `Implementation Preconditions`
-- `Acceptance Criteria`
-- `Document Sync Check`
-
-If a related document does not exist, write `N/A - 사유`. Do not leave the field blank. If the missing document is required to make a safe implementation decision, pause implementation and write or update the document first.
-
-**Backlog item template:**
-
-```markdown
-### [ ] TASK-000: Implement feature name
-
-- Status: ToDo
-- Related Concept Docs:
-  - [Product Specs](../01_Concept_Design/03_PRODUCT_SPECS.md) - feature purpose and user value
-- Related UI Docs:
-  - [Screen Flow](../02_UI_Screens/00_SCREEN_FLOW.md) - target screen and interaction flow
-- Related HTML Preview:
-  - [Main Flow Preview](../02_UI_Screens/previews/01_main_flow_preview.html) - browser-viewable UI for user review
-- Related Technical Docs:
-  - [API Specs](../03_Technical_Specs/02_API_SPECS.md) - endpoint and data contract
-- Related QA Docs:
-  - [QA Checklist](../05_QA_Validation/02_QA_CHECKLIST.md) - acceptance and release criteria
-- Implementation Preconditions:
-  - [ ] Read all related documents before coding
-  - [ ] Confirm screen/UI before coding
-  - [ ] Show the HTML UI preview to the user and capture feedback
-  - [ ] Confirm user path and screen-by-screen data flow
-  - [ ] Confirm loading, empty, and error states
-  - [ ] Confirm implementation scope does not conflict with documented intent
-- Acceptance Criteria:
-  - [ ] Feature follows the confirmed screen structure and user path
-  - [ ] Feature behavior matches linked Concept/UI/Technical docs
-  - [ ] QA criteria are testable and satisfied
-- Document Sync Check:
-  - [ ] No mismatch between implementation and linked documents
-  - [ ] Update related documents if implementation changes the agreed behavior
-```
-
----
-
-### Pitch Deck
-
-Create a pitch deck from existing `docs-plan` documents.
-
-**Prerequisites:** `docs-plan` Layer 1 documents (VISION_CORE, LEAN_CANVAS, PRODUCT_SPECS) should exist first.
-
-**Output modes:**
-
-| Mode | When to use | Output |
-|:---|:---|:---|
-| Markdown | Content-first, will export to Notion/Slides | `docs/01_Concept_Design/XX_PITCH_DECK.md` |
-| Reveal.js HTML | Present directly in browser, deploy to GitHub Pages | `pitch/index.html` |
-
-**Typical workflow:**
-
-```
-1. /docs-plan    → Ensure VISION_CORE, LEAN_CANVAS, PRODUCT_SPECS exist
-2. /docs-pitch   → Select output mode → Answer Phase 0-2 questions → Generate deck
-```
-
----
-
-### Development Workflow
-
-**Typical workflow:**
-
-```
-1. /rules-dev                → Review conventions before writing code
-2. /rules-product            → Orchestrate the development pipeline
-3. /verify-implementation    → Run all verify-* skills before PR
-4. /manage-collaboration     → Check branch naming, PR format, and workflow status
-```
-
----
-
-### Governance
-
-**Role-based skills** define protocols for team lead and team member roles:
-
-```
-/role-team-lead    → Branch protection, PR review, DB migration, deployment
-/role-team-member  → Branching, commits (Conventional Commits in Korean), PR creation
-```
-
----
-
-### Proactive Skill Suggestions (Hooks)
-
-Install hook scripts so Claude **automatically suggests** the right skill as you work — without needing to invoke them manually.
-
-**Two layers work together:**
-
-| Layer | Mechanism | Trigger |
-|:---|:---|:---|
-| Method 1 | AGENTS.md rules | Claude judges context and suggests skills by reasoning |
-| Method 2 | Hook scripts | Keyword/file-pattern matching fires on every prompt or file edit |
-
-**Install hooks into your project:**
+For Claude Code, install hooks to get keyword and file-pattern skill suggestions:
 
 ```bash
-# 1. Install the hooks skill first (if not already installed)
-npx solmate-skills install hooks
-
-# 2. Run the installer from your project root
+npx solmate-skills@latest install hooks
 bash .agent/skills/hooks/install.sh
 ```
 
-This copies two scripts to `.claude/hooks/` and merges the hook config into `.claude/settings.json`:
-
-| Script | Event | What it detects |
-|:---|:---|:---|
-| `solmate-suggest.sh` | UserPromptSubmit | Keywords: 결정/설계, 보안, 성능, PR, 코드리뷰, 문서, 기능구현, 피치덱, 새 프로젝트 |
-| `solmate-watch.sh` | PreToolUse | File patterns: `schema.ts`, `.env*`, `SKILL.md`, `page.tsx`, `api/route.ts`, `auth.ts`, `AGENTS.md` |
-
-**To review or disable hooks:** open `/hooks` in Claude Code.
-
-**To uninstall:** remove `.claude/hooks/` and the `hooks` section from `.claude/settings.json`.
+Details: [USAGE.md §8 Hooks](./USAGE.md#8-hooks-claude-code-suggestions) (EN) · [§8 Hooks 한국어](./USAGE.md#8-hooks-claude-code-자동-제안) (KO)