From jkit
Generates Flutter iOS build configuration files. Use for requests like "Set up iOS", "Configure iOS build", "Set up xcodeproj".
How this skill is triggered — by the user, by Claude, or both
Slash command
/jkit:flutter-ios-setup <AppName> [-entry <dir>] [package_name]<AppName> [-entry <dir>] [package_name]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automatically configures iOS build settings for a Flutter project.
Automatically configures iOS build settings for a Flutter project.
$ARGUMENTS: App name (required, PascalCase, e.g. MyApp)-entry <dir>: Entry directory (optional, e.g. -entry app). Defaults to ios/... if omitted.-entry option, and package name from $ARGUMENTS
-entry app is present, set entry directory to app-entry is absent, use ios/... as base pathPRODUCT_BUNDLE_IDENTIFIER value from {entry}/ios/Runner.xcodeproj/project.pbxprojcd ${CLAUDE_PLUGIN_ROOT} && node scripts/flutter/template/flutter-ios-pbxproj-template.mjs <AppName> <package_name> {entry}/ios/Runner.xcodeproj/project.pbxproj
Save the output to {entry}/ios/Runner.xcodeproj/project.pbxprojcd ${CLAUDE_PLUGIN_ROOT} && node scripts/flutter/setup/flutter-ios-info-plist-setup.mjs {entry}/ios/Runner/Info.plist
Save the output to {entry}/ios/Runner/Info.plistcd ${CLAUDE_PLUGIN_ROOT} && node scripts/flutter/template/flutter-ios-xcscheme-template.mjs production
cd ${CLAUDE_PLUGIN_ROOT} && node scripts/flutter/template/flutter-ios-xcscheme-template.mjs development
cd ${CLAUDE_PLUGIN_ROOT} && node scripts/flutter/template/flutter-ios-xcscheme-template.mjs staging
cd ${CLAUDE_PLUGIN_ROOT} && node scripts/flutter/template/flutter-ios-xcscheme-template.mjs qa
Save each output to {entry}/ios/Runner.xcodeproj/xcshareddata/xcschemes/{flavor}.xcscheme{entry}/ios/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme (if exists)pod install instructionsWhen running /flutter-ios-setup MyApp -entry app com.example.myapp:
app/ios/
├── Runner.xcodeproj/
│ ├── project.pbxproj ← Full replacement (12 build configurations)
│ └── xcshareddata/xcschemes/
│ ├── Runner.xcscheme ← Deleted
│ ├── production.xcscheme ← Newly created
│ ├── development.xcscheme ← Newly created
│ ├── staging.xcscheme ← Newly created
│ └── qa.xcscheme ← Newly created
└── Runner/
└── Info.plist ← Patched (preserves existing settings)
Expands the default Flutter 3 build configurations (Debug/Release/Profile) to 12:
Runner target build settings per flavor:
| Flavor | APP_DISPLAY_NAME | APP_URL_SCHEMES | PRODUCT_BUNDLE_IDENTIFIER |
|---|---|---|---|
| production | {AppName} | {scheme} | {package_name} |
| development | {AppName} (dev) | {scheme}-dev | {package_name}.dev |
| staging | {AppName} (stg) | {scheme}-stg | {package_name}.stg |
| qa | {AppName} (qa) | {scheme}-test | {package_name}.test |
Reads the existing file and adds the following items if missing:
CFBundleDisplayName to build variable $(APP_DISPLAY_NAME)CFBundleURLTypes block (deep link URL scheme: $(APP_URL_SCHEMES))Creates a separate Xcode scheme for each flavor:
production.xcscheme: Debug-production / Release-production / Profile-productiondevelopment.xcscheme: Debug-development / Release-development / Profile-developmentstaging.xcscheme: Debug-staging / Release-staging / Profile-stagingqa.xcscheme: Debug-qa / Release-qa / Profile-qa/flutter-ios-setup MyApp -entry app com.example.myapp
→ Replace app/ios/Runner.xcodeproj/project.pbxproj (12 build configurations)
→ Patch app/ios/Runner/Info.plist
→ Create 4 schemes in app/ios/Runner.xcodeproj/xcshareddata/xcschemes/
→ Delete Runner.xcscheme
→ Provide pod install instructions
/flutter-ios-setup MyApp -entry app
→ Extract PRODUCT_BUNDLE_IDENTIFIER from existing project.pbxproj
→ Process same as above
/flutter-ios-setup MyApp
→ Uses ios/Runner.xcodeproj/... as base path (no entry)
→ Prompt user for package_name
flutter create, before pod installpod install after execution (CocoaPods automatically adds Pods-related settings)-entry is absent, uses ios/... as base path-entry app, uses app/ios/... as base pathProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub josephnk/jkit-code-plugin --plugin jkit