Your calm window into the Atmosphere.
morgen.blue
rss
atproto
chore(claude): add path-scoped rules and Skills section
Wire `.claude/rules/` so file-type-matched skills (laravel-best-practices,
pest-testing, inertia-react-development, wayfinder-development, morgenblau-designer,
tailwindcss-development) get nudged automatically. Add a CLAUDE.md Skills section
to surface morgenblau-designer for frontend work and the atproto-* skills for
protocol work.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
+23
+6
.claude/rules/inertia.md
+6
.claude/rules/inertia.md
···
1
+
---
2
+
paths:
3
+
- "resources/js/**/*.{ts,tsx}"
4
+
---
5
+
6
+
Use the `inertia-react-development` skill for Inertia/React work, `wayfinder-development` when wiring frontend to backend routes/actions, `morgenblau-designer` for any UI/styling/copy decisions, and `tailwindcss-development` for Tailwind class work.
+6
.claude/rules/pest.md
+6
.claude/rules/pest.md
+6
.claude/rules/php.md
+6
.claude/rules/php.md
···
1
+
---
2
+
paths:
3
+
- '**/*.php'
4
+
---
5
+
6
+
Use the `laravel-best-practices` skill when working with Laravel PHP code. Also invoke `inertia-react-development`: Inertia spans both sides, so PHP controllers returning `Inertia::render()` need the same skill loaded as the React pages they target.
+5
CLAUDE.md
+5
CLAUDE.md
···
26
26
- **Test like an experienced senior dev**: focus on meaningful behavior and likely failure modes, not exhaustive edge-case enumeration. Each test should earn its place.
27
27
- No frontend test runner is installed yet; add Vitest when the first interaction-worthy UI lands.
28
28
29
+
## Skills
30
+
31
+
- For any frontend/UI task (components, styling, layout, copy, polish), invoke `morgenblau-designer`.
32
+
- For ATProto protocol work, invoke the matching skill: `atproto-oauth`, `atproto-lexicon`, `atproto-publish-lexicon`, `atproto-identity-resolution`, `atproto-repository`, `atproto-cid`, `atproto-attestation`.
33
+
29
34
## Verification
30
35
31
36
After each batch of work, run: