UI Design & Agent Automation Skills

Use when a developer asks what a Bittensor subnet does, whether it's up right now, or how to call/integrate its API — e.g. "which subnet does image generation", "is subnet 7 healthy", "how do I call the Chutes API", "build on a Bittensor subnet". Backed by metagraphed (api.metagraph.sh), the live operational + integration registry for ~129 subnets.

Maintenance of the contributor issue pipeline for JSONbored/metagraphed — closing issues that are already done but not marked so, and keeping the contributor-available backlog at its 50-100+ steady-state floor with well-scoped new issues. Runs every ~8h via the scheduled task (raised from daily on 2026-07-15 so the floor is maintained continuously, not caught up once a day). Invoke for "run the issue gardening", "audit open issues for stale/complete ones", "generate new contributor issues", or any recurring/scheduled run of this process. reference.md (next to this file) has the exhaustive label/milestone/template detail — read it before doing real work, not just this file. This is the metagraphed-specific instance; JSONbored/gittensory (loopover) has its own separate copy with different conventions — do not cross-apply either repo's specifics to the other without being asked.

Systematic visual QA sweep of the live metagraphed frontend (apps/ui, served at metagraph.sh) — actually browsing pages at real viewports and looking for defects only visible on inspection (crowding, overflow, truncation, misalignment), not catchable by reading code or trusting a PR's own screenshot table. Produces precise, root-caused GitHub issues a contributor's AI coding agent can act on correctly without needing design judgment of its own. Invoke for "run a visual QA sweep", "find real UI/UX bugs", "check the site for mobile/tablet crowding issues", or any request to audit the live frontend for visual defects. Distinct from the metagraphed skill (which covers writing a contribution) and code-review (which reviews a diff, not live rendered output) — this skill's whole point is that a defect can look completely correct in code and still be visually broken.

Add PostHog MCP analytics to a TypeScript, JavaScript, or Python MCP server. Instruments the server so every tool call, agent intent, and failure is captured as a $mcp event — the @posthog/mcp Node SDK for TS/JS, or posthog.mcp (shipped inside the posthog package) for Python. Detects the server style (official MCP SDK Server/McpServer/FastMCP, mcp-handler, @rekog/mcp-nest, jlowin fastmcp, or a custom HTTP/edge dispatcher) and wires in the matching instrumentation, credentials, and graceful shutdown.

Use when writing, validating, or preparing ANY contribution or pull request to the JSONbored/metagraphed repo — adding/enriching a subnet's public surfaces (the most common contribution), a code/schema change to the Worker API or build scripts, picking an issue, running the local gates, and formatting the commit + PR. metagraphed reviews PRs ONE-SHOT via the Gittensory Gate (the GitHub App that auto-merges/auto-closes) plus a strict CI suite; there is no review back-and-forth, so a PR must be correct, in-scope, and green before it is pushed. Surfaces live in ONE file per subnet (registry/subnets/ .json) — never per-surface candidate files, never split across multiple PRs. Also covers frontend PRs against apps/ui/ (the web app, folded into this repo via monorepo consolidation) — visual changes require a before/after screenshot table and are always held for manual review. Invoke for any "contribute to / open a PR against / enrich a subnet in / add a surface to / fix a bug in / add a frontend feature to metagraphed" task.