NV Elements Catalog Starters Repo System Themes About Getting Started Changelog Metrics Support Accessibility Contributions Requests Migration Integrations Installation MCP CLI Lint Angular Bundles Extensions Golang Hugo Import Maps Lit NextJS Nuxt Preact React SolidJS Svelte TypeScript Vue Foundations Typography Iconography Themes Design Tokens Size & Space Objects Interactions Support Status Color Animation Fonts Layers Custom Layout Horizontal Vertical Grid Popovers i18n Visualization View Transitions Elements Accordion Alert Avatar Badge Breadcrumb Button Button Group Card Chat Message Checkbox Color Combobox Copy Button Datagrid Integrations Column Action Column Alignment Column Fixed Column width Container Card Display Settings Footer Heatmap Keynav Multi Select Pagination Panel Detail Panel Grid Performance Placeholder Row Action Row Groups Row Sort Scroll Height Single Select Stripe Date Datetime Dialog Divider Dot Drawer Dropdown Dropdown Group Dropzone File Format Datetime Format Number Format Relative Time Forms Validation Actions Control Icon Icon Button Input Input Group Logo Menu Month Notification Page Page Header Page Loader Pagination Panel Progressive Filter Chip Progress Bar Progress Ring Password Preferences Input Pulse Radio Range Resize Handle Search Select Skeleton Sort Button Sparkline Star Rating Steps Switch Tabs Tag Textarea Time Toast Toggletip Toolbar Tooltip Tree Week Patterns Authentication Browse Dashboard Editor Empty States Heatmap Keyboard Shortcut Logging Media Navigation Onboarding Panel Responsive Search Subheader Trend Code Codeblock Monaco Input Diff Input Editor Diff Editor Problems Markdown Markdown CSS Utility Labs Responsive Layout Viewport Container Patterns Forms API Design Properties & Attributes Slots Registration CustomEvents Stateless Composition Styles Packaging Glossary Logs Internal Guidelines Agent Harness Agent Tooling Agent Ownership Documentation Examples TypeScript Testing Unit Testing Accessibility Testing Lighthouse Testing SSR Testing Visual Testing Troubleshooting Component Creation Internal Examples All Examples

Agent Ownership

Agent-assisted work is still engineering work. The agent can draft code, search a repository, run tools, and expose options faster than a person can type. It cannot own the result. Ownership stays with the engineer who ships the change.

Using an agent to explore an idea, prototype UI, inspect an API, or generate boilerplate is useful. Shipping output without understanding it, testing it, and making the system reject the known failure modes is shipping unowned risk.

Levels of Accountability

The agent can help in the workflow. Accountability stays attached to the engineer from intent through review.

problem framing reviewable change Intent Engineer Framing Agent Draft Useful Assist Engineering Pass Human Judgment Harness Gates Tests, Types, Lint Review Risk Inspection engineer accountability

    Ownership Means

    Owning an agent-assisted change means you can defend the implementation from first principles.

    • Intent: You know why the change exists and which user, API, or system behavior it serves.
    • Design: You chose the public API, boundaries, state model, and failure behavior deliberately.
    • Correctness: You tested happy paths, invalid states, edge cases, and integration behavior that can regress.
    • Maintainability: You removed incidental complexity, dead code, speculative abstraction, and unexplained patterns.
    • Review: You kept the diff small enough for another engineer to reason about the risk.
    • Automation: You strengthened the harness when the same failure can recur.

    The prompt is not evidence. Passing tests are not evidence if the tests do not assert the risk. Review approval is not evidence if nobody can explain the behavior. The evidence is the code, the tests, the static gates, and the engineer's command of the system.

    Professional Use Of AI Agents

    Use agents to speed up the loop. Do not use them to outsource judgment.

    Do Don't
    • Start with the invariant. Decide what must stay true before generating code.
    • Constrain the task. Ask for the smallest useful change, then inspect the result.
    • Read the diff. Review generated code with the same care as hand-written code.
    • Delete aggressively. Keep the solution small, local, and aligned with existing patterns.
    • Test the risk. Add the test that would fail for the mistake that concerns you.
    • Strengthen the harness. Turn repeated guidance into lint, types, tests, metadata, or CLI validation.
    • Do not ship prompts. Prompts are not governance, documentation, or a validation strategy.
    • Do not accept generated architecture blindly. The agent does not know the long-term cost.
    • Do not hide behind the model. The engineer owns the change, not the tool.
    • Do not merge code nobody can explain. Plausible code is not the same as correct code.
    • Do not rely on style review. Review the behavioral and architectural risk first.
    • Do not normalize flakes. A flaky gate is a missing gate.

    Do not make review discover basic ownership. Professional software engineering means taking responsibility for consequences, not producing code-shaped output.

    Agents are most useful when the repository has a strong harness: strict types, lint rules, deterministic tests, clear package boundaries, generated metadata, reviewable diffs, and engineers who understand the systems they change. Without that harness, agents only increase the rate at which weak process reaches production.