torsti-tapiola-website
Copilot instructions0 starsChanged 3 days agoMITView on GitHub
Follow the project rules in AGENTS.md at the repository root. For multi-step tasks, read the matching guide in .agents/skills/. Key points: - TanStack Start with file-based routes in src/routes/. Never edit src/routeTree.gen.ts. - Public data: server fn (src/data/portfolio.functions.ts) → queryOptions (src/data/index.ts) → route loader → useSuspenseQuery. - Site content lives in the database and is edited in /admin, not in code. - Every table uses RLS. Writes are allowed only through public.has_role(auth.uid(), 'admin'). Never use a service-role key on the…
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-page-sectionSkill
- database-changeSkill
- portfolio-security-checkSkill
- verify-changesSkill
- add-page-sectionSkill
- database-changeSkill
- portfolio-security-checkSkill
- verify-changesSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Follow the project rules in AGENTS.md at the repository root.
- Very specific: line 10
Every table uses RLS. Writes are allowed only through public.has_role(auth.uid(), 'admin').
- Very specific: line 11
Do not hand-edit src/components/ui/*, src/integrations/supabase/types.ts or applied migrations.
- Very specific: line 12
Before you finish: bunx eslint <changed files>, bunx tsc --noEmit, bun run test, bun run build.
≈ “Common” is an estimate: at least 1 in 5 of the 3,827 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
Follow the project rules in AGENTS.md at the repository root.
For multi-step tasks, read the matching guide in .agents/skills/.
Key points:
- TanStack Start with file-based routes in
src/routes/. Never editsrc/routeTree.gen.ts. - Public data: server fn (
src/data/portfolio.functions.ts) →queryOptions(src/data/index.ts) → routeloader→useSuspenseQuery. - Site content lives in the database and is edited in
/admin, not in code. - Every table uses RLS. Writes are allowed only through
public.has_role(auth.uid(), 'admin'). Never use a service-role key on the client. - Do not hand-edit
src/components/ui/*,src/integrations/supabase/types.tsor applied migrations. - Before you finish:
bunx eslint <changed files>,bunx tsc --noEmit,bun run test,bun run build. Fullbun run linthas known Prettier errors in existing code.
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.

