allyouneedisgnu/allyouneedisgnu-first-assistant icon
public
Published on 3/21/2025
My First Assistant

This is an example custom assistant that will help you complete the Python onboarding in VS Code. After trying it out, feel free to experiment with other blocks or create your own custom assistant.

Rules
Prompts
Models
Context
anthropic Claude 3.7 Sonnet model icon

Claude 3.7 Sonnet

anthropic

200kinput·8.192koutput
anthropic Claude 3.5 Haiku model icon

Claude 3.5 Haiku

anthropic

200kinput·8.192koutput
mistral Codestral model icon

Codestral

mistral

voyage Voyage AI rerank-2 model icon

Voyage AI rerank-2

voyage

voyage voyage-code-3 model icon

voyage-code-3

voyage

- You are an Angular developer
- Use Angular CLI for project scaffolding
- Use TypeScript with strict mode enabled
- Use RxJS for state management and async operations
- Use the typical naming conventions:
  - Components: .component.ts
  - Services: .service.ts
  - Pipes: .pipe.ts
  - Module: .module.ts
  - Test: .spec.ts
  - Directives: .directive.ts
- Always write valid TypeScript code
NgRx Signalshttps://ngrx.io/guide/signals/signal-store
RxJS Docshttps://rxjs.dev/guide/overview
Angular Docshttps://angular.io/docs

Prompts

Learn more
New NgRx SignalStore
Create a new NgRx SignalStore
Please create a new NgRx SignalStore following these guidelines:
- Define a clear state interface first
- Use signalStore() with feature composition functions
- Choose appropriate injection scope (providedIn)
- Use withState() to create the initial state
- Use JSDoc comments for public properties and methods
- Implement selectors with withComputed() for derived state
- Add methods with withMethods() for state updates
- Consider using patchState() for partial updates and update() for computed updates
- Implement side effects with withHooks()
- Separate store logic into different features for better maintainability
- Implement error handling in state updates
- Export the store type for dependency injection
- Include unit tests with Jest in a separate test file

New Component
Create a new Angular component
Please create a new Angular component following these guidelines:
- Include JSDoc comments for component and inputs/outputs
- Implement proper lifecycle hooks
- Include TypeScript interfaces for models
- Follow container/presentational component pattern where appropriate
- Include unit tests with Jasmine/Karma in a separate test file
- Make sure to create separate files for any services, pipes, modules, and directives
Review
Review changes
Please review the current code changes looking for:

- Memory leaks (unsubscribed observables)
- Proper change detection strategy
- Proper use of async pipe
- Proper error handling

Format the review as:
```
## <FILENAME>
- <ISSUE>
...
- <ISSUE>
```

Context

Learn more
@code
Reference specific functions or classes from throughout your project
@docs
Reference the contents from any documentation site
@diff
Reference all of the changes you've made to your current branch
@terminal
Reference the last command you ran in your IDE's terminal and its output
@problems
Get Problems from the current file
@folder
Uses the same retrieval mechanism as @Codebase, but only on a single folder
@codebase
Reference the most relevant snippets from your codebase

No Data configured

MCP Servers

Learn more

No MCP Servers configured