Loading...
Loading...
Found 939 Skills
Scaffold a new Decentraland SDK7 scene project. Use when the user wants to start a new scene or create a project. Do NOT use for deployment (see deploy-scene or deploy-worlds).
Apply physics forces to the player in Decentraland scenes. Impulses (one-shot pushes), knockback (push away from a point with falloff), continuous forces (wind tunnels, anti-gravity, lift, hover), timed forces, and repulsion fields. Use when the user wants launch pads, knockback on hit, wind zones, gravity fields, or lifting/floating/hovering the player. THIS is also the right skill when an agent's first instinct is to mutate `Transform` on `engine.PlayerEntity` to move/lift/push the player — that does NOT work (player Transform is engine-controlled and read-only); use the Physics API instead. Do NOT use for player movement speed (see player-avatar AvatarLocomotionSettings) or platform movement (see animations-tweens).
Add sound effects, music, audio streaming, and video players to Decentraland scenes with AudioSource, AudioStream, and VideoPlayer. Use when the user wants sound, music, video screens, radio, live streams, or media playback. Do NOT use for player emotes (see player-avatar) or screen-space UI sounds (sounds attach to entities, not UI).
Animate objects in Decentraland scenes. Play GLTF model animations with Animator, create procedural motion with Tween, chain sequences with TweenSequence. Use when the user wants to animate, move, rotate, scroll a texture, or create motion effects. Do NOT use for audio/video playback (see audio-video), player emotes (see player-avatar), or physics-driven motion (see player-physics).
Reference for the Decentraland `.composite` JSON format that declares the initial entities of a scene in `assets/scene/main.composite`. Use when creating or editing a main.composite file, or when other skills point to the composite reference. For scaffolding a whole scene project see create-scene.
Wait. I didn't understand the previous message—please re-explain it.
Ask me questions within this workspace regarding the workflow requirements I want to build.
Set up Husky pre-commit hooks in the current repository, integrating lint-staged (Prettier), type checking, and testing. Use this when users want to add pre-commit hooks, set up Husky, configure lint-staged, or add formatting/type checking/testing on commit.
A rigorous interrogation session for refining plans or designs, with documentation (ADR and glossary) generated during the process.
Grill the user's plans, decisions, or ideas layer by layer. Use this when the user wants to stress-test their thinking or uses any 'grill' trigger phrase.
Harbor CLI command reference and usage patterns. Covers harbor run, harbor jobs, harbor trials, harbor datasets, harbor adapters, harbor tasks, harbor view, harbor sweeps, harbor traces, harbor cache, and harbor admin commands. Use this skill whenever running Harbor evaluations, managing datasets, viewing results, debugging tasks, exporting traces, or working with any harbor CLI command. Also use when constructing harbor command lines, looking up flag names, or troubleshooting CLI errors.
Stand up (or extend) an operator-only in-app scratchpad / internal test-bed — a single gated internal page that reuses the project's real components and library functions so you can judge work-in-progress by eye: eyeball generated visuals (OG/social cards, emails, avatars, empty states), compare variants side by side or with live sliders, check config/env readiness, and exercise real side-effecting flows with fake data — without shipping any of it to users or clicking through the whole product. Boards and config panels get a "Copy as JSON" button so a tuned-by-eye result round-trips straight back into the code or to an agent to apply. Bootstraps into the user's existing stack: detects the framework, auth, and env conventions, writes a fail-closed access gate first, then a route with a section switcher seeded from their own code. Use when a user says "spin up a scratchpad", "internal test bed / dev playground / sandbox page", "an operator/admin preview page", "a page to eyeball my work", "preview my OG cards / emails / component variants", "add a test page for these components", or "an internal page to exercise a flow with fake data". NOT for public/user-facing features, NOT a replacement for tests (pass/fail machine-checkable → write a test), NOT Storybook (this lives inside the real app), and NOT a place to do load-bearing production operations.