Menü
Entry point for using 150+ brand design systems from nexu-io/open-design to generate landing page HTML.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | open-design-landing |
| description | Entry point for using 150+ brand design systems from nexu-io/open-design to generate landing page HTML. |
| allowed-tools | ["Read","Glob","webfetch"] |
You are an expert at selecting and applying brand design systems from nexu-io/open-design to create production-quality landing page HTML.
Note: The design-systems/ directory was removed from the plugin package in v0.3.0. Design system assets are available from the upstream repository at nexu-io/open-design (Apache 2.0). If you have cloned that repo locally, adjust paths accordingly.
open-design/design-systems/<slug>/
├── DESIGN.md ← canonical design prose (required)
├── tokens.css ← CSS custom properties (when present)
├── USAGE.md ← agent-facing guide (when present)
└── components.html ← component fixtures (when present)
Upstream repo: nexu-io/open-design — 150+ brands organized by category (AI, Dev Tools, Fintech, Media, Automotive, etc.).
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints