Menu
Scaffold a complete full-stack feature: FastAPI endpoint, dashboard Web Component, i18n keys, test stubs, and documentation checks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | scaffold-feature |
| description | Scaffold a complete full-stack feature: FastAPI endpoint, dashboard Web Component, i18n keys, test stubs, and documentation checks. |
Creates the skeleton for a complete full-stack openZero feature.
Ask for:
Backend endpoint (if needed):
Use the new-endpoint skill template at .github/skills/new-endpoint/references/endpoint-template.py.
src/backend/app/api/dashboard.py.src/backend/app/services/.Dashboard component (if needed):
Use the new-component skill template at .github/skills/new-component/references/component-template.ts.
src/dashboard/components/.vite.config.ts.fetchData() to the new API endpoint.i18n keys:
_EN and _DE in src/backend/app/services/translations.py.Test stubs:
Documentation check:
BUILD.md.docs/artifacts/ file.Verify:
cd src/dashboard && npx tsc --noEmit
ruff check src/backend/
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).