Is Test-Driven Development (TDD) required?

Yes, this skill treats TDD as mandatory for unit tests, requiring that tests are written and fail before any implementation code is generated.

How does this skill enforce 3-tier architecture?

The skill validates that files are placed in specific tiers (Presentation, Logic, Data) and ensures that dependency flows only move in one direction, preventing logic leaks into the UI or data layers.

What are the docstring requirements?

Every public API must include a purpose statement, parameters with types, return values, side effects, possible errors, and realistic usage examples.

What is 'Directional Clarity' in naming?

It is a naming convention that uses prepositions like 'to' or 'from' (e.g., transfer_to, receive_from) to make the flow of data or ownership explicit in method names.

Code Quality Standards

Name: Code Quality Standards
Author: AlexanderStephenThompson

byAlexanderStephenThompson

Security & Testing

Enforces non-negotiable standards for 3-tier architecture, Test-Driven Development, and self-documenting code.

About

The Code Quality Skill acts as a rigorous guardian for your codebase, mandating a strict 3-tier architecture (Presentation, Logic, Data) and Test-Driven Development (TDD) as a baseline requirement. It transcends basic linting by enforcing directional clarity in naming conventions and requiring exhaustive, living docstrings for all public APIs. This skill is ideal for engineering teams looking to eliminate architectural drift, ensure robust test coverage, and maintain a highly readable, professional repository through automated structural validation and best-practice enforcement.

Key Features

0 GitHub stars
Strict 3-tier architecture enforcement (Presentation, Logic, Data)
Comprehensive docstring requirements including usage examples
Mandatory Test-Driven Development (TDD) workflow integration
Directional naming conventions for unambiguous data flow
Automated validation of directory structures and dependency flows

Use Cases

Enforcing rigorous TDD practices to ensure high-quality, bug-free releases
Refactoring legacy code to align with modern clean code and naming standards
Bootstrapping a new project with a scalable and modular folder structure

About

Key Features

0 GitHub stars
Strict 3-tier architecture enforcement (Presentation, Logic, Data)
Comprehensive docstring requirements including usage examples
Mandatory Test-Driven Development (TDD) workflow integration
Directional naming conventions for unambiguous data flow
Automated validation of directory structures and dependency flows

Use Cases

Enforcing rigorous TDD practices to ensure high-quality, bug-free releases
Refactoring legacy code to align with modern clean code and naming standards
Bootstrapping a new project with a scalable and modular folder structure