菜单
The design-truth gateway — resolves which design files are authoritative right now (core law + self-learning overlays). Run at the START of any UI/design task, before reading the design law.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Atelier's native asset tools — image→webp compression, video→webp frame sequences, scrollytelling scaffolding, and AI video generation (Gemini Omni Flash / Veo 3.1) with a graceful no-credentials fallback. Load when handling images, video, storytelling sections, or media generation.
Turn any component site, asset library, or API into something agents can use — a registry entry, a skill, or a full MCP server. Load when the user says "add this site/library to Atelier" or wants to contribute a new integration.
The Atelier operating loop — understand → clarify → plan → execute → review → compare-vs-done-state. Governs when to stop, when to ask, which model tier runs each phase, and when to think deep or compact. Load for ANY nontrivial task.
The thinking protocol — load FIRST on every prompt, before any other skill. Makes any model (Opus, Sonnet, Haiku) reason like a principal engineer - decisive answers, root-cause debugging, security reflexes, outcome-first communication. This is step 0 of the loop.
The Atelier Auth Law — production-hardened session architecture (rotating refresh tokens, families, grace window, silent refresh, sliding window) plus the anti-patterns that corrupt auth. Load before designing or touching ANY authentication code.
The Atelier Clean Code Law — 250-word-per-file budget, DRY via the graph, ponytail minimalism, and the comment policy. Load before writing or refactoring any source code.
基于 SOC 职业分类
| name | gateway |
| description | The design-truth gateway — resolves which design files are authoritative right now (core law + self-learning overlays). Run at the START of any UI/design task, before reading the design law. |
The core design law is read-only; learned taste lives in overlay files pointed to by the store. This skill tells you what to read, in order.
python <plugin>/db/store.py sql "SELECT path, kind, promoted FROM design_guide_versions ORDER BY id"
(no db / no rows → core law only). Promoted rows live in the project's
docs/design/; unpromoted ones in workspace/overlays/ — read both.skills/design-law/SKILL.md first, then each overlay —
later overlays override earlier ones; every overlay overrides core except
the anti-style list and the token-centralization rule, which are inviolable.python <plugin>/db/store.py rules design (rows with source=overlay:*).workspace/overlays/ + a design_guide_versions row (the learner agent's
job, via /atelier:learn)./atelier:promote), never automatic.