agentleFS
Sign inStart free
dwsilvardwsilvar/LBaC/.github/copilot-instructions.md

LBaC

Copilot instructions0 starsChanged 4 months agoMITView on GitHub

MANDATORY: Before suggesting any code, read the full project rules in .agents/AGENTS.md and the Master Blueprint in docs/LBAC.md. This repository is a documentation-first framework. There is no application source code to generate — only structured Markdown documents. After any code change, you are responsible for: * Updating all file:/// links in docs/ if any file was renamed or deleted. * Moving resolved tech debt from Pending → Resolved in docs/technical_debt.md AND updating the Feature Map's Related Technical Debt section. *…

The file

We split this copilot-instructions.md into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Tell Me the Project (Step 0): Run docs/templates/project.prompt.md with any AI to generate Feature Maps, user stories, roadmap, and …

    line 13
  2. Very specific:

    Read before writing: Check docs/features/ for the Feature Map and docs/technical_debt.md for related debt before any suggestion.

    line 14
  3. Distinctive:

    Never duplicate: Do not create files, models, or structures that already exist.

    line 15
  4. Very specific:

    Plan first: Create an Implementation Plan in docs/implementations/.

    line 16
  5. Distinctive:

    Localized edits only: Never rewrite entire files.

    line 19
  6. Distinctive:

    After any code change, you are responsible for:

    line 23

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

GitHub Copilot — Project Instructions

MANDATORY: Before suggesting any code, read the full project rules in .agents/AGENTS.md and the Master Blueprint in docs/LBAC.md.

Project: Living Blueprint-as-Code (LBaC) — Template Repository

This repository is a documentation-first framework. There is no application source code to generate — only structured Markdown documents.

Core Rules (Summary)

  1. Tell Me the Project (Step 0): Run docs/templates/project.prompt.md with any AI to generate Feature Maps, user stories, roadmap, and business rules. Tracks progress in docs/planning/tmtp_session.md. Skip if Feature Maps already exist.
  2. Read before writing: Check docs/features/ for the Feature Map and docs/technical_debt.md for related debt before any suggestion.
  3. Never duplicate: Do not create files, models, or structures that already exist.
  4. Plan first: Create an Implementation Plan in docs/implementations/. Wait for explicit approval before writing code.
  5. Verify after coding: Complete the Verification Report in docs/implementations/ with all BDD scenario results.
  6. Language policy: English for AI files (docs/features/, docs/LBAC.md, docs/technical_debt.md, .agents/AGENTS.md). Local language for stakeholder files (docs/business/, docs/adr/).
  7. Localized edits only: Never rewrite entire files. Provide minimal diff-style edits.

Auto-Sync Rules (Summary)

After any code change, you are responsible for:

  • Updating all file:/// links in docs/ if any file was renamed or deleted.
  • Moving resolved tech debt from Pending → Resolved in docs/technical_debt.md AND updating the Feature Map's Related Technical Debt section.
  • Marking completed stories as [x] in docs/planning/sprint_history.md and updating docs/planning/proposal_planning_qa.md when a sprint closes.
  • Adding new entries to docs/LBAC.md index when a new Feature Map, ADR, or Business Rule is created.
  • Updating a superseded ADR's Status field and its row in docs/LBAC.md.
  • Adding ⚠️ Requires Re-verification to an existing Verification Report if its Feature Map's To-Be section changes.

Full Rules Reference

→ .agents/AGENTS.md
→ docs/LBAC.md

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.

Check your setup, free