b08x/skills/rubysmithing

Rubysmithing

Convention-aware Ruby code generator. Generates complete, idiomatic Ruby files calibrated to project-detected conventions and task scope.

Agent Delegation Pattern

This skill acts as the hub and delegates to specialized sub-agents for complex tasks. When a task falls outside this skill's scope, use the corresponding agent:

| Task Type | Agent | When to Delegate | |:----------|:------|:-----------------| | Gem API verification | rubysmithing-context | Before generating code using non-stdlib gems | | Project scaffolding | rubysmithing-scaffold | New project initialization (rubysmith/gemsmith) | | LLM/AI/NLP code | rubysmithing-genai | Chatbots, RAG, embeddings, DSPy, MCP servers | | TUI interfaces | rubysmithing-tui | BubbleTea, Lipgloss, Huh, Gum, Bubbles | | Refactoring | rubysmithing-refactor | Convention fixes, Zeitwerk compliance | | QA assessment | rubysmithing-report | SIFT audits, design reviews | | YARD docs | rubysmithing-yardoc | Documentation generation |

Delegation pattern: When delegating, invoke the agent using the Task tool with the appropriate agent name from $CLAUDE_PLUGIN_ROOT/agents/.

Step 1: Detect Mode

Lite Mode (single-file output ≤ ~50 lines, or explicitly simple tasks)

Triggers: "quick script", "simple utility", "one-off", "no dependencies", "stdlib only", or a clearly small self-contained task.

Multi-file scaffold requests always trigger Standard Mode regardless of individual file line count. If the task would produce more than one file, apply Standard Mode.

For new project initialization (rubysmith or gemsmith scaffold): delegate to rubysmithing-scaffold. This skill handles code within an existing project; rubysmithing-scaffold handles the project skeleton itself.

In Lite Mode:

• Generate pure Ruby using stdlib only
• No dry-schema, no dry-types, no async, no circuit_breaker
• No frozen_string_literal mandate (still recommended, but not enforced)
• Output a single file with a brief inline comment explaining any non-obvious choice
• Do not suggest adding gems unless the user asks

Standard Mode (default for all other tasks)

Apply full conventions from references/conventions.md.

Step 2: Detect Convention Target

See references/convention-detection.md for the canonical detection cascade and reporting format. Summary:

1. .rubocop.yml present → use RuboCop config
2. standard in Gemfile → use StandardRB
3. .rubysmith / rubysmith gem → use Rubysmith defaults
4. None → apply community idioms from references/conventions.md

Always state which target was detected and from which artifact before generating.

Step 3: Gem Context Check

Before writing any code that touches a gem:

• Note which gems are involved
• State: "Deferring to rubysmithing-context for [gem] API verification"
• In practice, if rubysmithing-context is active in the session and has already resolved the gem, use the cached result directly

Skip this step for: stdlib only, Lite Mode tasks, gems already resolved this session.

Step 4: Generate

Generate complete files. No truncation. No # ... rest of implementation stubs.

Standard Mode conventions — always apply

# frozen_string_literal: true          # first line of every file

• Two-space indent, no tabs
• snake_case methods/vars, CamelCase classes/modules, SCREAMING_SNAKE constants
• Struct.new(keyword_init: true) for value objects
• Keyword args for 3+ param methods
• Guard clauses over nested conditionals
• Zeitwerk-compliant path ↔ class name
• module_function not extend self
• journald-logger not puts
• Async { } not Thread.new for I/O
• circuit_breaker wrapping external API calls

Output Format

1. File path — relative to project root
2. Complete file content
3. Rationale — one sentence for non-obvious decisions only
4. Gemfile additions — if new gems required
5. Mode applied — "Lite Mode" or "Standard Mode [convention target]"