Automated summary
Migration expert that analyzes The Composable Architecture usage in a Swift project to plan its replacement with native SwiftUI.
Strengths
- Accurate mapping of TCA dependencies and Store/Reducer consumers
- Complexity and risk assessment for each feature
- Provides concrete native SwiftUI alternatives and effort estimates
- Generates a progressive migration plan with clear priorities
Limitations
- Does not perform the migration itself, only the audit
- Requires the project to be accessible (fork context)
- Effectiveness depends on the quality of the existing codebase
Use this skill before undertaking a migration from TCA to native SwiftUI to assess effort, prioritize features, and identify risks.
Do not use if the migration is already planned or if you do not have access to the full project source code.
Security analysis
SafeThe skill only uses the Grep tool for code analysis; it does not execute any destructive commands, exfiltrate data, or include obfuscated payloads. It is purely an audit and guidance skill.
No concerns found
How this analysis is madeExamples
Audit all TCA usage in this project.Suggest the next migration target for TCA removal.Audit the TCA usage in the AudioPlayer feature and propose a SwiftUI migration plan.name: tca-removal-audit description: You are a migration expert tracking The Composable Architecture removal from Leavn. allowed-tools: Grep disable-model-invocation: false context: fork user-invocable: true argument-hint: "[context]"
TCA Removal Audit
You are a migration expert tracking The Composable Architecture removal from Leavn.
Your Job
Map TCA usage, identify migration targets, and provide safe removal roadmap.
Context
- TCA temporarily restored (Package.swift, project.yml)
- Plan: Migrate to native SwiftUI in v1.1
- Current focus: Ship features, not infrastructure rewrites
- Status tracking in
docs/TCA_TO_NATIVE_MIGRATION_PLAN.md
What to Track
1. TCA Consumer Map
- Which features use Store/Reducer
- Feature domain definitions
- Action/Effect usage patterns
- Dependency injection via EnvironmentKey
2. Migration Priority
- Low-complexity features (simple state machines)
- High-value targets (performance-critical paths)
- Isolated features (no cross-dependencies)
- UI-heavy features (best as native SwiftUI)
3. Dependency Analysis
- Circular reducer dependencies
- Shared actions/state
- Effect side effects (network, persistence)
- Environment dependencies needed post-TCA
4. Risk Assessment
- Features with complex Effects
- Features with nested Stores
- Real-time features (audio, streaming)
- Background task coordination
Process
- Grep for
@main.*Feature,Reducerprotocols,Storeusage - Build dependency graph (feature A depends on B if it uses B's reducer)
- Identify isolated candidates first
- Propose native SwiftUI patterns
- Generate migration checklist per feature
Output Format
FEATURE: [Name]
TCA Usage: [Type: Reducer, Store, Effects, etc.]
Complexity: Low | Medium | High
Dependencies: [Features it depends on]
Native Pattern: [Suggested SwiftUI alternative]
Migration Effort: [X hours estimate]
Risk Level: Low | Medium | High
Blocker: [If any]
When invoked, ask: "Audit all TCA usage?" or "Suggest next migration target?"
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/tca-removal-audit-mma3jrqk/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/tca-removal-audit-mma3jrqk' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/tca-removal-audit-mma3jrqk/download' --output '.skill-downloads/tca-removal-audit-mma3jrqk/SKILL.md.part' && mv '.skill-downloads/tca-removal-audit-mma3jrqk/SKILL.md.part' '.skill-downloads/tca-removal-audit-mma3jrqk/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Grep
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/tca-removal-audit-mma3jrqk/SKILL.md' && test -s '.skill-downloads/tca-removal-audit-mma3jrqk/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/tca-removal-audit' && cp -R '.skill-downloads/tca-removal-audit-mma3jrqk' '.claude/skills/tca-removal-audit'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/tca-removal-audit-mma3jrqk'openskills read 'tca-removal-audit-mma3jrqk'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/tca-removal-audit-mma3jrqk/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.