- 96 skills
- 0 followers
- 9 hours ago last updated
- ▌ Iwsdk Dev 2 · facebook bundleSingle entry point for IWSDK development. Invoke first for every IWSDK implementation request. Routes fresh builds to an internal planning playbook and bounded changes to an established app to an internal iteration playbook.
- ▌ Buck2 Rule Basics · facebook bundleGuide users through writing their first Buck2 rule to learn fundamental concepts including rules, actions, targets, configurations, analysis, and select(). Use this skill when users want to learn Buck2 basics hands-on or need help understanding rule writing.
- ▌ Modify Shaped Array Dsl · facebookUse when Pyrefly computes a wrong tensor shape (or is missing one that can't be expressed in a stub signature) and you need to add or fix a shape-DSL rule. Requires a Pyrefly checkout (fbsource or a clone); not usable from a pip/site-packages install.
- ▌ Add Torch Shapes Example · facebookUse when adding a new PyTorch model to Pyrefly's shape-tracking example corpus under tensor-shapes/pyrefly-torch-stubs/examples — i.e. importing a model as a tested, corpus-quality reference port. This is maintainer-facing fbsource work. For porting your own model elsewhere, use the porting skill directly; for fixing a wrong/missing shape rule, use modify-shaped-array-dsl.
- ▌ Add Shape Types To Torch Model · facebook bundlePort a PyTorch model to use pyrefly's tensor shape type system (Tensor[[B, C, H, W]], Int[T]). Use this skill whenever the user wants to add shape annotations to a PyTorch model, type a model with tensor dimensions, port a model to use shape tracking, or annotate model forward methods with tensor shapes. Also use when the user mentions tensor shape ports, Int types for PyTorch, or pyrefly shape checking on a model file. Invoke BEFORE starting any model port — the skill's gated workflow prevents common failure modes.
- ▌ Investigating Gha Failures · facebookUse when GitHub Actions CI is failing, when investigating build or test failures on a branch or PR, when the user asks about CI status, or when you need to diagnose why a workflow failed, or when you need to examine GHA build logs (e.g. sccache stats, cache usage, build timing). Triggers on keywords like "CI", "GHA", "GitHub Actions", "build failure", "tests failing", "pipeline broken", "build logs", "sccache", "cache stats", "build performance".
- ▌ Rebalancer · facebook bundleDebugging tool for rebalancer constraint violations and move failures using eval_move, list_server_moves, and query_mip CLIs.
- ▌ Rebalancer Perf · facebookPerformance testing CLI for the rebalancer solver (algopt/rebalancer/). Use when benchmarking solver performance, comparing commits for regressions, profiling solver execution, running A/B tests, or querying the rebalancer_runs Scuba table. Covers local, Skycastle (distributed), and ServiceLab (isolated hardware) execution environments. Also handles replaying saved solver configs and managing predefined run collections like the pareto golden set. Only for the rebalancer project — not for general ServiceLab benchmarks, non-rebalancer services, or functional correctness testing.
- ▌ Relay Performance · facebookPerformance best practices for Relay applications. Use when optimizing data fetching, reducing re-renders, configuring caching, or improving time to first meaningful paint. Covers query placement, @defer, pagination, fetch policies, garbage collection, fragment granularity, and server-side filtering. Companion to the relay-best-practices skill which covers correctness and architecture.
- ▌ Relay Best Practices · facebookBest practices for writing idiomatic Relay code. ALWAYS use this skill when writing or modifying React components that use Relay for data fetching. Covers fragments, queries, mutations, pagination, and common anti-patterns. Use when you see `useFragment`, `useLazyLoadQuery`, `usePreloadedQuery`, `useMutation`, `usePaginationFragment`, `graphql` template literals, `react-relay` imports, or `__generated__/*.graphql` files. Also use when asked to explain Relay concepts, debug Relay issues, or review Relay code.
- ▌ Relay E2e Test · facebook bundleWrite and run markdown-driven e2e tests for Relay. Covers fixture format, server/client code patterns, interaction DSL, snapshots, and running tests.
- ▌ Openzl Codec Design · facebookDesign patterns and requirements for OpenZL codecs (located under `src/openzl/codecs/`). **USE AUOMATICALLY** when creating, modifying, or reviewing codecs in OpenZL.
- ▌ Unitbench Openzl Scenarios · facebookUse when creating benchmark scenarios for new openzl codec nodes in unitBench - adding kernel-level encode/decode benchmarks or graph-level compress/decompress benchmarks for codecs like bitsplit, delta, transpose, entropy, etc.
- ▌ Openzl Gpu Test Frames · facebookHow to mint real OpenZL frames and chunks for GPU decoder tests using the contrib/gpu/testkit utilities (frame_factory, multichunk_frame, frame_verifier), and how to extract a codec's encoded streams via reflection for differential GPU decode. USE when writing or reviewing GPU-decoder tests that need OpenZL-encoded fixtures.
- ▌ Fboss Review · facebook bundleComprehensive FBOSS code review with 11 parallel reviewers (5 generic + 6 FBOSS-specific). Covers reliability, engineering, code quality, silent failures, agent architecture, SAI/SDK, FSDB/thrift_cow, platform/config, testing, and cross-cutting design. Self-contained alternative to /review-diff for FBOSS diffs. Findings shown to user only, never auto-posted.
- ▌ Debug Agent Hw Test · facebook bundleDebug FBOSS AgentHwTest failures - build, run, analyze logs, crash debug, vendor diag shell, hypothesis-driven debugging. Use when running sai_agent_hw_test or multi_switch_agent_hw_test and investigating test failures.
- ▌ Fboss Code Standards · facebook bundleFBOSS coding standards and patterns. Auto-loaded when writing code in fboss/ to catch architecture violations, SAI/SDK misuse, thrift_cow pitfalls, platform config errors, and testing gaps. For explicit multi-reviewer review, use /fboss-review instead.
- ▌ Hw Test Dedup · facebook bundleFind and remove redundant FBOSS agent_hw_tests without losing coverage. Use when asked to reduce/combine/dedup HW tests, retire non-dataplane (set/get) tests where dataplane tests exist, or cut HW test runtime while keeping coverage. Report-first; applying edits is a separate opt-in step.
- ▌ Bisect Triage · facebookTriage a failing FBOSS test by bisecting commits and investigating code changes. Use when a test is broken and you need to find the commit that caused the failure.
- ▌ Gc Safe Coding · facebookRules for writing and reviewing GC-safe C++ code in the Hermes VM runtime. Use when writing, modifying, or reviewing C++ runtime VM code that uses internal Hermes VM APIs (as opposed to code using JSI). This includes working with GC-managed types (HermesValue, Handle, PinnedValue, JSObject, StringPrimitive, etc.), Locals, GCScope, PseudoHandle, CallResult, or any function with _RJS suffix. Typically in lib/VM/, include/hermes/VM/, API/hermes/, or API/napi/.
- ▌ Add Ir Instruction · facebookGuide for adding a new IR instruction to the Hermes compiler. Use when the user asks to add, create, or define a new IR instruction (Inst/Instruction) in the Hermes intermediate representation. Covers all required files and the patterns for each.
- ▌ Modify Jsi Features · facebookGuide for adding new JSI functionality to the JavaScript Interface (JSI) layer. Use when the user asks to add, create, or implement new methods or features in the JSI Runtime interface. Covers all required files across JSI core, Hermes implementation, and SynthTrace replay support.
- ▌ Binary Size Analysis · facebookThis skill should be used when the user wants to analyze hermesvm binary size changes across a range of commits. Use when the user mentions "binary size", "size analysis", "size regression", "size increase", or asks to measure how commits affect the hermesvm library size.
- ▌ Non Interactive Git Rebase · facebookUse when needing to reorder, split, drop, or amend git commits that are not the top commit, without interactive editor access. Covers programmatic rebase via GIT_SEQUENCE_EDITOR, commit splitting with automated hunk selection, and metadata changes (author, message, dates) on any commit in a range.
- ▌ Architecture · facebookUse when you need to understand the Pyre or Pysa codebase architecture, find where specific functionality is implemented, or navigate the source directory structure. Use when working on OCaml code, debugging type checking or taint analysis issues, or exploring the codebase.
- ▌ Pysa JSON Models · facebookUse when reading, writing, or debugging Pysa JSON model output (.models files). Use when working with taint models that describe sources, sinks, TITO, sanitizers, or issues in JSON format.
- ▌ Commit Conventions · facebookUse when creating commits or diffs to apply the correct title prefix, reviewer, and test plan based on the area of the codebase being changed.
- ▌ Pysa Integration Tests · facebookUse when running, debugging, updating, or creating Pysa end-to-end integration tests. Use when taint analysis tests fail, when expected output files need updating, or when working with .models, .cg, .hofcg, .overrides files under `source/interprocedural_analyses/taint/test/integration`.
- ▌ Pysa False Negative Debugger · facebookUse when debugging a Pysa false negative (missing taint issue), comparing two Pysa output directories, or finding where taint flow is lost.
- ▌ Eden Research · facebookLoad FIRST before searching code in eden/. Contains component-to-file maps, key type names, and architecture diagrams for EdenFS, Sapling, and Mononoke. Tells you exactly which files to read for any task. References contain per-component quick reference tables.
- ▌ Creating Endpoints · facebookThis guide explains how to create new EdenAPI/SLAPI endpoints, covering both streaming and non-streaming patterns.
- ▌ Write Hook · facebook bundleCreate a Mononoke server-side hook with 3-diff split (tests, wiring, implementation), unit tests, and integration tests
- ▌ Edenfs Systemd Triage · facebook bundleTriage systemd-managed EdenFS issues on Linux devservers and OnDemands. Use when investigating EdenFS service failures, unexpected restarts, systemctl errors, edenfs_upgrade/edenfs_restarter problems, or when a user reports EdenFS is down on a systemd-enabled host. Also use when someone asks how systemd-managed EdenFS works, how to monitor it, or how to check its health. Use when asked to build a timeline of EdenFS lifecycle events, show edenfs restart history, or understand how edenfs reached its current state. Trigger on mentions of edenfs systemd, edenfs@ service, edenfs_upgrade timer, edenfs auto-restart, eden status --debug, systemctl edenfs, edenfs lifecycle management, edenfs timeline, edenfs restart history, or "what happened to edenfs".
- ▌ Structured Error Logging · facebookAdd or review structured error logging in EdenFS daemon (C++) — the ErrorLogger / EdenErrorInfo system that feeds the edenfs_errors table. Use when writing a catch block or handling a boxed/async exception (folly::Try / exception_wrapper / .thenError), instrumenting a failure path, or debugging a wrong stack trace or wrong component. Covers throw-site trace rules, component choice, errorType, noise filtering, gating, and testing.
- ▌ API Health · facebookMonitor API health for a Meta app — check rate limits, call volume, and API deprecations. Use whenever a user asks whether their app is being throttled, is near its rate limits, how much of its call volume or quota is being used, or about deprecated Graph API versions. Prefer this skill over calling devtools_api_usage directly — it resolves the app, pulls rate limits, call volume, and deprecations together, and turns them into one prioritized report, including the cases an ad-hoc call misreads: an unmetered app is not the same as an idle one, and a capped usage_rate is not the same as headroom.
- ▌ Search Docs · facebookSearch Meta developer documentation for API guides, references, and tutorials. Use when looking up how a Meta API works, finding integration guides, or exploring platform capabilities.
- ▌ Webhook Setup · facebookSet up webhooks for a Meta app end-to-end — discover available topics, subscribe to fields, and verify with a test payload. Use when configuring webhooks for the first time or adding new subscriptions.
- ▌ Debug Webhooks · facebookTroubleshoot webhook issues for a Meta app — inspect active subscriptions, identify misconfiguration, and send test payloads to verify delivery. Use when webhooks aren't working as expected.
- ▌ API Integration · facebookGuide a developer through setting up a Meta API integration from scratch — discovers the right APIs, fetches setup guides, authentication requirements, permissions, and code examples. Use when the user wants to build with a specific Meta product (WhatsApp, Instagram, Messenger, Pages, Ads, etc.).
- ▌ App Review Prep · facebookPrepare a Meta app for App Review — checks current status, outstanding requirements, granted privileges, and submission history. Use before submitting an app for review.
- ▌ App Health Check · facebookRun a comprehensive health check on a Meta app — audits settings, security, compliance, app review status, rate limits, and API deprecations in one pass. Use when you want a full picture of an app's current state.
- ▌ Compliance Check · facebookCheck compliance status for a Meta app — surfaces open required actions, active violations, and recommendations with remediation guidance. Use to audit compliance posture or resolve compliance blockers.
- ▌ Debug Access Token · facebook bundleDiagnose a Meta access token problem (expired, wrong scopes, wrong app, invalid) WITHOUT the token ever entering the agent or AI provider context. Guides the developer to inspect the token themselves via the Access Token Debugger web tool or the public debug_token Graph API, then interprets the returned metadata. Use when an API call fails with an auth/OAuthException error (e.g. code 190) or a token isn't behaving as expected.
- ▌ Add UI · facebook bundleAdd UI components to a Meta Display Glasses webapp — screens, buttons, lists, cards, forms, toggles, counters, or nav bars. Works with vanilla JS and React apps. Use when the user wants to add any interactive UI element or new screen.
- ▌ Qr Code · facebook bundleGenerate QR codes locally without third-party services or dependencies. Uses a self-contained pure Python script (stdlib only). Data never leaves the machine. Supports PNG file output.
- ▌ Add Offline · facebookMake a Meta Display Glasses webapp work offline with a Service Worker + Cache API (precache the app shell, cache-first fetch, online/offline UI). Use when the user wants offline support or resilience to flaky Wi-Fi.
- ▌ Connect API · facebookConnect a Meta Display Glasses webapp to REST APIs or WebSockets. Use when the user wants to fetch data from an API, add real-time updates, show loading/error states, or cache API responses.
- ▌ Add Gestures · facebookHandle EMG pinch (tap-to-activate) and opt into continuous pinch-and-drag in a Meta Display Glasses webapp. Use when the user wants sliders, drawing, maps, drag interactions, or game-style continuous input.
- ▌ Create Webapp · facebook bundleCreate a new webapp for Meta Display Glasses with D-pad navigation and 600x600 dark-theme display. Use when the user wants to build a new glasses app, start a project, or scaffold a webapp for smart glasses.
- ▌ Add Text Input · facebookAdd text entry to a Meta Display Glasses webapp. Standard HTML inputs open the on-glasses composer (handwriting + voice) when focused and tapped. Use when the user wants a text field, search box, form input, or notes area.
- ▌ Test On Device · facebookDeploy uncommitted webapp changes to a public staging URL for live HTTPS testing on Meta Display Glasses. Use when the user wants to test, debug, preview, or try their webapp on the glasses without committing code. Uses Vercel by default.
- ▌ Add Local Storage · facebookAdd client-side data persistence to a Meta Display Glasses webapp using the W3C Web Storage API (localStorage and sessionStorage). Use when the user wants to save settings, cache data, persist state, or store user preferences.
- ▌ Publish To Vercel · facebookPublish a Meta Display Glasses webapp to Vercel for live HTTPS access on device. Use when the developer is ready to publish, host, ship, or release a webapp to a stable production URL for everyone. Handles server setup, Vercel project creation, and direct deploys without GitHub.
- ▌ Add Device Sensors · facebookAdd device sensor data to a Meta Display Glasses webapp — IMU (accelerometer, gyroscope, orientation) via DeviceMotionEvent/DeviceOrientationEvent, and GPS location via navigator.geolocation. Use when the user wants motion tracking, compass, level tool, step counter, shake detection, head tracking, or location.
- ▌ Passcode For Testing · facebook bundleAdd a 3-digit combination lock passcode screen to a Meta Display Glasses webapp to gate public access during testing. Offered as an opt-in step within /test-on-device since Vercel deployment protection is disabled for glasses browser compatibility.
- ▌ Debugging · facebookCommon issues, Developer Mode, version compatibility, and session and stream diagnosis
- ▌ Display Access · facebookDisplay capability setup, display-capable device selection, UI DSL, icons, buttons, images, and video playback
- ▌ Dat Conventions · facebookKotlin patterns, DatResult, session and capability conventions for DAT SDK Android development
- ▌ Getting Started · facebookSDK setup, Gradle integration, AndroidManifest configuration, and first connection to Meta glasses
- ▌ Camera Streaming · facebookSession and Stream capability setup, video frames, photo capture, resolution and frame rate configuration
- ▌ Sample App Guide · facebookBuilding a complete DAT app with session creation, camera streaming, and photo capture
- ▌ Session Lifecycle · facebookSession state, stream state, pause and resume behavior, and device availability monitoring
- ▌ Live Debugging MCP · facebookUse this whenever debugging an Android DAT app with local DAT Inspector MCP tools, live device events, Meta AI app/device boundary issues, permissions, registration, sessions, streaming, or user reports that the app cannot communicate with glasses.
- ▌
- ▌
- ▌ Iwsdk Dev · facebook bundleMUST read this skill BEFORE developing VR/MR/desktop 3D applications using IWSDK (Immersive Web SDK). Covers project scaffolding, headless browser setup, CLI tools, reference system, ECS debugging, XR emulation, verification workflows, deployment, and known issues.
- ▌ Test UI · facebookTest UIKitML asset and ScreenSpace UI behavior against the poke example using the iwsdk CLI.
- ▌ Test All · facebookParallel test orchestrator. Runs all 9 test suites concurrently via Task sub-agents and the iwsdk CLI. Handles build, example setup, dev servers, agent launch, polling, retries, and result aggregation.
- ▌ Test Grab · facebookTest grab system (distance grab, one-hand grab, two-hand grab) against the grab example using the iwsdk CLI.
- ▌ Test Audio · facebookTest audio system (AudioSource loading, playback state, stop, spatial audio) against the audio example using the iwsdk CLI.
- ▌ Test Level · facebookTest level system (LevelRoot, LevelTag, authored environment, scene hierarchy) against the poke example using the iwsdk CLI.
- ▌ Click Target · facebookFind and click a target object in XR. Use when testing UI interactions, clicking buttons, or verifying interactable elements work correctly.
- ▌ Test Physics · facebookTest Havok physics system (gravity, rigid bodies, static vs dynamic) against the physics example using the iwsdk CLI.
- ▌ Xr Mode Test · facebookTest XR session lifecycle and mode transitions. Use when verifying XR enter/exit behavior, testing mode-dependent features, or debugging session state issues.
- ▌ Test Ecs Core · facebookTest ECS core functionality (system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots) against the poke example using the iwsdk CLI.
- ▌ Iwsdk UI Panel · facebookCreate, place, preview, debug, and connect manifest-backed IWSDK UIKitML assets. Use for spatial panels, browser HUDs, UIKitML layout, fonts, editor previews, or runtime element behavior.
- ▌ Test Locomotion · facebookTest locomotion system (slide, snap turn, teleport, jump) against the locomotion example using the iwsdk CLI.
- ▌ Test Environment · facebookTest environment system (authored DomeGradient and IBLGradient, component schemas) against the poke example using the iwsdk CLI.
- ▌ Test Interactions · facebookTest XR interactions (ray, poke/touch, dual-mode, audio, UI panel) against the poke example using the iwsdk CLI.
- ▌ Iwsdk Migrate 0 5 · facebookMigrate an existing IWSDK 0.4.x application to IWSDK 0.5.0. Use when upgrading across the 0.5 boundary, replacing Meta Spatial Editor or GLXF, removing retired Vite plugins, moving UIKitML to runtime-loaded assets, adopting native scene JSON, or resolving 0.5 migration errors.
- ▌ Iwsdk UI · facebookBuild or modify manifest-backed IWSDK UIKitML with bounded preview, placement, and runtime verification. Use for spatial panels, browser HUDs, UIKitML layout, fonts, editor previews, and runtime element behavior.
- ▌ Iwsdk Ray · facebookVerify ray clicks, UIKit selections, and DistanceGrabbable interactions with emulated XR controllers. Use for pointing, selecting, pressing spatial UI, or moving an object through a distance grab.
- ▌ Iwsdk Grab · facebookUse emulated XR controllers to verify proximity grabbing for OneHandGrabbable and TwoHandsGrabbable objects. Use for pick up, move, release, or regression-test requests involving near-hand grab with the squeeze button.
- ▌ Iwsdk Debug · facebookDiagnose and verify real-time IWSDK behavior with bounded ECS pause, query, snapshot, step, and diff loops. Use for physics, animation, collision, interaction, or state bugs that cannot be proven from a screenshot.
- ▌ Iwsdk Hosting · facebook bundlePublish an IWSDK app to a public HTTPS origin so it can be installed as a PWA and packaged for the Meta Horizon Store. Use when deploying, hosting, or publishing the app, choosing a host, or when a file (web manifest, icons, .well-known/assetlinks.json) must reach an already-hosted site. Always asks first whether hosting already exists — recommends Vercel if not, and pauses with concrete upload steps if it does.
- ▌ Iwsdk Physics · facebook bundleAdd or repair IWSDK rigid-body simulation, collision shapes, forces, and physics-aware grabbing. Use for gravity, falling, collision, bouncing, kinematic motion, or physics tuning.
- ▌ Iwsdk Build Model · facebook bundleBuild or materially repair one reusable IWSDK 3D model as a glTF or deterministic parentless Three.js Object3D, including geometry, surface-relative detail, materials, semantic hierarchy, isolated inspection, and focused refinement. Does not arrange scenes, lighting, environment, or cameras; use iwsdk-compose-scene for those.
- ▌ Iwsdk Compose Scene · facebook bundleCompose and review IWSDK scenes from existing manifest assets using scene JSON, placement, scale, contacts, prefabs, patterns, lighting, environment, cameras, and final framing. Does not author geometry or materials; create or repair an individual 3D asset with iwsdk-build-model.
- ▌ Iwsdk Pwa Packaging · facebook bundleShip an IWSDK app to Meta Quest and the Horizon Store as a PWA/TWA — both immersive WebXR and 2D windowed panel modes. Use for PWA packaging, web app manifest and icons, auto-enter-XR on launch, bubblewrap APK builds, signing keystores, Digital Asset Links, sideloading, and Horizon Store upload. Also use when a packaged app is stuck loading, shows a URL bar, or will not launch.
- ▌ Iwsdk Depth Occlusion · facebookAdd or repair IWSDK WebXR depth sensing and real-world occlusion in AR. Use for DepthSensingSystem, DepthOccludable, occlusion modes, or passthrough depth troubleshooting.
- ▌ Rust Port Status · facebookShow the status of all Rust port plan documents and recent related commits. Use when you need to understand what's been done vs what remains.
- ▌ Compiler Commit · facebookUse when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
- ▌ Compiler Review · facebookReview Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
- ▌ Compiler Verify · facebookUse when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
- ▌ Compiler Port · facebookPort a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
- ▌ Plan Update · facebookUse when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.