spark-component-use-case
Create or update an use case file in the UseCase folder in Sources of a spark-ios-component-XXX and add or update unit tests.
SKILL.md.claude/skills/spark-component-use-case/SKILL.md
GitHubAdd Repository Skill
Overview & Prerequisites
This skill guides you to implement/update an use case in spark component.
Component Selection
Parameter Handling:
If the skill is invoked with a parameter (e.g.,
/spark-component-use-case 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")
- List all folders in the
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 use case and the unit tests.
Rules
The UseCase file must respect theses rules :
- must be located in Sources/Core/ViewModel and in Tests/UnitTests/ViewModel.
- should contains
procotoland astructimplementation. - should have only one
func executeexcept if I ask to have other func. - should have this comment before the protocol
// sourcery: AutoMockable, AutoMockTest - if the parameter contains a theme, add before the func
// sourcery: theme = "Identical"
Workflow
- Add/Update the code.
- Add/Update the documentation if the use case is public.
- Run swiftlint
$ swiftlint. - Run sourcery
$ sourcery - Implement the unit tests. Read theses folders to get mocks :
- spark-ios-component-XXX/Sources/Testing
- spark-ios-common/Sources/Testing
- spark-ios-theming/Sources/Testing
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, ...)