@skills · Owner

Agent skills by bfollington

36 skills indexed from github.com/bfollington. Reference any of them in AdaL, Claude Code, Cursor or any coding agent — nothing to install.

• bevy · Skill · 52 stars

  This skill should be used when working on Bevy game engine projects. It provides specialized knowledge for Bevy's Entity Component System (ECS) architectur

• claude-plugins · Skill · 52 stars

  Reference for building and distributing Claude Code plugins — plugin.json and marketplace.json structure, bundling commands, agents, skills and hooks, vers

• code-review · Skill · 52 stars

  Use when reviewing written code — your own or someone else's. Concerns finding what the code will cost later rather than what it violates now, and saying i

• domain-driven-design · Skill · 52 stars

  This skill should be used whenever domain modeling is taking place. It provides specialized guidance for type-driven and data-driven design based on Rich H

• godot · Skill · 52 stars

  This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architectur

• godot-interactive · Skill · 52 stars

  Interact with a running Godot game via MCP — launch, screenshot, click, inspect scene tree, get/set properties, call methods, run dev-console commands. Pow

• ideate · Skill · 52 stars

  Use when thinking needs to open rather than close — generating possibilities, breaking out of a stuck frame, reading the state of a creative process, or no

• implement · Skill · 52 stars

  Use when carrying out a change that is already decided — building the thing rather than choosing it. Concerns staying oriented while the code is in motion

• notes · Collection · 52 stars
• orient · Skill · 52 stars

  Use when arriving in an unfamiliar codebase, or returning to one after long enough that its shape has been forgotten. Concerns building a working model of

• pattrns · Skill · 52 stars

  Guide for creating generative, emergent music with Pattrns, the Lua-based pattern sequencing engine for Renoise. Use when composing algorithmic patterns, g

• plan · Skill · 52 stars

  Entry point for planning work — routes to the skills that own the substance. Use when the user asks to plan, sequence, or scope something and it is not yet

• plugins · Collection · 52 stars
• research · Skill · 52 stars

  Use when a specific question must be answered before work can sensibly proceed — how something currently works, whether an approach is viable, what already

• shadertoy · Skill · 52 stars

  This skill should be used when working with Shadertoy shaders, GLSL fragment shaders, or creating procedural graphics for the web. Use when writing .glsl f

• skill-improver · Skill · 52 stars

  Use at a checkpoint after real friction — a task where something was repeatedly confusing, a skill misfired or failed to fire, or a workaround was invented

• skill-management · Skill · 52 stars

  Create, update, and manage Claude Code skills. Use when working with SKILL.md files, slash commands, or extending Claude's capabilities.

• skills · Collection · 52 stars
• skills · Collection · 52 stars
• skills · Collection · 52 stars
• sqlite-db · Skill · 52 stars

  General guide for using the sqlite3 CLI to build composable knowledge databases. Use this skill when creating SQLite databases, designing schemas, querying

• sqlite-notes · Skill · 52 stars

  Personal note-taking, thinking trails, and knowledge management using plain SQLite. Supports capture-heavy workflows with clear provenance tracking, AI-gen

• strudel · Skill · 52 stars

  This skill should be used when working with Strudel.cc, a live-coding music environment. Use when creating musical patterns, drum sequences, melodies, bass

• terma · Collection · 52 stars
• terma · Collection · 52 stars
• tsal · Collection · 52 stars
• writing-code · Skill · 52 stars

  Use when writing or restructuring code in any language. Concerns the shape of the code itself — what is data and what is function, where effects live, what

• authoring-skills · Skill

  Use when writing, revising, or judging a skill. A skill is a packet of wisdom that changes how a situation is seen, not a procedure to follow — dense, comp

• concurrent-change · Skill

  Use when work is about to be split across multiple agents, or when deciding whether it should be. Concurrency is a property of the change, not a scheduling

• convergent-planning · Skill

  Use when planning any multi-step change, or when a plan already exists and is about to be executed. A plan is a sequence of ambiguity collapses, not a list

• decomposition · Skill

  Use when deciding where the boundaries in a system go — what becomes a module, a service, a process, a package; what gets extracted, merged, or left duplic

• domain-modeling · Skill

  Use when deciding what the concepts in a system are and what they are called — the types, the boundaries between contexts, the vocabulary. Concerns whether

• idea-to-prototype · Skill

  Use when an idea needs to become something buildable, or needs to die honestly before anything is built. Concerns the alternation between opening a possibi

• investigate-debug · Skill

  Use when something is wrong and the cause is not yet known — failures, regressions, flaky behaviour, performance problems, incidents, or a user report that

• map-the-space · Skill

  Explore a problem space before committing to a direction. Use this whenever the user is circling an idea rather than executing one — thinking out loud, ask

• surface-forks · Skill

  Use during any implementation, design, refactor, or debugging task, in any language or codebase. Before changing anything that touches an existing domain c

Browse the @skills marketplace