rc
SolidExplains RC — a pure agent plugin (skills, commands, agents, hooks) for Claude Code, OpenCode and other tools — its workflow pipeline, artifact structure, bundled specialist agents, hooks, and configuration. Use when the user asks how to use RC, what skills or commands exist, or how the workflow pipeline works. Do not use to execute workflow steps — use the specific rc-* skills instead.
Install
Quality Score: 79/100
Skill Content
Details
- Author
- rodolfochicone
- Repository
- rodolfochicone/rc-project
- Created
- 1 months ago
- Last Updated
- 2 weeks ago
- Language
- JavaScript
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
rc-skill-best-practices
Author, refactor, and debug agent skills. Use when creating a new skill from scratch, pruning or restructuring a bloated SKILL.md, tightening a skill description's triggers, or diagnosing bundled references the agent ignores. Do not use for agent instruction files like CLAUDE.md or AGENTS.md (rc-agents-md), for measuring what the whole config surface costs in tokens (rc-context-budget), or for general documentation and READMEs (rc-readme).
rc-memory
The single place for RC's durable, cross-session memory and learning. Records and recalls curated project facts (decisions, conventions, gotchas, glossary), distills recurring corrections/workflows into confidence-scored learnings, and harvests a proven multi-step golden path into a project-local skill. Use to consult memory before working, to record durable facts or distilled learnings afterward, and whenever a task only worked after several attempts or revealed a non-obvious operational route — reaching a database, deploying, running migrations, verifying live — in which case harvest it unprompted. Do not use for workflow/task-scoped notes (use rc-workflow-memory) or for on-demand reflection on a diff (use lesson-learned).
rc-analyze
Performs a deep, evidence-based analysis of an existing codebase to answer a specific analytical prompt — diagnosing the root cause of a bug, hunting inconsistencies and contradictions, understanding how something works, or tracing a behavior or data flow — then writes a thorough report to disk, ending with an actionable implementation plan when a change is implied. Use to understand, trace, or diagnose existing code, or to assess impact and feasibility. Do not use to review a change set or diff for defects (use rc-code-review), to generate remediation issues (use rc-review-round), to apply a plan's code changes (use rc-fix-analysis), or to edit source code directly.