Every studio has rules that live in someone's head or a document nobody opens mid-brief: the art bible, the palette, the hero's proportions, the icon style, the colour rules for VFX, the names that are canon. When those rules have to be retyped into every prompt, they get retyped differently by every person, and the output drifts from the game it is meant to belong to.
Workspace Skills write those rules down once, where Layer's agent reads them. A skill is a named set of plain-language instructions, with the references and assets that back it up. Choose when it loads, which specialist agents follow it, and whether it covers the whole workspace or one project. Every teammate's chats then follow it, across image, video, audio and 3D.
Key Capabilities
Instructions in plain language A skill is written the way you would brief a new artist: what to do, what to avoid, what good looks like. Give it a name and a description, and the agent follows it without anyone re-explaining.
References and assets travel with the rules Each skill has room for reference files and assets alongside its instructions. The palette swatches, the proportion sheet, and the approved icon set sit with the rule they illustrate.
Three ways to load Set a skill to Always and it applies in full to every chat it covers, the right choice for an art bible or a style guide. Set it to When relevant and the agent reads the description and loads it when the task matches. Set it to Manual and it waits until someone invokes it as /name.
Aimed at the right specialist Choose which of Layer's specialist agents a skill applies to: asset generation, the game art director, playable generation, the UA expert, the workflow architect, LoRA training, the planner, documentation, or onboarding. Each rule reaches the work it is about.
Workspace-wide or per project Enable a skill for the whole workspace, or add it to specific Projects so everyone working on that title gets it. A studio-wide brand rule and one game's lore can each live at the level they belong to.
Create or import Write a skill in the app, or import one your team already keeps, and re-import it when the source changes.
How It Works
Write the rule Create a skill, name it, and describe what it is for. Write the instructions in plain language and add the references and assets that show what you mean.
Choose where it applies Pick the loading mode, the specialist agents it applies to, and its scope: the whole workspace or the Projects that need it.
Generate as usual Ask for the asset you want. The agent brings in the skills that fit the task, so characters, ads, icons and video come back following your rules without anyone restating them.
Built for Game Production
An art bible the agent actually reads Palette, proportions, line weight, lighting: set the art bible to Always and every generation starts from it. Art directors stop giving the same note twice.
UI and VFX that match the game Icon style and VFX colour rules are where generated assets most often give themselves away. A skill per rule keeps them consistent with what already shipped.
Lore and naming that stay canon Character names, faction terms, and tone of voice belong in a skill. Store copy, event text, and ad hooks all draw on the same source.
Store and UA specs, on call Keep the store screenshot specs or an ad format as a Manual skill, and run it with /name whenever a launch or a test cycle needs it.
A higher bar for the whole team Skills put your best artist's standards into every teammate's chat. New joiners and external partners produce on-brand work from their first session, because the rules are in the workspace, not in a handover document.
Combined with Projects and Memory, skills are how Layer's agent works to your studio's standard rather than a generic one. Write the rules once, and quality stops depending on who wrote the prompt.