clean-code

Enforce strict typing and clean imports in TypeScript and Python code.

Updated May 29, 2025
One-click install
npx skills add https://github.com/crozzbite/DnDApp --skill clean-code-crozzbite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/crozzbite/DnDApp/tree/main/.agent/skills/clean-code
Command: npx skills add https://github.com/crozzbite/DnDApp --skill clean-code-crozzbite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy ensures code produced for SkullRender projects avoids ambiguity and runtime errors by enforcing strict typing, removing unused imports, and upholding CSS hygiene.

Core Features & Use Cases

  • Zero Any policy across TypeScript and Python to guarantee explicit data structures.
  • Import hygiene to eliminate unused imports and reduce bundle size.
  • CSS architecture guidelines to avoid !important and promote CSS variables.
  • Enforcement during EXECUTION and VERIFICATION phases to guarantee compliance.

Quick Start

Enforce strict typing and clean imports in all new commits.

Frequently Asked Questions about clean-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce strict typing and eliminate Any usage in TypeScript and Python?

Strict typing enforcement applies a zero Any policy across TypeScript and Python codebases to guarantee explicit data structures. Deterministic checks during execution and verification phases ensure compliance and prevent runtime ambiguity.

What is the best way to remove unused imports and reduce bundle size in frontend and backend code?

Import hygiene eliminates unused imports across frontend, backend, and shared libraries to reduce bundle size. Guardrails applied during execution and verification phases deterministically catch and remove unused dependencies.

How do I maintain CSS hygiene and avoid !important in shared library architectures?

CSS hygiene is maintained by applying architecture guidelines that avoid !important and promote CSS variables. These deterministic checks run across frontend code during the verification phase to ensure compliance.

Does this static analysis policy work with both frontend and backend shared libraries?

Yes, static analysis checks apply across frontend, backend, and shared libraries. The policy enforces strict typing, clean imports, and CSS hygiene uniformly to prevent runtime issues in both TypeScript and Python environments.

When do I need deterministic checks and guardrails for code quality verification?

Deterministic checks and guardrails are needed during the execution and verification phases of new commits. They satisfy phase requirements by enforcing strict typing, import hygiene, and zero Any usage to prevent runtime errors.