codenomad-architecture-guide

Trace CodeNomad monorepo feature flows and OpenCode SDK V2 integration patterns.

2.5k|168|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/NeuralNomadsAI/CodeNomad --skill codenomad-architecture-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codenomad-architecture-guide
Source: https://github.com/NeuralNomadsAI/CodeNomad/tree/main/.opencode/skills/codenomad-architecture-guide
Command: npx skills add https://github.com/NeuralNomadsAI/CodeNomad --skill codenomad-architecture-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It reduces time wasted searching through the CodeNomad monorepo by showing exactly where cross-area logic lives and how OpenCode SDK V2 is integrated.

Core Features & Use Cases

  • Architecture & package navigation: Maps the monorepo into the six functional areas (UserInterface, ServerBackend, DesktopClient, SpeechAndAudio, BuildAndPackaging, CloudflareDeployment) and links them to key entry points for quick orientation.
  • Cross-package dependency tracing: Guides debugging across UI ↔ server boundaries by pointing to conventions, mirrored types, and end-to-end feature traces.
  • OpenCode SDK V2 integration patterns: Helps you follow the required SDK usage approach (client lifecycle, worktree-based routing, requestData error handling) and avoid common schema pitfalls.
  • Implementation guardrails: Highlights anti-patterns (i18n misuse, SSE handling issues, metadata schema violations for assistant parts) and provides checklist-driven impact validation.

Quick Start

Use the codenomad-architecture-guide skill when you are about to implement a new UI feature that requires server changes, so you can trace the full end-to-end flow, then locate the exact route/store/client integration points before writing code.

Frequently Asked Questions about codenomad-architecture-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I navigate a Fastify and SolidJS monorepo to trace cross-package feature flows?

To navigate a Fastify and SolidJS monorepo, map functional areas like UserInterface and ServerBackend to trace end-to-end feature flows across UI and server boundaries. This approach links key entry points and mirrored types for quick orientation during feature work.

How do I integrate OpenCode SDK V2 for schema-safe file operations and session management?

Integrate OpenCode SDK V2 by following required patterns for client lifecycle, worktree-based routing, and requestData-wrapped calls for schema-safe file operations. This ensures correct session management and prevents common schema pitfalls like assistant-part metadata violations.

What is the best way to debug cross-boundary issues between a SolidJS UI and a Fastify server backend?

The best way to debug SolidJS UI and Fastify server boundaries is to use cross-package dependency tracing. This points to shared conventions and mirrored types, allowing you to follow end-to-end feature traces to locate the exact integration points causing issues.

Why does my OpenCode SDK V2 implementation fail with assistant-part metadata schema violations?

OpenCode SDK V2 fails with assistant-part metadata schema violations when implementation guardrails are ignored. Avoid this by applying checklist-driven impact validation and adhering to required SDK behaviors like requestData error handling and worktree-based client routing.

Does the CodeNomad monorepo include specific anti-patterns to avoid during feature implementation?

Yes, the CodeNomad monorepo highlights specific anti-patterns to avoid during feature implementation, including i18n misuse, SSE handling issues, and metadata schema violations. Implementation guardrails provide checklist-driven validation to ensure compliance.

Can I use this architecture guide to locate Cloudflare deployment and desktop client entry points?

Yes, you can use this architecture guide to locate Cloudflare deployment and desktop client entry points. It organizes the monorepo into six functional areas, linking CloudflareDeployment and DesktopClient to key entry points for quick orientation and debugging.