senior-fullstack
tessl i github:alirezarezvani/claude-skills --skill senior-fullstackComprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.
Activation
67%This description provides a solid foundation with explicit 'Use when' guidance and names specific technologies, earning good marks for completeness. However, it suffers from being overly broad in scope, which creates potential conflicts with more specialized skills, and the actions described are somewhat abstract rather than concrete. The trigger terms could be expanded to include more natural user language variations.
Suggestions
Add more natural trigger term variations like 'web app', 'frontend', 'backend', 'API development', 'full-stack', and common file extensions (.tsx, .jsx, .sql)
Make actions more concrete by specifying things like 'scaffold Next.js projects', 'create GraphQL resolvers', 'configure PostgreSQL schemas' instead of generic 'architecture patterns'
Consider narrowing the scope or adding distinguishing context to reduce overlap with potential React-specific, Node-specific, or database-specific skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (fullstack development) and lists technologies (React, Next.js, Node.js, GraphQL, PostgreSQL), but actions like 'project scaffolding', 'code quality analysis', and 'architecture patterns' are somewhat vague rather than concrete specific actions like 'create API endpoints' or 'configure database migrations'. | 2 / 3 |
Completeness | Clearly answers both what (fullstack development with specific technologies, scaffolding, code quality, architecture) and when ('Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good technology keywords (React, Next.js, Node.js, GraphQL, PostgreSQL) that users would mention, but missing common variations and natural phrases like 'web app', 'frontend', 'backend', 'API', 'database', 'full-stack', or file extensions like '.tsx', '.js'. | 2 / 3 |
Distinctiveness Conflict Risk | The broad scope covering 'fullstack development' with multiple technologies could overlap with more specialized skills for React-only, Node.js-only, or database-specific tasks. Terms like 'code quality analysis' and 'architecture patterns' are generic enough to conflict with other skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
7%This skill is a template shell with almost no substantive content. It lists tools and references without explaining what they do, provides generic best practices Claude already knows, and offers no concrete guidance for actually building fullstack applications. The skill promises comprehensive coverage but delivers only vague placeholders.
Suggestions
Replace generic script descriptions with actual examples showing input/output - e.g., 'python scripts/fullstack_scaffolder.py my-app --template=nextjs-prisma' creates a project with specific structure
Add a concrete end-to-end example: scaffold a project, implement a feature (with actual code), run quality checks, deploy - showing real commands and expected outputs
Remove generic best practices sections (Code Quality, Security, Maintainability) that explain concepts Claude already knows - focus on project-specific patterns and gotchas
Provide actual code snippets for common tasks: setting up Prisma schema, creating GraphQL resolvers, configuring Next.js API routes - not just 'see references'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic filler content. Phrases like 'Automated tool for fullstack scaffolder tasks' and 'Expert-level automation' are meaningless padding. Lists generic best practices Claude already knows (validate inputs, write tests, keep it simple). | 1 / 3 |
Actionability | Almost no concrete, executable guidance. Script commands show generic placeholders like '[options]' and '[arguments]' without explaining what they actually do. No real code examples showing how to build anything - just vague references to external files. | 1 / 3 |
Workflow Clarity | No clear workflow for building a fullstack application. Steps like 'Implement Best Practices' and 'Follow the patterns' are not actionable sequences. No validation checkpoints, no feedback loops, no concrete process for going from zero to deployed application. | 1 / 3 |
Progressive Disclosure | References external documentation files appropriately (tech_stack_guide.md, architecture_patterns.md, development_workflows.md), but the main content is so thin and generic that it's unclear what value those references provide. Structure exists but content quality undermines it. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.