style-guide

Enforce Swift coding standards and naming conventions across a codebase.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/vjr2005/Challenge --skill style-guide-vjr2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: style-guide
Source: https://github.com/vjr2005/Challenge/tree/main/.claude/skills/style-guide
Command: npx skills add https://github.com/vjr2005/Challenge --skill style-guide-vjr2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consistent set of rules for writing Swift code, naming types, and configuring SwiftLint to improve readability, maintainability, and team alignment.

Core Features & Use Cases

  • Enforces naming conventions such as Protocol suffixes with Contract and Mock suffixes for mocks
  • Encourages safe coding practices by avoiding force unwraps and minimizing internal visibility
  • Serves as a centralized reference during code reviews, onboarding, and new project setup

Quick Start

Apply the style guide to your Swift project to start enforcing coding standards across the codebase.

Frequently Asked Questions about style-guide

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

FAQPage Schema
How do I enforce Swift naming conventions for protocols and mocks?

Enforce Swift naming conventions by applying rules that require the Contract suffix for protocols and the Mock suffix for mock implementations. This ensures readability and consistency across your codebase during code reviews and CI checks.

Can I use this style guide to configure SwiftLint for safe coding practices?

Yes, you can configure SwiftLint using this style guide to encourage safe coding practices. It specifically helps you avoid force unwraps and minimize internal visibility, improving overall code maintainability and team alignment.

What's the best way to set up Swift coding standards for a new project?

The best way to set up Swift coding standards is applying a centralized style guide during new module development and onboarding. This provides a consistent reference for naming types and configuring SwiftLint to ensure codebase alignment.

Does this Swift style guide require any dependencies to run?

No, this Swift style guide requires no dependencies to run. It operates as a standalone Markdown reference with YAML frontmatter, providing actionable instructions for code reviews and CI checks without external component installations.

Why should I avoid force unwraps in Swift codebase reviews?

Avoid force unwraps in Swift codebase reviews to encourage safe coding practices and prevent runtime crashes. The style guide enforces this constraint during CI checks to minimize risky constructs and improve project maintainability.