marcelorodrigo

Shared design principles for all technical agents. Load these when you need cross-cutting design standards without loading a full specialist (Architect, Implementer, or Code Reviewer).

Architecture formalizer. Takes a brainstorm brief and produces a formal architecture specification grounded in the project's tech stack and any available skills. Sits after Rubber Duck and before Implementer in the pipeline.

Code review specialist. Validates implementations against architecture specs, project conventions, and any loaded skills. Read-only, never modifies code. Sits at the end of the pipeline after the Implementer.

Builder. Takes an architecture specification and implements it, writing production code, tests, and configuration matching the project's conventions and any available skills. Sits after Architect and before Code Reviewer in the pipeline.

Brainstorming sparring partner. Helps explore vague ideas, challenge assumptions, and widen the solution space before committing to formal decisions. Sits before the Architect in the pipeline. Invoke when you have a vague idea, want to explore trade-offs, or need to think through a problem before formalizing.

Bootstrap skill that teaches how to use the Development Crew skill pipeline. Explains the four specialist skills, when to invoke each one, and how the pipeline flows from brainstorming to code review.

Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.

Write technical content for senior engineering audiences using narrative arcs, hooks, and structured conventions.

Create Pull Requests following best conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review.

Expert Spring Boot 4 testing specialist that selects the best Spring Boot testing techniques for your situation with Junit 6 and AssertJ.

Build Laravel admin panels with Filament v5. Use for creating resources, forms, tables, widgets, and testing admin interfaces with Livewire v4.

Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"