deflock
Copilot instructions1k starsChanged 2 months agoMITView on GitHub
This monorepo contains multiple subprojects. Below are the specific instructions for each. This is a TypeScript + Vue 3 + Vuetify application. This is being deprecated. No new features should be added. Backend functionality should be migrated to serverless functions where possible. This contains Terraform code for infrastructure management. This contains serverless functions to support the web application.
We split this copilot-instructions.md into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- Distinctive: line 19
Prefer helper classes (provided by Vuetify) for styling over CSS rules
- Distinctive: line 21
Use the Hero component for prominent page headings
- Distinctive: line 28
Do not introduce tracking, analytics, or telemetry
- Distinctive: line 31
Do not generate placeholder logic
- Distinctive: line 32
If something is unknown, leave a TODO comment
- Distinctive: line 33
Prefer simple, readable solutions over clever ones
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 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 Instructions
This monorepo contains multiple subprojects. Below are the specific instructions for each.
Web Application
/webapp
This is a TypeScript + Vue 3 + Vuetify application.
Architecture
- Vue 3 (Composition API)
- State management is local-first; avoid global stores unless required
- Vuetify for UI components and styling
Page Structure
- Each page resides in
src/views - Shared components go in
src/components - Styles are scoped to components; avoid global styles unless necessary
- Prefer helper classes (provided by Vuetify) for styling over CSS rules
- Wrap most pages in DefaultLayout.vue for consistent headers/footers
- Use the Hero component for prominent page headings
Coding Style
- Prefer functional patterns
Security & Privacy
- Never log PII
- Do not introduce tracking, analytics, or telemetry
General Rules
- Do not generate placeholder logic
- If something is unknown, leave a TODO comment
- Prefer simple, readable solutions over clever ones
Backend Service
/shotgun
This is being deprecated. No new features should be added. Backend functionality should be migrated to serverless functions where possible.
Terraform
/terraform
This contains Terraform code for infrastructure management.
Serverless Functions
/serverless
This contains serverless functions to support the web application.
Trending
Quiet since July.thin dataabout the whole repository
Who's talking about FoggedLens/deflock
- perfectly-preserved-pie/larentals“Add Flock camera layer”GitHub · Jul 10, 2026 · 1 reactions
- @tom-doerr.bsky.social“https://github.com/FoggedLens/deflock”Bluesky · Feb 11, 2026 · 1 likes
- FoggedLens/identification-catalog“Cross check this list of vendors”GitHub · Jun 13, 2026
The biggest 3 of 3 mentions linking to the repository that our crawl found. Each line is their own headline.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

