From siftcoder
Use to regenerate architecture/component diagrams after structural changes. Companion to /codemap. "Refresh the architecture map", "diagrams are stale".
How this skill is triggered — by the user, by Claude, or both
Slash command
/siftcoder:update-codemapsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Regenerate architecture diagrams. Detects what changed; redraws what needs redrawing.
Regenerate architecture diagrams. Detects what changed; redraws what needs redrawing.
Diagrams found:
- ARCHITECTURE.md (Mermaid)
- docs/data-flow.mmd
Drift since last gen (date: <last>):
+ Added: src/services/ (4 new modules)
- Removed: vendor/sift-compress/ (extracted to companion)
~ Restructured: skills/ (subdirs for families)
Updated:
✓ ARCHITECTURE.md — added services/ block, removed vendor/ block
✓ docs/data-flow.mmd — no change (data flow unchanged)
Verification:
✓ All depicted nodes exist in repo
✓ All major modules represented
✓ Memorialised: <commit SHA>
/siftcoder:knowledge can then track diagram drift over time.Explore for current structuregeneral-purpose for diagram editingCC will draw diagrams. CC won't naturally do incremental regen, drift detection vs last snapshot, or verify all depicted nodes exist. The incremental discipline IS the value.
npx claudepluginhub ialameh/sift-coder --plugin siftcoderGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.