ciembor

The jokes about vibe coding aged poorly, as long as you know how to vibe code and use common sense.

I built a small repo of ready-to-use project rules for AI coding agents, based on classic software engineering books.

Supported tools:

- Codex: AGENTS.md

- Cursor: .cursor/rules/.mdc

- Claude Code: .claude/rules/.md

Books included:

1. A Philosophy of Software Design — John Ousterhout

2. Clean Architecture — Robert C. Martin

3. Clean Code — Robert C. Martin

4. Code Complete — Steve McConnell

5. Designing Data-Intensive Applications — Martin Kleppmann

6. Domain-Driven Design — Eric Evans

7. Domain-Driven Design Distilled — Vaughn Vernon

8. Implementing Domain-Driven Design — Vaughn Vernon

9. Patterns of Enterprise Application Architecture — Martin Fowler

10. Refactoring — Martin Fowler

11. Release It! — Michael T. Nygard

12. The Pragmatic Programmer — Andrew Hunt and David Thomas

13. Working Effectively with Legacy Code — Michael Feathers

The idea is not to summarize or replace the books, but to turn their engineering principles into practical instructions that can guide agent behavior during implementation, refactoring, review, and testing.

Repo: https://github.com/ciembor/agent-rules-books

Have fun, Maciej Ciemborowicz

I built a small repo of ready-to-use project rules for AI coding agents, based on classic software engineering books.

Supported tools:

- Codex: AGENTS.md

- Cursor: .cursor/rules/.mdc

- Claude Code: .claude/rules/.md

Books included:

1. A Philosophy of Software Design — John Ousterhout

2. Clean Architecture — Robert C. Martin

3. Clean Code — Robert C. Martin

4. Code Complete — Steve McConnell

5. Designing Data-Intensive Applications — Martin Kleppmann

6. Domain-Driven Design — Eric Evans

7. Domain-Driven Design Distilled — Vaughn Vernon

8. Implementing Domain-Driven Design — Vaughn Vernon

9. Patterns of Enterprise Application Architecture — Martin Fowler

10. Refactoring — Martin Fowler

11. Release It! — Michael T. Nygard

12. The Pragmatic Programmer — Andrew Hunt and David Thomas

13. Working Effectively with Legacy Code — Michael Feathers

The idea is not to summarize or replace the books, but to turn their engineering principles into practical instructions that can guide agent behavior during implementation, refactoring, review, and testing.

Repo: https://github.com/ciembor/agent-rules-books

Have fun, Maciej Ciemborowicz

Someone on polish wykop.pl told me, that this way works only with terminals based on libXt (for example xterm, aterm, eterm, urxvt). Someone else want to contribute and write export to other terminals, that would be very nice:). If you want to use these colors right now, you may just copy hex codes into your terminal's configuration.

Attention please! There was a bug:D. Magenta was inverted with cyan. It's corrected now. Sorry for any problems.

.Xdefaults do the same thing, but it looks this file is deprecated. I may recomend the Arch Linux Wiki: https://wiki.archlinux.org/index.php/X_resources .

Good point! I was inspired by this topic on Arch Linux forum - https://bbs.archlinux.org/viewtopic.php?id=51818&p=1. There are more similar scripts.

Personaly I'm in love with Monokai: https://twitter.com/#!/ciembor/media/slideshow?url=pic.twitt.... But I think even the most beloved themes bores after some time:).

Thanks! I spent the last three days coding this, and now I only hope it will stand out anywhere:).

Hi all. I think I did something cool and I want to share it with you. Who loves Linux knows, that customizing things sometimes takes too much time. Customizing terminal color schemes is one of these things. I present you the 4bit - Terminal Color Scheme Designer, which allows you to create your own theme and generate .Xresources / .Xdefaults config in just few minutes:). Thanks for voting, digging, tweeting, liking or whatever - I really appreciate it! Enjoy. :)