Senior Fullstack
Apply senior fullstack architecture patterns, trade-off notes, and anti-pattern guards while designing and implementing a product with an agent.
Overview
senior-fullstack is an agent skill most often used in Build (also Ship, Operate) that guides architecture patterns, performance, security practices, and anti-patterns for fullstack products.
Install
npx skills add https://github.com/davila7/claude-code-templates --skill senior-fullstackWhat is this skill?
- Pattern catalog with when-to-use scenarios and TypeScript-oriented examples
- Guidelines for code organization, performance, and scaling considerations
- Security best practices: validation, auth, authorization, data protection
- Documented anti-patterns to avoid alongside recommended tools
- Advanced async/example implementations for senior-level techniques
Adoption & trust: 793 installs on skills.sh; 27.8k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent writes features quickly but without senior-level structure, explicit trade-offs, or guardrails against common fullstack mistakes.
Who is it for?
Solo builders shipping SaaS or APIs who want agent answers aligned with senior fullstack architecture reference material.
Skip if: Beginners seeking step-by-step framework tutorials or teams that already enforce a fixed internal architecture RFC process without agent assistance.
When should I use this skill?
User needs senior fullstack architecture guidance, pattern trade-offs, performance scaling notes, or anti-pattern review during agent-led development.
What do I get? / Deliverables
Implementation discussions follow documented patterns, typed examples, and anti-pattern checks across organization, performance, and security.
- Architecture recommendations aligned to documented patterns
- Trade-off and anti-pattern notes in plans or reviews
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Architecture and pattern choice are decided early in build and revisited across implementation and hardening. Packaged as a reference guide for organization, performance, and security patterns—PM/architecture shelf before deep single-layer coding.
Where it fits
Choose module boundaries and async data-access patterns before implementing core API routes.
Align component organization with shared patterns instead of one-off page structures.
Apply input validation, auth, and data-protection checklists while hardening a feature branch.
Discuss scaling techniques and bottleneck monitoring using the performance considerations section.
How it compares
Pattern-and-anti-pattern reference skill, not a scaffolding CLI or automated code review bot.
Common Questions / FAQ
Who is senior-fullstack for?
Indie and small-team builders using coding agents who want architecture, performance, and security framing at senior fullstack depth.
When should I use senior-fullstack?
In build when structuring modules and APIs; in ship when applying security and quality guidelines; in operate when discussing scaling and monitoring approaches.
Is senior-fullstack safe to install?
It is documentation-style guidance; review the Security Audits panel on this Prism page and validate any generated code before production deploy.
SKILL.md
READMESKILL.md - Senior Fullstack
# Architecture Patterns ## Overview This reference guide provides comprehensive information for senior fullstack. ## Patterns and Practices ### Pattern 1: Best Practice Implementation **Description:** Detailed explanation of the pattern. **When to Use:** - Scenario 1 - Scenario 2 - Scenario 3 **Implementation:** ```typescript // Example code implementation export class Example { // Implementation details } ``` **Benefits:** - Benefit 1 - Benefit 2 - Benefit 3 **Trade-offs:** - Consider 1 - Consider 2 - Consider 3 ### Pattern 2: Advanced Technique **Description:** Another important pattern for senior fullstack. **Implementation:** ```typescript // Advanced example async function advancedExample() { // Code here } ``` ## Guidelines ### Code Organization - Clear structure - Logical separation - Consistent naming - Proper documentation ### Performance Considerations - Optimization strategies - Bottleneck identification - Monitoring approaches - Scaling techniques ### Security Best Practices - Input validation - Authentication - Authorization - Data protection ## Common Patterns ### Pattern A Implementation details and examples. ### Pattern B Implementation details and examples. ### Pattern C Implementation details and examples. ## Anti-Patterns to Avoid ### Anti-Pattern 1 What not to do and why. ### Anti-Pattern 2 What not to do and why. ## Tools and Resources ### Recommended Tools - Tool 1: Purpose - Tool 2: Purpose - Tool 3: Purpose ### Further Reading - Resource 1 - Resource 2 - Resource 3 ## Conclusion Key takeaways for using this reference guide effectively. # Development Workflows ## Overview This reference guide provides comprehensive information for senior fullstack. ## Patterns and Practices ### Pattern 1: Best Practice Implementation **Description:** Detailed explanation of the pattern. **When to Use:** - Scenario 1 - Scenario 2 - Scenario 3 **Implementation:** ```typescript // Example code implementation export class Example { // Implementation details } ``` **Benefits:** - Benefit 1 - Benefit 2 - Benefit 3 **Trade-offs:** - Consider 1 - Consider 2 - Consider 3 ### Pattern 2: Advanced Technique **Description:** Another important pattern for senior fullstack. **Implementation:** ```typescript // Advanced example async function advancedExample() { // Code here } ``` ## Guidelines ### Code Organization - Clear structure - Logical separation - Consistent naming - Proper documentation ### Performance Considerations - Optimization strategies - Bottleneck identification - Monitoring approaches - Scaling techniques ### Security Best Practices - Input validation - Authentication - Authorization - Data protection ## Common Patterns ### Pattern A Implementation details and examples. ### Pattern B Implementation details and examples. ### Pattern C Implementation details and examples. ## Anti-Patterns to Avoid ### Anti-Pattern 1 What not to do and why. ### Anti-Pattern 2 What not to do and why. ## Tools and Resources ### Recommended Tools - Tool 1: Purpose - Tool 2: Purpose - Tool 3: Purpose ### Further Reading - Resource 1 - Resource 2 - Resource 3 ## Conclusion Key takeaways for using this reference guide effectively. # Tech Stack Guide ## Overview This reference guide provides comprehensive information for senior fullstack. ## Patterns and Practices ### Pattern 1: Best Practice Implementation **Description:** Detailed explanation of the pattern. **When to Use:** - Scenario 1 - Scenario 2 - Scenario 3 **Implementation:** ```typescript // Example code implementation export class Example { // Implementation details } ``` **Benefits:** - Benefit 1 - Benefit 2 - Benefit 3 **Trade-offs:** - Consider 1 - Consider 2 - Consider 3 ### Pattern 2: Advanced Technique **Description:** Another important pattern for senior fullstack. **Implementation:** ```typescript // Advanced example async function advancedExample() { // Code here } ``` ## Guidelines ### Cod