Skip to content
Prompt

microcks-testcontainers-dotnet-demo — Copilot Instructions

by microcks

AI Summary

Copilot instructions for developers integrating Microcks Testcontainers into .NET applications, providing guidance on C# code generation and development workflows with OpenAPI and Kafka testing.

Install

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

I want to add the "microcks-testcontainers-dotnet-demo — Copilot Instructions" prompt rules to my project.
Repository: https://github.com/microcks/microcks-testcontainers-dotnet-demo

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

.NET demonstration app on how to use Microcks Testcontainers in your dev/test workflow

Language Policy

All instructions and prompts in this repository must be written in English. This applies to: • All rule and instruction files in .github/instructions/ • All prompt files in .github/prompts/ • All documentation and code comments intended for contributors

Development code generation

When working with C# code, follow these instructions very carefully. It is EXTREMELY important that you follow the instructions in the rule files very carefully.

Workflow implementation

IMPORTANT: Always follow these steps when implementing new features: • Consult any relevant instructions files listed below and start by listing which rule files have been used to guide the implementation (e.g. Instructions used: [minimal-api.instructions.md, domain-driven-design.instructions.md]). • Follow TDD when it is possible. Always start new changes by writing new test cases (or changing existing tests). Remember to consult Unit and Integration Tests for details on how to write tests. • Always run dotnet test or dotnet build to verify that all tests pass before committing your changes. Don't ask to run the tests, just do it. If you are not sure how to run the tests, ask for help. You can also use dotnet watch test to run the tests automatically when you change the code. • Fix any compiler warnings and errors before going to the next step. When you see paths like /[project]/features/[feature]/ in rules, replace [project] with the name of the project you are working on (e.g. Ordering), and [feature] with the name of the feature you are working on (e.g. VerifyOrAddPayment).

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 1mo ago
Active
AdoptionUnder 100 stars
4 ★ · Niche
DocsREADME + description
Well-documented

GitHub Signals

Stars4
Forks2
Issues1
Updated1mo ago
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