菜单
Create distinctive, production-grade frontend interfaces with high design quality. Use this when building web components, pages, artifacts, posters, or applications (websites, landing pages, react components). Generates creative, polished code that avoids generic aesthetics.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Comprehensive code review covering Functionality, Security (OWASP), Performance, and Maintainability. Includes good/bad examples.
Generates robust, cross-platform launcher scripts (Windows .bat, Unix .sh, Mac .sh) with dependency checking, .env handling, and graceful shutdown logic.
Automates the creation of professional-grade Antigravity skills. Incorporates best practices for progressive disclosure, resource organization, and automatic agent registration.
Scans the current conversation thread and updates a project work log. Useful for tracking progress and generating release notes.
A strict, scientific debugging protocol (The "Iron Law"). No fixes allowed without root cause investigation.
Generates standardized API documentation (OpenAPI/Markdown) for backend endpoints.
| name | frontend_design |
| description | Create distinctive, production-grade frontend interfaces with high design quality. Use this when building web components, pages, artifacts, posters, or applications (websites, landing pages, react components). Generates creative, polished code that avoids generic aesthetics. |
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
NEVER use generic AI-generated aesthetics (cliched colors, predictable layouts).
If the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout.
For calibration: AI-generated design right now clusters around three looks: (1) warm cream background with a high-contrast serif display and terracotta accent; (2) near-black background with a single bright acid-green or vermilion accent; (3) broadsheet-style layout. These are defaults rather than choices. Don't spend freedom on these defaults. Work in two passes:
Spend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected.
Words are design material, not decoration. Write from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Use active voice as default ("Save changes," not "Submit."). Treat failure and emptiness as moments for direction, not mood. Keep the register conversational and tuned: plain verbs, sentence case, no filler.
