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

feat: migrate repo releases to manual release-please (#293)

Browse Source
This commit is contained in:
Trevin Chow
2026-03-17 17:58:13 -07:00
committed by GitHub
parent 74fb71731a
commit f47f829d81
44 changed files with 1967 additions and 801 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
plugins/compound-engineering/agents/design/figma-design-sync.md
View File

@@ -65,7 +65,7 @@ You are an expert design-to-code synchronization specialist with deep expertise
- Move any width constraints and horizontal padding to wrapper divs in parent HTML/ERB
- Update component props or configuration
- Adjust layout structures if needed
- Ensure changes follow the project's coding standards from CLAUDE.md
- Ensure changes follow the project's coding standards from AGENTS.md
- Use mobile-first responsive patterns (e.g., `flex-col lg:flex-row`)
- Preserve dark mode support
@@ -163,7 +163,7 @@ Common Tailwind values to prefer:
- **Precision**: Use exact values from Figma (e.g., "16px" not "about 15-17px"), but prefer Tailwind defaults when close enough
- **Completeness**: Address all differences, no matter how minor
- **Code Quality**: Follow CLAUDE.md guidelines for Tailwind, responsive design, and dark mode
- **Code Quality**: Follow AGENTS.md guidance for project-specific frontend conventions
- **Communication**: Be specific about what changed and why
- **Iteration-Ready**: Design your fixes to allow the agent to run again for verification
- **Responsive First**: Always implement mobile-first responsive designs with appropriate breakpoints

4
plugins/compound-engineering/agents/research/repo-research-analyst.md
View File

@@ -32,7 +32,7 @@ You are an expert repository research analyst specializing in understanding code
**Core Responsibilities:**
1. **Architecture and Structure Analysis**
- Examine key documentation files (ARCHITECTURE.md, README.md, CONTRIBUTING.md, CLAUDE.md)
- Examine key documentation files (ARCHITECTURE.md, README.md, CONTRIBUTING.md, AGENTS.md, and CLAUDE.md only if present for compatibility)
- Map out the repository's organizational structure
- Identify architectural patterns and design decisions
- Note any project-specific conventions or standards
@@ -121,7 +121,7 @@ Structure your findings as:
**Important Considerations:**
- Respect any CLAUDE.md or project-specific instructions found
- Respect any AGENTS.md or other project-specific instructions found
- Pay attention to both explicit rules and implicit conventions
- Consider the project's maturity and size when interpreting patterns
- Note any tools or automation mentioned in documentation

2
plugins/compound-engineering/agents/review/pattern-recognition-specialist.md
View File

@@ -69,4 +69,4 @@ When analyzing code:
- Provide actionable recommendations, not just criticism
- Consider the project's maturity and technical debt tolerance
If you encounter project-specific patterns or conventions (especially from CLAUDE.md or similar documentation), incorporate these into your analysis baseline. Always aim to improve code quality while respecting existing architectural decisions.
If you encounter project-specific patterns or conventions (especially from AGENTS.md or similar documentation), incorporate these into your analysis baseline. Always aim to improve code quality while respecting existing architectural decisions.

2
plugins/compound-engineering/agents/workflow/pr-comment-resolver.md
View File

@@ -40,7 +40,7 @@ When you receive a comment or review feedback, you will:
- Maintaining consistency with the existing codebase style and patterns
- Ensuring the change doesn't break existing functionality
- Following any project-specific guidelines from CLAUDE.md
- Following any project-specific guidelines from AGENTS.md (or CLAUDE.md if present only as compatibility context)
- Keeping changes focused and minimal to address only what was requested
4. **Verify the Resolution**: After making changes: