メニュー
Synchronize patterns from docs/**/findings.md to CLAUDE.md and skill documentation. Use when updating specs, consolidating learnings, preventing outdated documentation, or running /findings-sync command.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Add a selectable planner keyword end-to-end across FE, BE, and i18n with the proper in-game translation. Use when adding a plan keyword, synergy keyword, faction keyword, or a value to the planner keyword filter.
Add a new announcement to all 5 JSON files with auto-translation, commit, and tag. Use when adding announcements, writing update notices, or posting new content.
Full commit workflow — pre-commit validation, branch creation, commit message writing, staging, and checkout. Use this skill whenever the user asks to commit, create a commit, write a commit message, stage changes, finalize work, or prepare code for a PR. Also triggers on phrases like "commit the change", "ready to commit", "let's commit this", "wrap this up", or any git commit-related request.
Create and manage Claude Code skills. Use when creating skills, modifying skill-rules.json, or debugging activation.
Interview simulator that tests understanding of architectural decisions. Asks "why" questions, gives hints instead of answers, probes deeper on correct responses. Supports topic-based and random code quiz modes.
| name | findings-sync |
| description | Synchronize patterns from docs/**/findings.md to CLAUDE.md and skill documentation. Use when updating specs, consolidating learnings, preventing outdated documentation, or running /findings-sync command. |
Extract patterns, recommendations, and learnings from docs/**/findings.md files and update the corresponding skill documentation to keep specs current and prevent knowledge decay.
/findings-sync command┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ 1. COLLECT │────▶│ 2. ANALYZE │────▶│ 3. PROPOSE │
│ Scan findings │ │ Extract & diff │ │ Generate diffs │
└─────────────────┘ └─────────────────┘ └─────────────────┘
│
▼
┌─────────────────┐
│ 4. APPLY │
│ Update skills │
└─────────────────┘
Files are processed by recency (higher directory numbers = newer):
docs/tasks/006-planner-creation/08-skill-replacement/ (newest)
docs/tasks/006-planner-creation/07-comprehensive-ego-gift-list/
docs/tasks/005-code-refactoring/...
docs/tasks/004-ego-gift-browser/...
... (older)
| Section | Purpose | Target |
|---|---|---|
| Pattern Recommendations | New patterns to document | Skill resources |
| Key Learnings | Important discoveries | CLAUDE.md or skills |
| Things to Watch | Potential issues | Skill warnings |
| Next Time | Process improvements | Workflow docs |
1. Frontend Patterns → frontend-dev-guidelines
2. Backend Patterns → backend-dev-guidelines
3. Process Patterns → CLAUDE.md
4. Cross-cutting Patterns → CLAUDE.md or new skill
Compare extracted patterns against current documentation:
Pattern: "Set mutation after spreading for React state"
├── Found in: 07-comprehensive-ego-gift-list/findings.md
├── Current skill: frontend-dev-guidelines/component-patterns.md
└── Status: MISSING - needs to be added
## Findings Sync Report
### Summary
- Findings scanned: 8 (06-01 through 06-08)
- New patterns found: 6
- Already documented: 2
- Conflicts: 0
### Proposed Updates
#### 1. frontend-dev-guidelines/resources/component-patterns.md
**Add section: State Mutation Safety**
```typescript
// CORRECT: Create new Set for React state updates
setSelectedIds(prev => new Set([...prev, newId]))
// WRONG: Mutating existing Set
selectedIds.add(newId) // React won't detect change
setSelectedIds(selectedIds)
Source: 07-comprehensive-ego-gift-list/findings.md
Add to Pre-Write Checklist:
accessibilityChecked - Verify keyboard nav, ARIA labels before implementation
Source: 05-start-gift/findings.md, 07-comprehensive-ego-gift-list/findings.md
---
## Step 4: APPLY - Update Documentation
### Application Order
1. **CLAUDE.md** - Global rules first
2. **SKILL.md** files - Domain-specific guidance
3. **resources/*.md** - Detailed patterns
### Conflict Resolution
If a pattern conflicts with existing documentation:
1. Keep the more recent/specific version
2. Note the conflict in the sync report
3. Ask user for resolution if critical
---
## Pattern Extraction Templates
### From "Key Learnings"
Finding: "React Compiler eliminates manual optimization" → Skill Update: component-patterns.md → Content: Remove references to manual useCallback/useMemo
### From "Pattern Recommendations"
Finding: "Document hover-overlay pattern: TierLevelSelector + enhancement selector" → Skill Update: common-patterns.md → Content: New section "Hover Overlay Pattern" with code example
### From "Things to Watch"
Finding: "State synchronization risk: Enhancement state exists in multiple places" → Skill Update: component-patterns.md → Content: Warning box about state duplication anti-pattern
---
## Automation Hooks (Future)
### Option A: Post-task-code Hook
```typescript
// After /task-code completes, if findings.md was created/modified:
// → Prompt: "New findings detected. Run /findings-sync?"
# If findings.md in staged files:
# → Run sync analysis, warn if patterns not reflected in skills
/findings-sync - Run full sync workflow/findings-sync --dry-run - Show proposed changes only/findings-sync --from=06 - Sync only from specific directory prefixdocs/**/findings.md - Source of patterns.claude/skills/*/SKILL.md - Target documentation.claude/skills/*/resources/*.md - Detailed pattern docsCLAUDE.md - Global project rules