Loading...
Loading...
Found 295 Skills
Manage App Store app preview video sets and uploads using the `asc` CLI tool. Use this skill when: (1) Listing preview sets for a localization: "asc app-preview-sets list --localization-id ID" (2) Creating a preview set: "asc app-preview-sets create --localization-id ID --preview-type IPHONE_67" (3) Listing previews in a set: "asc app-previews list --set-id ID" (4) Uploading a preview video: "asc app-previews upload --set-id ID --file preview.mp4" (5) User says "upload app preview", "add preview video", "create preview set", or "list previews"
Manage App Store review contact info and demo account settings using the `asc` CLI tool. Use this skill when: (1) Getting current review info: "asc version-review-detail get --version-id ID" (2) Setting review contact info before submission: "asc version-review-detail update --version-id ID ..." (3) Configuring demo account credentials for App Review team (4) User asks "set review info", "add review contact", "configure demo account", "fix reviewContactCheck" (5) Diagnosing a failed reviewContactCheck from asc versions check-readiness
Manage App Clips and App Clip default experiences using the `asc` CLI tool. Use this skill when: (1) Listing App Clips for an app: "asc app-clips list --app-id ID" (2) Listing default experiences for an App Clip: "asc app-clip-experiences list --app-clip-id ID" (3) Creating a default experience: "asc app-clip-experiences create --app-clip-id ID [--action OPEN|VIEW|PLAY]" (4) Deleting a default experience: "asc app-clip-experiences delete --experience-id ID" (5) Listing experience localizations: "asc app-clip-experience-localizations list --experience-id ID" (6) Creating an experience localization: "asc app-clip-experience-localizations create --experience-id ID --locale CODE [--subtitle TEXT]" (7) Deleting an experience localization: "asc app-clip-experience-localizations delete --localization-id ID" Trigger phrases: "app clip", "app clips", "clip experience", "clip localization", "default experience", "OPEN action", "VIEW action", "PLAY action", "App Clip card", "App Clip subtitle"
Manage App Store Connect team members and user invitations using the `asc` CLI tool. Use this skill when: (1) Listing team members with their roles (`asc users list`) (2) Filtering members by role (`asc users list --role DEVELOPER`) (3) Updating or replacing a member's roles (asc users update --user-id ID --role ADMIN) (4) Revoking or removing access for a departing employee (asc users remove --user-id ID) (5) Listing pending invitations (asc user-invitations list) (6) Inviting a new team member by email (asc user-invitations invite) (7) Cancelling a pending invitation (asc user-invitations cancel) (8) User says "revoke access", "remove team member", "offboard user", "invite developer", "add someone to App Store Connect", "manage team roles", "who has admin access", "grant access", "onboard", or any team/user management task in App Store Connect
iOS/macOS app localization management for Tuist-based projects with .strings files. Use when: (1) Adding new translation keys to modules, (2) Validating .strings files for missing/duplicate keys, (3) Syncing translations across languages, (4) AI-powered translation from English to other locales, (5) Checking placeholder consistency (%@, %d), (6) Generating localization reports, (7) Updating Swift code to use localized strings instead of hardcoded text.
Upload IPA/PKG builds to App Store Connect and manage the full build distribution workflow. Use this skill when: (1) Uploading a build: "asc builds upload --app-id ... --file MyApp.ipa ..." (2) Checking or listing build upload records: "asc builds uploads list/get/delete" (3) Linking a build to an App Store version before submission: "asc versions set-build" (4) Adding or removing a beta group from a build for TestFlight distribution (5) Setting TestFlight "What's New" notes: "asc builds update-beta-notes" (6) User says "upload my build", "distribute to TestFlight", "set what's new", "link build to version"
Initialise a project's App Store Connect context using the `asc init` command. Use this skill when: (1) Saving app context to a project directory: "asc init", "pin my app ID", "set up project context" (2) Auto-detecting the app from an Xcode project: user says "run asc init in my project folder" (3) Searching by app name: "asc init --name 'My App'" (4) Explaining what .asc/project.json is used for (5) Reading saved project context to avoid running asc apps list every session
Manage App Store Connect authentication using the `asc` CLI tool. Use this skill when: (1) Logging in with an API key: "asc auth login", "save my credentials", "set up authentication" (2) Managing multiple accounts: "asc auth list", "switch account", "use work account", "add another account" (3) Switching the active account: "asc auth use NAME", "switch to personal account" (4) Logging out: "asc auth logout", "remove credentials", "remove account" (5) Verifying current credentials: "asc auth check", "which account am I using?" (6) Updating account settings: "asc auth update --vendor-number", "save my vendor number" (7) Explaining the credentials file format (~/.asc/credentials.json) (8) Troubleshooting 401 auth errors or "missing credentials" errors
Use when writing, reviewing, or refactoring vitest tests. Load when you see *.test.ts or *.spec.ts files, nested describe blocks, loose assertions (toBeTruthy), over-mocking, slow tests, or async testing needs. Covers AAA pattern, parameterized tests, test doubles hierarchy, mock cleanup, test isolation, and performance optimization. Keywords include vitest, testing, TDD, assertions, mocks, stubs, fakes, spies, beforeEach, describe, it, expect, vi.mock, it.each.
React component and hook testing patterns with Testing Library and Vitest. Use when writing tests for React components, custom hooks, or data fetching logic. Covers component rendering tests, user interaction simulation, async state testing, MSW for API mocking, hook testing with renderHook, accessibility assertions, and snapshot testing guidelines. Does NOT cover E2E tests (use e2e-testing) or TDD workflow enforcement (use tdd-workflow).
Complete unit testing skill for TypeScript/NestJS projects using Jest, @golevelup/ts-jest, and in-memory databases. ALWAYS use this skill when user needs to: **SETUP** - Initialize or configure unit testing: - Set up Jest for a new project - Configure test infrastructure (jest.config.ts) - Install testing dependencies (@nestjs/testing, @golevelup/ts-jest) - Create mock helpers or test utilities - Set up coverage configuration **WRITE** - Create or add unit tests: - Write, create, add, or generate unit tests - Test a service, usecase, controller, guard, interceptor, pipe, or filter - Add tests for new code or features - Improve test coverage or add missing tests - Mock dependencies or set up test fixtures - Working on any file ending in .spec.ts **REVIEW** - Audit or evaluate unit tests: - Review existing tests for quality - Check test coverage and gaps - Audit testing patterns and conventions - Evaluate assertion quality **RUN** - Execute or analyze test results: - Run unit tests - Analyze test results or coverage reports - Understand test failures or successes - Check which tests are passing/failing **DEBUG** - Fix failing or broken tests: - Fix failing unit tests - Debug test errors or exceptions - Resolve mock issues or setup problems - Troubleshoot test timeouts or flaky tests - Diagnose "undefined" or unexpected results **OPTIMIZE** - Improve test performance and maintainability: - Speed up slow tests - Fix open handles preventing clean exit - Improve test organization - Reduce test execution time - Clean up test code Keywords: unit test, spec, jest, typescript, nestjs, mock, DeepMocked, createMock, AAA, test coverage, TDD, .spec.ts, testing, write test, add test, create test, fix test, debug test, run test, review test, optimize test, test setup, jest config
Tests applications using the Pest 4 PHP framework. Activates when writing tests, creating unit or feature tests, adding assertions, testing Livewire components, browser testing, debugging test failures, working with datasets or mocking; or when the user mentions test, spec, TDD, expects, assertion, coverage, or needs to verify functionality works.