Skip to content
Prompt

nanvix — Copilot Instructions

by nanvix

AI Summary

This file contains only cross-cutting instructions that apply to most tasks. Task-specific and procedural details must live in . Use the corresponding skill when the user request matches the topic:

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "nanvix — Copilot Instructions" prompt rules to my project.
Repository: https://github.com/nanvix/nanvix

Please read the repo to find the rules/prompt file, then:
1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type)
2. If there's an existing rules file, merge the new rules in rather than overwriting
3. Confirm what was added

Description

Lightweight Sandbox Powered by a Purpose-Built VM and OS

Copilot Instructions for Nanvix

This file contains only cross-cutting instructions that apply to most tasks. Task-specific and procedural details must live in .github/skills/*/SKILL.md.

Scope and Priority

• Follow this file for global behavior. • For task-specific work, load and follow the matching skill document. • If there is overlap, keep this file generic and keep procedures in skills.

Skill Routing

Use the corresponding skill when the user request matches the topic: • benchmarking → benchmark setup, execution, and result interpretation. • build → build, format, lint, and spell-check commands. • test → running unit tests, integration tests, and the full test suite. • ci-cd-pipeline → CI workflow behavior, failures, and release flow. • coding-standards → detailed style, documentation, and review conventions. • daemon-development → daemon architecture, implementation, and debugging. • gdb-debugging → GDB remote debugging of Nanvix guests via the microvm GDB server. • kernel-development → kernel internals and kernel-call paths. • library-development → crates under src/libs and related architecture. • test-development → writing and debugging tests. • troubleshooting → diagnosis of build/runtime/test failures (includes Windows-specific issues). • user-app-development → user-space app implementation and execution (includes Windows standalone mode).

Platform Support

Nanvix supports two host platforms: • Linux — Full development workflow: build, run, test, benchmark, and debug. Uses KVM for the microvm backend. • Windows 11 — Host-side development with the Windows Hypervisor Platform (WHP) backend. Guest components (kernel, user binaries) are cross-compiled using a local toolchain; the UserVM is built natively. Only standalone interactive mode is available (no HTTP mode or L2 deployments). Use z.ps1 instead of ./z. When modifying or generating code, keep platform differences in mind: • Use z.ps1 for Windows commands and ./z for Linux commands. • Linux-only features: HTTP mode, L2 deployments, GDB debugging, network namespaces. • Windows-supported features: standalone interactive mode, benchmarking (boot-time, cold-start, warm-start-vmm). • Windows-only concerns: WHP enablement, Developer Mode for symlinks, GNU Make on PATH.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted Today
Active
Adoption100+ stars on GitHub
253 ★ · Growing
DocsMissing or thin
Undocumented

GitHub Signals

Stars253
Forks109
Issues279
UpdatedToday
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more