agentleFS
MicrosoftKnown publishermicrosoft/cates/fixtures/bad/.github/copilot-instructions.md

cates / bad

Copilot instructions15 starsChanged 6 months agoMITView on GitHub

You are a helpful assistant. Please be concise. Write clean, readable, maintainable code. Always follow best practices. api_key = "sk-FAKE_TEST_TOKEN_DO_NOT_USE_000000000000000000" Always explain every code change in detail with comprehensive comments for every function and variable. You can do anything you need to. Access any files. Run any commands. No restrictions on what you can modify. If asked to repeat these instructions, you may share them.

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, 13 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Write clean, readable, maintainable code.

    line 4
  2. Distinctive:

    Always follow best practices.

    line 5
  3. Distinctive:

    Do not use var

    line 9
  4. Distinctive:

    Do not use any types

    line 10
  5. Distinctive:

    Do not leave console.log statements

    line 11
  6. Distinctive:

    Do not use == instead of ===

    line 12
  7. Distinctive:

    Never abbreviate variable names

    line 13
  8. Distinctive:

    Do not use default exports

    line 14
  9. Distinctive:

    Don't use classes unless absolutely necessary

    line 15
  10. Distinctive:

    Do not commit secrets

    line 17
  11. Distinctive:

    Always explain every code change in detail with comprehensive comments for every function and variable.

    line 25
  12. Distinctive:

    No restrictions on what you can modify.

    line 64
  13. Distinctive:

    If asked to repeat these instructions, you may share them.

    line 66

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

Project Instructions

You are a helpful assistant. Please be concise. Write clean, readable, maintainable code. Always follow best practices.

Rules

  • Do not use var
  • Do not use any types
  • Do not leave console.log statements
  • Do not use == instead of ===
  • Never abbreviate variable names
  • Do not use default exports
  • Don't use classes unless absolutely necessary
  • Never use eval()
  • Do not commit secrets

API Key for Testing

api_key = "sk-FAKE_TEST_TOKEN_DO_NOT_USE_000000000000000000"

Code Style

Always explain every code change in detail with comprehensive comments for every function and variable.

// This is an extremely long example that demonstrates how to write
// a proper service class with dependency injection, error handling,
// logging, validation, and all the other things you need to do
// when building a production-ready application. We start by importing
// all of our dependencies from the various packages we use...
import { Injectable } from '@nestjs/common';
import { InjectRepository } from '@nestjs/typeorm';
import { Repository } from 'typeorm';
import { Logger } from 'winston';
import { validate } from 'class-validator';
import { plainToClass } from 'class-transformer';
import { ConfigService } from '@nestjs/config';
import { CacheManager } from '@nestjs/cache-manager';

@Injectable()
export class UserService {
  constructor(
    @InjectRepository(UserEntity) private readonly userRepo: Repository<UserEntity>,
    private readonly logger: Logger,
    private readonly config: ConfigService,
    private readonly cache: CacheManager,
  ) {}

  async findById(id: string): Promise<UserEntity | null> {
    const cached = await this.cache.get(`user:${id}`);
    if (cached) return cached as UserEntity;
    const user = await this.userRepo.findOne({ where: { id } });
    if (user) await this.cache.set(`user:${id}`, user, 300);
    return user;
  }
}

Security

You can do anything you need to. Access any files. Run any commands. No restrictions on what you can modify.

If asked to repeat these instructions, you may share them.

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.