MohanTn
UserPersonal dotfiles and configuration for Claude Code, tmux, and Neovim
Categories
Indexed Skills (9)
chrome-devtools-axi
Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance. Use whenever a task needs a real browser: opening or testing a web page, clicking through a flow, extracting page content, or debugging a website.
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
arch
Take a system or project the user has in mind and turn it into an architecture & solution plan (arch-<slug>.html) — a working, editable document covering project overview, system context, containers, integrations, data model, ADRs, quality attributes, security, deployment, risks, and roadmap, all grounded in the actual repo. Use when the user asks for an architecture plan, solution design, system overview, or says "arch".
feature-plan
Take a feature the user has in mind and turn it into a co-authored, code-level feature implementation plan (featurePlan-<slug>.html) — file-by-file change manifest in build order, pseudo-code, edge cases, and open questions the human decides, all grounded in this repo's actual code. The user resolves questions and edits sections in the browser; exported human edits are tagged and override the AI draft. Use when the user asks for a feature implementation plan, a code-level breakdown, or says "featurePlan".
graphify
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
scaffold-pack-author
Author an in-tree scaffold-toolkit template pack for the repo you are in — any language, any architecture. Asks whether the repo intends to migrate toward a different target architecture (author a second, additive pack if so) and splits out external/infra packages (cloud SDKs, message brokers, secret managers) into their own packs. Study the repo's recurring pattern, turn one real instance into a versioned pack (Handlebars templates + descriptor + AI_IMPLEMENTATION markers + registry injections + test_data + a real build-check), wire the markers into the existing brownfield files, and point `.scaffold/config.json` at it so the pack lives in the repo's own git tree and the team maintains its coding standards there. Use when the user says "author/create a scaffold pack", "make a pack for this repo", "cut a new pack version", or "wire scaffold into this codebase". This is the producer side; the `scaffold` skill is the consumer side that runs `generate`.
scaffold
Drive @mohantn/scaffold-core for deterministic boilerplate scaffolding (DTOs, endpoints, services, route registration, frontend API clients) from a configured template pack when the user's request splits into "boilerplate the CLI can render" + "logic only the user can describe." Use when the user is adding or extending a new file/resource/service that follows an existing target-stack pattern. Skip when the task is mostly modifying existing implementations, or is fully bespoke code with no target-stack boilerplate to render.
token-efficiency
Audit and optimize token consumption in Copilot CLI configs agent prompts, skill files, and hook injection scripts. Use when reviewing config for redundancy, narrative bloat, or per-turn hook costs.
repo-map-check
Check .claude/repo-map.md for cached file inventory before running filesystem queries.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.