Komluk Scaffolding Pattern Recognition

Pattern Recognition Skill

Standards for identifying and applying existing codebase patterns to maintain consistency.

When to Apply

• Before writing new code
• When implementing similar features
• Code review for pattern consistency
• Refactoring decisions

Pattern Detection Process

Step 1: Scan Existing Code

Step 2: Extract Patterns

Step 3: Apply Consistently

Example: React + TypeScript conventions (illustrative)

Illustrative — the naming, component, hook, service, and type conventions below are one team's React/TypeScript catalog shown as a concrete example. The reusable skill is the process above (scan → extract → apply existing conventions). Substitute your stack's actual conventions; the value of this skill is matching whatever your codebase already does, not adopting these specific rules.

Naming Conventions

File Naming

Code Naming

Component Patterns

Standard Component Structure

Component Organization by Type

Hook Patterns

Custom Hook Standards

Hook Return Pattern

Service Patterns

API Service Standards

Error Handling Pattern

Type Patterns

Type Location Rules

Type Naming

Anti-Patterns

Code Reuse Protocol

The universal rule: before writing ANY new utility, grep the codebase for an existing one. Map your project's shared modules and reuse them instead of creating parallel helpers, exception hierarchies, or clients.

Example: a backend core/ layout (illustrative)

Illustrative — one team's shared-module layout. Substitute your project's actual shared modules. The reusable rule is "search before you create".

Rules

1. Grep before creating - Search shared modules for an existing function before writing a new one
2. Inherit base exceptions - New domain errors must extend the project's base error type
3. Use shared clients - Reuse the project's shared HTTP/DB client, never spin up a new one ad hoc
4. Follow service pattern - New services should match the structure of existing services

Pattern Compliance Checklist

Before Submitting Code

• Follows existing component structure
• Uses established naming conventions
• Types defined in types/index.ts
• Error handling matches project style
• Uses import type where appropriate
• File location matches pattern
• Hooks follow return pattern
• Services follow error handling pattern

Pattern Documentation

When to Document New Pattern

Source: komluk/scaffolding — distributed by TomeVault.