code-quality-standards
Code quality standards including SOLID principles, design patterns, code smells, refactoring techniques, naming conventions, and technical debt management. Use when reviewing code, refactoring, ensuring quality, or detecting code smells.
What this skill does
# Code Quality Standards
This skill provides comprehensive guidance for writing clean, maintainable, and high-quality code.
## SOLID Principles
### S - Single Responsibility Principle
**Definition**: A class should have only one reason to change.
```typescript
// ❌ BAD - Multiple responsibilities
class UserManager {
createUser(data: UserData) {
// Validation logic
if (!data.email.includes('@')) throw new Error('Invalid email');
// Database logic
const user = database.insert('users', data);
// Email logic
emailService.send(data.email, 'Welcome!');
// Logging logic
logger.info(`User created: ${data.email}`);
return user;
}
}
// ✅ GOOD - Single responsibility per class
class UserValidator {
validate(data: UserData): void {
if (!data.email.includes('@')) {
throw new Error('Invalid email');
}
}
}
class UserRepository {
create(data: UserData): User {
return database.insert('users', data);
}
}
class UserNotificationService {
sendWelcomeEmail(email: string): void {
emailService.send(email, 'Welcome!');
}
}
class UserService {
constructor(
private validator: UserValidator,
private repository: UserRepository,
private notificationService: UserNotificationService,
private logger: Logger
) {}
async createUser(data: UserData): Promise<User> {
this.validator.validate(data);
const user = await this.repository.create(data);
await this.notificationService.sendWelcomeEmail(user.email);
this.logger.info(`User created: ${user.email}`);
return user;
}
}
```
### O - Open/Closed Principle
**Definition**: Classes should be open for extension but closed for modification.
```typescript
// ❌ BAD - Must modify class to add new payment methods
class PaymentProcessor {
process(type: string, amount: number) {
if (type === 'credit_card') {
// Process credit card
} else if (type === 'paypal') {
// Process PayPal
} else if (type === 'bitcoin') {
// Process Bitcoin
}
}
}
// ✅ GOOD - Can extend without modifying
interface PaymentMethod {
process(amount: number): Promise<PaymentResult>;
}
class CreditCardPayment implements PaymentMethod {
async process(amount: number): Promise<PaymentResult> {
// Process credit card
return { success: true };
}
}
class PayPalPayment implements PaymentMethod {
async process(amount: number): Promise<PaymentResult> {
// Process PayPal
return { success: true };
}
}
class PaymentProcessor {
async process(method: PaymentMethod, amount: number): Promise<PaymentResult> {
return await method.process(amount);
}
}
// Add new payment method without modifying existing code
class BitcoinPayment implements PaymentMethod {
async process(amount: number): Promise<PaymentResult> {
// Process Bitcoin
return { success: true };
}
}
```
### L - Liskov Substitution Principle
**Definition**: Subtypes must be substitutable for their base types.
```typescript
// ❌ BAD - Violates LSP
class Rectangle {
constructor(protected width: number, protected height: number) {}
setWidth(width: number) {
this.width = width;
}
setHeight(height: number) {
this.height = height;
}
getArea(): number {
return this.width * this.height;
}
}
class Square extends Rectangle {
setWidth(width: number) {
this.width = width;
this.height = width; // Violates expectation
}
setHeight(height: number) {
this.width = height; // Violates expectation
this.height = height;
}
}
// ✅ GOOD - Separate abstractions
interface Shape {
getArea(): number;
}
class Rectangle implements Shape {
constructor(private width: number, private height: number) {}
getArea(): number {
return this.width * this.height;
}
}
class Square implements Shape {
constructor(private side: number) {}
getArea(): number {
return this.side * this.side;
}
}
```
### I - Interface Segregation Principle
**Definition**: Clients shouldn't be forced to depend on interfaces they don't use.
```typescript
// ❌ BAD - Fat interface
interface Worker {
work(): void;
eat(): void;
sleep(): void;
getPaid(): void;
}
class HumanWorker implements Worker {
work() { /* ... */ }
eat() { /* ... */ }
sleep() { /* ... */ }
getPaid() { /* ... */ }
}
class RobotWorker implements Worker {
work() { /* ... */ }
eat() { /* Not applicable */ }
sleep() { /* Not applicable */ }
getPaid() { /* Not applicable */ }
}
// ✅ GOOD - Segregated interfaces
interface Workable {
work(): void;
}
interface Eatable {
eat(): void;
}
interface Sleepable {
sleep(): void;
}
interface Payable {
getPaid(): void;
}
class HumanWorker implements Workable, Eatable, Sleepable, Payable {
work() { /* ... */ }
eat() { /* ... */ }
sleep() { /* ... */ }
getPaid() { /* ... */ }
}
class RobotWorker implements Workable {
work() { /* ... */ }
}
```
### D - Dependency Inversion Principle
**Definition**: Depend on abstractions, not concretions.
```typescript
// ❌ BAD - Depends on concrete implementation
class UserService {
private database = new MySQLDatabase(); // Tight coupling
async getUser(id: string) {
return this.database.query(`SELECT * FROM users WHERE id = ${id}`);
}
}
// ✅ GOOD - Depends on abstraction
interface Database {
query(sql: string): Promise<any>;
}
class MySQLDatabase implements Database {
async query(sql: string): Promise<any> {
// MySQL implementation
}
}
class PostgreSQLDatabase implements Database {
async query(sql: string): Promise<any> {
// PostgreSQL implementation
}
}
class UserService {
constructor(private database: Database) {} // Dependency injection
async getUser(id: string) {
return this.database.query(`SELECT * FROM users WHERE id = ${id}`);
}
}
// Can easily swap database implementations
const userService = new UserService(new PostgreSQLDatabase());
```
## DRY (Don't Repeat Yourself)
### Identifying Duplication
```typescript
// ❌ BAD - Repeated validation logic
function createUser(data: UserData) {
if (!data.email || !data.email.includes('@')) {
throw new Error('Invalid email');
}
if (!data.password || data.password.length < 8) {
throw new Error('Password too short');
}
// Create user
}
function updateUser(id: string, data: UserData) {
if (!data.email || !data.email.includes('@')) {
throw new Error('Invalid email');
}
if (!data.password || data.password.length < 8) {
throw new Error('Password too short');
}
// Update user
}
// ✅ GOOD - Extract common logic
function validateUserData(data: UserData): void {
if (!data.email || !data.email.includes('@')) {
throw new Error('Invalid email');
}
if (!data.password || data.password.length < 8) {
throw new Error('Password too short');
}
}
function createUser(data: UserData) {
validateUserData(data);
// Create user
}
function updateUser(id: string, data: UserData) {
validateUserData(data);
// Update user
}
```
## KISS (Keep It Simple, Stupid)
```typescript
// ❌ BAD - Over-engineered
class NumberProcessor {
private strategy: ProcessingStrategy;
constructor(strategy: ProcessingStrategy) {
this.strategy = strategy;
}
process(numbers: number[]): number[] {
return this.strategy.execute(numbers);
}
}
interface ProcessingStrategy {
execute(numbers: number[]): number[];
}
class MultiplyByTwoStrategy implements ProcessingStrategy {
execute(numbers: number[]): number[] {
return numbers.map(n => n * 2);
}
}
// ✅ GOOD - Simple and clear
function multiplyByTwo(numbers: number[]): number[] {
return numbers.map(n => n * 2);
}
```
## YAGNI (You Aren't Gonna Need It)
```typescript
// ❌ BAD - Building features you might need
class User {
id: string;
email: string;
name: string;
// Future features that aren't needed yet
preferences?: UserPreferences;
badges?: Badge[];
followers?: User[];
following?: User[];
achievements?: Achievement[];
notRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.