Claude Behavior Layer — the rules and review pages I use with Claude Code
This is how I set up Claude Code. I wanted short answers and decisions I could review easily.
It combines writing rules, reusable skills, and local browser pages. Claude puts questions or prototype choices there for me. I review them, then send my answers back.
The complete setup currently uses macOS, iTerm2, and Python. Individual rules and skills can be reused separately. It’s free, with an MIT licence.
I also used it while building my Blindfold Chess trainer. Both repositories are public if you want a concrete example.
Chess example: Ceasar369/blindfold-chess
I’m sharing my own setup in case it helps someone. What would make the setup easier to try?
1 point
I made a blindfold chess trainer for my own practice
I wanted a way to practise without seeing the pieces. So I made Blindfold Chess.
It includes coordinate, movement, notation, and position exercises. It runs in your browser without an account. Progress stays on your device.
Play: ceasar369.github.io
Code and local download: Ceasar369/blindfold-chess
I used my Claude Code setup to build it. That setup is also public: Ceasar369/claude-behavior-layer
I’d like feedback on exercises that feel awkward or unclear.
3 points · 10 comments
The Claude Code setup I use for my projects
I’ve put my Claude Code setup on GitHub. It works well for me. I’m sharing it in case parts of it are useful.
The main pieces are rules, skills, and local decision pages. The rules ask for short answers and clear decisions. The skills cover planning, coding, prototypes, checks, and handovers. They also coordinate separate Claude Code sessions.
For example, a session proposes two implementation choices. I review both on a local page. I can agree or add feedback before it continues. A handover saves written context for a fresh session.
I also tried the same setup with Blindfold Chess. It’s a trainer I wanted for my own practice. It has exercises for playing without seeing the pieces. The same setup worked well on that separate project.
The full setup uses macOS, iTerm2, and Claude Code. You can also take just the rules or skills. The code is MIT licensed.
Claude setup: Ceasar369/claude-behavior-layer
Chess: ceasar369.github.io
The screenshots use a fictional reading-list project. They show the real pages with prepared demo content.
Demo: reviewing where the reading list saves articles.
Demo: assistant plan with clarification, prototypes, implementation, and checks.
Demo: comparing three layouts for the same reading list.
Demo: opening one prototype before choosing or giving feedback.
1 point · 7 comments
Mentions
Claude Behavior Layer — the rules and review pages I use with Claude Code This is how I set up Claude Code. I wanted short answers and decisions I could review easily. It combines writing rules, reusable skills, and local browser pages. Claude puts questions or prototype choices there for me. I review them, then send my answers back. The complete setup currently uses macOS, iTerm2, and Python. Individual rules and skills can be reused separately. It’s free, with an MIT licence. I also used it while building my Blindfold Chess trainer. Both repositories are public if you want a concrete example. Chess example: Ceasar369/blindfold-chess I’m sharing my own setup in case it helps someone. What would make the setup easier to try?
I made a blindfold chess trainer for my own practice I wanted a way to practise without seeing the pieces. So I made Blindfold Chess. It includes coordinate, movement, notation, and position exercises. It runs in your browser without an account. Progress stays on your device. Play: ceasar369.github.io Code and local download: Ceasar369/blindfold-chess I used my Claude Code setup to build it. That setup is also public: Ceasar369/claude-behavior-layer I’d like feedback on exercises that feel awkward or unclear.
The Claude Code setup I use for my projects I’ve put my Claude Code setup on GitHub. It works well for me. I’m sharing it in case parts of it are useful. The main pieces are rules, skills, and local decision pages. The rules ask for short answers and clear decisions. The skills cover planning, coding, prototypes, checks, and handovers. They also coordinate separate Claude Code sessions. For example, a session proposes two implementation choices. I review both on a local page. I can agree or add feedback before it continues. A handover saves written context for a fresh session. I also tried the same setup with Blindfold Chess. It’s a trainer I wanted for my own practice. It has exercises for playing without seeing the pieces. The same setup worked well on that separate project. The full setup uses macOS, iTerm2, and Claude Code. You can also take just the rules or skills. The code is MIT licensed. Claude setup: Ceasar369/claude-behavior-layer Chess: ceasar369.github.io The screenshots use a fictional reading-list project. They show the real pages with prepared demo content. Demo: reviewing where the reading list saves articles. Demo: assistant plan with clarification, prototypes, implementation, and checks. Demo: comparing three layouts for the same reading list. Demo: opening one prototype before choosing or giving feedback.