Enforce language-agnostic coding standards for naming, structure, and reuse.
npx skills add https://github.com/tale-project/tale --skill clean-code-tale-project
Please help me install this Agent Skill. Skill: clean-code Source: https://github.com/tale-project/tale/tree/main/.claude/skills/clean-code Command: npx skills add https://github.com/tale-project/tale --skill clean-code-tale-project
The language-agnostic baseline for every line in Tale — intention-revealing names, small single-purpose functions, guard clauses, comments that explain why, fail-fast errors, immutability, and the reuse-and-centralization procedure (search packages/ui → shared app/lib → feature before creating anything). Read before writing or changing code in any language — naming, function shape, error handling, comments, and whether to reuse instead of write new. Syntax lives in typescript / react / ui-components / convex.
Adopt the clean-code baseline before creating any component, hook, util, type, validator, or constant.
High-intent search queries and answers about installing and using this skill.
Clean code baseline rules require small, single-purpose functions with intention-revealing names, guard clauses, and immutability to ensure code is easy to test, understand, and reuse across languages.
To enforce code quality and naming conventions across multiple languages, apply a centralized, language-agnostic baseline that standardizes identifiers, structure, and reuse practices before creating components or utils.
Use guard clauses and fail-fast errors to improve code structure by validating conditions early and reducing surprises, which keeps functions small, single-purpose, and easy to read.
Yes, the clean code baseline works with TypeScript and React components by providing a language-agnostic foundation that guides naming, hook structure, and reuse alongside specific per-language syntax guides.
The best way to centralize and reuse code is to search existing packages, shared libraries, and feature directories to extend current primitives before writing new components, hooks, or constants.
You should not use immutable patterns if your architecture explicitly requires in-place mutation for performance, as the clean code baseline enforces immutability by default to reduce side effects and unexpected state changes.
tractorjuiceSynthesize project architecture artifacts into a centralized TOGAF-aligned repository.
buddypiaValidate feature integration with export, route, data flow, and lint checks.
gustavofsantosTranslate natural language queries into ast-grep YAML rules for structural code search.
botPhUDetect code smells and apply refactoring techniques without changing external behavior.
