ReddRadar
Topic: best-practices
63 skills in this topic.
-
talk-stage3-concepts
Builds a numbered, categorized concept catalogue from the talk summary and timeline, scoring each concept HIGH / MEDIUM / LOW for talk potential with optional repo enrichment. Use when you need a structured inventory of concepts before choosing a talk angle, or when assessing which ideas have the strongest presentation potential.
FlorianBruniaux/claude-code-ultimate-guide 3,172
-
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
FlorianBruniaux/claude-code-ultimate-guide 3,172
-
MCP Server (Ruby)
This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when editing MCP server files, working with tool/prompt/resource definitions, or discussing LLM tool integrations in Ruby.
hoblin/claude-code-rails-skills 2
-
activerecord
hoblin/claude-code-rails-skills 2
-
Draper Decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing *_decorator.rb files, working in app/decorators/ directory, questioning where formatting methods belong (models vs decorators vs views), or discussing methods like full_name, formatted_*, display_* that don't belong in models. Provides guidance on Draper gem best practices for Rails applications.
hoblin/claude-code-rails-skills 2
-
RSpec Testing
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing *_spec.rb files, working in spec/ directory, planning implementation phases that include tests (TDD/RGRC workflow), writing Testing Strategy or Success Criteria sections, discussing unit or integration tests, or reviewing spec output and test failures. Comprehensive RSpec and FactoryBot reference with best practices, ready-to-use patterns, and examples.
hoblin/claude-code-rails-skills 2
-
skill-builder
Create new Claude Code skills with best practices. Use when user wants to create, extract, or build a new skill. Provides templates and GitHub automation. Trigger phrases include "create a skill", "build a skill", "extract a skill", "new skill", "/skill-builder".
wrsmith108/skill-builder-claude-skill 6
-
ai-collaboration-standards
Prevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions.
Use when: analyzing code, making recommendations, providing options, or when user asks about confidence/certainty.
Keywords: certainty, assumption, inference, evidence, source, 確定性, 推測, 假設, 來源, 證據.
AsiaOstrich/universal-dev-skills 44
-
testing-guide
Testing pyramid and test writing standards for UT/IT/ST/E2E.
Use when: writing tests, discussing test coverage, test strategy, or test naming.
Keywords: test, unit, integration, e2e, coverage, mock, 測試, 單元, 整合, 端對端.
AsiaOstrich/universal-dev-skills 44
-
requirement-assistant
Guide requirement writing, user story creation, and feature specification.
Use when: writing requirements, user stories, issues, feature planning.
Keywords: requirement, user story, issue, feature, specification, 需求, 功能規劃, 規格.
AsiaOstrich/universal-dev-skills 44
-
release-standards
Semantic versioning and changelog formatting for software releases.
Use when: preparing releases, updating version numbers, writing changelogs.
Keywords: version, release, changelog, semver, major, minor, patch, 版本, 發布, 變更日誌.
AsiaOstrich/universal-dev-skills 44
-
git-workflow-guide
Guide Git branching strategies, branch naming, and merge operations.
Use when: creating branches, merging, pull requests, Git workflow questions.
Keywords: branch, merge, PR, pull request, GitFlow, GitHub Flow, 分支, 合併, 工作流程.
AsiaOstrich/universal-dev-skills 44
-
documentation-guide
Guide documentation structure, README content, and project documentation best practices.
Use when: creating README, documentation, docs folder, project setup.
Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, 文件, 說明文件.
AsiaOstrich/universal-dev-skills 44
-
commit-standards
Format commit messages following conventional commits standard.
Use when: writing commit messages, git commit, reviewing commit history.
Keywords: commit, git, message, conventional, 提交, 訊息, feat, fix, refactor.
AsiaOstrich/universal-dev-skills 44
-
code-review-assistant
Systematic code review checklist and pre-commit quality gates for PRs.
Use when: reviewing pull requests, checking code quality, before committing code.
Keywords: review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入.
AsiaOstrich/universal-dev-skills 44