Agent Coder
Skill Verified ActiveAgent skill for coder - invoke with $agent-coder
To empower developers with expert-level guidance and best practices for writing production-quality code, ensuring maintainability, efficiency, and robustness.
Features
- Expert code implementation guidance
- API design and refactoring support
- Performance optimization strategies
- Robust error handling implementation
- MCP tool integration for memory and performance
Use Cases
- When writing new code that needs to adhere to high quality standards
- When refactoring existing code for better maintainability or performance
- When designing new APIs or interfaces
- When implementing complex error handling logic
Non-Goals
- Automatically debugging runtime errors
- Writing code without any human oversight
- Replacing the need for a human software architect
Documentation
- info:Configuration & parameter referenceWhile some MCP tool parameters are shown, there is no explicit documentation of defaults or precedence for configuration, making some aspects implicit.
Scope
- info:Tool surface sizeThe skill itself exposes minimal tools, but the broader Ruflo project has a large number of plugins and agents which could be considered part of its ecosystem.
Installation
npx skills add ruvnet/rufloRuns the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.
Quality Score
VerifiedTrust Signals
Similar Extensions
Coding Standards
100Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
Refactoring Patterns
99Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", or "decompose conditional". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation to apply to a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.
Karpathy Guidelines
99Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Neon Postgres
100Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
Sdk Dx
100Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"
Csharp Async
100Get best practices for C# async programming