메뉴
Keeps idev skill caches fresh after source files are created, deleted, or renamed. Use after structural file changes or when the user says refresh caches.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Senior backend architect for system design decisions — service decomposition, database schema design, API contract governance, migration strategy, reliability and observability patterns. Use when designing a new backend system or service, choosing between monolith/microservices, designing schemas or APIs, or planning a data migration. Advisory only — produces specifications, does not write code.
Branch synchronization agent — merges the team base branch into the current feature branch before a PR, resolves merge conflicts with three-way evidence and intent analysis, verifies the merge with a build and targeted tests, and reports what was merged and how each conflict was resolved. Use when preparing a branch for a PR, when a PR has conflicts with its target, or when asked to sync/update a feature branch with developer/main.
Browser testing agent — verifies web features and user flows end-to-end by writing and running re-runnable Playwright scripts, capturing screenshot/console/network evidence, and producing structured test reports. Use when a UI change needs real-browser verification, a user flow needs smoke testing, a UI bug needs reproduction, or the user asks to test the site in a browser and report results.
Expert code reviewer providing constructive, prioritized feedback on correctness, security, maintainability, performance, and test coverage — not style preferences. Use when reviewing a diff, branch, or PR for general quality. For a security-only deep audit, use the security-reviewer agent instead.
Expert frontend developer for building and improving web UI — components, state management, responsive layouts, accessibility, and Core Web Vitals performance. Use when implementing UI features or component libraries, fixing layout/responsiveness issues, improving accessibility compliance, or optimizing bundle size and page performance.
"Codebase onboarding specialist — builds fast, accurate mental models of unfamiliar repositories by reading source, tracing execution paths, and stating only facts grounded in inspected code. Use when onboarding into a new codebase, asking "where should I start", "what owns this behavior", or "how does a request flow through this system". Strictly read-only and descriptive — no reviews, refactors, or recommendations."
| name | cache-refresh |
| description | Keeps idev skill caches fresh after source files are created, deleted, or renamed. Use after structural file changes or when the user says refresh caches. |
Keep all skill caches fresh by detecting when source files change and triggering targeted cache updates. Prevents stale data from causing wrong file paths, missing registrations, or outdated function line numbers.
Note: skills do not run at session start. The session-start hook surfaces cache ages; this skill defines what to do when the user or another skill asks for a refresh (for example, after the hook reports stale caches).
This skill does NOT use a file watcher daemon. Instead, it hooks into Claude's own actions — every time Claude creates or modifies a file, this skill updates the relevant caches incrementally.
After Claude creates, renames, or deletes a source file, determine which caches are affected:
File change → Affected caches:
New .cs file (Entity) → file-index, backend-patterns (Function Index), post-creation-verify
New .cs file (Controller) → file-index, architecture-scanner (apiRoutes), backend-patterns
New .cs file (Service) → file-index, backend-patterns
New .tsx/.ts file → file-index, frontend-patterns (Function Index)
New .service.ts file → file-index, architecture-scanner (apiRoutes)
New .hook.ts file → file-index, frontend-patterns
New route added → architecture-scanner, file-index
DI registration changed → post-creation-verify (registration points may shift)
DbContext changed → post-creation-verify (registration points may shift)
Any file deleted → file-index (remove entry), pattern cache Function Index (remove entry)
1. Add new files to file-index/index.md under the correct feature section
2. Add new API routes to architecture-scanner/cache.json apiRoutes
3. Add new function entries to pattern cache Function Index sections
4. Update post-creation-verify registration points if DI/DbContext files were modified
5. Update session-resume recentFiles.modified list
6. Update task-journal with completed task
1. If function was added/removed → update Function Index entries
2. If DI file was modified → update post-creation-verify registration points
3. If route was added → update architecture-scanner apiRoutes
1. Remove from file-index
2. Remove from architecture-scanner apiRoutes (if controller/service)
3. Remove function entries from the pattern cache Function Index
When a refresh is requested (or the session-start hook has flagged old caches), check what is actually stale:
1. Read each cache's "generated" date
2. If older than 7 days → mark for full refresh
3. If git is available: run `git log --since="CACHE_DATE" --name-only --pretty=format:""`
→ Get list of files changed since cache was generated
→ If changed files overlap with cached paths → mark for targeted refresh
4. If no git: compare cache date only
Fresh (< 1 day old, no conflicting changes): Use as-is
Stale (1-7 days, minor changes): Incremental update
Expired (> 7 days): Full rescan
When triggered by user ("refresh caches") or expiry:
1. Regenerate file-index/index.md (scan all features)
2. Regenerate architecture-scanner/cache.json (scan routes)
3. Regenerate backend-patterns function-index (scan key files)
4. Regenerate frontend-patterns function-index (scan key files)
5. Regenerate post-creation-verify/cache.json (rescan DI line numbers)
6. Regenerate build-check/cache.json (rescan build commands)
7. Update all "generated" dates
Run these as parallel agents for speed.
After every file creation/modification by Claude:
1. cache-refresh determines which caches are affected
2. Updates them incrementally (add/remove entries)
3. No full rescan needed for single-file changes
When the session-start hook reports cache ages:
1. If a refresh is warranted, run the staleness check (~1 grep command)
2. If stale → targeted refresh
3. If fresh → use as-is