Senior Frontend
Load senior-level frontend patterns, guidelines, and anti-patterns so your agent implements UI code with consistent structure, performance, and security habits.
Overview
Senior Frontend is an agent skill most often used in Build (also Ship review) that supplies senior frontend patterns, performance guidance, security practices, and anti-patterns for agent-driven UI work.
Install
npx skills add https://github.com/davila7/claude-code-templates --skill senior-frontendWhat is this skill?
- Structured patterns with when-to-use scenarios, TypeScript examples, benefits, and trade-offs
- Guidelines for code organization, performance bottlenecks, monitoring, and scaling
- Security section covering input validation, authentication, authorization, and data protection
- Documented anti-patterns to avoid alongside recommended tools and further reading hooks
Adoption & trust: 1.6k installs on skills.sh; 27.8k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your coding agent produces frontend code that works in demos but lacks senior structure, performance awareness, or client-side security discipline.
Who is it for?
Indie developers shipping SaaS or extension UIs who want a standing senior-frontend playbook in Claude Code or Cursor.
Skip if: Complete beginners who need framework installation tutorials only, or backend-only work with no UI surface.
When should I use this skill?
When implementing or reviewing senior-level frontend work and you want pattern-guided TypeScript UI decisions.
What do I get? / Deliverables
The agent applies documented patterns, guidelines, and anti-pattern guardrails so UI changes stay organized, performant, and safer by default.
- Code and refactors aligned to documented frontend patterns
- Review feedback mapped to guidelines, common patterns, and anti-patterns
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Frontend implementation is the canonical Build shelf even though the reference informs review and hardening in Ship. Content is explicitly senior frontend engineering—components, performance, and security on the client—so frontend subphase fits best.
Where it fits
You scaffold a dashboard and invoke the skill so new components follow the documented organization and pattern templates.
Before merge, you ask the agent to check the PR against listed anti-patterns and security guidelines.
You extend marketing pages in the same codebase and want performance considerations applied to content-heavy routes.
How it compares
A narrative best-practices skill—not a component library generator or a Lighthouse automation MCP.
Common Questions / FAQ
Who is senior-frontend for?
Solo builders and tech leads who already write TypeScript frontends and want their agent to follow senior patterns for organization, performance, and security.
When should I use senior-frontend?
During Build frontend when implementing or refactoring UI; during Ship review when auditing structure and client security; when growth work touches lifecycle-heavy SPA surfaces.
Is senior-frontend safe to install?
It is primarily reference prose and examples—still review the Security Audits panel on this page and the repo SKILL.md before enabling broader agent permissions.
SKILL.md
READMESKILL.md - Senior Frontend
# Frontend Best Practices ## Overview This reference guide provides comprehensive information for senior frontend. ## 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 frontend. **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. # Nextjs Optimization Guide ## Overview This reference guide provides comprehensive information for senior frontend. ## 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 frontend. **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. # React Patterns ## Overview This reference guide provides comprehensive information for senior frontend. ## 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 frontend. **Implementation:** ```typescript // Advanced example async function advancedExample() { // Code here } ``` ## Guidelines ### Code