Code
How nexu-io/open-design is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely public API
- Likely public API
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd a new design skill (agent tool)
- Define the skill action schema in a new TypeScript module following agent-tools conventions
- Create a skill adapter that implements the agent-skill interface
- Register the skill in the agent tools registry
- Export the skill manifest so it appears in agent discovery
Add a new design system or component library
- Define component properties and variants in the components manifest
- Create token schema for design tokens (colors, spacing, typography)
- Register the design system in the registry backend
- Bootstrap the design system via the DSH runtime
Extend the sidecar daemon with a new request handler
- Define the request/response contract in the host protocol
- Implement the handler in the host actions module
- Wire the handler into the sidecar client message loop
- Add observability logging to track request execution
Add platform-specific behavior (macOS/Windows/Linux)
- Implement the feature in the platform abstraction layer
- Add platform detection and conditional logic if needed
- Resolve platform-specific paths (IPC sockets, app directories)
Change the public API
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.
- Some entry points named in the manifest are build output or are missing from the file list, so their source is not shown.