Skip to content

Instantly share code, notes, and snippets.

View sevos's full-sized avatar

Artur Roszczyk sevos

View GitHub Profile
<role>
You are an experienced Product Owner specializing in backlog management, ticket refinement, and sprint planning. You work with small agile teams (3-5 developers, 15-25 story points/sprint) and focus on maintaining clean, actionable backlogs through continuous refinement.
</role>
<communication_approach>
Lead with questions to understand context, then provide clear recommendations:
- Ask 1-2 clarifying questions before suggesting solutions
- Provide specific, actionable recommendations with brief rationale
- Invite feedback: "Does this approach work for your team?"
- Enable team autonomy—facilitate rather than prescribe
@sevos
sevos / onboarding-material-generator.md
Last active December 1, 2025 14:25
Drop this agent into your ~/.claude/agents/ and call it via @agent-onboarding-material-generator to create documentation of an existing codebase, e.g. "Read code in this project and explain to me how the accounting system works, especially around payment reconciliation @agent-onboarding-material-generator" -> Will produce a nice HTML doc.

name: onboarding-material-generator description: Use this agent when the user requests creation of learning materials, onboarding documentation, or educational content that explains how a specific part of the codebase works. This includes requests for:\n\n- Tutorial pages explaining system concepts or architecture\n- Onboarding materials for new engineers\n- Step-by-step guides for understanding code areas\n- Educational content with diagrams and examples\n- Explanations of database schemas, models, or workflows\n\nExamples of when to use this agent:\n\n\nuser: "Can you create an onboarding page for the multi-tenancy system?"\nassistant: "I'll use the onboarding-material-generator agent to create comprehensive learning material about the multi-tenancy architecture."\n\n\n\n\nuser: "I need a tutorial page explaining how contracts and terms work in this system"\nassistant: "Let me use the onboarding-material-generator agent t

require "active_record"
require "pg"
require "sqlite3"
# PostgreSQL database configuration
postgres_config = {
adapter: "postgresql",
host: ENV["POSTGRES_HOST"],
username: ENV["POSTGRES_USER"],
password: ENV["POSTGRES_PASSWORD"],
#!/usr/bin/env bash
# At each invocation of this script, this script cycles through the next config from ~/.config/hypr/monitor-config/
# directory and symlinks it to ~/.config/hypr/monitor-config.nix
if [ -f ~/.config/hypr/monitor-config.conf ]; then
CURRENT_CONFIG="$(readlink ~/.config/hypr/monitor-config.conf)"
NEXT_CONFIG=$(find ~/.config/hypr/monitor-config/*.conf | grep -A 1 "$CURRENT_CONFIG" | tail -n 1)
# if next config is the same as the current, start from the beginning of the list
@sevos
sevos / docker-compose.yml
Created February 7, 2024 13:29
Docker compose for Send
version: '3.7'
services:
app:
image: registry.gitlab.com/timvisee/send:latest
volumes:
- uploads:/uploads
ports:
- published: 1443
target: 1443
<div id="categories" data-controller="persist-scroll-position" data-action="scroll->persist-scroll-position#persist:passive" class="flex-auto flex flex-col gap-4 overflow-y-auto">
...
</div>
@sevos
sevos / README.md
Last active May 9, 2019 16:13
Rails 5.2 + Komponent + Turbolinks + Stimulus

Usage

rails new my_app --rc=template.rc -m template.rb
@sevos
sevos / feature_spec.rb
Created March 24, 2017 14:52
This is a helper simulating mouse events related to hovering over an element: onmouseenter onmouseleave etc.
require 'rails_helper'
RSpec.feature 'Feature', js: true do
include InteractionHelper
scenario 'Scenario' do
visit '/'
hover_mouse(find('div#id')) do
click_on 'Button'

Keybase proof

I hereby claim:

  • I am sevos on github.
  • I am sevos (https://keybase.io/sevos) on keybase.
  • I have a public key ASAnWvwdcqTcBoAhocP3U5ugAXF9rJMkfsh7RVo9CDcOjAo

To claim this, I am signing this object:

@sevos
sevos / value_object.rb
Last active December 28, 2015 16:39
This is just an idea of value objects API and dirty implementation for Ruby. A frankenstein created from merge of Struct's and OpenStruct's APIs. It supoprts mandatory and optional fields. It raises exceptions if API of value object is misused. Feel free to comment and refactor the implementation!
# TODO: ValueObject should be immutable. Setter should return new instance.
class ValueObject < Struct
def self.new(*fields)
all_fields, optional_fields = if fields.last.is_a?(Hash)
optional_fields = fields.pop
[fields + optional_fields.keys, optional_fields]
else
[fields, {}]
end