ayushyaandClaude Sonnet 5
51682a901d
Moved into .claude/context/ (alongside the other topic docs CLAUDE.md points agents at) rather than the repo root, so it's discovered the same way as architecture.md/styling.md/etc. Flags styling.md as documenting the pre-rework theme in the meantime, so the two don't read as contradictory. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.8 KiB
Noo — Nextcloud Client
A Flutter (Material 3) client for Nextcloud: browse files, view photos, check activity, manage shares/trash. Auth uses Nextcloud's Login Flow v2 — the app never collects a password directly, only a server address.
Detailed, topic-specific context lives in .claude/context/. Read the
relevant file(s) before working in that area rather than loading all of them:
architecture.md— folder layout, state management, navigation/screen flowserver.md— Nextcloud API/WebDAV integration, login flow, session persistencestyling.md— theming, Material 3 conventions, fonts, reusable chrome widgetsstandards.md— code style, comment conventions, linting, testingdesign-system/DESIGN_SYSTEM.md— the target visual/component spec (tokens, components, platform mapping, screen recipes) for the in-progress UI rework; the sibling.dc.html/noo-kit.jsfiles it references are the visual/token reference builds, not something to read directly
Common commands
flutter test # run tests
flutter analyze # static analysis / lints
Keeping docs current
After making a change that affects architecture, server integration,
styling conventions, or code standards, update the relevant file(s) in
.claude/context/ in the same session — don't leave documentation to drift
from the code. This applies whether the change is a new feature, a
refactor, or a convention shift (e.g. a new reusable widget, a changed
state-management pattern, a new dependency). If a change doesn't fit any
existing topic file, add a section rather than skipping the update.