Spectacles 522 Portable Design

Design rules for building Spectacles lenses in Lens Studio 5.22 (CLAD/MCP workflow) so they downgrade to LS 5.15.4 for device testing in under an hour. Load when STARTING or architecting a new 5.22 Spectacles project that will later be tested on Spectacles (2024), when the user says "we will downgrade to 5.15" / "5.15-portable" / "we will test on device later", or before adding any shader/material/package to a 5.22 project that must survive the downgrade. Distilled from two full real-project migrations.

9 stars 1 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add PtPavloTkachenko/spectacles-agent-skills --skill spectacles-522-portable-design
Manual install
git clone --depth 1 https://github.com/PtPavloTkachenko/spectacles-agent-skills.git /tmp/spectacles-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/spectacles-agent-skills/skills/spectacles-522-portable-design ~/.claude/skills/spectacles-522-portable-design

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Building 5.15-portable lenses in Lens Studio 5.22

**Why this exists:** CLAD/agentic development lives in LS 5.22+, but Spectacles (2024)
device work ships from LS 5.15.4. Two real projects proved
you can have both — IF the project is architected for portability from day one.
The second migrated in ~1 hour with ZERO code changes (19 scripts compiled first try).
Companion skill for the actual move: `spectacles-522-to-515-migration`.

## The Golden Rule: runtime-first architecture

**The scene must be trivially reconstructible.** Target: ONE SceneObject with the root
controller script + a handful of @input references (modules, base materials, font).
EVERYTHING else — meshes, materials-on-clones, UI, FX, colliders, Interactables — is
created in `onStart()` from code.

- Migration cost of a code-built scene = create 1 object + set N inputs (minutes via
  the 5.15 granular MCP ChatTools: CreateLensStudioSceneObject →
  CreateLensStudioComponent(ScriptComponent) → SetLensStudioProperty scriptAsset +
  inputs by name).
- Migration cost of an editor-built scene = re-authoring everything by hand. Don't.
- Add a `DebugHarness` object (debugState seeder) as the ONLY other scene object —
  it makes every state reachable in preview without play-through AND survives
  migration the same cheap way.

## Materials & shaders (where migrations die)

1. **Base materials = ImageMaterialPreset ONLY**, passed as @input. It has the
Read the full skill on GitHub

Details

Skill name
spectacles-522-portable-design
Path
skills/spectacles-522-portable-design/SKILL.md
License
MIT
Repo updated
20 July 2026

FAQ

What does the Spectacles 522 Portable Design skill do?

Design rules for building Spectacles lenses in Lens Studio 5.22 (CLAD/MCP workflow) so they downgrade to LS 5.15.4 for device testing in under an hour. Load when STARTING or architecting a new 5.22 Spectacles project that will later be tested on Spectacles (2024), when the user says "we will downgrade to 5.15" / "5.15-portable" / "we will test on device later", or before adding any shader/material/package to a 5.22 project that must survive the downgrade. Distilled from two full real-project migrations.

How do I install the Spectacles 522 Portable Design skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add PtPavloTkachenko/spectacles-agent-skills --skill spectacles-522-portable-design. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Spectacles 522 Portable Design popular?

It lives in PtPavloTkachenko/spectacles-agent-skills, which has 9 GitHub stars and 1 forks.

Related skills

Spectacles 522 to 515 Migration

9

PtPavloTkachenko/spectacles-agent-skills

Battle-tested playbook for migrating a Lens Studio 5.22 project down to LS 5.15.4 for Spectacles (2024). Triggers on: migrate 5.22 to 5.15, downgrade lens studio project, 5.22 package errors in 5.15, SingleCompressionSettings error, PerformanceCompressionSettings error, Invalid graph header, !passList.empty(), duplicate PassInfo reimport loop, PassInfo transplant, materials white after clone, 5.22 lspkg crashes 5.15.

Other

Experiment Designer

9

Grafuja/Product-Manager-Skills

Design quick validation experiments for product features. Use this skill when the user needs to validate a hypothesis, test a feature idea before building, has low confidence in an initiative, or asks "should I build this" or "how do I validate this". Also trigger when user mentions prototypes, MVPs, testing, validation, or wants to reduce risk before investing in development. Guide them through choosing the right experiment method and defining success criteria.

Testing & QA

Dpia Generator

9

wnallen/dpia-generator

Use whenever the user wants to run, draft, or stress-test a Data Protection Impact Assessment or any jurisdiction's equivalent for a new or modified processing. Triggers: "run a DPIA on", "assess privacy risk for", "is this Article 35 / high risk?", "need a Colorado data protection assessment / LGPD RIPD / PIPL PIPIA / Law 25 PIA?", any new-processing description (tool, vendor, AI feature, monitoring) with a privacy-risk question, or a pasted vendor page with a GDPR/ICO/CNIL/EDPB/CPPA/ANPD question. Also "index our privacy notice" — a portable notice profile later runs check for policy drift.

Testing & QA

Onboard Workshop

9

canonical/use-workshop-skill

Analyze an arbitrary repository and bootstrap a tailored Workshop definition from its existing build, test, and debug toolchain — feasibility verdict first, then propose, generate, launch, and verify. Use when a repo has no workshop definition yet and the user wants one derived from how the repo already builds and tests — "set up a workshop for this repo", "workshop-ify this project", "can this repo run in Workshop?".

Testing & QA

Eng Testing

23

jpoehnelt/skills

Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.

Testing & QA

Self Test Skill Invocation

9

konflux-ci/agent-plugins

Use when user asks to "test skill invocation framework" or mentions "canary skill test". This is a self-test skill to verify the test framework correctly loads and invokes skills.

Testing & QA18

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.