rei
Copilot instructions8 starsChanged 5 months agoMITView on GitHub
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- grill-with-docsSkill
- change-walkthroughSkill
The file
Show its rules and text
We split this copilot-instructions.md into the rules it gives an agent
13 rules. About 0 are common, 2 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Always use English for comments.
- Very specific: line 6
Use inject() for Dependency Injection (Never constructor).
- Very specific: line 11
Always readonly for injections.
- Very specific: line 17
Use signal(), computed(), and selectSignal().
- Very specific: line 28
Use @if, @for (with track), and @switch.
- Very specific: line 33
Use async/await for one-off HTTP calls.
- Distinctive: line 34
Use Observables ONLY for streams.
- Very specific: line 35
Always use takeUntilDestroyed(this.destroyRef) for cleanup.
- Very specific: line 36
Prefer delay() and interval() over setTimeout/setInterval.
- Very specific: line 41
Use SdAccessibilityTags enum for all HTML roles.
- Very specific: line 42
Use ClientNames for environment detection.
- Very specific: line 47
Only // TODO: or // NOTE:.
- Very specific: line 48
Do not create .md files unless explicitly asked.
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Copilot Custom Development Rules - Angular/Ionic
Core Principles
- Always use English for comments.
- Use
inject()for Dependency Injection (Never constructor). - Mandatory
standalone: trueandChangeDetectionStrategy.OnPush.
1. Dependency Injection & Access Modifiers
- Always
readonlyfor injections. - Order: private → protected → public.
- Format:
private readonly service = inject(Service);
2. Signals & Modern Reactivity
- Use
signal(),computed(), andselectSignal(). - Inputs: Use
input()orinput.required<T>(). Never @Input(). - Outputs: Use
output<T>(). Never @Output() or EventEmitter.
3. SignalStore Pattern (NgRx)
- Order:
withDevtools→withState→withEntities→withComputed→withMethods. - Business logic MUST live in
withMethods.
4. Modern Template Syntax
- Use
@if,@for(withtrack), and@switch. - **Never use ngIf, ngFor or *ngSwitch.
5. Async & RxJS
- Use
async/awaitfor one-off HTTP calls. - Use Observables ONLY for streams.
- Always use
takeUntilDestroyed(this.destroyRef)for cleanup. - Prefer
delay()andinterval()oversetTimeout/setInterval.
6. Type Safety
- Strictly NO
any. - Use
SdAccessibilityTagsenum for all HTML roles. - Use
ClientNamesfor environment detection.
7. Logging & Documentation
- No excessive
console.log. - Only
// TODO:or// NOTE:. - Do not create
.mdfiles unless explicitly asked.
Copilot Custom Development Rules - TypeScript
Tech Stack Preferences
- Language: TypeScript estricto. Evitar el uso de
any. - Patterns: Programación funcional, Inyección de Dependencias
- Style: Clean Code y principios SOLID.
Coding Rules
- Naming:
- Interfaces con PascalCase (ej:
UserEntry). - Métodos y variables en camelCase.
- Componentes con el sufijo
.component.ts.
- Interfaces con PascalCase (ej:
- Async: Preferir
async/awaitsobre Promises crudas. - Functions: Métodos pequeños (menos de 20 líneas). Una sola responsabilidad por función.
- Refactoring: Al renombrar métodos, buscar siempre las referencias en el "Repo Map" para asegurar cambios atómicos.
- Comentarios: Solo cuando el código no es autoexplicativo. Evitar comentarios redundantes.
- **Imports: **Usar rutas relativas claras. Evitar imports profundos (ej:
import { X } from '../../../../../'). Solo usar imports al principio del archivo.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

