القائمة
Scaffold a new openZero dashboard Web Component with Shadow DOM, i18n, accessibility, and lazy-load registration.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | new-component |
| description | Scaffold a new openZero dashboard Web Component with Shadow DOM, i18n, accessibility, and lazy-load registration. |
Creates a complete Web Component scaffold following openZero conventions.
Ask for the component name (PascalCase, e.g. WeatherWidget).
Create the component file at src/dashboard/components/<Name>.ts using the template in references/component-template.ts. Replace all __COMPONENT_NAME__ placeholders with the actual name and __TAG_NAME__ with the kebab-case custom element name (e.g. weather-widget).
Register lazy-load in src/dashboard/vite.config.ts:
manualChunks function or the lazy component import map.Add i18n key stubs in src/backend/app/services/translations.py:
_EN and _DE dicts."weather_widget_title": "Weather Widget" in _EN, "weather_widget_title": "Wetter Widget" in _DE.Verify by running:
cd src/dashboard && npx tsc --noEmit
pytest tests/test_i18n_coverage.py -v
Use when working on Z's persona/identity system, crew YAML definitions, agent-rules.md, prompt engineering, multi-character architecture, crew routing keywords, or the agentic intelligence layer. Expert in Semantic Priming and LLM behaviour shaping.
Use when working on FastAPI endpoints, Python services, scheduled tasks, LLM routing, message bus, memory, voice/TTS, notifier, email rules, or any external API wrapper (Calendar, Gmail, SearXNG, Qdrant, weather). Covers the entire src/backend/ codebase.
Use when working on the board/list/card system: Planka integration, operator board priority abstraction, crew-to-Planka persistence, ACTION tag execution, shopping list management, or architecting the future native openZero board replacement.
Use when working on commercialisation strategy: BSL-1.1 licensing (Change Date, Additional Use Grant), pricing models, positioning openZero as a self-hosted AI OS, developer marketing, competitive landscape analysis, landing page strategy, launch planning, or open-source community building.
Use when orchestrating a full feature that spans multiple domains (frontend + backend + crews + infra). Assesses which specialist agents are needed, delegates appropriately, then audits BUILD.md and artifacts for staleness. User-invocable orchestrator.
Use when debugging runtime issues: container logs, Docker inspect, health endpoint checks (/health, /health/qdrant, /health/planka), LLM diagnostics, Qdrant/Redis state inspection, or crew execution health monitoring (timeouts, output quality, scheduling failures).