Results for “2d”

Applies Qt Canvas2D (QtCanvas2D / Qt Canvas Painter, Qt 6.12+) best practices when producing or working with Canvas2D QML source code. Use whenever Canvas2D, Canvas2DContext, path2d, boxshadow2d, boxgradient2d, gridpattern2d, conicalgradient2d or transform2d is the subject: writing, reviewing, fixing, optimizing, or porting Qt Quick Canvas / HTML5 canvas drawing code to Canvas2D. Also use for GPU-accelerated imperative 2D drawing in QML — gauges, dials, charts, waveforms, oscilloscopes, clocks, freehand drawing — including choosing between Canvas2D and Shape/ShapePath when the renderer has not been decided yet. Do NOT trigger for plain Qt Quick Canvas work that must stay on the old CPU element, or for reviewing existing Shape/ShapePath code where the renderer is already settled.

The English summary is being prepared. Showing the original description.

Expert patterns for Godot 2D physics including collision layers/masks, Area2D triggers, raycasting, and PhysicsDirectSpaceState2D queries. Use when implementing collision detection, trigger zones, line-of-sight systems, or manual physics queries. Trigger keywords: CollisionShape2D, CollisionPolygon2D, collision_layer, collision_mask, set_collision_layer_value, set_collision_mask_value, Area2D, body_entered, body_exited, RayCast2D, force_raycast_update, PhysicsPointQueryParameters2D, PhysicsShapeQueryParameters2D, direct_space_state, move_and_collide, move_and_slide.

The English summary is being prepared. Showing the original description.

Expert patterns for Godot 2D physics including collision layers/masks, Area2D triggers, raycasting, and PhysicsDirectSpaceState2D queries. Use when implementing collision detection, trigger zones, line-of-sight systems, or manual physics queries. Trigger keywords: CollisionShape2D, CollisionPolygon2D, collision_layer, collision_mask, set_collision_layer_value, set_collision_mask_value, Area2D, body_entered, body_exited, RayCast2D, force_raycast_update, PhysicsPointQueryParameters2D, PhysicsShapeQueryParameters2D, direct_space_state, move_and_collide, move_and_slide.

The English summary is being prepared. Showing the original description.

Inspect and edit Live2D Cubism model files from the command line. Check referenced assets, adjust motion and expression settings, compare versions, process multiple models, and prepare model files for distribution without opening Live2D Editor.

• Check for missing assets and unused files
• Adjust motion fade times across multiple models
• Compare model versions

Build reusable data packages for local 2D character animation. Define separate body parts, rotation points, layer order, movement limits, and views so a shared renderer can animate each character using its own rig data.

• Prepare a 2D character for local animation
• Define joint rotation points and movement limits
• Organize mouths, eyes, and props as separate parts

Make game-ready 2D characters, creatures, props, icons and FX as master stills, sprite sheets or animation clips. Plan size, motion and finish; generate the art (image generation is the default, through generate2dmedia route_media.py - the API when a key is configured, else the local Codex or Grok CLI); approve one master still per character; then key, slice, register, scale, palette, QA and export frames for a game engine (Aseprite JSON, Godot SpriteFrames or Sprite3D). HD finish by default, pixel finish on request. Character animation is one image-to-video clip per action from the master (video2dsprite); sheets are for FX, icons and props. Use for sprites, masters, sheets, frame-by-frame animation and packaging frames from any source. Not for maps, tiles or backgrounds (generate2dmap), video clips (video2dsprite), code-drawn art (codeart2d, only on request) or calling an image or video API by itself (generate2dmedia).

The English summary is being prepared. Showing the original description.

Plan and build 2D game maps and scenes - top-down and side-scrolling levels, tilemaps, prop packs, parallax backgrounds and HD-2D battle or story plates - with collision, navigation and reachability checks, environment motion, a playable HTML preview and export to Tiled, Godot 4 or LDtk. Map art (terrain, tiles, props, plates, parallax layers) is image generation by default, through generate2dmedia route_media.py (the API when a key is configured, else the local Codex or Grok CLI); map data (layout, collision, exits, spawns) is written as data. Use for any map, level, room, scene, background, terrain or prop-kit request. Not for characters, creatures, items or FX (generate2dsprite), character animation (video2dsprite), code-drawn tiles or maps (codeart2d, only on request) or calling an image or video API by itself (generate2dmedia).

The English summary is being prepared. Showing the original description.

Plan and build 2D game maps and scenes - top-down and side-scrolling levels, tilemaps, prop packs, parallax backgrounds and HD-2D battle or story plates - with collision, navigation and reachability checks, environment motion, a playable HTML preview and export to Tiled, Godot 4 or LDtk. Map art (terrain, tiles, props, plates, parallax layers) is image generation by default, through generate2dmedia route_media.py (the API when a key is configured, else the local Codex or Grok CLI); map data (layout, collision, exits, spawns) is written as data. Use for any map, level, room, scene, background, terrain or prop-kit request. Not for characters, creatures, items or FX (generate2dsprite), character animation (video2dsprite), code-drawn tiles or maps (codeart2d, only on request) or calling an image or video API by itself (generate2dmedia).

The English summary is being prepared. Showing the original description.

Make game-ready 2D characters, creatures, props, icons and FX as master stills, sprite sheets or animation clips. Plan size, motion and finish; generate the art (image generation is the default, through generate2dmedia route_media.py - the API when a key is configured, else the local Codex or Grok CLI); approve one master still per character; then key, slice, register, scale, palette, QA and export frames for a game engine (Aseprite JSON, Godot SpriteFrames or Sprite3D). HD finish by default, pixel finish on request. Character animation is one image-to-video clip per action from the master (video2dsprite); sheets are for FX, icons and props. Use for sprites, masters, sheets, frame-by-frame animation and packaging frames from any source. Not for maps, tiles or backgrounds (generate2dmap), video clips (video2dsprite), code-drawn art (codeart2d, only on request) or calling an image or video API by itself (generate2dmedia).

The English summary is being prepared. Showing the original description.

Plan game development by choosing specialized skills for the target platform, 2D or 3D graphics, and gameplay needs. Get guidance on shared foundations such as game loops, input handling, design patterns, and performance budgets.

• Planning a browser-based 2D platformer
• Designing a mobile puzzle game
• Organizing development for a multiplayer VR game

Create and update 2D DXF drawings from written requirements or CAD geometry using Python and build123d. Prepare cutting profiles and marking layers, check for open contours and duplicate geometry, and review drawings in CAD Viewer.

• Create dimensioned gasket or panel drawings
• Generate flat profiles from STEP geometry
• Separate cutting and engraving geometry into layers

Plan the early stages of a browser game by choosing suitable technology and coordinating gameplay, interface, assets, and playtesting. It defaults to Phaser for 2D games and routes more specific work to the relevant specialist skills.

• Choosing technology for a browser-game prototype
• Planning gameplay loops, failure states, and progression
• Coordinating interfaces and 2D or 3D assets

Expert patterns for migrating 2D games to 3D including node type conversions, camera systems (third-person, first-person, orbit), physics layer migration, sprite-to-model art pipeline, and control scheme adaptations. Use when porting 2D projects to 3D or adding 3D elements. Trigger keywords: CharacterBody2D to CharacterBody3D, Area2D to Area3D, Camera2D to Camera3D, Vector2 to Vector3, collision_layer migration, sprite to MeshInstance3D, 2D to 3D conversion.

The English summary is being prepared. Showing the original description.

Expert patterns for migrating 2D games to 3D including node type conversions, camera systems (third-person, first-person, orbit), physics layer migration, sprite-to-model art pipeline, and control scheme adaptations. Use when porting 2D projects to 3D or adding 3D elements. Trigger keywords: CharacterBody2D to CharacterBody3D, Area2D to Area3D, Camera2D to Camera3D, Vector2 to Vector3, collision_layer migration, sprite to MeshInstance3D, 2D to 3D conversion.

The English summary is being prepared. Showing the original description.

Unity 6 2D game development guide. Use when building 2D games, working with sprites, sprite atlas, SpriteRenderer, tilemaps, 2D physics (Rigidbody2D, Collider2D), 2D lighting, sorting layers, or sorting groups. Based on Unity 6.3 LTS documentation.

The English summary is being prepared. Showing the original description.

Windows アプリ開発 (DirectX / WinRT メディア) のグラフィックス・メディア API リファレンス。 Direct2D (ID2D1Factory, ID2D1DeviceContext, ID2D1Bitmap1, ID2D1Effect, D2D1 Effects, ID2D1PathGeometry), DirectWrite (IDWriteFactory, IDWriteTextLayout, DWriteCore), Direct3D 11/12 (D3D11CreateDevice, D3D11On12, DXGI SwapChain, HLSL, D3D12 PipelineState, D3D12 DRED), Microsoft.UI.Composition (Compositor, Visual, ExpressionAnimation, InteractionTracker, MicaController), カメラ・画面キャプチャ (MediaCapture, MediaFrameReader, GraphicsCaptureSession, Windows Studio Effects, OpenCV)、音声・動画再生 (MediaPlayer, MediaPlaybackSession, AudioGraph, MediaTranscoder, AdaptiveMediaSource, HLS, DASH, CastingDevicePicker, AudioPlaybackConnection)。

The English summary is being prepared. Showing the original description.

Read, analyze, modify, and visualize molecular structures with RDKit in Python. Calculate molecular properties, search for similar structures or specific structural patterns, apply reaction rules, and generate 2D or 3D coordinates with detailed control over processing.

• Calculating properties for a collection of molecules
• Searching for molecules with similar structures
• Filtering molecules by specific structural patterns

Read and display CARLA object bounding boxes, then project them onto a camera image as 2D rectangles. Export an annotated PNG and box coordinates in JSON for object detection annotation work.

• Adding vehicle boxes to a camera image
• Exporting box coordinates for detection annotations
• Checking vehicle dimensions

Create 2D sprite animations from an approved character frame. Generate all frames together, normalize their size and alignment, and prepare preview sheets to check consistency before using the animation in a game.

• Create an animation from an approved character frame
• Normalize frame size and anchor alignment
• Match the first frame to an existing game sprite

Build 2D browser games with Phaser, TypeScript, and Vite. Organize gameplay rules separately from rendering, implement cameras and sprite animation, and add HTML overlays for status displays and menus.

• Building a turn-based grid tactics game
• Creating top-down exploration or side-view action
• Adding status displays and command menus

Create interactive views of dense datasets, spatial paths, and flows using WebGL, which uses the GPU for rendering. Choose suitable libraries and design navigation, labels, animation, and static alternatives around the analytical task.

• Explore spatial trajectories and point clouds
• Build dense scatterplots and network views
• Animate flows between locations or nodes

Build dense, frequently updated charts with Canvas2D, including zooming, clicking, and dragging. Guides rendering performance, mobile interactions, and the use of SVG or HTML for labels, controls, and accessibility.

• Build a scatterplot with a million points
• Add selection and zoom to a timeline
• Move an SVG heatmap to Canvas while preserving labels

The art-route layer of the Forge skills. route_media.py is the one command that generates an image or an image-to-video clip - through the paid API of any provider whose key is configured (OpenAI, Google Gemini, xAI, BytePlus ModelArk, fal.ai; the configured key is the owner's consent), else through the user's own signed-in Codex or Grok CLI - and prints one JSON line with the route, artifact, sha256 and cost estimate; with no route it answers no-route (codeart2d is then the last resort). Also the capability check (forge_doctor), API key configuration, the spend ledger, resume and Codex image adoption. Use when a Forge skill sends a generation here, for the capability check, or when the user asks about keys, routes or spend. Not for planning, processing or QA of sprites, video frames or maps (generate2dsprite, video2dsprite, generate2dmap) or for code-drawn art (codeart2d).

The English summary is being prepared. Showing the original description.

Turn one approved master still into a character's whole animated sprite set - one image-to-video clip per action (idle, walk, run, attack, jump, hurt, cast and so on), all from that still, generated through generate2dmedia route_media.py (the xAI API when a key is configured, else the local Grok CLI) - then gate each take, key it with a soft matte, register it to the master, pick loops or retime actions, finish (HD by default, pixel on request) and package fixed-canvas frames, alpha WebM, packed MP4 for iPhone and a PNG fallback with engine metadata and a JS runtime. Also processes a supplied clip. Use for character and creature animation, fluid motion and any video-to-sprite work. Not for FX, icon or prop sheets (generate2dsprite), maps or plate loops (generate2dmap), code-drawn animation (codeart2d, only on request) or calling a video API by itself (generate2dmedia).

The English summary is being prepared. Showing the original description.