skills/ariegoldkin/quality-reviewer/SKILL.md
Automatically reviews DevPrep AI code for quality standards including ESLint compliance, TypeScript strict mode, 180-line file limits, complexity under 15, proper naming conventions, import patterns, and architectural compliance with the 6-folder structure
npx skillsauth add aiskillstore/marketplace quality-reviewerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automatically enforces DevPrep AI code quality standards during development.
Auto-triggered by keywords:
any typesI prefix (e.g., IButtonProps)import type { ... }IUserProfile, IButtonPropsQuestionType, DifficultycamelCasePascalCaseUse path aliases:
@shared/ui/button // ✅ Correct
@modules/practice/* // ✅ Correct
@lib/trpc/client // ✅ Correct
@store/hooks // ✅ Correct
../../../shared/ui/* // ❌ Wrong
app/ Routes only
modules/ Features (practice, assessment, results, profile, questions, home)
shared/ Cross-cutting (ui, components, hooks, utils)
lib/ Integrations (trpc, claude)
store/ Zustand state
styles/ Design system
# Target specific issues
./.claude/skills/quality-reviewer/scripts/check-file-size.sh
./.claude/skills/quality-reviewer/scripts/check-complexity.sh
./.claude/skills/quality-reviewer/scripts/check-imports.sh
./.claude/skills/quality-reviewer/scripts/check-architecture.sh
./.claude/skills/quality-reviewer/scripts/check-naming.sh
# Run all 7 checks at once
./.claude/skills/quality-reviewer/scripts/full-review.sh
Checks: file size → complexity → imports → architecture → naming → ESLint → TypeScript
interface ButtonProps { } // ❌
interface IButtonProps { } // ✅
import { ReactElement } from 'react'; // ❌
import type { ReactElement } from 'react'; // ✅
import { Button } from '../../../shared/ui/button'; // ❌
import { Button } from '@shared/ui/button'; // ✅
const data: any = fetchData(); // ❌
const data: IUserData = fetchData(); // ✅
Split into:
Component.tsx - UI onlyhooks.ts - Logictypes.ts - Typesutils.ts - HelpersSee: examples/refactor-after/
// ❌ Before: Nested ifs (complexity 18)
if (user.role === 'admin') {
if (user.isActive) {
if (user.permissions.includes('write')) {
// do something
}
}
}
// ✅ After: Early returns (complexity 3)
if (!user.role === 'admin') return;
if (!user.isActive) return;
if (!user.permissions.includes('write')) return;
// do something
Quick fixes:
const MAP = { key: 'value' };SKILL.md is self-sufficient for:
Load additional docs only when needed:
| Need | Load | Lines |
|------|------|-------|
| File splitting strategies | examples/refactor-after/ | ~256 |
| Complexity reduction tactics | docs/standards.md (lines 75-163) | ~88 |
| Architecture patterns | docs/standards.md (lines 224-280) | ~56 |
| Type safety patterns | docs/standards.md (lines 283-348) | ~65 |
| Deep-dive on any violation | docs/standards.md (full file) | ~370 |
Code examples:
examples/good-code.tsxexamples/bad-code.tsxexamples/refactor-after/Full project standards: Docs/code-standards.md
Version: 1.1.0 (Optimized) | Updated: October 2025 Optimization: 31% smaller, 52% fewer tokens for typical usage
Note: Example files use // @ts-nocheck and /* eslint-disable */ directives to suppress IDE warnings, since they demonstrate intentional violations or reference non-existent paths for educational purposes. They are also excluded from build-time TypeScript compilation via frontend/tsconfig.json.
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.