enhance: Improve fullstack-developer agent (automated review)#475
Merged
Conversation
- Add AI-native integration section covering LLM APIs, RAG pipelines, streaming responses, multi-provider abstraction, prompt versioning, and eval harnesses - Anchor technology stack to specific versions: Next.js 15+/React 19, Node.js 22+/Hono/tRPC, PostgreSQL/Drizzle ORM, Vercel/Railway/Fly.io - Expand monorepo tooling bullet with Turborepo vs Nx vs pnpm workspaces trade-offs - Add edge computing and server component patterns section with per-route rendering decision framework (RSC/SSR/ISR/static/edge) - Add 4th description example for AI-powered semantic search feature development - Restructure from 8 flat bullet-list sections into focused action-oriented sections (Focus Areas, Approach, Edge Computing, AI-Native Integration, Implementation Workflow) - Remove redundant JSON communication protocol blocks - Tighten Implementation Workflow to 3 concise phases with concrete checklists Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
| Metric | Count |
|---|---|
| Total Components | 755 |
| ✅ Passed | 360 |
| ❌ Failed | 395 |
| 999 |
❌ Failed Components (Top 5)
| Component | Errors | Warnings | Score |
|---|---|---|---|
vercel-edge-function |
3 | 4 | 81/100 |
prompt-engineer |
2 | 0 | 90/100 |
neon-expert |
2 | 2 | 88/100 |
agent-overview |
2 | 1 | 89/100 |
unused-code-cleaner |
2 | 1 | 89/100 |
...and 390 more failed component(s)
📊 View Full Report for detailed error messages and all components
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="cli-tool/components/agents/development-team/fullstack-developer.md">
<violation number="1" location="cli-tool/components/agents/development-team/fullstack-developer.md:3">
P1: Custom agent: **Component Reviewer**
Agent frontmatter is missing the required `model` field.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| @@ -1,234 +1,98 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
P1: Custom agent: Component Reviewer
Agent frontmatter is missing the required model field.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At cli-tool/components/agents/development-team/fullstack-developer.md, line 3:
<comment>Agent frontmatter is missing the required `model` field.</comment>
<file context>
@@ -1,234 +1,98 @@
---
name: fullstack-developer
-description: "Use this agent when you need to build complete features spanning database, API, and frontend layers together as a cohesive unit. Specifically:\\n\\n<example>\\nContext: User wants to build a new user authentication system for a web application that requires database schema, API endpoints, and frontend forms.\\nuser: \"Build a complete user registration feature with PostgreSQL schema, Node.js API endpoints, and React forms including validation and error handling.\"\\nassistant: \"I'll implement this as a full-stack feature. Let me start by analyzing the existing database schema, then design the API contracts, and finally build the React components with proper integration and testing across all layers.\"\\n<commentary>\\nThis is a core fullstack-developer use case: new feature that touches all stack layers requires coordinated development from database to UI. The agent needs context on existing patterns and must ensure type-safety and consistency across all three layers.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Existing backend API needs frontend implementation along with database optimization to support a new real-time dashboard.\\nuser: \"We have the API endpoints ready, but need to build the React dashboard UI and optimize the database queries for real-time data streaming.\"\\nassistant: \"I'll examine your API structure and database schema, then build the React components with WebSocket integration for real-time updates, and optimize the queries for performance. This ensures the frontend, API, and database work together seamlessly.\"\\n<commentary>\\nWhen an incomplete feature chain exists (missing frontend or backend) and requires end-to-end integration testing, use the fullstack developer to coordinate across all layers and ensure optimal data flow, caching, and performance.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Refactoring payment processing system to change from polling to event-driven architecture across all layers.\\nuser: \"Refactor our payment system from polling the database to an event-driven model using WebSockets and message queues, affecting database design, API middleware, and frontend state management.\"\\nassistant: \"I'll redesign the database schema for event sourcing, implement the API event handlers and WebSocket server, rebuild the frontend state management for real-time updates, and ensure proper error recovery across the entire flow.\"\\n<commentary>\\nUse the fullstack developer for complex architectural changes that require synchronized updates across database design, API patterns, and frontend state management. The agent's cross-layer perspective prevents silos and ensures consistent implementation.\\n</commentary>\\n</example>"
+description: "Use this agent when you need to build complete features spanning database, API, and frontend layers together as a cohesive unit. Specifically:\\n\\n<example>\\nContext: User wants to build a new user authentication system for a web application that requires database schema, API endpoints, and frontend forms.\\nuser: \"Build a complete user registration feature with PostgreSQL schema, Node.js API endpoints, and React forms including validation and error handling.\"\\nassistant: \"I'll implement this as a full-stack feature. Let me start by analyzing the existing database schema, then design the API contracts, and finally build the React components with proper integration and testing across all layers.\"\\n<commentary>\\nThis is a core fullstack-developer use case: new feature that touches all stack layers requires coordinated development from database to UI. The agent needs context on existing patterns and must ensure type-safety and consistency across all three layers.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Existing backend API needs frontend implementation along with database optimization to support a new real-time dashboard.\\nuser: \"We have the API endpoints ready, but need to build the React dashboard UI and optimize the database queries for real-time data streaming.\"\\nassistant: \"I'll examine your API structure and database schema, then build the React components with WebSocket integration for real-time updates, and optimize the queries for performance. This ensures the frontend, API, and database work together seamlessly.\"\\n<commentary>\\nWhen an incomplete feature chain exists (missing frontend or backend) and requires end-to-end integration testing, use the fullstack developer to coordinate across all layers and ensure optimal data flow, caching, and performance.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Refactoring payment processing system to change from polling to event-driven architecture across all layers.\\nuser: \"Refactor our payment system from polling the database to an event-driven model using WebSockets and message queues, affecting database design, API middleware, and frontend state management.\"\\nassistant: \"I'll redesign the database schema for event sourcing, implement the API event handlers and WebSocket server, rebuild the frontend state management for real-time updates, and ensure proper error recovery across the entire flow.\"\\n<commentary>\\nUse the fullstack developer for complex architectural changes that require synchronized updates across database design, API patterns, and frontend state management. The agent's cross-layer perspective prevents silos and ensures consistent implementation.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User wants to add a semantic search feature powered by AI to an existing product catalog.\\nuser: \"Add AI-powered semantic search to our product catalog using embeddings and a vector database.\"\\nassistant: \"I'll design the full pipeline: generate and store embeddings in pgvector via a background job, expose a /search API route using the Anthropic SDK for query embedding, stream results to the React frontend with useChat, and add an evaluation harness to measure retrieval quality.\"\\n<commentary>\\nAI feature work spanning embedding ingestion, RAG pipeline, streaming API, and frontend integration requires coordinated fullstack development. The agent ensures data flow, latency, and prompt versioning are handled coherently across all layers.\\n</commentary>\\n</example>"
tools: Read, Write, Edit, Bash, Glob, Grep
---
</file context>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Component Improvement
Changes
useChat/useCompletion, multi-provider abstraction, prompt versioning, evaluation harnesses, and cost control guidelines.Research Summary
The original agent lacked coverage of the modern TypeScript-first fullstack ecosystem (Next.js App Router, Drizzle ORM, tRPC, edge functions) and had no guidance for AI-powered feature development — an increasingly common fullstack concern. The flat bullet-list structure with JSON communication blocks was verbose without being actionable. The research identified these as the highest-impact gaps given current developer workflows.
Validation
name,description,tools)name: fullstack-developermatches filename in kebab-case<commentary>tagscli-tool/components/agents/development-team/Automated review cycle by Component Improvement Loop
Summary by cubic
Enhances the
fullstack-developercomponent with modern stack guidance, edge/server component patterns, and AI-native integration to make its output more actionable. This aligns it withNext.jsApp Router projects and end‑to‑end feature work.Anthropic SDK/Vercel AI SDK, RAG withpgvector/Pinecone, streaming viauseChat/useCompletion, prompt versioning, and eval harnesses.Next.js 15+/React 19,Node.js 22+,PostgreSQL+Drizzle ORM, deploy toVercel/Railway/Fly.io, and monorepo notes forTurborepo/pnpm/Nx; restructures content into focused sections and a 3‑phase workflow, removing noisy JSON blocks.cli-tool/components/). No new components; catalog (docs/components.json) regeneration not required. No new environment variables or secrets.Written for commit 529499e. Summary will update on new commits.