Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By bfollington
Gain specialized AI expertise for Bevy ECS game development in Rust, Godot scene manipulation and interactive runtime testing, GLSL fragment shaders on Shadertoy, live-coding algorithmic music with Strudel and Pattrns, domain-driven design modeling with Mermaid diagrams, and quick references for Claude Code plugins to streamline creative coding and game projects.
npx claudepluginhub bfollington/terma --plugin tsalThis skill should be used when working on Bevy game engine projects. It provides specialized knowledge for Bevy's Entity Component System (ECS) architecture, component-driven design patterns, system ordering, UI development, build strategies, and common pitfalls. Use this skill when implementing game features, debugging Bevy code, designing component architectures, or working with Bevy's UI system.
Full docs:
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 Hickey and Scott Wlaschin's principles. The skill helps contextualize current modeling within the existing domain model, identifies inconsistencies, builds ubiquitous language, and creates visualizations (Mermaid, Graphviz/DOT, ASCII diagrams) to communicate domain concepts clearly. Use this skill when designing types, modeling business domains, refactoring domain logic, or ensuring domain consistency across a codebase.
Interact with a running Godot game via MCP — launch, screenshot, click, inspect scene tree, get/set properties. Powered by godot-mcp + GodotMCPBridge autoload.
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Opinionated library of philosophy and process for developing software with LLMs
Editorial "Indie Game Dev" bundle for Claude Code from Antigravity Awesome Skills.
Develop, test, build, and deploy Godot 4.x games. Includes GdUnit4 testing, PlayGodot automation, web/desktop exports, CI/CD pipelines, and deployment.
Bevy game engine development - ECS, rendering, game architecture
Comprehensive game development learning system with 7 specialized agents, 21 in-depth skills, 4 slash commands, and automation hooks. Master game design, programming, graphics, audio, networking, tools, and publishing across Unity, Unreal Engine, and Godot.
Agentic skills framework for Godot 4.x game development — 48 domain-specific skills for GDScript and C#
Use sqlite for managing notes (instead of markdown files)
Opinionated library of philosophy and process for developing software with LLMs
This is a highly-opinionated library of philosophy and process for developing software with LLMs, specifically Claude Code.
Distributed as a Claude Code plugin marketplace.
From within Claude Code:
/plugin marketplace add <git-url-or-local-path>
/plugin install terma@terma
/plugin install terma@tsal
Or test locally during development:
claude --plugin-dir ./plugins/terma --plugin-dir ./plugins/tsal
Use /terma:orient to begin each session. Use /terma:research :question to probe the codebase and write a report to /research. Then, use /terma:plan to plan a change to the application.
Use /terma:implement to spin up one or more well-instructed subagents to implement the plan.
Use /terma:code-review after implementation. Use /terma:ideate to brainstorm.
| Command | Purpose |
|---|---|
/terma:orient | Explore and summarize the project structure |
/terma:research | Deep-dive investigation, writes report to /research |
/terma:plan | Plan next steps without implementing |
/terma:implement | Delegate implementation to subagents |
/terma:code-review | Review code for quality and consistency |
/terma:ideate | Brainstorm using the ideation card deck |
/terma:orient, /terma:plan, /terma:implement, /terma:code-review/terma:orient, /terma:research/terma:ideate.claude-plugin/marketplace.json # Marketplace manifest
plugins/terma/ # Process & philosophy plugin
.claude-plugin/plugin.json # Plugin manifest
agents/ # Subagent definitions
skills/ # Commands & meta skills
lib/ # Shared philosophy & process modules
plugins/tsal/ # Domain-specific skills plugin
.claude-plugin/plugin.json # Plugin manifest
skills/ # Domain skills (bevy, godot, strudel, etc.)
Edit anything under plugins/terma/ or plugins/tsal/. The lib/ directory in terma contains composable modules referenced by skills via @ paths. Domain-specific skills live in tsal and can be modified independently.
The subagent.md lib module encourages "ultrathinking", which may burn through usage quickly. Consider customizing it manually until we have variables.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.