By aryaxt
Aryan's shared Claude Code skills — iOS dev (simulator/device/testflight), web dev (chrome), Firebase debugging, ship workflows, and decision tooling. Project-specific values come from each project's scripts/ios-config.sh.
Boot the local Next.js dev server (or reuse a running one) and open the app in Google Chrome on macOS so the user can test changes. Use whenever the user types /chrome, asks to "run the app in chrome", "open in chrome", "test in chrome", "fire up the app and let me see", "boot the dev server", or otherwise wants a working browser session for the current branch. If the user passes a path argument (e.g. /chrome /dashboard), open Chrome to that path; otherwise open the root.
Use when the user wants to capture a new task, bug, or feature as a GitHub issue. Takes a brief plain-text description, researches the codebase for context, and creates a rich, implementation-ready issue on the your GitHub project board in Backlog with appropriate type / surface / priority labels and an optional release-blocker ship-gate.
Scaffold a new Next.js + Firebase + iOS SaaS project from the saas-template monorepo. Walks through 16 guided onboarding steps (Firebase setup, env vars, GitHub repo, deploy). Use when the user says "create a new project", "scaffold a new app", "start a new project from saas-template", or similar. Replaces the deprecated saas-template MCP create_project tool.
Use when facing a non-trivial design or scope decision where you suspect your own framing is biased — e.g. "should we include X in this PR?", "is approach A or B better here?", "is my scope too wide/narrow?". Spawns 3 adversarial-role subagents under strict bias controls, then a synthesis pass, and returns a structured recommendation. Do NOT use for factual lookups, trivial choices, or questions you already have full context and clear reasoning on — there it adds noise.
Build and install the iOS app on a real iPhone or iPad connected by USB or Wi-Fi. Use whenever the user types /device, says "install on my phone", "run on my iphone", "install on device", "test on real device", "push to my phone", "deploy to ipad", "run on connected phone", or any variant of "install it on my actual phone/ipad/device". Optional positional arg: a device name fragment (e.g. "iphone", "arya's phone"); with no arg, picks the first available paired device. USB and Wi-Fi devices are treated the same once paired in Xcode. If no device is connected, surface a clear "no paired device found" message and stop.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Aryan's shared Claude Code skills. Lives as a single plugin so updates propagate to every project (PhotoAI, ai-mini-app, saas-template-derived apps) via one git push instead of N copy-pastes.
/plugin marketplace add aryaxt/aryaxt-skills
/plugin install aryaxt-skills@aryaxt
After install, skills are namespaced: invoke as /aryaxt:simulator,
/aryaxt:testflight, etc.
If you want the short forms (/simulator, /testflight) for muscle
memory, add a 1-line wrapper skill in your project's .claude/skills/:
---
name: simulator
description: Wrapper — calls aryaxt:simulator
---
Invoke `aryaxt:simulator` with any args passed by the user.
| Skill | What it does |
|---|---|
simulator | Build + launch the iOS app on an iPhone/iPad simulator, or the Android app on an emulator (simulator android). |
emulator | Build + launch the Android app on an emulator (alias for simulator android). |
device | Build + install on a real device. |
testflight | Bump build, archive, upload to App Store Connect. |
playstore | Bump versionCode, build a signed AAB, upload to the Google Play internal track. |
chrome | Boot Next.js dev server + open in Chrome. |
doit | Review local/committed changes → split PRs → multi-agent review → merge. |
qa | Per-feature visual smoke test on iOS simulator via computer-use. |
error | Query Firestore errorLogs to find the real root cause behind a 500. |
free-space | Clean Xcode DerivedData, npm cache, etc. |
create-issue | Create a richly-labeled GitHub issue on the project board. |
work-on-issue | Autonomous loop: read issue → branch → plan → implement → test → PR. |
decision-council | Spawn 3 adversarial subagents for biased framing problems. |
generate-image | Generate AI photos via the project's Gemini setup. |
create-project | Scaffold a new SaaS project from saas-template: copy → rename → 16-step Firebase + GitHub + deploy onboarding. Replaces the deprecated saas-template MCP create_project tool. |
research-idea | Run a 7-phase market research framework on a business idea before writing code. Forces a GO / NO-GO decision via a scorecard. Run BEFORE building. Replaces the deprecated saas-template MCP research_idea tool. |
plan-features | Translate a validated product idea (post research-idea) into a per-task implementation plan, prioritized mvp / v1 / v2. Replaces the deprecated saas-template MCP plan_features tool. |
All iOS skills source $PROJECT_ROOT/scripts/ios-config.sh at the start
to pick up project-specific values:
export IOS_BUNDLE_ID="com.shivaapps.photoai"
export IOS_SCHEME="DatingAIAssistant"
export IOS_PROJECT_DIR="ios"
export IOS_TEAM_ID="C5GK8X5LBQ"
Each project ships its own scripts/ios-config.sh. The plugin's skill
files reference $IOS_BUNDLE_ID etc. as variables — they don't bake
values in.
If you don't have scripts/ios-config.sh yet, either create one (copy
from any saas-template-based project) or export the variables in your
shell rc.
Project-specific skills stay in the project's .claude/skills/:
/scenes, /add-style, /record-demo (depend on PhotoAI's
schema, scene catalog, fine-tuned models)If you find yourself wanting a new skill that's generic, add it here and update the table above. If it's project-specific, keep it local.
npx claudepluginhub aryaxt/aryaxt-skills --plugin aryaxt-skillsComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Browser automation and end-to-end testing MCP server by Microsoft. Enables Claude to interact with web pages, take screenshots, fill forms, click elements, and perform automated browser testing workflows.
Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques