frontend-dev-guidelines
An AI agent skill from diet103/claude-code-infrastructure-showcase, scored 72 out of 100 by code.
Code score by group
It loses the most points in Description (12), the group that checks whether the description says what the skill does and when to use it.
What the author says it does
Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.
This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.
- Folder
- .agents/skills/frontend-dev-guidelines
- License
- MIT
- GitHub stars
- 10,054
- SKILL.md lines
- 401
- Other files
- 10
Add frontend-dev-guidelines to your agent
npx skills add diet103/claude-code-infrastructure-showcase --skill frontend-dev-guidelines
The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.
Labelled for
More skills from diet103/claude-code-infrastructure-showcase
-
skill-developer
Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hoo…
Verified80B -
error-tracking
Add Sentry v8 error tracking and performance monitoring to your services. Use this skill when adding error handling, creating new controllers, instrumenting cron jobs, or tracking…
78B -
backend-dev-guidelines
Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Ex…
61C -
source-command-verify-setup
Run the infrastructure health check and fix anything that fails
61C
All skills in diet103/claude-code-infrastructure-showcase
Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.