dajuice/test icon
public
Published on 8/13/2025
TEST

Rules
Prompts
Models
Context
lmstudio Qwen3 Coder model icon

Qwen3 Coder

lmstudio

lmstudio Qwen3 Coder REMOTE model icon

Qwen3 Coder REMOTE

lmstudio

openai OpenAI GPT-4.1 model icon

OpenAI GPT-4.1

OpenAI

1047kinput·32.768koutput
anthropic Claude 4 Sonnet model icon

Claude 4 Sonnet

anthropic

200kinput·64koutput
openai GPT-5 model icon

GPT-5

OpenAI

400kinput·128koutput
- 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
Continuehttps://docs.continue.dev
Angular Docshttps://angular.dev/overview
RxJS Docshttps://rxjs.dev/guide/overview
Angular CLIhttps://angular.io/cli
Angular Materialhttps://material.angular.io/
Angular Docshttps://angular.io/docs

Prompts

Learn more
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>
```
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

Context

Learn more
@diff
Reference all of the changes you've made to your current branch
@codebase
Reference the most relevant snippets from your codebase
@url
Reference the markdown converted contents of a given URL
@folder
Uses the same retrieval mechanism as @Codebase, but only on a single folder
@terminal
Reference the last command you ran in your IDE's terminal and its output
@code
Reference specific functions or classes from throughout your project
@file
Reference any file in your current workspace
@repo-map
Reference the outline of your codebase
@docs
Reference the contents from any documentation site
@open
Reference the contents of all of your open files
@jira
Reference the conversation in a Jira issue

No Data configured

MCP Servers

Learn more

Playwright

npx -y @executeautomation/playwright-mcp-server