El Feo Ai Context
el-feo-ai-context is a Claude Code plugin collection for the Build phase that bundles six dev and DevOps-oriented plugins for GitHub coordination, Rails and TypeScript quality, testing, and deployment-aware agent workflo
by el-feo · github.com/el-feo/ai-context
Install a six-plugin Claude Code dev toolkit for Rails and TypeScript projects that ties together GitHub workflows, Kamal deploy context, testing, and task orchestration.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install el-feo-ai-context@el-feo/ai-contextBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:el-feo/ai-context") and the paste-ready config with skillselion.get_install_config("plugin:el-feo/ai-context").
What it does
el-feo-ai-context is a community Claude Code plugin collection from el-feo/ai-context that packages six plugins aimed at full-stack and DevOps-minded solo builders. Rather than a single narrow skill, it spreads context across GitHub project management (GHPM and GHPM Plus), autonomous and parallel task execution, Rails and TypeScript quality gates, testing with RSpec and Vitest, infrastructure notes around Kamal and Tailscale, and documentation or diagram generation. Builders running Ruby APIs or mixed Rails plus JavaScript frontends benefit when they want the agent to respect real repo conventions—linting, security scanning, coverage, and structured task breakdown—without re-prompting the same rules every session. The bundle is intermediate in spirit: you should already have a project skeleton and CI habits. Use it during Build and early Ship when integration with GitHub, worktrees, and deploy tooling matters as much as feature code, and you want Claude Code plugins that mirror how a small team coordinates delivery.
Highlights
- Six Claude Code plugins in one repo for general dev, DevOps, and workflow coordination
- Ruby on Rails stack signals: Brakeman, RuboCop, RSpec, SimpleCov, Sandi Metz-style review keywords
- JavaScript/TypeScript toolchain: ESLint, Vitest, and documentation or Mermaid diagram support
- GHPM and EpicTask-style project and parallel worktree orchestration for autonomous execution
- Kamal deployment and failure recovery patterns for shipping from the agent session
Why builders use it
Claude Code sessions drift from your real GitHub, Rails, TypeScript, and Kamal setup when context lives only in chat instead of repeatable plugins.
After install, your agent can lean on bundled plugins for epic task breakdown, parallel worktrees, linters, tests, and DevOps-aligned guidance matched to el-feo’s stack.
At a glance
- Type - Plugin in DevOps.
- Adoption - 0 installs, 8 stars, 0 votes.
FAQ
Who is el-feo-ai-context for?
It is for developers using Claude Code on Ruby and JavaScript/TypeScript projects who want coordinated plugins for GitHub, testing, and deployment practices.
When should I use el-feo-ai-context?
Use it when you are building or maintaining a repo and need persistent agent context for task orchestration, linting, CI-style checks, and Kamal-oriented DevOps.
How do I add el-feo-ai-context to my agent?
Add the el-feo/ai-context repository as a Claude Code plugin source, enable the bundle, and turn on the individual plugins that match your stack (Rails, Vitest, GHPM, etc.).
Comments
Share how you use el-feo-ai-context, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.