senior-fullstack
Complete toolkit for senior fullstack with modern tools and best practices.
Install
npx skills add https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/senior-fullstack
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install sickn33-agentic-awesome-skills@llmmart
git clone https://github.com/sickn33/agentic-awesome-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole sickn33/agentic-awesome-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Senior Fullstack
Complete toolkit for senior fullstack with modern tools and best practices.
Quick Start
Main Capabilities
This skill provides three core capabilities through automated scripts:
# Script 1: Fullstack Scaffolder
python scripts/fullstack_scaffolder.py [options]
# Script 2: Project Scaffolder
python scripts/project_scaffolder.py [options]
# Script 3: Code Quality Analyzer
python scripts/code_quality_analyzer.py [options]
Core Capabilities
1. Fullstack Scaffolder
Automated tool for fullstack scaffolder tasks.
Features:
- Automated scaffolding
- Best practices built-in
- Configurable templates
- Quality checks
Usage:
python scripts/fullstack_scaffolder.py <project-path> [options]
2. Project Scaffolder
Comprehensive analysis and optimization tool.
Features:
- Deep analysis
- Performance metrics
- Recommendations
- Automated fixes
Usage:
python scripts/project_scaffolder.py <target-path> [--verbose]
3. Code Quality Analyzer
Advanced tooling for specialized tasks.
Features:
- Expert-level automation
- Custom configurations
- Integration ready
- Production-grade output
Usage:
python scripts/code_quality_analyzer.py [arguments] [options]
Reference Documentation
Tech Stack Guide
Comprehensive guide available in references/tech_stack_guide.md:
- Detailed patterns and practices
- Code examples
- Best practices
- Anti-patterns to avoid
- Real-world scenarios
Architecture Patterns
Complete workflow documentation in references/architecture_patterns.md:
- Step-by-step processes
- Optimization strategies
- Tool integrations
- Performance tuning
- Troubleshooting guide
Development Workflows
Technical reference guide in references/development_workflows.md:
- Technology stack details
- Configuration examples
- Integration patterns
- Security considerations
- Scalability guidelines
Tech Stack
Languages: TypeScript, JavaScript, Python, Go, Swift, Kotlin Frontend: React, Next.js, React Native, Flutter Backend: Node.js, Express, GraphQL, REST APIs Database: PostgreSQL, Prisma, NeonDB, Supabase DevOps: Docker, Kubernetes, Terraform, GitHub Actions, CircleCI Cloud: AWS, GCP, Azure
Development Workflow
1. Setup and Configuration
# Install dependencies
npm install
# or
pip install -r requirements.txt
# Configure environment
cp .env.example .env
2. Run Quality Checks
# Use the analyzer script
python scripts/project_scaffolder.py .
# Review recommendations
# Apply fixes
3. Implement Best Practices
Follow the patterns and practices documented in:
references/tech_stack_guide.mdreferences/architecture_patterns.mdreferences/development_workflows.md
Best Practices Summary
Code Quality
- Follow established patterns
- Write comprehensive tests
- Document decisions
- Review regularly
Performance
- Measure before optimizing
- Use appropriate caching
- Optimize critical paths
- Monitor in production
Security
- Validate all inputs
- Use parameterized queries
- Implement proper authentication
- Keep dependencies updated
Maintainability
- Write clear code
- Use consistent naming
- Add helpful comments
- Keep it simple
Common Commands
# Development
npm run dev
npm run build
npm run test
npm run lint
# Analysis
python scripts/project_scaffolder.py .
python scripts/code_quality_analyzer.py --analyze
# Deployment
docker build -t app:latest .
docker-compose up -d
kubectl apply -f k8s/
Troubleshooting
Common Issues
Check the comprehensive troubleshooting section in references/development_workflows.md.
Getting Help
- Review reference documentation
- Check script output messages
- Consult tech stack documentation
- Review error logs
Resources
- Pattern Reference:
references/tech_stack_guide.md - Workflow Guide:
references/architecture_patterns.md - Technical Guide:
references/development_workflows.md - Tool Scripts:
scripts/directory
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Files (agentic-awesome-skills)
-
references
-
architecture_patterns.md 1.6 KB
# 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.md 1.6 KB
# 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.md 1.6 KB
# 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 ### 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.
-
-
scripts
-
code_quality_analyzer.py 3.6 KB
#!/usr/bin/env python3 """ Code Quality Analyzer Automated tool for senior fullstack tasks """ import os import sys import json import argparse from pathlib import Path def safe_user_path(path_value, base_dir="."): """Resolve a CLI path under the current workspace.""" if base_dir != ".": raise ValueError("Custom base directories are not supported for CLI paths") base_path = Path.cwd().resolve() resolved_path = Path(path_value).expanduser().resolve() try: resolved_path.relative_to(base_path) except ValueError as exc: raise ValueError(f"Path escapes allowed directory: {path_value}") from exc return resolved_path from typing import Dict, List, Optional class CodeQualityAnalyzer: """Main class for code quality analyzer functionality""" def __init__(self, target_path: str, verbose: bool = False): self.target_path = safe_user_path(target_path) self.verbose = verbose self.results = {} def run(self) -> Dict: """Execute the main functionality""" print(f"🚀 Running {self.__class__.__name__}...") print(f"📁 Target: {self.target_path}") try: self.validate_target() self.analyze() self.generate_report() print("✅ Completed successfully!") return self.results except Exception as e: print(f"❌ Error: {e}") sys.exit(1) def validate_target(self): """Validate the target path exists and is accessible""" if not self.target_path.exists(): raise ValueError(f"Target path does not exist: {self.target_path}") if self.verbose: print(f"✓ Target validated: {self.target_path}") def analyze(self): """Perform the main analysis or operation""" if self.verbose: print("📊 Analyzing...") # Main logic here self.results['status'] = 'success' self.results['target'] = str(self.target_path) self.results['findings'] = [] # Add analysis results if self.verbose: print(f"✓ Analysis complete: {len(self.results.get('findings', []))} findings") def generate_report(self): """Generate and display the report""" print("\n" + "="*50) print("REPORT") print("="*50) print(f"Target: {self.results.get('target')}") print(f"Status: {self.results.get('status')}") print(f"Findings: {len(self.results.get('findings', []))}") print("="*50 + "\n") def main(): """Main entry point""" parser = argparse.ArgumentParser( description="Code Quality Analyzer" ) parser.add_argument( 'target', help='Target path to analyze or process' ) parser.add_argument( '--verbose', '-v', action='store_true', help='Enable verbose output' ) parser.add_argument( '--json', action='store_true', help='Output results as JSON' ) parser.add_argument( '--output', '-o', help='Output file path' ) args = parser.parse_args() tool = CodeQualityAnalyzer( args.target, verbose=args.verbose ) results = tool.run() if args.json: output = json.dumps(results, indent=2) if args.output: with safe_user_path(args.output).open('w') as f: f.write(output) print(f"Results written to {args.output}") else: print(output) if __name__ == '__main__': main() -
fullstack_scaffolder.py 3.6 KB
#!/usr/bin/env python3 """ Fullstack Scaffolder Automated tool for senior fullstack tasks """ import os import sys import json import argparse from pathlib import Path def safe_user_path(path_value, base_dir="."): """Resolve a CLI path under the current workspace.""" if base_dir != ".": raise ValueError("Custom base directories are not supported for CLI paths") base_path = Path.cwd().resolve() resolved_path = Path(path_value).expanduser().resolve() try: resolved_path.relative_to(base_path) except ValueError as exc: raise ValueError(f"Path escapes allowed directory: {path_value}") from exc return resolved_path from typing import Dict, List, Optional class FullstackScaffolder: """Main class for fullstack scaffolder functionality""" def __init__(self, target_path: str, verbose: bool = False): self.target_path = safe_user_path(target_path) self.verbose = verbose self.results = {} def run(self) -> Dict: """Execute the main functionality""" print(f"🚀 Running {self.__class__.__name__}...") print(f"📁 Target: {self.target_path}") try: self.validate_target() self.analyze() self.generate_report() print("✅ Completed successfully!") return self.results except Exception as e: print(f"❌ Error: {e}") sys.exit(1) def validate_target(self): """Validate the target path exists and is accessible""" if not self.target_path.exists(): raise ValueError(f"Target path does not exist: {self.target_path}") if self.verbose: print(f"✓ Target validated: {self.target_path}") def analyze(self): """Perform the main analysis or operation""" if self.verbose: print("📊 Analyzing...") # Main logic here self.results['status'] = 'success' self.results['target'] = str(self.target_path) self.results['findings'] = [] # Add analysis results if self.verbose: print(f"✓ Analysis complete: {len(self.results.get('findings', []))} findings") def generate_report(self): """Generate and display the report""" print("\n" + "="*50) print("REPORT") print("="*50) print(f"Target: {self.results.get('target')}") print(f"Status: {self.results.get('status')}") print(f"Findings: {len(self.results.get('findings', []))}") print("="*50 + "\n") def main(): """Main entry point""" parser = argparse.ArgumentParser( description="Fullstack Scaffolder" ) parser.add_argument( 'target', help='Target path to analyze or process' ) parser.add_argument( '--verbose', '-v', action='store_true', help='Enable verbose output' ) parser.add_argument( '--json', action='store_true', help='Output results as JSON' ) parser.add_argument( '--output', '-o', help='Output file path' ) args = parser.parse_args() tool = FullstackScaffolder( args.target, verbose=args.verbose ) results = tool.run() if args.json: output = json.dumps(results, indent=2) if args.output: with safe_user_path(args.output).open('w') as f: f.write(output) print(f"Results written to {args.output}") else: print(output) if __name__ == '__main__': main() -
project_scaffolder.py 3.6 KB
#!/usr/bin/env python3 """ Project Scaffolder Automated tool for senior fullstack tasks """ import os import sys import json import argparse from pathlib import Path def safe_user_path(path_value, base_dir="."): """Resolve a CLI path under the current workspace.""" if base_dir != ".": raise ValueError("Custom base directories are not supported for CLI paths") base_path = Path.cwd().resolve() resolved_path = Path(path_value).expanduser().resolve() try: resolved_path.relative_to(base_path) except ValueError as exc: raise ValueError(f"Path escapes allowed directory: {path_value}") from exc return resolved_path from typing import Dict, List, Optional class ProjectScaffolder: """Main class for project scaffolder functionality""" def __init__(self, target_path: str, verbose: bool = False): self.target_path = safe_user_path(target_path) self.verbose = verbose self.results = {} def run(self) -> Dict: """Execute the main functionality""" print(f"🚀 Running {self.__class__.__name__}...") print(f"📁 Target: {self.target_path}") try: self.validate_target() self.analyze() self.generate_report() print("✅ Completed successfully!") return self.results except Exception as e: print(f"❌ Error: {e}") sys.exit(1) def validate_target(self): """Validate the target path exists and is accessible""" if not self.target_path.exists(): raise ValueError(f"Target path does not exist: {self.target_path}") if self.verbose: print(f"✓ Target validated: {self.target_path}") def analyze(self): """Perform the main analysis or operation""" if self.verbose: print("📊 Analyzing...") # Main logic here self.results['status'] = 'success' self.results['target'] = str(self.target_path) self.results['findings'] = [] # Add analysis results if self.verbose: print(f"✓ Analysis complete: {len(self.results.get('findings', []))} findings") def generate_report(self): """Generate and display the report""" print("\n" + "="*50) print("REPORT") print("="*50) print(f"Target: {self.results.get('target')}") print(f"Status: {self.results.get('status')}") print(f"Findings: {len(self.results.get('findings', []))}") print("="*50 + "\n") def main(): """Main entry point""" parser = argparse.ArgumentParser( description="Project Scaffolder" ) parser.add_argument( 'target', help='Target path to analyze or process' ) parser.add_argument( '--verbose', '-v', action='store_true', help='Enable verbose output' ) parser.add_argument( '--json', action='store_true', help='Output results as JSON' ) parser.add_argument( '--output', '-o', help='Output file path' ) args = parser.parse_args() tool = ProjectScaffolder( args.target, verbose=args.verbose ) results = tool.run() if args.json: output = json.dumps(results, indent=2) if args.output: with safe_user_path(args.output).open('w') as f: f.write(output) print(f"Results written to {args.output}") else: print(output) if __name__ == '__main__': main()
-
-
SKILL.md 4.6 KB
--- name: senior-fullstack description: "Complete toolkit for senior fullstack with modern tools and best practices." risk: critical source: community date_added: "2026-02-27" --- # Senior Fullstack Complete toolkit for senior fullstack with modern tools and best practices. ## Quick Start ### Main Capabilities This skill provides three core capabilities through automated scripts: ```bash # Script 1: Fullstack Scaffolder python scripts/fullstack_scaffolder.py [options] # Script 2: Project Scaffolder python scripts/project_scaffolder.py [options] # Script 3: Code Quality Analyzer python scripts/code_quality_analyzer.py [options] ``` ## Core Capabilities ### 1. Fullstack Scaffolder Automated tool for fullstack scaffolder tasks. **Features:** - Automated scaffolding - Best practices built-in - Configurable templates - Quality checks **Usage:** ```bash python scripts/fullstack_scaffolder.py <project-path> [options] ``` ### 2. Project Scaffolder Comprehensive analysis and optimization tool. **Features:** - Deep analysis - Performance metrics - Recommendations - Automated fixes **Usage:** ```bash python scripts/project_scaffolder.py <target-path> [--verbose] ``` ### 3. Code Quality Analyzer Advanced tooling for specialized tasks. **Features:** - Expert-level automation - Custom configurations - Integration ready - Production-grade output **Usage:** ```bash python scripts/code_quality_analyzer.py [arguments] [options] ``` ## Reference Documentation ### Tech Stack Guide Comprehensive guide available in `references/tech_stack_guide.md`: - Detailed patterns and practices - Code examples - Best practices - Anti-patterns to avoid - Real-world scenarios ### Architecture Patterns Complete workflow documentation in `references/architecture_patterns.md`: - Step-by-step processes - Optimization strategies - Tool integrations - Performance tuning - Troubleshooting guide ### Development Workflows Technical reference guide in `references/development_workflows.md`: - Technology stack details - Configuration examples - Integration patterns - Security considerations - Scalability guidelines ## Tech Stack **Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin **Frontend:** React, Next.js, React Native, Flutter **Backend:** Node.js, Express, GraphQL, REST APIs **Database:** PostgreSQL, Prisma, NeonDB, Supabase **DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI **Cloud:** AWS, GCP, Azure ## Development Workflow ### 1. Setup and Configuration ```bash # Install dependencies npm install # or pip install -r requirements.txt # Configure environment cp .env.example .env ``` ### 2. Run Quality Checks ```bash # Use the analyzer script python scripts/project_scaffolder.py . # Review recommendations # Apply fixes ``` ### 3. Implement Best Practices Follow the patterns and practices documented in: - `references/tech_stack_guide.md` - `references/architecture_patterns.md` - `references/development_workflows.md` ## Best Practices Summary ### Code Quality - Follow established patterns - Write comprehensive tests - Document decisions - Review regularly ### Performance - Measure before optimizing - Use appropriate caching - Optimize critical paths - Monitor in production ### Security - Validate all inputs - Use parameterized queries - Implement proper authentication - Keep dependencies updated ### Maintainability - Write clear code - Use consistent naming - Add helpful comments - Keep it simple ## Common Commands ```bash # Development npm run dev npm run build npm run test npm run lint # Analysis python scripts/project_scaffolder.py . python scripts/code_quality_analyzer.py --analyze # Deployment docker build -t app:latest . docker-compose up -d kubectl apply -f k8s/ ``` ## Troubleshooting ### Common Issues Check the comprehensive troubleshooting section in `references/development_workflows.md`. ### Getting Help - Review reference documentation - Check script output messages - Consult tech stack documentation - Review error logs ## Resources - Pattern Reference: `references/tech_stack_guide.md` - Workflow Guide: `references/architecture_patterns.md` - Technical Guide: `references/development_workflows.md` - Tool Scripts: `scripts/` directory ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.