sujeet-pro
UserA plugin system for Claude Code that adds skills, agents, guidelines, repo-aware configurations, and MCP integrations to supercharge your development workflow.
Categories
Indexed Skills (10)
diagramkit
Create, render, embed, and audit diagrams in any repo that uses diagramkit. Triggers on "draw / create / render / re-render / embed / audit a diagram", "fix diagram contrast / WCAG warnings", "run the repo-wide diagram health check", or any mention of a diagramkit engine (mermaid / excalidraw / draw.io / graphviz). Writes diagram sources, rendered SVGs, and the light/dark embed markup into the LOCAL repo and runs the local diagramkit CLI (doctor / skills install / render / validate); it never commits, pushes, or publishes — it stops at local files. Version-sensitive authoring detail (engine choice, palettes, readability budgets, config schema) is NEVER restated here — it is delegated to the consumer's installed copy at node_modules/diagramkit/skills/*. Routes broader Pagesmith content / site / deploy work to /adk:pagesmith; the repo-wide audit runs diagramkit's own review flow.
document
Draft a technical document from an intent or a source. Triggers on "write the runbook / ADR / RCA / PR description / commit message / changelog / diagram / README / migration guide / API reference / experiment report / incident summary / onboarding doc / design doc". Markdown-first: produces a draft in a local file and NEVER publishes (no Confluence / Jira / Slack / GitHub posting — that is a separate concern). Reader-first voice: leads with the reader's question, cites every non-trivial claim to a repo path or quoted source, caps external quotes at 15 words, cuts filler. Audience-tuned (engineer / pm / exec / mixed) — the voice does not mix. GitHub context (PR / issue) is read via the gh CLI.
implement
Implement, build, ship, or wire up a change in an existing repo. Polymorphic on input: a Jira URL/KEY-123, a GitHub issue URL or #N (fetched via the gh CLI), a Confluence/Slack link (fetched via MCP), or freeform "build the X" prose. Plans before it acts: gathers context, presents 2-4 approaches with trade-offs, confirms, then writes the smallest correct change matching repo conventions, with tests for new behavior. Validates with the repo's own typecheck/lint/narrow tests at every checkpoint. Git via git directly (feature branch, never protected, never force, never merge); GitHub via the gh CLI only (PRs via gh pr create); clones SSH-only.
investigate
Investigate, diagnose, RCA, "why is X slow/broken/down", "what changed" for any production symptom. Triggers on a free-text symptom + service, a Datadog incident/monitor/dashboard/log URL, a Slack alert permalink, a Statsig gate/experiment URL, or a Mixpanel/Snowflake/Looker question. Read-only — never modifies a monitor, dashboard, flag, or experiment, and never triggers a rollback or restart (recommends; the human executes). Pins an explicit time window on every query, correlates >=2 independent signals before naming a root cause, and states confidence (low/med/high) with anchored evidence and <=15-word verbatim quotes. Produces a timeline + hypothesis + a lowest-blast-radius next action.
pagesmith
Build, extend, or maintain an EXISTING Pagesmith site (or a @pagesmith/* package itself) — author pages, configure nav / theme / search, validate, and deploy. Triggers on "add a docs page / write a guide / document this in Pagesmith", "configure the sidebar / nav / theme / search", "build / validate / deploy the Pagesmith site", or working on @pagesmith/core|site|docs. Detects the site flavor (docs-preset via `pagesmith.config.json5` vs core-native via `site.config.json5`) and then delegates the deep authoring to the CONSUMER'S version-matched package skills under node_modules — it NEVER restates package config schemas, frontmatter fields, or CLI flags from memory. Writes content + config and can deploy, but is read-only until a plan is confirmed and the gh-pages push is gated. Routes diagram work to /adk:diagramkit and greenfield scaffolding to /adk:scaffold-pagesmith-docs.
pr-review
HEAVYWEIGHT, GitHub-only deep PR review. Takes a GitHub PR URL, prepares a read-only git worktree at the PR head (SSH clone only), and reviews the diff with full cross-file context via Read/Grep/Glob. Fans out one agent per dimension (correctness, security, tests, performance, api, docs, observability, concurrency, feature-flow) through the Workflow tool, then adversarially verifies every finding before it survives. Traces feature flags / experiments via the statsig MCP and pulls linked Jira/Confluence via the atlassian MCP. Posts inline review comments, a review summary, and appreciations through the gh CLI after confirmation. NEVER merges, never force-pushes, never edits the PR's code. For a quick read-only pass with no worktree, use /adk:review.
review
Review, audit, sanity-check, look-at any review-able target. Triggers on a GitHub PR URL (fetched via the gh CLI), a local path or "." (review the working tree), a markdown/doc file, or a comment-thread URL. Read-only by default; --fix applies accepted findings locally and pushes to the PR branch after confirmation (never force, never merge, never to a protected branch). Produces severity-tiered findings (blocker / critical / should / may / nit) with path:line and <=15-word verbatim evidence quotes. Six dimensions: correctness, tests, security, performance, readability, consistency. For a deep PR review with cross-file code-context retrieval, use /adk:pr-review.
scaffold-pagesmith-docs
Stand up a brand-new Pagesmith documentation site from nothing — @pagesmith/docs wired to diagramkit, sample content, package skills installed, ending on a running preview. Triggers on "scaffold / bootstrap / stand up / start / create a new docs site", "new Pagesmith docs from scratch", "set up a docs site with diagrams". Writes to disk and runs local tooling (npm install, skills install, site build, dev server) — it configures a deploy target but NEVER deploys, pushes, or opens a PR; it prints the deploy command for a human to run. Confirms before touching an existing pagesmith.config. This is the greenfield counterpart to /adk:pagesmith (use that for an EXISTING site) and hands diagram-only work to /adk:diagramkit. It restates no package config schema, no engine flags, no palette — every version-sensitive authoring detail is delegated to the consumer's installed skills under node_modules.
slack-post
Post or send a message to Slack — a channel, DM, or thread reply. Triggers on "post / send / message / DM / reply / drop this in Slack", "tell #channel", "ping @someone on Slack", or any request to write into Slack (as opposed to reading/searching it). Governs posting IDENTITY: posts as YOU (user token) by default, and as the BOT only when the prompt says so ("as the bot", "use the bot", "post as the app"). Every Claude-sent message gets a "Sent using Claude" footer. Read-only Slack work (search, history, who's-in-a-channel) does NOT use this skill.
prj-add-adk-skill
Add a skill to the adk plugin, create a new /adk: command, modify an existing adk skill's workflow / rules, or register a skill in the marketplace. Derives the house convention from the repo itself (AGENTS.md, SAFETY.md, existing skills) rather than memory. Writes repo files only — never publishes, never commits.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.