You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goose Subagents Recipe Collection - Complete catalog with usage examples and workflow patterns
Goose Subagents Recipe Collection
A curated collection of powerful Goose recipes for code analysis, testing, documentation, and research.
📚 About
These recipes are specialized configurations for Goose subagents that help automate common development workflows. Each recipe is designed to be reusable, parameterized, and production-ready.
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
Installation Instructions
Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On implementing a client for feature flags in your UI codebase
This document isn't an explainer on Feature Flags, you can find that with my amateur writeup, or literally hundreds of better writeups out there.
This document is also agnostic to the choice of service you'd use: LaunchDarkly or split.io or optimizely or whatever; that's orthogonal to this conversation.
Instead, this document is a list of considerations for implementing a client for using Feature Flags for User Interface development. Service providers usually give a simple fetch and use client and that's it; I contend that there's a lot more to care about. Let's dive in.
To encourage usage, we'd like for the developer experience to be as brutally simple as possible. So, this should be valid usage:
Docker commands to remove all containers and images
docker kill $(docker ps -q) to kill all running containers docker rm $(docker ps -a -q) to delete all stopped containers. docker volume rm $(docker volume ls -q) to delete all volumes. docker rmi $(docker images -q) to delete all images.
All articles on #beginners should be written for those new to programming, development, networking, or to a particular language. These posts should also require little to no prerequisite knowledge. If you wish, you may rewrite your post to meet these requirements, at which point you may request that the tag be added back. Otherwise, just use the appropriate technology tags. (Read more about the tag rules here.)