agent-scripts

Pre-commit/ship code review: Codex default; optional Claude, Pi, Droid, Copilot, Cursor, or OpenCode.

Install, repair, or diagnose App Store Connect version/build-number guards for Xcode Cloud iOS apps. Triggers: version guard, release hooks, Xcode Cloud rejection, MARKETING_VERSION, build number collision.

Things 3 CLI for reading the local Things database and creating/updating tasks/projects via the Things URL scheme. Use when you need to list, search, or modify Things tasks, projects, areas, or tags from the terminal (deletes use AppleScript).

Fetch secrets and env vars from 1Password via the `op` CLI. Primary path is a non-interactive service-account token (no prompts); Touch ID is the fallback. Use whenever a command needs an API key, token, password, or `.env` value — read it from 1Password instead of hardcoding, printing, or asking the user to paste it. Triggers: op, op read, op run, op inject, op://, 1Password, fetch a secret, get an API key, inject env vars.

Operate the Post Queue repo command surface effectively. Use when an agent needs to run local dev servers, local Supabase/Drizzle workflows, scheduler ticks or loops, cron-runner checks, tests, lint, typecheck, or database migrations in this repo.

Add a redacted agent transcript section to GitHub PR or issue bodies during agent-created PR/issue workflows.

Notion API for reading, querying, creating, and updating Notion pages, databases, data sources, and blocks. Use this whenever the user asks to inspect, migrate, sync, or automate Notion content, especially work items or task databases.

Delegated maintainer ops: decision-ready PRs, worker monitoring, queue cleanup, releases.

Operate the private Notion/Things to GitHub issue migration system. Use this whenever the user mentions migrating Notion tasks, Things inbox/project items, private GitHub issue intake, scheduled Things processing, work-migrate, or mapping Things projects to repos.

Bridge Content Machine output into Post Queue. Use whenever an agent needs to inspect PostQ context, generate or select Content Machine posts, create PostQ drafts, or schedule Walkmon TikTok posts through PostQ while preserving TikTok inbox-draft/manual-finish delivery.

Delegated maintainer/orchestrator for Rebtech's Azure DevOps repos using Claude Code. Discovers scoped work (Azure Boards work items + active PRs), classifies it autonomous-vs-needs-owner, implements safe items on isolated branches, creates decision-ready pull requests with proof, and monitors branch policies, pipelines, and PR review threads — stopping cleanly at the open-PR boundary. Use when the user asks to triage and work the Azure DevOps queue, run repo maintenance, clear the backlog, prepare decision-ready PRs, babysit pipelines/PRs, or run the maintainer loop across rebtech-website, skill-library, raid-plugin, or raid-telemetry. Pairs with rebtech-devops-triage (queue assessment) and the az-cli skill (command reference). Adapts the GitHub/Codex maintainer-orchestrator pattern to Azure DevOps + Claude Code: az devops CLI instead of gh, subagents instead of Codex threads.

Read-only triage of Rebtech's Azure DevOps queue from Claude Code: assess Azure Boards work items and active pull requests across the RAID and Assets projects, each with a plain-language what-it-is, type, fit, risk, proof/CI state, blocker, and the exact next maintainer action. Use when the user asks to triage the Azure DevOps backlog, review the work-item/PR queue, see what is worth doing, prioritize, or get a maintainer-grade read on the queue without changing anything. This is the assessment front-end for the rebtech-devops-maintainer skill (which actually implements + opens PRs). It maps the GitHub/Codex github-project-triage pattern onto az devops: WIQL + az repos pr instead of gh/RepoBar. Triage only — it never edits, pushes, comments, votes, or merges.

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.

GitHub issue/PR triage: queues, CI, blockers, risk, proof, next actions.

Release iOS and Expo apps to TestFlight and the App Store. Triggers: iOS release, Expo release, version bump, TestFlight, App Store review, Xcode Cloud, EAS, .ios-release.env.

Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.

Render data visualizations with Canvas2D. Use when the visualization needs high mark counts, fast redraws, immediate-mode rendering, custom hit testing, or a hybrid Canvas plus SVG or HTML architecture.

Build custom data visualizations with D3. Use when the user needs SVG or DOM-based charts, rich annotation, domain-native contextual backgrounds, data joins, custom scales or interactions, scroll-driven SVG scene states, or precise control over browser visualization behavior.

Design dashboards and live visualization systems. Use when the user needs monitoring views, streaming charts, coordinated interactions, downsampling, or performance-aware operational visualization.

Route web data visualization work. Use when the user needs chart choice, visual critique, dashboards, maps or geospatial views, Gantt timelines, UML/software diagrams, scrollytelling, reports or exports, testing, accessibility, browser implementation, or concept-first visual design.

Design, critique, route, and implement Gantt charts and schedule visualizations. Use when the user mentions Gantt charts, project schedules, roadmaps with task spans, milestones, dependencies, predecessors, critical path, baselines, WBS, resource plans, capacity timelines, MS Project, Primavera P6, Jira Advanced Roadmaps, GitHub Projects, Smartsheet, monday.com, Asana, ClickUp, Azure DevOps iterations, or importing/exporting project-management data for a timeline chart.

Design geospatial and cartographic visualizations. Use when the user needs help deciding whether to use a map, choosing projections or basemaps, building choropleths or symbol maps, or implementing thematic maps, slippy maps, or geospatial interactions with D3 geo, Leaflet, MapLibre, Mapbox GL JS, Google Maps, OpenLayers, deck.gl, ArcGIS Maps SDK, Azure Maps, HERE Maps, CesiumJS, or related tools.

Build data visualizations with declarative grammars. Use when the user needs Vega-Lite, Vega, Observable Plot, or grammar-of-graphics reasoning, especially for tabular charts that do not require bespoke rendering.

Choose and apply automatic layout strategies for node-link diagrams and connected-node visuals. Use when the user asks how to auto-arrange nodes, reduce line crossings, route edges, avoid overlaps, stabilize layout, or choose graph-layout algorithms for network diagrams, dependency graphs, database schema diagrams, ERDs, state machines, decision trees, flow diagrams, box-and-line editors, or other line-connected nodes.

Integrate data visualizations into React and Next.js applications. Use when the user needs chart components, UML-like or architecture diagram components, React integration patterns, Next.js client or server boundaries, hydration-safe rendering, lazy loading, framework-aware performance, scroll-driven visual stories, or export guidance.

Lay out and export data-rich reports and documents. Use when the user needs report structure, figure packaging, PDFs, PowerPoint or Google Slides automation, or programmatic insertion of visualizations, UML-like diagrams, or architecture diagrams into documents.

Design and implement parallax scrolling and scrollytelling data visualizations. Use when the user asks for parallax scrolling, scrollytelling, scroll-driven timelines, sticky graphics, Scrollama, ScrollTrigger, ScrollTimeline, view timelines, rich-media timelines, moviescrollers, scroll-scrubbed charts, staged narrative reveals, or interactive visual stories where scrolling changes a data visualization or media scene.

Design statistically honest and uncertainty-aware visualizations. Use when the user needs help showing distributions, intervals, confidence, missingness, sampling effects, or analytical rigor in charts and dashboards.

Test data visualizations and dashboards. Use when the user needs chart or diagram test strategy, screenshot or image diff testing, visual regression, mocked or synthetic chart data, component or unit tests, E2E dashboard QA, interactive UML-like diagram verification, scroll-driven story verification, export verification, or guidance on avoiding brittle over-testing.

Render WebGL-accelerated data visualizations with Three.js, raw WebGL, deck.gl, luma.gl, PixiJS, Sigma.js, Plotly WebGL traces, ECharts GL, CesiumJS, Babylon.js, or related GPU libraries. Use when the visualization needs true spatial structure, dense 2D or 3D GPU rendering, particle or flow animation, volumetric views, or interactive exploration that adds real analytical value.

Build typed data visualizations in TypeScript. Use when the user wants TypeScript visualization code, typed data models, browser visualization components, UML-like diagram models, interactive graph or architecture diagram contracts, scroll-driven scene contracts, library selection guidance, or a maintainable visualization architecture beyond React- or Next-specific concerns.

Design, critique, read, write, render, and implement UML and UML-like software diagrams. Use when the user mentions UML, sequence diagrams, class diagrams, activity diagrams, state machines, use case diagrams, component diagrams, deployment diagrams, object diagrams, package diagrams, profile diagrams, timing diagrams, communication diagrams, interaction overview diagrams, composite structure diagrams, ERDs, database schema diagrams, C4, BPMN, swimlanes, flowcharts, network diagrams, application architecture diagrams, software architecture diagrams, diagram-as-code, model-as-code, XMI, UMLDI, PlantUML, Mermaid, Graphviz DOT, D2, Structurizr, DBML, diagrams.net/draw.io, Kroki, or interactive diagram editors and explorers.

Choose, lay out, critique, and explain data visualizations. Use when the user asks what visualization fits a dataset or goal, how a chart, dashboard, operational workspace, UML-like diagram, or software architecture diagram should be composed or interacted with, asks for visual page design, a layout mockup, generated large-screen and mobile concept images, or to be shown what a visualization could look like, when domain-native contextual surfaces or graphical backgrounds may help, when scrollytelling or parallax might be appropriate, wants a critique of an existing visualization, or needs guidance grounded in trusted visualization theory and practice. For advanced visual design or page-layout prompts where composition affects understanding, Codex must generate and show both large-screen and mobile portrait image concepts before implementation or text-only design handoff, plus mobile landscape when needed.

Design, test, or improve App Store app icons for tap-through and conversion. Triggers: app icon, icon design, A/B test, variants, tap-through rate, icon refresh.

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.

Build App Store/Google Play screenshot pages and editors. Triggers: screenshots, marketing assets, iOS/Android, html-to-image, phone mockup, feature graphic.

Audit, write, translate, and sync App Store listing metadata with the `asc` CLI on canonical files under `./metadata`. Use to run an ASO/keyword audit, localize descriptions/keywords/subtitle/name to multiple languages, or write engaging localized "What's New" release notes (from git log, bullets, or free text) plus promotional text.

Manage App Store subscription and in-app purchase pricing and catalog with the `asc` CLI. Use to set territory-specific / purchasing-power-parity (PPP) prices via setup, pricing summary, CSV import, and schedules, or to reconcile ASC subscriptions and IAPs with RevenueCat products, entitlements, offerings, and packages (RevenueCat MCP).

Build, version, upload, and submit iOS/macOS apps to App Store Connect with the `asc` CLI. Use to create an IPA/PKG, bump Xcode version/build numbers, run asc commands, drive the release/submission flow (including first-time fixes for availability, IAP, subscriptions, Game Center, App Privacy), or wire repeatable `asc workflow` automations into CI.

CLI UX/spec: args, flags, help, output, errors, config, dry-run.