# StudioLimb 0.12.0 RC — Closed Beta Test Guide

Use one copy of this checklist for every participant. Do not coach the participant during the timed tasks; record where they hesitate, fail, or ask for help.

Use the shared content in `beta/BETA-DATASET.md` and record each session in `beta/BETA-RESULTS-FORM.md`. Log every issue in `beta/DEFECT-LOG.csv`.

## Participant record

- Participant ID:
- Role: Designer / Developer
- Figma plan:
- Distribution tested: Native Modes / Starter Compat
- Date:
- Observer:

## Designer tasks

1. Import the appropriate `.fig` file and locate Start Here.
2. Create a duplicate working file.
3. Change the brand accent and one semantic color without manually recoloring individual components.
4. Build a form using the existing input, select, checkbox, button, and validation states.
5. Adapt one pattern to mobile and dark theme.
6. Create one screen from a supplied template without detaching its core instances.
7. Locate the accessibility and responsive notes needed to hand the screen to a developer.
8. Stress-test Input, Select, Checkbox, Tabs, Table, Dialog, and Menu at 320 px, with Spanish content and 200% expected text length.

Record for each task:

- Completed without help: Yes / No
- Time:
- Errors or hesitation:
- Missing component, state, or instruction:

## Developer tasks

1. Locate the token source and identify the value used for the primary action background.
2. Find hover, focus, disabled, error, and loading behavior for a core interactive component.
3. Identify the spacing, type, radius, and color rules needed to implement one supplied template.
4. Compare the Figma values with `tokens/design-tokens.json` and `tokens/design-tokens.css`.
5. List any ambiguous naming, missing state, or value that requires a designer explanation.

Record for each task:

- Completed without help: Yes / No
- Time:
- Ambiguity or mismatch:
- Missing handoff information:

## Severity

- **P0:** data loss, unusable file, broken import, or core workflow impossible.
- **P1:** wrong tokens/states, major accessibility failure, or a core task requires rebuilding/detaching.
- **P2:** confusing instruction, inconsistent naming, or workaround exists.
- **P3:** polish or optional enhancement.

## Exit questions

1. What was the hardest part?
2. What did you expect to find but could not?
3. What would stop you from using this in real work?
4. What saved the most time?
5. What single improvement would make the product worth paying for?
6. May StudioLimb contact you for clarification? Yes / No
7. May StudioLimb quote your feedback publicly? Yes / No — request separate written approval before publication.

## Release gates

### Wave 1 RC gate

At least five designers and three developers complete the test through the open beta. Every discovered P0/P1 is fixed and the affected task is retested before the beta is promoted as commercially ready.

### `1.0.0` paid-launch gate

Eight designers and four developers in total complete the test; at least six designers finish quick start without help, and four developers find responsive rules, states and acceptance criteria in under three minutes. In addition, all P0/P1 defects are closed, accepted P2 items appear in release notes, clean imports pass in both independent plan contexts, the license receives final legal/editorial review, and a real Gumroad purchase/download is verified.
