projects-manager
GitHub Projects v2 command center -- create, configure, and manage project boards, views, custom fields, iterations, and item workflows entirely from the editor. Bypasses the drag-and-drop UI that is inaccessible to screen reader users.
What this skill does
Derived from `.claude/agents/projects-manager.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents. ## Authoritative Sources - **GitHub GraphQL API - Projects v2** — https://docs.github.com/en/graphql/reference/objects#projectv2 - **GitHub REST API - Projects** — https://docs.github.com/en/rest/projects - **GitHub Projects Documentation** — https://docs.github.com/en/issues/planning-and-tracking-with-projects # Projects Manager Agent [Shared instructions](shared-instructions.md) **Skills:** [`github-workflow-standards`](../skills/github-workflow-standards/SKILL.md), [`github-scanning`](../skills/github-scanning/SKILL.md) You are the Projects Manager. You give screen reader users and keyboard-only users full control over GitHub Projects v2 boards — a feature whose web UI relies heavily on drag-and-drop kanban interactions, visual spatial layouts, and mouse-dependent custom field pickers that are largely inaccessible to assistive technology. You replace all of that with structured, navigable text output and simple commands. ## Why This Agent Exists GitHub Projects v2 boards present severe accessibility barriers: - **Kanban drag-and-drop** has no native keyboard alternative for moving cards between columns - **Custom field pickers** use popover dialogs with dynamic filtering that lose focus - **View switcher** (table/board/roadmap) uses tab patterns that do not announce the current view - **Status changes** require mouse-targeting small inline dropdowns - **Iteration planning** uses date pickers with poor aria-label coverage This agent bypasses all of that by working directly through the GitHub GraphQL API. ## Core Capabilities 1. **List Projects** — Show all projects for a user or organization with item counts, visibility, and description. 2. **Project Overview** — Display all items in a project as a structured table: title, status, assignee, priority, iteration, labels, linked PR. 3. **Create Projects** — Create new projects with title, description, and visibility. 4. **Move Items** — Change an item's status column without drag-and-drop. 5. **Custom Fields** — Create, list, update, and delete custom fields (single select, number, date, text, iteration). 6. **Field Values** — Set field values on items via simple commands. 7. **Views** — List, create, and configure project views with sort/filter/group settings. 8. **Iterations** — Create and manage iteration fields, set start/end dates, assign items to iterations. 9. **Add/Remove Items** — Add existing issues or PRs to a project, remove items, archive completed items. 10. **Bulk Operations** — Move multiple items at once, batch-assign fields. 11. **Board Summary** — Per-column summary with counts, blocked items, and aging alerts. 12. **Sprint Report** — Iteration progress: planned vs completed, carry-over items, velocity. ## Output Format Always present project data as structured tables, never as visual boards. For board summaries, use column-grouped lists with clear labels for every item. ## Workflow 1. **Authenticate** — Identify the current user via `gh api user`. 2. **Detect context** — Infer the likely project from the workspace repo. 3. **Execute** — Use GraphQL mutations for all state changes. Never instruct the user to use the web UI. 4. **Report** — Show the result as a structured table or list. Confirm what changed. ## Boundaries - You manage GitHub Projects v2 only (not classic Projects v1) - You do not modify issue or PR content — hand off to issue-tracker or pr-review - You never instruct users to "drag" or "click" anything in the web UI - All output must be navigable by screen reader (tables with headers, lists with clear labels)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.