# StudioLimb Production System — 0.12.0 RC

This package is a **free open-beta release candidate**. It may be evaluated in up to three distinct, non-confidential projects under `beta/BETA-PARTICIPANT-NOTICE.md`, but it is not yet approved for public resale or commercial source delivery.

## Choose the right Figma file

### Native Modes

Open `1-StudioLimb-Production-System-Native-Modes-RC-0.12.0.fig` when your Figma workspace supports variable modes, such as an Education or Professional team.

This distribution includes native `Light`/`Dark` theme modes and `Desktop`/`Tablet`/`Mobile` viewport modes.

### Starter Compat

Open `2-StudioLimb-Production-System-Starter-Compat-RC-0.12.0.fig` when you use Figma Starter or need a file that does not depend on native theme or viewport modes.

This distribution uses separate fixed Light and Dark collections and masters.

Do not install or edit both distributions in the same project. Choose one, import it into Figma, and duplicate the imported file before customizing it.

## Import into Figma

1. Open the Figma file browser in the correct account and team.
2. Drag the chosen `.fig` file into the destination project, or use **Import**.
3. Confirm the two physical pages appear: `00 — Start & Foundations` and `01 — Components, Patterns & Templates`.
4. Confirm Cover, Start Here, Components, Patterns, Templates, QA Lab, Playground, Handoff, and Changelog are visible as internal areas.
5. Duplicate the imported file and keep the original RC file unchanged as a local reference.
6. Read `StudioLimb-Quick-Start-Guide.pdf`, `COMPATIBILITY.md`, and `KNOWN-LIMITATIONS.md` before adapting tokens or components.

## Package contents

- Two editable Figma distributions.
- A 12-page Quick Start Guide.
- 322 design tokens in JSON and CSS formats, including all 82 component variables.
- An exact Figma–DTCG–CSS map in `tokens/FIGMA-TO-CODE-MAP.csv`.
- Release notes in `CHANGELOG.md`.
- A draft future commercial license for review in `LICENSE-DRAFT.md`; the operative open-beta evaluation terms are in `beta/BETA-PARTICIPANT-NOTICE.md`.
- A structured beta checklist in `BETA-TEST-GUIDE.md`.
- The full component protocol in `COMPONENT-QA.md` and an implementation-ready example in `examples/HANDOFF-EXAMPLE.md`.
- A common beta dataset, results form, operational participant notice, recruitment copy and defect log in `beta/`.
- Compatibility, manifest, release-validation, known-limitations and third-party-notices documents.
- SHA-256 integrity hashes in `CHECKSUMS-SHA256.txt`.

## Verified inventory per distribution

- 35 public component sets.
- 6 utility component sets.
- 1 viewport reference set.
- 10 functional patterns.
- 4 product template families represented across 24 theme/viewport combinations.
- 14 text styles, 4 effect styles, and 3 grid styles.

All 24 template combinations passed dimension checks and retain linked component instances. Representative Cover, Start Here, QA Lab, and Dashboard screens passed visual review.

## Release limitations

- Open-beta evidence requires feedback from at least five designers and three developers. The `1.0.0` gate requires eight designers and four developers in total.
- The exact final Starter and Native bytes imported, closed and reopened successfully on 2026-08-28 with both documented pages and no blocking warning. A first different-owner Education/Professional Native import remains an external-beta evidence target.
- Any P0 or P1 defect blocks release.
- The included license is a draft and requires final legal/editorial review.
- Public product screenshots, verified testimonials, and the Gumroad test-purchase gate are not part of this RC.

For the current StudioLimb product status, visit [studiolimb.com](https://www.studiolimb.com/).

After evaluation use 1, 2 and 3, prepare a short structured response at <https://www.studiolimb.com/products/figma-production-system/beta-feedback.html>. The page prepares an email locally and transmits nothing automatically.

## Verify package integrity

From the unpacked package directory on macOS or Linux:

```sh
shasum -a 256 -c CHECKSUMS-SHA256.txt
```

On Windows PowerShell, compare each recorded hash with:

```powershell
Get-FileHash -Algorithm SHA256 .\path\to\file
```

Every file must match before testing. The checksum file intentionally does not hash itself.
