gierd

gierd

engineeringClaude Codeby gierd-inc

Summary

Gierd Dev Skills — process tools (grill/triage/to-prd/to-issues/diagnose/tdd), Rails 8.1+ domain references, OOP extraction patterns, Rails antipattern references, and the PRD-to-shipped workflow. Commands namespaced under /gierd:.

Install to Claude Code

/plugin install gierd@gierd

Run in Claude Code. Add the marketplace first with /plugin marketplace add gierd-inc/dev-skills if you haven't already.

README.md

Gierd Skills

> [!WARNING] > This repository is deprecated. It has been replaced by gierd-inc/g-hive. No further updates will be made here. Please migrate to g-hive.

![skills.sh](https://skills.sh/gierd-inc/dev-skills)

Plugin name: gierd. Commands: /gierd:build, /gierd:prd-to-spec, /gierd:status, etc.

Agent skills for Gierd's Ruby on Rails engineering workflow — daily-driver process tools, the Gierd Dev Skills PRD-to-shipped pipeline, and a complete set of Rails-domain skills.

> Forked from mattpocock/skills and ryenski/agency-plugin. Process skills (grill, triage, to-prd, to-issues, diagnose, tdd, improve-architecture) come from Matt Pocock's set; Rails skills and the Gierd Dev Skills workflow come from the agency-plugin. Both are credited inline in their respective SKILL.md files where retained verbatim.

What's in this repo

These skills are designed to be small, easy to adapt, and composable. They work with any model. Hack around with them. Make them your own.

The skills cover six broad areas:

1. Process — grill the agent into alignment, triage incoming bugs, break PRDs into issues, debug systematically. 2. Rails domain knowledge — one focused skill per Rails layer (models, controllers, views, jobs, mailers, migrations, security, performance, testing, Hotwire, etc.), targeted at Rails 8.1+. Each is loaded on-demand based on what the agent is touching. 3. OOP extraction patterns — value objects, null objects, concerns, presenters, query objects, form objects, service objects, policy objects, and (rarely) repository pattern. Loaded when fat models stop being enough. 4. Rails antipatterns — named smells (fat-controller, callback-hell, service-object-soup, etc.) drawn from Rails Antipatterns (Pytel & Saleh) and the 37signals tradition. Loaded when reviewing or refactoring code that exhibits a smell. 5. The Gierd Dev Skills workflow — PRD → Spec → Issues → Code → draft PR, with file-based subagent contracts and resumable per-feature state under .dev-skills/. 6. Productivitygrill-me, caveman mode, write-a-skill.

Installation

This is a private Claude Code plugin. Install it through Claude Code's plugin marketplace system.

From GitHub

Add the marketplace and install with the claude plugin CLI:

claude plugin marketplace add gierd-inc/dev-skills
claude plugin install gierd@gierd

You'll need GitHub access to gierd-inc/dev-skills (SSH key or HTTPS credentials configured for git).

From a local directory

If you've already cloned the repo somewhere, point Claude Code at the path:

claude plugin marketplace add ~/Projects/dev-skills
claude plugin install gierd@gierd

After installing

Run /setup-gierd-skills in your agent. It will:

  • Ask which issue tracker you use (Linear by default for Gierd repos, with GitHub / GitLab / local-markdown as alternatives)
  • Confirm the triage label vocabulary
  • Confirm whether the repo is single- or multi-context (multi-context is default for repos with CONTEXT-MAP.md)

Development

If you're actively editing the skills, install via the local directory route above. Claude Code reads from your working tree, so edits to any SKILL.md (or command, agent, etc.) are picked up on the next agent session — no reinstall step:

claude plugin marketplace add ~/Projects/dev-skills
claude plugin install gierd@gierd

For lightweight iteration on just the skills (without registering as a full plugin), use the bundled symlink scripts:

./scripts/link-skills.sh    # symlink every skill into ~/.claude/skills/
./scripts/unlink-skills.sh  # remove the symlinks created above

link-skills.sh symlinks every SKILL.md directory under skills/ (excluding deprecated/) into ~/.claude/skills/. unlink-skills.sh removes only the symlinks pointing back into this repo, leaving any unrelated entries in ~/.claude/skills/ untouched. Useful when you only need the skills loaded and don't care about the /gierd:* slash commands or Gierd Dev Skills subagents.

Slash-command wrappers

Skills auto-load by description match, but they don't appear in the / picker. To make every skill invokable as a slash command, run:

./scripts/generate-skill-commands.sh

This walks skills/**/SKILL.md and writes a thin wrapper into commands/ for each one — so skills/oop/oop/SKILL.md becomes /gierd:oop, skills/gierd/deploy-to-dev/SKILL.md becomes /gierd:deploy-to-dev, etc. Re-run it after adding, renaming, or removing skills.

The script is idempotent: wrappers carry an HTML comment marker, and only marked files are touched. Hand-written commands (build.md, prd-to-spec.md, etc.) are preserved.

Why these skills exist

These skills exist to fix common failure modes with Claude Code, Codex, and other coding agents.

#1 — Misalignment

The most common failure mode in software development is misalignment. The fix is a grilling session — getting the agent to ask you detailed questions about what you're building before it writes anything.

  • /grill-with-docsprefer this for product work. Routes through CONTEXT-MAP.md and the per-context CONTEXT.md files, sharpens terminology, and updates ADRs inline. Produces durable artifacts so the next session inherits the alignment.
  • /grill-me — non-code grilling, no docs touched. Use for smaller tasks where you only need clarity in the moment and don't want to commit to artifacts.

#2 — Verbose agents drifting from the team's language

Agents are usually dropped into a project and asked to figure out the jargon as they go. The fix is a shared, written domain language — CONTEXT.md per bounded context, plus docs/adr/ for decisions that span contexts. /grill-with-docs builds and maintains these.

#3 — Code that doesn't work

Static feedback loops, TDD, and disciplined debugging:

  • /tdd — Minitest + fixtures, red-green-refactor
  • /diagnose — reproduce → minimise → hypothesise → instrument → fix → regression-test

#4 — Ball-of-mud architectures

Agents accelerate software entropy. Counter it:

Reference

Engineering

Skills used daily for code work.

  • diagnose — Disciplined diagnosis loop for hard bugs and performance regressions.
  • grill-with-docs — Grilling session that updates CONTEXT.md (single- or multi-context) and ADRs inline.
  • improve-codebase-architecture — Find deepening opportunities, informed by CONTEXT-MAP.md and docs/adr/.
  • setup-gierd-skills — Scaffold per-repo config (issue tracker, triage labels, domain doc layout). Run once per repo.
  • tdd — Test-driven development with red-green-refactor. Minitest + Rails fixtures.
  • to-issues — Break a plan, spec, or PRD into independently-grabbable issues using vertical slices.
  • to-prd — Turn the current conversation into a PRD on the configured issue tracker.
  • triage — Triage issues through a state machine of triage roles.
  • zoom-out — Higher-level context for an unfamiliar section of code.
  • prototype — Throwaway prototype to flush out a design.

Rails

Hub-and-spoke skill covering all Rails layers. The hub (skills/rails-expert/SKILL.md) carries the routing table; each layer's reference lives in skills/rails-expert/references/. Loaded on-demand based on what the agent is touching; invoke /gierd:rails-expert for a full-layer sweep.

See skills/rails-expert/SKILL.md for the reference guide and routing table.

OOP Patterns

Hub-and-spoke skill covering extraction patterns for when Rails' defaults stop being enough — value objects, null objects, concerns, presenters, query objects, form objects, service objects, policy objects, and (rarely) repository pattern. Invoke /gierd:oop for a full-pattern sweep.

See skills/oop/SKILL.md for the reference guide and routing table.

Rails antipatterns

Hub-and-spoke skill covering named Rails smells — what not to do, and what to do instead. Drawn from Rails Antipatterns (Pytel & Saleh) and the 37signals tradition (DHH, Jorge Manrubia). Invoke /gierd:rails-antipatterns for a full-antipattern sweep.

See skills/rails-antipatterns/SKILL.md for the antipattern catalog and routing table.

Gierd Dev Skills workflow

PRD → Spec → Issues → Code → draft PR. Resumable per-feature state under .dev-skills/.

See commands/ for the slash commands (/gierd:prd-to-spec, /gierd:spec-to-issues, /gierd:build, /gierd:create-pr, /gierd:status, /gierd:resume, etc.).

Productivity

General workflow tools, not code-specific.

  • caveman — Ultra-compressed communication mode.
  • grill-me — Get relentlessly interviewed about a plan or design.
  • write-a-skill — Create new skills with proper structure and progressive disclosure.

Misc

License & attribution

This repo bundles work originally authored by Matt Pocock and Ryan Heneise. See individual SKILL.md files and commit history for attribution.

Related plugins

Browse all →