Guide code placement for cross-cutting features across Juliaz Agents components.
npx skills add https://github.com/abzhaw/juliaz_agents --skill juliaz-feature
Please help me install this Agent Skill. Skill: juliaz-feature Source: https://github.com/abzhaw/juliaz_agents/tree/main/.claude/skills/juliaz-feature Command: npx skills add https://github.com/abzhaw/juliaz_agents --skill juliaz-feature
This guide helps teams and AI agents decide where to implement a new feature across the juliaz_agents architecture, ensuring consistent patterns and integration points.
Follow the patterns to implement a new feature: select the target component (orchestrator, bridge, backend, frontend, cowork-mcp, or OpenClaw), implement the corresponding tool or API, and verify end-to-end integration.
High-intent search queries and answers about installing and using this skill.
To add a new feature across orchestrator, backend, and frontend, you identify the correct target component, implement the corresponding tool or API using established patterns, and verify end-to-end integration to maintain system coherence.
The correct pattern for adding MCP tools involves implementing specific MCP tool patterns in the bridge and cowork-mcp components, ensuring proper integration points and updating related prompts and tests for system coherence.
To create a new REST endpoint and Prisma model for the backend, you follow the provided backend implementation patterns which include defining the Prisma model structure and adding the corresponding REST API endpoints.
Yes, you can build a new OpenClaw skill and UI page simultaneously by following the specific patterns for OpenClaw skill structure and frontend UI pages, ensuring proper updates to prompts and tests for full integration.
You should add a tool to the orchestrator for core orchestration capabilities, while adding an MCP tool to the bridge is necessary when integrating external tool patterns and cowork-mcp functionalities for multi-agent stack coherence.
Yes, adding cross-cutting features requires proper updates to prompts and tests to maintain system coherence across the multi-agent stack and verify end-to-end integration of the newly implemented tools, endpoints, or UI components.
hffmnnjAnalyze unfamiliar codebases to map directory layout, entry points, dependencies, and data flows.
jh941213Automate end-to-end UI verification in a real browser with Playwright, Cypress, or agent-browser.
4lermanTranslate requirements into database schemas and generate Drizzle, Prisma, and Alembic migrations.
Xza85hrfRoute task aspects to domain-specific AI models with orchestrator integration.
