CodeWithJuber
UserOne config for every AI coding agent — cross-tool config + a cognitive substrate (memory, blast-radius, guardrails) for Claude Code, Codex, Cursor, Gemini, Aider, and more.
Categories
Indexed Skills (19)
code-modernizer
Modernize or refactor a legacy codebase incrementally while preserving business logic. Replaces hand-rolled logic with the standard library, a native feature, an already-installed dependency, or (only after live research) a well-vetted new package, then applies minimal design patterns to whatever custom code remains. Confirms scope first (full-codebase, one module/partial, or only the exact lines named) and flags file count, line count, and breaking-change risk before generating a large diff, asking instead of assuming when scope, a library choice, or a behavior change is unclear. Use for migrations (framework/language/version upgrades), killing tech debt, refactoring an old project, or "bring this up to date". Use whenever the user asks to refactor, modernize, de-bloat, clean up, simplify, upgrade, or audit code; asks "is there a library for this", "don't reinvent the wheel", "replace with a framework", "reduce boilerplate", or "apply proper design patterns"; wants a root-cause fix over a quick patch; says "
dev-radar
Pull current, real-world software-dev signal on demand from GitHub trending, Reddit, research papers, and blogs — filtered to the user's stack, hype-filtered, with verified sources. Use when the user asks "what's new/trending", "latest in <tech>", "should I adopt X", or wants a dev digest. Coding topics only.
hostlelo-deploy
Safe, staged deploy of Hostlelo services to the VPS. Use when asked to deploy, ship, or release a Hostlelo change (kernel, widget, or Telegram control plane).
cognitive-substrate
Use before ambiguous, expensive, multi-file, or mutating coding work to run Forge's cognitive substrate: assumption gate, model routing, impact prediction, scope decomposition, memory/lesson lookup, minimality check, and verification planning. Trigger when a user asks to edit/refactor/fix/design production code, integrate features, choose model effort, inspect blast radius, or avoid agent assumptions.
cost-guard
Reduce token/cost burn on large or exploratory tasks. Use when a task will touch many files, involves broad codebase search, a big migration, or when the user asks to keep cost/context low.
problem-solver
Universal problem-solving engine that fuses proven frameworks (ASQ 4-step cycle, DMAIC/PDCA, 5 Whys, Fishbone, First Principles, TRIZ, Cynefin, Design Thinking, weighted decision matrix) into one staged loop. Use when the user asks to solve, analyze, or break down a problem, find root causes, choose between options, innovate, make a hard decision, handle a crisis, or wants structured/step-by-step problem solving.
reuse-first
Engineering standards for writing production code — reuse before building, follow existing patterns, testable/reusable design, and verify. Use for any non-trivial feature, refactor, or "add X" task, and when choosing what to build vs. adopt.
self-improve
Self-correction and cross-session learning loop. Use when a check fails and needs iterating to green, when the user corrects the same thing more than once, or when a non-obvious fix/gotcha is worth remembering for next time.
ui-workflow
Reliable workflow for building or fixing UI so results look intentional, not generic. Use for any frontend/UI task — new screen, component, redesign, "make it look better", layout, styling, or when the user says UI is the pain point.
atlas
Forge's code-graph. Use to find where a symbol is defined (where-is-X), to discover reusable code before writing new, and to check a symbol actually exists before calling it (anti-hallucination). Backed by `forge atlas`.
catchup
Start-of-session context rebuild. Use when resuming work in a repo after a gap, a /clear, or a machine switch — "where were we?" answered from recorded state (goal, session snapshot, decisions, recent commits) instead of assumptions.
design-md
Create and maintain a per-project DESIGN.md that pins the ONE visual direction so UI stays consistent across sessions and screens. Use when starting UI on a project, when look feels inconsistent, or the user mentions design system / DESIGN.md / visual guidelines.
explore-plan-code
Structured workflow for non-trivial features or unfamiliar code — explore, then plan, then implement, then verify. Use when a change spans multiple files, the approach is uncertain, or the user asks for a spec/plan first.
handoff
End-of-session checkpoint. Use when finishing, pausing, or switching away from work in a repo — it rewrites the bounded session snapshot (.forge/state.md) the NEXT session is re-injected with, so nothing essential dies with this conversation. Backed by `forge handoff`.
lean
Forge's minimalism discipline. Use for any "add X" / "build Y" / refactor / bug-fix — before writing code, to choose the smallest change that actually solves the problem. Reuse over rewrite, delete over add, boring over clever.
recall
Forge's cross-session memory. Use when the user says "remember this", when you learn a durable non-obvious fact/decision/gotcha worth keeping, or to recall past context. Backed by `forge recall` + the recall-load guard.
sync-docs
After ANY code change, sweep the diff for documentation that just went stale. Use when finishing an edit, before a commit/PR, or when the completion gate blocks — it turns "did I forget a doc?" into a mechanical checklist. Backed by `forge docs sync`.
taste
Pick a visual design direction for a repo from Forge's menu (minimalist, brutalist, editorial, playful, corporate). Use when starting UI work or when the user wants a specific look. Sets DESIGN.md, which every AI tool then follows.
tech-selector
Choose a library, framework, or tool by verifying the CURRENT best option from live sources — not from training data. Use whenever picking a dependency, starting a project, or the user asks "what's the best X for Y", "latest", "which library", or wants an unbiased/current recommendation.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.