all publishers

pmndrs

@pmndrs source repo

45 published skills

  1. ▌
    Pine · pmndrs bundle
    Run, configure and extend pine, the event-driven multi-agent daemon built on the pi coding agent SDK. Use when setting up agents and their workspaces, subscribing agents to event sources (Telegram, folders, MQTT, webhooks, FTP uploads, web addresses, commands), scheduling what happens at a time, adding MCP servers and skills, routing events to agents, reaching agents on Telegram, delegating between agents, reviewing what is protected against prompt injection, or changing pine's code.
    0 installs
  2. ▌
    Vitexec 3 · pmndrs bundle
    Use this skill when an AI agent needs to inspect, verify, or debug a live Vite app by running temporary snippets inside the browser page and reading browser logs. Use for client state after interactions, imported app modules, DOM state, human-like input, canvas/WebGL/Three.js state, screenshots, videos, WebXR/Three.js XR with IWER, and runtime-only behavior without editing app files.
    2 installs
  3. ▌
    Vitexec 2 · pmndrs bundle
    Use this skill when an AI agent needs to inspect, verify, debug, or profile a live Vite app by running temporary snippets inside the browser page and reading browser logs or captured artifacts. Use for client state after interactions, imported app modules, DOM state, human-like input, canvas/WebGL/Three.js state, screenshots, videos, CPU/network/performance/heap analysis, WebXR/Three.js XR with IWER, and runtime-only behavior without editing app files.
    5 installs
  4. ▌
    Speckit Git Remote · pmndrs
    Detect Git remote URL for GitHub integration
    5 installs
  5. ▌
    Speckit Git Validate · pmndrs
    Validate current branch follows feature branch naming conventions
    5 installs
  6. ▌
    Speckit Git Initialize · pmndrs
    Initialize a Git repository with an initial commit
    3 installs
  7. ▌
    Tsl 2 · pmndrs bundle
    Implement, migrate, review, debug, or verify Three.js Shading Language (TSL) materials, node graphs, WebGPU compute work, and post-processing. Use for `three/tsl`, `three/webgpu`, NodeMaterial, WebGPURenderer, storage buffers, shader-node typing, or GLSL-to-TSL work; verify every API against the repository's installed Three.js version.
    5 installs
  8. ▌
    Codemod 2 · pmndrs bundle
    Author, archive, apply, and verify TypeScript codemods with ts-morph for APIs that have reached the remote default branch or external users. Use for shipped public API migrations, symbol renames, call-signature rewrites, import moves, or requests to preserve a dated migration recipe. Do not use for unmerged work-in-progress APIs or global text replacement.
    1 install
  9. ▌
    Typegpu 2 · pmndrs bundle
    TypeGPU is type-safe WebGPU in TypeScript. Use whenever the user writes, debugs, or designs TypeGPU code: 'use gpu' shader functions, tgpu.fn, buffers, textures, bind groups, compute and render pipelines, command encoders, render passes, render bundles, vertex layouts, slots, accessors, @typegpu/react hooks (useRoot, useFrame, useUniform), React Native worklet rendering, and any TypeGPU API. Shader logic and CPU-side resources are tightly coupled - handle both sides here even if the user only mentions one (e.g. "how do I write a shader", "how do I create a buffer"). Trigger on any mention of typegpu, tgpu, "use gpu", TypedGPU, or WebGPU code written using TypeGPU's schema API (d.*, tgpu.*, std.*). Do NOT trigger for raw WebGPU (using GPUDevice/GPURenderPipeline directly without tgpu), WGSL-only questions, Three.js, Babylon.js, or WebGL.
    7 installs
  10. ▌
    Gh Stack 2 · pmndrs
    Manage dependent branches and pull requests with the gh-stack GitHub CLI extension. Use for stacked diffs, dependent pull requests, branch chains, stack navigation, rebasing, submission, synchronization, or merging.
    4 installs
  11. ▌
    Agent Router 2 · pmndrs bundle
    Route resumable external-model work through the pinned ai-cli-mcp server. Use for adversarial reviews, implementation reviews, research, and one-off delegated tasks when the user names Claude, Opus, Fable, OpenCode, 0x Alpha, Codex, or asks for an external model.
    5 installs
  12. ▌
    Diataxis Docs 2 · pmndrs bundle
    Design, classify, write, audit, or restructure technical documentation with the Diátaxis framework. Use for tutorials, how-to guides, reference material, explanations, documentation maps, README routing, documentation audits, or requests to separate mixed-purpose docs. Do not apply it automatically to internal plans, ADRs, research logs, or specifications unless the user wants those artifacts organized as product documentation.
    4 installs
  13. ▌
    Evidence First 2 · pmndrs bundle
    Shape human-facing engineering communication—including chat updates and final answers, reports, reviews, handoffs, debugging or benchmark summaries, PR and issue prose, READMEs, and technical documentation—around clear claims, measured support, explicit gaps, and scoped decisions. Use whenever Codex presents engineering work, evidence, or findings to a human; let document-specific frameworks retain their purpose and structure.
    6 installs
  14. ▌
    Engine Call Contract 2 · pmndrs
    How every call into the text engine is shaped, and where each entry point's names live. Use before adding, moving, or removing anything on a published surface, before adding an error path or a result type to an engine call, and when deciding whether a failure belongs to the caller or to this package.
    7 installs
  15. ▌
    Open Knowledge Format 2 · pmndrs bundle
    Create, migrate, inspect, query, validate, or maintain Open Knowledge Format v0.2 bundles made from linked Markdown concepts with YAML provenance. Use when the user mentions OKF, Open Knowledge Format, knowledge bundles, LLM wikis, portable agent knowledge, OKF conformance, provenance, trust, lifecycle, attested computations, or asks to make repository knowledge interoperable across human and agent tools. Do not use for ordinary Markdown unless OKF compatibility or a knowledge bundle is requested.
    1 install
  16. ▌
    Maintainability Review 2 · pmndrs bundle
    Audit and improve repository code milestone by milestone for correctness, clarity, local reasoning, DRY design, explicit state modeling, panic resistance, and trustworthy TypeScript boundaries. Use for deliberate cleanup passes, pre-release maintainability reviews, agent-assisted refactors, or requests invoking Jane Street-style algebraic data types, Rust newtypes, TypeScript discriminated unions, type guards, or evidence-backed simplification without public API churn.
    5 installs
  17. ▌
    Docs · pmndrs
    Look up the official pmndrs documentation before answering anything about react-three-fiber (R3F), drei or zustand — hooks, components, props, signatures, store patterns, migrations. Use it whenever code or an answer depends on one of these APIs, rather than recalling the API from memory.
    4 installs
  18. ▌
    Examples · pmndrs
    Find a working pmndrs demo before writing a react-three-fiber scene from scratch — caustics, transmission, physics, postprocessing, scroll rigs, GLTF, portals, instancing. Use it whenever the question is how something is put together rather than what an API takes, and read the demo's source instead of reconstructing it.
    5 installs
  19. ▌
    Pmndrs Viverse · pmndrs bundle
    Build, modify, debug, or publish VIVERSE-ready web games and 3D apps with Three.js, React Three Fiber, @pmndrs/viverse, @react-three/viverse, VIVERSE SDK integrations, character controllers, physics, avatars, actions, animations, AR, or VR.
    3 installs
  20. ▌
    Pmndrs Xr · pmndrs bundle
    Build, modify, debug, or validate XR, AR, VR, spatial interaction, pointer, controller, hand-tracking, hit-test, teleportation, layer, anchor, uikit, and handle-based React Three Fiber apps using @react-three/xr, @react-three/handle, and @react-three/uikit. Use when working on immersive WebXR experiences, R3F-to-XR conversions, XR games, spatial tools, or XR validation/test harnesses.
    6 installs
  21. ▌
    Tsl · pmndrs bundle
    Implement, migrate, review, debug, or verify Three.js Shading Language (TSL) materials, node graphs, WebGPU compute work, and post-processing. Use for `three/tsl`, `three/webgpu`, NodeMaterial, WebGPURenderer, storage buffers, shader-node typing, or GLSL-to-TSL work; verify every API against the repository's installed Three.js version.
    5 installs
  22. ▌
    Codemod · pmndrs bundle
    Author, archive, apply, and verify TypeScript codemods with ts-morph for APIs that have reached the remote default branch or external users. Use for shipped public API migrations, symbol renames, call-signature rewrites, import moves, or requests to preserve a dated migration recipe. Do not use for unmerged work-in-progress APIs or global text replacement.
    7 installs
  23. ▌
    Typegpu · pmndrs bundle
    TypeGPU is type-safe WebGPU in TypeScript. Use whenever the user writes, debugs, or designs TypeGPU code: 'use gpu' shader functions, tgpu.fn, buffers, textures, bind groups, compute and render pipelines, command encoders, render passes, render bundles, vertex layouts, slots, accessors, @typegpu/react hooks (useRoot, useFrame, useUniform), React Native worklet rendering, and any TypeGPU API. Shader logic and CPU-side resources are tightly coupled - handle both sides here even if the user only mentions one (e.g. "how do I write a shader", "how do I create a buffer"). Trigger on any mention of typegpu, tgpu, "use gpu", TypedGPU, or WebGPU code written using TypeGPU's schema API (d.*, tgpu.*, std.*). Do NOT trigger for raw WebGPU (using GPUDevice/GPURenderPipeline directly without tgpu), WGSL-only questions, Three.js, Babylon.js, or WebGL.
    4 installs
  24. ▌
    Gh Stack · pmndrs
    Manage dependent branches and pull requests with the gh-stack GitHub CLI extension. Use for stacked diffs, dependent pull requests, branch chains, stack navigation, rebasing, submission, synchronization, or merging.
    5 installs
  25. ▌
    Agent Router · pmndrs bundle
    Route resumable external-model work through the pinned ai-cli-mcp server. Use for adversarial reviews, implementation reviews, research, and one-off delegated tasks when the user names Claude, Opus, Fable, OpenCode, 0x Alpha, Codex, or asks for an external model.
    5 installs
  26. ▌
    Diataxis Docs · pmndrs bundle
    Design, classify, write, audit, or restructure technical documentation with the Diátaxis framework. Use for tutorials, how-to guides, reference material, explanations, documentation maps, README routing, documentation audits, or requests to separate mixed-purpose docs. Do not apply it automatically to internal plans, ADRs, research logs, or specifications unless the user wants those artifacts organized as product documentation.
    2 installs
  27. ▌
    Evidence First · pmndrs bundle
    Shape human-facing engineering communication—including chat updates and final answers, reports, reviews, handoffs, debugging or benchmark summaries, PR and issue prose, READMEs, and technical documentation—around clear claims, measured support, explicit gaps, and scoped decisions. Use whenever Codex presents engineering work, evidence, or findings to a human; let document-specific frameworks retain their purpose and structure.
    6 installs
  28. ▌
    Engine Call Contract · pmndrs
    How every call into the text engine is shaped, and where each entry point's names live. Use before adding, moving, or removing anything on a published surface, before adding an error path or a result type to an engine call, and when deciding whether a failure belongs to the caller or to this package.
    5 installs
  29. ▌
    Open Knowledge Format · pmndrs bundle
    Create, migrate, inspect, query, validate, or maintain Open Knowledge Format v0.2 bundles made from linked Markdown concepts with YAML provenance. Use when the user mentions OKF, Open Knowledge Format, knowledge bundles, LLM wikis, portable agent knowledge, OKF conformance, provenance, trust, lifecycle, attested computations, or asks to make repository knowledge interoperable across human and agent tools. Do not use for ordinary Markdown unless OKF compatibility or a knowledge bundle is requested.
    4 installs
  30. ▌
    Maintainability Review · pmndrs bundle
    Audit and improve repository code milestone by milestone for correctness, clarity, local reasoning, DRY design, explicit state modeling, panic resistance, and trustworthy TypeScript boundaries. Use for deliberate cleanup passes, pre-release maintainability reviews, agent-assisted refactors, or requests invoking Jane Street-style algebraic data types, Rust newtypes, TypeScript discriminated unions, type guards, or evidence-backed simplification without public API churn.
    9 installs
  31. ▌
    Speckit Plan · pmndrs
    Execute the implementation planning workflow using the plan template to generate design artifacts.
    4 installs
  32. ▌
    Speckit Tasks · pmndrs
    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
    4 installs
  33. ▌
    Speckit Analyze · pmndrs
    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
    6 installs
  34. ▌
    Speckit Clarify · pmndrs
    Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
    6 installs
  35. ▌
    Speckit Specify · pmndrs
    Create or update the feature specification from a natural language feature description.
    3 installs
  36. ▌
    Speckit Checklist · pmndrs
    Generate a custom checklist for the current feature based on user requirements.
    5 installs
  37. ▌
    Speckit Implement · pmndrs
    Speckit Implement
    5 installs
  38. ▌
    Speckit Git Commit · pmndrs
    Auto-commit changes after a Spec Kit command completes
    5 installs
  39. ▌
    Speckit Git Feature · pmndrs
    Create a feature branch with sequential or timestamp numbering
    5 installs
  40. ▌
    Speckit Constitution · pmndrs
    Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
    5 installs
  41. ▌
    Speckit Taskstoissues · pmndrs
    Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
    5 installs
  42. ▌
    Koota · pmndrs bundle
    Real-time ECS state management for TypeScript and React. Use when the user mentions koota, ECS, entities, traits, queries, or building data-oriented applications.
    4 installs
  43. ▌
    Math · pmndrs
    Use when writing or reviewing geometry, simulation, collision, navigation, culling, procedural generation, transforms, or other performance-sensitive algorithms with the npm `math` package, or when the user invokes /math. Not for routine arithmetic or textbook explanations.
    10 installs
  44. ▌
    React Three Start · pmndrs
    Build, explain, and modify @react-three/start apps that use file-based React Three Fiber scene and DOM composition. Use when working in a react-three-start project, when the user mentions @react-three/start, react-three-start, R3F app structure, .scene.tsx/.dom.tsx files, Scene/Dom slots, wrappers, start.config.ts, or the react-three-start/r3s CLI.
    7 installs
  45. ▌
    Vitexec · pmndrs bundle
    Use this skill when an AI agent needs to inspect, verify, debug, or profile a live Vite app by running temporary snippets inside the browser page and reading browser logs or captured artifacts. Use for client state after interactions, imported app modules, DOM state, human-like input, canvas/WebGL/Three.js state, screenshots, videos, CPU/network/performance/heap analysis, WebXR/Three.js XR with IWER, and runtime-only behavior without editing app files.
    5 installs