agent-tooling

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

any input (code, docs, papers, images) - knowledge graph - clustered communities - HTML + JSON + audit report

Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.

Build any of THREE self-contained, offline, single-file project-site types from a data JSON, all sharing ONE stylesheet (the Ramco Nebula / RXD design language — brand blue #316ADD, Inter-Tight + JetBrains-Mono, light + dark) so they read as one product: (1) DOCS — a documentation / reference / guide site with a sticky grouped sidebar + scrollspy, code blocks with copy, callouts, kv/step/table blocks and client-side Mermaid diagrams; (2) TRACKER — a status / progress / standup / milestone / KPI dashboard with stat tiles, progress bars, a resource-exchange, a calendar month-grid, a daily timeline, AND a dated log archive ingested from the project's journal files; (3) TUTORIAL — a multi-section field-course / explainer / onboarding / walkthrough with a hero, topic cards, hash-routed section pages and Mermaid diagrams. Use this whenever someone wants to make, set up, or KEEP UPDATING a docs site, a reference/guide/handbook, a status tracker or progress/delivery/sprint dashboard, a milestone or KPI board, a daily-updates/changelog/standup page, a shared-materials/resource-exchange page, a tutorial or field course, an explainer, or "a self-contained single-file docs/tracker/tutorial page". It prefers the HOST PROJECT's own stylesheet and theme when one exists (the skill's sheet is the fallback), can inherit an app's global CSS when embedded as a route, ingests mistakes.md/learnings.md/worklog.md into the tracker as a dated archive, and can OPTIONALLY password-gate any page (client-side AES-256-GCM, no server). NOT for a live dashboard over a database/API (build a real app) or arbitrary charts (use a charting tool).