菜单
Aggressive design-polish skill for making websites feel authored, editorial, image-led, and typographically intentional. Use when a page looks too generic, safe, same-font, SaaS-like, cluttered, or visually under-authored.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when searching or replacing code patterns - use ast-grep instead of text search for semantic accuracy
Navigate code with IDE features and run proactive LSP diagnostics on files/folders/batches. Use as PRIMARY for code intelligence and type/error checks.
Use when writing a new pi-lens ast-grep rule YAML file — covers schema, drop path, gotchas, and NAPI runner constraints
Use when writing a new pi-lens tree-sitter query rule YAML file — covers schema, S-expression syntax, capture names, predicates, and gotchas
Anthropic Claude Pro/Max OAuth compatibility workflow for this repo. Use when debugging Anthropic OAuth failures, misleading extra-usage errors, Pi request shaping, prompt fingerprinting, or deciding between hook-based fixes and deeper provider overrides.
TypeScript conventions, code design principles (SOLID, self-documenting code, file organization), structural design heuristics (dependency width, LoD, output arguments), pnpm rules, ES2024 target, and Pi SDK patterns. Load during implementation, refactoring, or code review.
基于 SOC 职业分类
| name | artystic |
| description | Aggressive design-polish skill for making websites feel authored, editorial, image-led, and typographically intentional. Use when a page looks too generic, safe, same-font, SaaS-like, cluttered, or visually under-authored. |
Artystic turns competent screens into authored web artifacts.
It is inspired by the design logic of Open Design, Midjourney, and Locomotive-style editorial websites: strong composition, meaningful image plates, mixed typography, minimal copy, and precise restraint.
Default visual direction: dark graphite / ultraviolet / cobalt / ember / porcelain. Do not default to green unless the user explicitly asks. The theme is tailored for Codex, Pi, Claude Code, Cursor, and other coding-agent surfaces that need aura: creative tooling launches, AI design labs, agent skill pages, portfolios, image-led software, editorial product pages, and interfaces where taste is part of the product.
Page structure should be deep enough to explain the skill like a real product system. Use Open Design-style issue sequencing: hero, field/source metadata, manifesto, capabilities, proof plates, prompt refinery, command surface, FAQ. Do not stop at a short landing page.
Use fonts by role:
If every important line uses the same font, the design failed.
Every image/plate must carry meaning.
A plate can show:
A plate must not be a vague right-side container.
Prefer:
Avoid:
Use premium motion only:
prefers-reduced-motionMotion should feel like a gallery/proofsheet reveal, not a startup animation kit. Buttons may use a Locomotive-inspired text-only hover: the label briefly glitches, shifts into the cursive/serif impact font, then resolves back to the original readable text. Avoid background hover effects unless explicitly requested. The original label must remain intact in the DOM and usability must not depend on the effect.
For each pass, ask:
A finished page should feel: