name: stephen-doc-writer description: Use this agent when you need to update, consolidate, or create technical documentation at the end of development sessions. Examples: Context: User has just completed implementing a new feature and needs documentation updated. user: 'I just finished implementing the new authentication system. Can you update the documentation?' assistant: 'I'll use the stephen-doc-writer agent to update the documentation with the new authentication system details.' Since the user needs documentation updated after completing work, use the stephen-doc-writer agent to create comprehensive yet concise documentation. Context: User has scattered documentation across multiple files that needs consolidation. user: 'We have documentation spread across 5 different README files. Can you consolidate this?' assistant: 'I'll use the stephen-doc-writer agent to consolidate all the scattered documentation into a minimal number of well-organized files
name: kent-beck-code-mentor description: Use this agent when you need expert guidance on code simplicity, readability, and maintainability. Perfect for code reviews, refactoring suggestions, or when you want to improve existing code following Kent Beck's principles of simple design and extreme programming practices. Examples: Context: User has written a complex function with multiple responsibilities and wants to improve it. user: 'I wrote this function that handles user authentication, logging, and data validation all in one place. It works but feels messy.' assistant: 'Let me use the kent-beck-code-mentor agent to review this code and provide suggestions for simplification and better separation of concerns.' Context: User is designing a new feature and wants guidance on keeping it simple and extensible. user: 'I'm about to implement a notification system that needs to handle email, SMS, and push notifications. How should I structure this?' assistant: 'I'll use the kent-beck-c
Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.
Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1
- Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
- Select "Create new custom chat mode file"
### WARNING: READ CAREFULLY BEFORE ATTEMPTING ### | |
# | |
# Officially, this is not recommended. YMMV | |
# https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os/ | |
# | |
# This mostly works if you are on 64bit. You are on your own if you are on 32bit or mixed 64/32bit | |
# | |
# Credit to anfractuosity and fgimenezm for figuring out additional details for kernels | |
# |
#!/bin/sh | |
usage() { | |
cat <<\EOF | |
usage: git jump <mode> [<args>] | |
Jump to interesting elements in an editor. | |
The <mode> parameter is one of: | |
diff: elements are diff hunks. Arguments are given to diff. |
WARNING: Article moved to separate repo to allow users contributions: https://github.com/raysan5/custom_game_engines
A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like [Unreal](https:
#!/usr/bin/env bash | |
# Author: Devin Waever <https://github.com/sukima> | |
# Author: Augusto Pascutti <[email protected]> | |
# Original source: https://github.com/sukima/dotfiles/blob/gh-pages/homeshick.sh | |
# For Windows : https://gist.github.com/augustohp/15183d64bcba18a9a773b7402ea63801 | |
# Fork source : https://gist.github.com/augustohp/0b0f96249e399d4ec731830280fbe776 | |
# | |
# Installs homeshick and clones castles of interest | |
# Usage: bash <(curl -Ls https://git.io/fNMTH) |
Some Jenkinsfile examples |
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages