Skip to content
Back to skills

Spark Component Constants

ASecurity

Create or update a constants file in the Constants folder in Sources of a spark-ios-component-XXX and add or update unit tests.

  • 22 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
testingswifttestingdocumentation

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 29, 2026

npx -y skills add leboncoin/spark-ios --skill spark-component-constants --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Spark Component Constants?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Spark Component Constants
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/leboncoin-spark-component-constants/badge)](https://www.skillsdirectory.com/skills/leboncoin-spark-component-constants)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: spark-component-constants
description: Create or update a constants file in the Constants folder in Sources of a spark-ios-component-XXX and add or update unit tests.
---

# Add Repository Skill

## Overview & Prerequisites

This skill guides you to implement/update an constants in spark component.

## Component Selection

**Parameter Handling:**
- If the skill is invoked with a parameter (e.g., `/spark-component-constants button`):
  - Use the parameter as the component name
  - Verify the folder exists in `Modules/Components/{component-name}/`
  - If found, use that component and skip the selection step

- If no parameter is provided:
  - List all folders in the `Modules/Components/` directory
  - Use AskUserQuestion to let the user select ONE component from the list
  - Format: Display folder names as options (e.g., "button", "card", "checkbox")

**Once the component is selected, all operations must be performed in `Modules/Components/{component-name}/` folder.**

Use the files in the **template** folder as reference to manage the *constants* and the *unit tests*.

## Best pratices
  - can contains sub enum
  - must contains only *static let* or *static func*

## Workflow
  - Add/Update the code.
  - Add/Update the documentation if the constants is public.
  - Implement the unit tests.

### Code Conventions
- [ ] File headers follow pattern: `Created by {firstname.lastname} on DD/MM/YYYY`
- [ ] Copyright line includes current year
- [ ] No empty lines contain whitespace or tabs
- [ ] All class members accessed with `self.`
- [ ] Protocol marked with `// sourcery: AutoMockable`
- [ ] Proper MARK comments in place

### Test Implementation
- [ ] Tests must be written in **Swift Testing** framework
- [ ] Proper imports (SparkComponentXXX, SparkCommon, SparkTheming, @testable, @_spi(SI_SPI) @testable import SparkComponentXXXTesting, Testing, ...)

Files in this skill

  • SKILL.md1.8 KB
  • template/XXXConstants.swift387 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…