Add rebuild guidance to Aspire skill for per-resource code changes

src/Aspire.Cli/Agents/CommonAgentApplicators.cs

@@ -165,6 +165,7 @@ This repository uses Aspire to orchestrate its distributed application. Resource
         | List resources | `aspire describe` or `aspire resources` |
         | Run resource command | `aspire resource <resource> <command>` |
         | Start/stop/restart resource | `aspire resource <resource> start|stop|restart` |
+        | Rebuild a .NET project resource | `aspire resource <resource> rebuild` |
         | View console logs | `aspire logs [resource]` |
         | View structured logs | `aspire otel logs [resource]` |
         | View traces | `aspire otel traces [resource]` |
@@ -198,7 +199,17 @@ aspire start --isolated
         aspire wait myapi
         ```
 
-        Relaunching is safe — `aspire start` automatically stops any previous instance. Re-run `aspire start` whenever changes are made to the AppHost project.
+        ### Applying code changes
+
+        Choose the right action based on what changed:
+
+        | What changed | Action | Why |
+        |---|---|---|
+        | AppHost project (`apphost.cs`/`apphost.ts`) | `aspire start` | Resource graph changed; full restart required |
+        | Compiled .NET project resource | `aspire resource <name> rebuild` | Rebuilds and restarts only that resource |
+        | Interpreted resource (JavaScript, Python) | Typically nothing — most run with file watchers | Restart the resource if no watch mode is configured |
+
+        **Never restart the entire AppHost just because a single resource changed.** Use `aspire resource <name> rebuild` for .NET project resources — it coordinates stop, build, and restart for just that resource. Use `aspire describe --format Json` to check which commands a resource supports.
 
         ### Debugging issues
 
@@ -229,9 +240,11 @@ aspire mcp tools --format Json                                # includes input s
 
         - **Always start the app first** (`aspire start`) before making changes to verify the starting state.
         - **To restart, just run `aspire start` again** — it automatically stops the previous instance. NEVER use `aspire stop` then `aspire run`. NEVER use `aspire run` at all.
+        - **Only restart the AppHost when AppHost code changes.** For .NET project resources, use `aspire resource <name> rebuild` instead.
         - Use `--isolated` when working in a worktree.
         - **Avoid persistent containers** early in development to prevent state management issues.
         - **Never install the Aspire workload** — it is obsolete.
+        - **For Aspire API reference and documentation, prefer `aspire docs search <query>` and `aspire docs get <slug>`** over searching NuGet package caches or XML doc files. The CLI provides up-to-date content from aspire.dev.
         - Prefer `aspire.dev` and `learn.microsoft.com/microsoft/aspire` for official documentation.
 
         ## Playwright CLI