メニュー
Record lessons learned and experiences for future reference. Use after solving bugs, discovering patterns, making decisions, or completing complex features.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Commit code changes with well-structured messages following Conventional Commits. Use when ready to commit after implementation or bug fix.
Review code for quality, bugs, security, and improvements. Use when self-reviewing before commit, reviewing PRs, or debugging issues.
Create design documents for features or systems. Use when architecture planning, API design, or technical decisions are needed before implementation.
Create distinctive, production-grade frontend interfaces. Use when building web components, pages, dashboards, React components, HTML/CSS layouts, or styling any web UI. Generates creative, polished code that avoids generic AI aesthetics.
Create structured requirement documents from user ideas. Use when capturing new features, tasks, or user stories that need documentation in requirement/INDEX.md.
Guide for creating effective skills. Use when creating a new skill or updating an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
| name | experience-record |
| description | Record lessons learned and experiences for future reference. Use after solving bugs, discovering patterns, making decisions, or completing complex features. |
Capture valuable lessons for future reference.
| Tag | Use For |
|---|---|
[BUG] | Bug solutions |
[PATTERN] | Successful patterns |
[PITFALL] | Things to avoid |
[DECISION] | Important choices |
[PERF] | Optimizations |
# [CATEGORY] Title
## TL;DR
[One sentence]
## Problem
[What was the issue]
## Solution
[How it was solved]
## Code Example
```language
// Before (bad)
...
// After (good)
...
[How to avoid in future]
#tag1 #tag2
## Example
```markdown
# [BUG] Null Pointer in User Query
## TL;DR
Check for null before accessing user properties.
## Problem
API crashed on non-existent user.
## Solution
Added null check and 404 response.
## Prevention
- Unit tests for null cases
- Use Optional types
wiki/experience/
├── bugs/
├── patterns/
└── decisions/