john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge upstream origin/main (v2.60.0) with fork customizations preserved

Browse Source 
Incorporates 78 upstream commits while preserving all local fork intent:
- Keep deleted: dhh-rails, kieran-rails, dspy-ruby, andrew-kane-gem-writer (FastAPI pivot)
- Merge both: ce-review (zip-agent-validator + design-conformance-reviewer wiring),
  kieran-python-reviewer (upstream pipeline + FastAPI conventions),
  ce-brainstorm/ce-plan/ce-work (upstream improvements + deploy wiring checks),
  todo-create (upstream template refs + assessment block),
  best-practices-researcher (upstream rename + FastAPI refs)
- Accept remote: 142 remote-only files, plugin.json, README.md
- Keep local: 71 local-only files (custom agents, skills, commands, voice)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
John Lamb
2026-03-31 12:27:52 -05:00
parent 1840b0c7cc
commit bf1f79aba4
58 changed files with 6413 additions and 1229 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
plugins/compound-engineering/agents/research/best-practices-researcher.md
View File

@@ -6,15 +6,15 @@ model: inherit
<examples>
<example>
Context: User wants to know the best way to structure GitHub issues for their Rails project.
Context: User wants to know the best way to structure GitHub issues for their FastAPI project.
user: "I need to create some GitHub issues for our project. Can you research best practices for writing good issues?"
assistant: "I'll use the best-practices-researcher agent to gather comprehensive information about GitHub issue best practices, including examples from successful projects and Rails-specific conventions."
assistant: "I'll use the best-practices-researcher agent to gather comprehensive information about GitHub issue best practices, including examples from successful projects and FastAPI-specific conventions."
<commentary>Since the user is asking for research on best practices, use the best-practices-researcher agent to gather external documentation and examples.</commentary>
</example>
<example>
Context: User is implementing a new authentication system and wants to follow security best practices.
user: "We're adding JWT authentication to our Rails API. What are the current best practices?"
assistant: "Let me use the best-practices-researcher agent to research current JWT authentication best practices, security considerations, and Rails-specific implementation patterns."
user: "We're adding JWT authentication to our FastAPI API. What are the current best practices?"
assistant: "Let me use the best-practices-researcher agent to research current JWT authentication best practices, security considerations, and FastAPI-specific implementation patterns."
<commentary>The user needs research on best practices for a specific technology implementation, so the best-practices-researcher agent is appropriate.</commentary>
</example>
</examples>
@@ -39,7 +39,7 @@ Before going online, check if curated knowledge already exists in skills:
2. **Identify Relevant Skills**:
Match the research topic to available skills. Common mappings:
- Rails/Ruby → `dhh-rails-style`, `andrew-kane-gem-writer`, `dspy-ruby`
- Python/FastAPI → `fastapi-style`, `python-package-writer`
- Frontend/Design → `frontend-design`, `swiss-design`
- TypeScript/React → `react-best-practices`
- AI/Agents → `agent-native-architecture`
@@ -97,7 +97,7 @@ Only after checking skills AND verifying API availability, gather additional inf
2. **Organize Discoveries**:
- Organize into clear categories (e.g., "Must Have", "Recommended", "Optional")
- Clearly indicate source: "From skill: dhh-rails-style" vs "From official docs" vs "Community consensus"
- Clearly indicate source: "From skill: fastapi-style" vs "From official docs" vs "Community consensus"
- Provide specific examples from real projects when possible
- Explain the reasoning behind each best practice
- Highlight any technology-specific or domain-specific considerations
@@ -120,7 +120,7 @@ For GitHub issue best practices specifically, you will research:
## Source Attribution
Always cite your sources and indicate the authority level:
- **Skill-based**: "The dhh-rails-style skill recommends..." (highest authority - curated)
- **Skill-based**: "The fastapi-style skill recommends..." (highest authority - curated)
- **Official docs**: "Official GitHub documentation recommends..."
- **Community**: "Many successful projects tend to..."