marcel/familienarchiv
1
0
Fork 0
Code Issues 111 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

chore: add Claude personas, skills, memory, and project docs

Browse Source 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Marcel
2026-04-14 20:22:39 +02:00
parent e4719b9487
commit 3d3d4b8616
26 changed files with 12123 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
.claude/projects/-home-marcel-Desktop-familienarchiv/memory/MEMORY.md Normal file
View File

@@ -0,0 +1,11 @@
# Memory Index
- [Shell environment setup](./feedback_shell_env.md) — source SDKMAN and nvm before running java/mvn/node/npm
- [Gitea instance](./reference_gitea.md) — self-hosted Gitea at 192.168.178.71:3005, MCP server configured as "gitea"
- [Issue workflow](./feedback_issue_workflow.md) — create Gitea issues not todo files; feature/bug/devops labels with title formats
- [Branch and PR workflow](./feedback_branch_pr.md) — always branch + PR, never commit directly to main
- [Docker commands one line](./feedback_docker_commands.md) — always write docker commands on a single line for easy copy-paste
- [Red/Green TDD](./feedback_tdd.md) — always write failing test first before any production code
- [TDD red/green flow](./feedback_tdd_flow.md) — write failing test then immediately go green, no pausing between phases
- [Atomic commits](./feedback_atomic_commits.md) — one logical change per commit, never bundle multiple things
- [Single-family access model](./project_single_family_access.md) — no multi-tenancy, no ownership, no row-level security; role-based access is sufficient

10
.claude/projects/-home-marcel-Desktop-familienarchiv/memory/project_single_family_access.md Normal file
View File

@@ -0,0 +1,10 @@
---
name: Single-family access model
description: Familienarchiv is used by one family — no multi-tenancy, no document ownership, no row-level security needed
type: project
---
The archive serves a single family. There is no multi-tenant isolation, no document ownership, and no row-level access control. Everyone with the correct role (READ_ALL / WRITE_ALL) can read and edit all documents. Do not suggest row-level security, per-user document ownership, or tenant filtering.
**Why:** Single-family use case — all authenticated users with the right role are trusted equally.
**How to apply:** Skip IDOR / ownership-check recommendations. Role-based access via `@RequirePermission` is the correct and sufficient access control model for this app.