Help us improve
Share bugs, ideas, or general feedback.
From stack
Stack decision table for routing work across kern, git-fs, vicky, Context7, pdf-reader, skills. Trigger when user says "follow stack routing", "route this", "which tool", or starts work in a stack-enabled project.
npx claudepluginhub yesitsfebreeze/stack --plugin stackHow this skill is triggered — by the user, by Claude, or both
Slash command
/stack:routingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Apply silently. Don't narrate unless asked.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes provided content for SEO quality, E-E-A-T signals, readability, keywords, and structure. Scores and recommends improvements based on best practices.
Share bugs, ideas, or general feedback.
Apply silently. Don't narrate unless asked.
| User signal | Route | Why |
|---|---|---|
| Library/SDK name + "how do I…" / API syntax / version migration | Context7 resolve-library-id → query-docs | Versioned, current. Training data drifts. |
| PDF file or URL → extract text/images/metadata | pdf-reader read_pdf | Native PDF; supports page ranges, batch, HTTP. |
| Project-internal "where is X" / "what does our code say about Y" | Grep/Glob; index via vicky if recurring | No kern in this stack |
| "Latest" / "current" / "in 2026" / open research | vicky query → if gap: web-search → remember | Persistent across sessions |
| Code review, refactor, "where is X called" | codegraph (if installed); else Grep | Structural > textual |
| Two+ parallel agents, throwaway experiment | git-fs git_fs_branch_create | Isolation w/o working-tree cost |
| External tool needs working tree (build/lint/LSP) | native worktree EnterWorktree | git-fs is object-only |
| Long session, context bloating | /compact or /clear + vicky recall of key facts | No kern surgical prune |
| Pure observability / logging | hook with discard injection mode | Zero context cost |
| Recurring specialized task | propose new skill | Auto-trigger amortizes setup |
Read whole file just to analyze → Grep or codegraphWebFetch library docs → Context7Read on .pdf → pdf-reader read_pdf (Read returns garbage on binary)vicky.query firstdiscard mode1. vicky.query (research KB)
2. context7.query-docs (library docs)
3. pdf-reader.read_pdf (PDF files / URLs)
4. codegraph (structural code, if installed)
5. Grep / Glob (raw search)
6. Read (only when editing)
7. WebSearch (only after vicky gap signal)
8. WebFetch (only for non-library content not in vicky)
question arrives
├─ about library API? → Context7
├─ involves a PDF? → pdf-reader
├─ about our project? → Grep / Glob
├─ "latest" / external? → vicky → web-search if gap
├─ code structure? → codegraph / Grep
└─ writing/editing files?
├─ multi-agent? → git-fs branch
├─ tool needs tree? → worktree
└─ solo, simple? → direct Edit