Docs

How to work with CopyLayers

How the library works, what you get in each category, and how to take a layer into whatever you're building.

FAQ & troubleshooting

Common questions about prompts, stacks, models, and licensing — and what to check first when a prompt doesn't produce what the preview showed.

If something isn't working, check the model first — a wrong or outdated model accounts for most reported mismatches.

What AI models work with these prompts?

The prompts are model-agnostic — plain structured language that runs on any current coding model, including Claude Fable 5, Claude Sonnet 5, Claude Opus 4.8, GPT-5.5, GPT-5.6 Sol, Gemini 3.1 Pro, Grok 4.5, GLM-5.2, DeepSeek V4-Pro, MiniMax M3, and Kimi K3.

The prompt isn't producing what I expected. What do I check?

Check the model first — every prompt is tested against Claude Opus 4.8, and weaker or older models tend to lose the motion and depth while keeping the structure. After that, confirm the prompt was pasted whole and unedited. Full Stack subscribers can raise it in the private Discord and we'll work through it.

Can I use these with WordPress, Astro, Vue, or another framework?

Yes. Prompts generate a single self-contained HTML file, which you can then hand to an AI along with your project and ask it to rebuild following your structure. Alternatively, state your target stack in the prompt up front and it will build there directly. Anything the AI can reach works.

Do you ship the source code, or only the prompt?

Both, depending on your plan. Every plan gives you prompts. Full Stack adds the downloadable source: Next.js for templates and sections, a self-contained HTML file for 3D scenes, and the raw file for video backgrounds.

Can I use layers in client or commercial projects?

Yes, with a Premium plan — Unlimited and Full Stack include a commercial-use licence, so you can ship the output as-is in any product with no attribution required. Free prompts are for browsing and experimenting. In every case, extend the layer rather than shipping it untouched.

Why is the source for templates Next.js and not my framework?

Because templates are heavily animated, and Next.js gives them server-side rendering and bundle separation — the two things that keep an immersive page crawlable and fast. If you ship something else, use the prompt path: the single-file HTML output is stack-agnostic by design.

How often do you add new layers?

Weekly. New prompts and source files ship every week, and they're included in Unlimited and Full Stack at no extra cost.