Full-stack development fundamentals - architecture, patterns, integration
Designs application architecture and defines API contracts for full-stack projects. Triggers when building new systems or integrating frontend/backend components.
/plugin marketplace add pluginagentmarketplace/custom-plugin-fullstack/plugin install fullstack-assistant@pluginagentmarketplace-fullstackThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/config.yamlassets/schema.jsonreferences/GUIDE.mdreferences/PATTERNS.mdscripts/validate.pyAtomic skill for full-stack development fundamentals including architecture design, API patterns, and system integration.
Single Purpose: Design and structure fullstack application architectures
design_architectureDesign the overall application architecture based on requirements.
// Input
{ action: "design_architecture", project_type: "microservices", scale: "growth" }
// Output
{
success: true,
result: {
pattern: "microservices",
services: ["api-gateway", "user-service", "product-service"],
communication: "async-messaging",
database_strategy: "database-per-service"
},
confidence: 0.85,
next_steps: ["Define service boundaries", "Design API contracts"]
}
define_apiDefine API contracts between frontend and backend.
setup_projectSet up project structure and development workflow.
integrate_systemsDesign integration patterns between system components.
function validateParams(params: SkillParams): ValidationResult {
if (!params.action) {
return { valid: false, error: "action is required" };
}
if (!["design_architecture", "define_api", "setup_project", "integrate_systems"].includes(params.action)) {
return { valid: false, error: "Invalid action" };
}
return { valid: true };
}
| Error Code | Description | Recovery |
|---|---|---|
| INVALID_ACTION | Unknown action specified | Check action enum |
| MISSING_CONTEXT | Insufficient project context | Request more details |
| INCOMPATIBLE_STACK | Tech stack conflict | Suggest alternatives |
{
"on_invoke": "log.info('fullstack-basics invoked', { action, project_type })",
"on_success": "log.info('Action completed', { result, duration_ms })",
"on_error": "log.error('Skill failed', { error, params })"
}
import { describe, it, expect } from 'vitest';
import { fullstackBasics } from './fullstack-basics';
describe('fullstack-basics skill', () => {
describe('design_architecture', () => {
it('should return microservices pattern for growth scale', async () => {
const result = await fullstackBasics({
action: 'design_architecture',
project_type: 'microservices',
scale: 'growth'
});
expect(result.success).toBe(true);
expect(result.result.pattern).toBe('microservices');
expect(result.confidence).toBeGreaterThan(0.7);
});
it('should return monolith for startup scale', async () => {
const result = await fullstackBasics({
action: 'design_architecture',
scale: 'startup'
});
expect(result.result.pattern).toBe('monolith');
});
});
describe('validation', () => {
it('should reject invalid action', async () => {
await expect(fullstackBasics({ action: 'invalid' }))
.rejects.toThrow('Invalid action');
});
});
});
| Version | Date | Changes |
|---|---|---|
| 1.0.0 | 2024-01 | Initial release |
| 2.0.0 | 2025-01 | Production-grade upgrade |
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.