Skip to content
Skills Library
Design & UX · Building & coding

forma-objects-3d

/forma-objects-3d

Integrate or refine reusable material objects, BookObject, books, covers and 2D/3D mascots, including geometry, materials, gestures and lifecycle. Use for object mechanisms and fidelity; not to add decorative 3D to every interface.

Repository
forma ↗
Licence
MIT
Last repository change
11.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Integrate or refine reusable material objects, BookObject, books, covers and 2D/3D mascots, including geometry, materials, gestures and lifecycle. Use for object mechanisms and fidelity; not to add decorative 3D to every interface.

Original author description

Integrate or refine reusable material objects, BookObject, books, covers and 2D/3D mascots, including geometry, materials, gestures and lifecycle. Use for object mechanisms and fidelity; not to add decorative 3D to every interface.

How it works

  1. When to use
  2. Inputs
  3. Procedure
  4. Output and stopping condition
  5. Coordination and execution boundaries
Original SKILL.md headings · 45 lines, 659 words
SKILL.md preview
---
name: forma-objects-3d
description: "Integrate or refine reusable material objects, BookObject, books, covers and 2D/3D mascots, including geometry, materials, gestures and lifecycle. Use for object mechanisms and fidelity; not to add decorative 3D to every interface."
metadata:
  version: 1.36.0
---

# Objects, material and 3D

## When to use

- Use to reuse BookObject, correct material/volume, preserve a mascot or adapt an authorized scene/object.
- Do not use to assume WebGL for every card, profile, mascot or campaign image.

This module guides execution after it is read; it does not start a renderer, generation or other modules by itself.
Preserve the brand and stack. When the request includes actual 3D, tilted CSS does not meet that acceptance criterion.

For a relevant saved capability, use [reuse by capability](../../references/capability-reuse.md): search by the task, not the source project, and bind the mechanism to the destination's own identity and state owners. Read only the matching contract; do not expand a local fix into a redesign. Source names and exact profiles remain provenance or explicit fidelity targets.

## Inputs

- Object and destination consumer, requested mechanism, reference/version, relevant states and views.
- Available code/assets, loader/dependencies, authorized identity, execution limits and fallback.

## Procedure

1. Establish content, geometry, materials, behavior and integration; separate static and runtime evidence.
   Read [reusable objects](../../references/reusable-objects.md) and reuse in [playbooks](../../references/playbooks.md); confirm whether the object fits the BookObject contract.
2. For an approved BookObject, use the [complete book integration](../../references/book-integration.md) and [book lab](../../assets/book-lab.html). Reuse BookPreset, the supplied Inter font and a real Three loader; preserve color management, lighting, shadows, stage size and reset semantics. Bare BookObject defaults are generic. Inspect the distributed asset and its consumer; adapt parameters without guessing mesh/material rewrites.
   Read the [refinement case study](../../references/book-polish-case-study.md). For existing articulated covers/pages, strip-like edges or leather lacking body, consult the [passport case](../../references/passport-polish-case-study.md): diagnose surface, fit, UVs and light before changing thickness. This is knowledge from an approved CSS 3D consumer, not BookObject geometry. The extracted [NeuronPassport component](../../references/reusable-components.md#neuronpassport-integration) preserves that CSS engine and its visual layers. Use it as the primary passport when reproducing Neuron; keep the complete companion assets and match host conditions. The older Three PassportObject is a legacy alternative, not a faithful substitute. For mascots, use [mascot refinement](../../references/mascot-refinement.md) and preserve silhouette, negative spaces and expression.
3. If a discrepancy exists, trace configuration through geometry, UVs, normals, shader, font, buffer and output.
   Use [package-to-pixel fidelity](../../references/3d-reference-fidelity.md); for scene mechanism/cost choices, read [immersive web](../../references/immersive-web-tech.md).
   For articulated pages, also consult the passport case's pages/divider section: distinguish the paper's starting edge, content inset and gesture pivot; check both sides' connection and overlap that may pass through the cover when closing.
4. Integrate code and assets into the destination project with a valid loader, events, resize, disposal and error/fallback handling.
   Connect the requested state and persistence. The [component lab](../../assets/components-lab.html) supplies a runnable example and real renderer counters; use its documented loader and adapt ownership/lifecycle in the destination. A snippet, contract or copied file without a consumer is not a mechanism available at runtime.
5. Observe the main path and test relevant views/gestures, materials, extreme content and unmounting.
   Use [rendered validation](../../references/rendered-validation.md) and [verification](../../references/verification.md); validate fallback and reduced motion separately. For release/reuse audits, follow the [browser proof matrix](../../references/release-validation.md#browser-proof-matrix): distinguish hardware/software WebGL, CPU render submission, GPU cost, live media changes, emulated touch and physical devices.

## Output and stopping condition

Deliver the integrated object or requested specification, the API actually used and renderer evidence in the destination.
Record what was integrated, adapted, replaced or not tested; a library comparison does not prove visual equivalence.
Stop when the consumer exercises the requested mechanism and views, gestures and material meet the established acceptance criteria.
If only the fallback works, do not conclude that the primary volume/renderer was validated. State the concrete remaining dependency.

## Coordination and execution boundaries

Use Forma Reference to investigate an unknown mechanism, Forma Motion for gestures, and Forma Validation for controlled rendered comparisons. Geometry, materials and renderer decisions remain in this module.
The coordinator selects additional modules; do not recursively dispatch between specialists. Use the available tools according to [capabilities](../../references/integrations.md); a tool name does not prove connection or execution.
Do not install engines or change the stack by visual association. Materiality, image generation and executable geometry are distinct deliverables.
Files in this package (2)
  • SKILL.md 6 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · figueirego/forma100MIT
figueirego/forma100MIT

Database snapshot: 13.11.2026 · package version b8ecba6ec251 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90forma-interface
    Build or refine operational interfaces, clean shells, forms, navigation, search, settings, appearance editors and material profiles. Use for usable components and states; not for broad research, campaigns or 3D geometry implementation.
  • 90forma-interface
    Build or refine operational interfaces, clean shells, forms, navigation, search, settings, appearance editors and material profiles. Use for usable components and states; not for broad research, campaigns or 3D geometry implementation.
  • 100forma
    Set up and use Forma, a headless CLI that renders designs from JSON frames and shared design tokens to PNG. Use this skill whenever the user mentions forma, a repo contains forma/config.json, or the user wants to add a design system (colors, type, logos, example images) to a…
  • 100forma
    Read and edit Forma boards, the designer's research boards that live as plain folders (board.json + media/ + components/). Use whenever the user asks to add, sort, connect, find or change anything on a Forma board, to bring research in (images, videos, links, notes, meetings,…
  • 100forma-templating
    Builds an installable project template (a separate plugin in the forma marketplace's templates/ directory) out of the current Forma project, under the name the human gives. Invoke when the human says "create a project template", "make a template from this project", "package the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.