agentleFS
lucasaguilarlucasaguilar/rei/.github/copilot-instructions.md

rei

Copilot instructions8 starsChanged 5 months agoMITView on GitHub

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
  1. Distinctive:

    Always use English for comments.

    line 5
  2. Very specific:

    Use inject() for Dependency Injection (Never constructor).

    line 6
  3. Very specific:

    Always readonly for injections.

    line 11
  4. Very specific:

    Use signal(), computed(), and selectSignal().

    line 17
  5. Very specific:

    Use @if, @for (with track), and @switch.

    line 28
  6. Very specific:

    Use async/await for one-off HTTP calls.

    line 33
  7. Distinctive:

    Use Observables ONLY for streams.

    line 34
  8. Very specific:

    Always use takeUntilDestroyed(this.destroyRef) for cleanup.

    line 35
  9. Very specific:

    Prefer delay() and interval() over setTimeout/setInterval.

    line 36
  10. Very specific:

    Use SdAccessibilityTags enum for all HTML roles.

    line 41
  11. Very specific:

    Use ClientNames for environment detection.

    line 42
  12. Very specific:

    Only // TODO: or // NOTE:.

    line 47
  13. Very specific:

    Do not create .md files unless explicitly asked.

    line 48

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

Copilot Custom Development Rules - Angular/Ionic

Core Principles

  • Always use English for comments.
  • Use inject() for Dependency Injection (Never constructor).
  • Mandatory standalone: true and ChangeDetectionStrategy.OnPush.

1. Dependency Injection & Access Modifiers

  • Always readonly for injections.
  • Order: private → protected → public.
  • Format: private readonly service = inject(Service);

2. Signals & Modern Reactivity

  • Use signal(), computed(), and selectSignal().
  • Inputs: Use input() or input.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 (with track), and @switch.
  • **Never use ngIf, ngFor or *ngSwitch.

5. Async & RxJS

  • Use async/await for one-off HTTP calls.
  • Use Observables ONLY for streams.
  • Always use takeUntilDestroyed(this.destroyRef) for cleanup.
  • Prefer delay() and interval() over setTimeout/setInterval.

6. Type Safety

  • Strictly NO any.
  • Use SdAccessibilityTags enum for all HTML roles.
  • Use ClientNames for environment detection.

7. Logging & Documentation

  • No excessive console.log.
  • Only // TODO: or // NOTE:.
  • Do not create .md files 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.
  • Async: Preferir async/await sobre 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.