Total Skills
9
Skills published by Jose-Luis-Nunez with real stars/downloads and source-aware metadata.
Total Skills
9
Total Stars
0
Total Downloads
0
Comparison chart based on real stars and downloads signals from source data.
create-feature
0
debugging-ui-tests
0
deep-research
0
reviewing-agent-effectiveness
0
reviewing-agent-infrastructure
0
reviewing-code-changes
0
reviewing-test-quality
0
updating-ui-tests
0
Scaffold a new SwiftUI feature module, extend an existing feature, or create a picker sheet with correct project conventions. Use when the user asks to create a new feature, screen, page, module, view, tab, picker, calendar, schedule, dashboard, settings, or add functionality to an existing feature. Also use when asked to build a neue Seite, neues Feature, neuer Screen, new screen, or new page in the FitnessApp iOS project.
Diagnose and fix failing XCUITest UI tests in the FitnessApp project. Investigate selector-not-found errors, scheme/build-config issues, fixture seeding mismatches after SwiftData refactors, and timing flakes. Use when a UI test fails, when a selector is not found, when investigating timeout errors, or when production-code changes broke UITestLaunchStrategy or test-fixture seeding.
Conduct systematic deep research on technical topics with source verification, triangulation, and citation-backed reports. Use when the user asks for deep research, comprehensive analysis, technology comparison, trend analysis, state of the art review, or architecture evaluation. Not for simple lookups, debugging, or questions answerable with 1-2 searches.
Diagnose which agent enforcement mechanisms (rules, hooks, skills) fired during a task and which did not. Produces a FIRED / NOT FIRED / N/A report per mechanism. Use when the user asks to review what worked, check enforcement, audit the agent system, or evaluate whether rules gripped. For fixing gaps found, hand off to reviewing-agent-infrastructure.
Validate and fix agent infrastructure after changes to .claude/ files. Checks reference integrity, agent-system-overview sync, description accuracy, handoff links, hook alignment, and name consistency. Uses a Verifier subagent to independently confirm findings before writing the stamp. Use after editing rules, skills, hooks, references, or when the user asks to reflect or improve the agent system.
Review Swift/SwiftUI code and validate changes. Checks for architecture violations, hardcoded styling, dead code, missed reuse, AppStyle consistency, layout robustness, MVVM compliance, referential integrity, and anti-patterns. Use when the user asks to review code, audit styling, verify architecture, validate changes, or clean up after refactoring.
Review unit and integration test quality in the FitnessApp project. Use when the user asks to review tests, check test quality, analyze test coverage, assess testability, find test gaps, or improve test structure. Covers Swift Testing (@Test/@Suite) and FitnessTestSupport conventions.
Update, refactor, or modernize existing XCUITest UI tests in the FitnessApp project. Use when the user asks to update, refactor, modernize, or clean up an existing UI test, or when a test is outdated or uses wrong patterns. For tests that fail or have selectors that cannot be found, use `debugging-ui-tests` instead.
Create new XCUITest UI tests for the FitnessApp project. Use when the user asks to create, write, or add a new UI test, test a new feature, add test coverage for a screen, or add accessibility identifiers for testing.