Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Modeling Toolkit panel

Open
  • Is something wrong?
#64 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
ai-infra-agents, desktop

Research direction

This is a design-level feature with no implementation yet and a dependency on in-progress UI parity work (slice A) and the pinned Maya reference in #5. Start by reading .project-docs/mcp.md and its coverage inventory to see how Editor operations are exposed. Done means the acceptance criteria hold: implemented-only controls, MCP schemas and protocol tests, a reviewed native screenshot, and failure cases that preserve the baseline.

Written by the indexing model from the issue text.

Description

area/modeling area/ui-parity type/feature

Problem

Not present.

Current behavior

Not implemented.

Expected behavior

Modeling Toolkit with selection, components and tool sections, populated only with implemented operations. The per-element Autodesk Maya 2026 doc links are being collected in the UI parity inventory (slice A, in progress); add them here when it lands.

Acceptance criteria

  • Unimplemented controls stay visibly disabled with a reason; no dummy tools or controls.
  • MCP coverage in the same change: implemented operations and relevant state exposed with synchronized tool schemas, real Editor protocol tests (scene token, draft, modal, close and busy guards) and updates to .project-docs/mcp.md and its coverage inventory.
  • Native visual check of the real window (screenshot reviewed), not only headless tests.
  • Tests cover malformed, empty, boundary and failure cases; failed operations preserve the baseline.
  • No parity claim without comparison against the pinned Maya reference (#5); unverified constants are documented as provisional.
Dominant language
Rust
Stars
4
Forks
2
Avg merge
2h 28m
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cristim/AztecCraft

All issues in cristim/AztecCraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.