Results for “code-conventions”

Transforms working code into clean, readable, and maintainable code following Robert C. Martin's principles.

Generates a comprehensive developer onboarding guide from a codebase, covering tech stack, setup, architecture, conventions, and troubleshooting.

Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.

Learn Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.

Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md.

Enforces a principal-engineer self-review checklist on every code block before output, covering correctness, performance, security, naming, and testability.

Maps, documents, and onboards into an existing codebase by generating seven structured documents covering stack, structure, architecture, conventions, integrations, testing, and concerns.

Reviews staged and unstaged code changes for security vulnerabilities, code quality issues, and adherence to project conventions, reporting findings by severity.

Analyzes a codebase to create or improve an AGENTS.md file, capturing conventions, constraints, and rationale that are expensive to rediscover.

Comprehensive guide to prevent unmaintainable code, especially from AI generation. Covers code duplication, documentation, error handling, naming conventions, architecture, performance, dependencies, modularity, testing, and technical debt prevention. Essential for code reviews and ensuring long-term code health.

Generates unit tests for code changed in the current branch by comparing against origin/main and following existing test conventions.

Generate a complete, production-ready application from an OpenAPI specification using the active framework's conventions and best practices.

Audits UI code for compliance with the StyleSeed design system, covering design tokens, component conventions, accessibility, mobile UX, and typography.

Establish clear naming conventions for design assets, components, and tokens to make design systems predictable and maintainable.

Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.

COCO: Microsoft COCO: Common Objects in Context

Draft privacy policies, terms of service, disclaimers, and legal notices with GDPR, CCPA, and other regulatory compliance.

Guides coding workflows with planning, implementation, verification, and testing, storing user preferences locally on request.

code-generation-standards

Reviews and authors Cloudflare Workers code against production best practices, covering configuration, request handling, architecture, observability, code patterns, and security.

Analyzes codebases to generate detailed technology stack blueprints with version information, licensing, usage patterns, coding conventions, and architecture diagrams.

Identifies common software anti-patterns in code and suggests refactoring solutions to improve code quality.

Creates, updates, or optimizes an AGENTS.md file for a repository with minimal, high-signal instructions covering non-discoverable coding conventions, tooling quirks, workflow preferences, and project-specific rules that agents cannot infer from reading the codebase.

Guides implementing authentication, authorization, input validation, and OWASP Top 10 prevention with secure code patterns and validation checkpoints.

Universal code quality principles applicable to all languages. Covers Clean Code, SOLID, complexity metrics, and quality standards. USE WHEN: user mentions "clean code", "SOLID", "code smells", "refactoring", "complexity", asks about "cyclomatic complexity", "cognitive complexity", "code review", "maintainability" DO NOT USE FOR: language-specific linting - use ESLint/Biome skills, security - use OWASP skills, testing - use testing skills

Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

Terraform infrastructure-as-code agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Covers module design patterns, state management strategies, provider configuration, security hardening, policy-as-code with Sentinel/OPA, and CI/CD plan/apply workflows. Use when: user wants to design Terraform modules, manage state backends, review Terraform security, implement multi-region deployments, or follow IaC best practices.

Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and platform-specific Kubernetes work for EKS, GKE, AKS, OpenShift, GitOps controllers, or observability stacks.

Use when setting up a new personal project, or when deciding which root file a piece of documentation, configuration, environment variable, or agent instruction belongs in. Covers the standard root files and what each one owns. Does not cover source code layout.

Code Cleanup