Enforce pragmatic coding standards for AI software projects.
npx skills add https://github.com/gelsonsimoes/wms-verticalparts --skill clean-code-gelsonsimoes
Please help me install this Agent Skill. Skill: clean-code Source: https://github.com/gelsonsimoes/wms-verticalparts/tree/main/.agent/skills/clean-code Command: npx skills add https://github.com/gelsonsimoes/wms-verticalparts --skill clean-code-gelsonsimoes
Pragmatic coding standards that keep AI code concise, direct, and free of unnecessary complexity.
Apply these rules to your next AI coding task to produce clean, readable, and robust code.
High-intent search queries and answers about installing and using this skill.
Clean code standards for AI software projects enforce pragmatic rules like SRP, DRY, and KISS to keep functions focused, reduce unnecessary complexity, and ensure robust, readable code generation.
Apply coding standards to AI-generated code reviews by checking for clear naming, small functions, early returns, and guardrails, ensuring the code aligns with YAGNI and Boy Scout principles for maintainability.
The best way to reduce cognitive load in software engineering is implementing clean code principles, utilizing early returns and small functions focused on a single responsibility to minimize bugs and complexity.
Yes, this clean code approach works for team onboarding and mentoring by providing consistent coding guidelines that align developers on style, quality, and pragmatic software engineering best practices.
You should avoid overengineering in AI development tasks by applying the YAGNI principle, ensuring you only build necessary features to keep code concise, direct, and free of unnecessary complexity.
You need coding guardrails for AI applications when generating code that requires strict adherence to software engineering standards, preventing bugs and reducing cognitive load through structured, focused functions.
mcj-coderAutomate project scaffolding with quality gates, CI/CD, and repository structure.
ajsai47Analyze git diffs for SQL injection, race conditions, and shell injection risks.
jnPiyushDocuments software design principles (SOC, TOC, SOC, COC, LOC, DOC, LOC, VOC, YOCNI, etc. wait, let's be accurate: SRP, OCP, LSP, ISP, DIP, DRY, KISS, YAGNI and common design patterns for C# development workflows and code reviews.
DevQwietArchitects digital interfaces enforcing metric-based design rules for variance, motion intensity and density, plus UI concepts and animations.
