axiom-swiftui-search-ref▌
charleswiltgen/axiom · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
SwiftUI search is environment-based and navigation-consumed. You attach .searchable() to a view, but a navigation container (NavigationStack, NavigationSplitView, or TabView) renders the actual search field. This indirection is the source of most search bugs.
SwiftUI Search API Reference
Overview
SwiftUI search is environment-based and navigation-consumed. You attach .searchable() to a view, but a navigation container (NavigationStack, NavigationSplitView, or TabView) renders the actual search field. This indirection is the source of most search bugs.
API Evolution
| iOS | Key Additions |
|---|---|
| 15 | .searchable(text:), isSearching, dismissSearch, suggestions, .searchCompletion(), onSubmit(of: .search) |
| 16 | Search scopes (.searchScopes), search tokens (.searchable(text:tokens:)), SearchScopeActivation |
| 16.4 | Search scope activation parameter (.onTextEntry, .onSearchPresentation) |
| 17 | isPresented parameter, suggestedTokens parameter |
| 17.1 | .searchPresentationToolbarBehavior(.avoidHidingContent) |
| 18 | .searchFocused($isFocused) for programmatic focus control |
| 26 | Bottom-aligned search, .searchToolbarBehavior(.minimize), Tab(role: .search), DefaultToolbarItem(kind: .search) — see axiom-swiftui-26-ref |
When to Use This Skill
- Adding search to a SwiftUI list or collection
- Implementing filter-as-you-type or submit-based search
- Adding search suggestions with auto-completion
- Using search scopes to narrow results by category
- Using search tokens for structured queries
- Controlling search focus programmatically
- Debugging "search field doesn't appear" issues
For iOS 26 search features (bottom-aligned, minimized toolbar, search tab role), see axiom-swiftui-26-ref.
Part 1: The searchable Modifier
Core API
.searchable(
text: Binding<String>,
placement: SearchFieldPlacement = .automatic,
prompt: LocalizedStringKey
)
Availability: iOS 15+, macOS 12+, tvOS 15+, watchOS 8+
How It Works
- You attach
.searchable(text: $query)to a view - The nearest navigation container (NavigationStack, NavigationSplitView) renders the search field
- The view receives
isSearchinganddismissSearchthrough the environment - Your view filters or queries based on the bound text
struct RecipeListView: View {
@State private var searchText = ""
let recipes: [Recipe]
var body: some View {
NavigationStack {
List(filteredRecipes) { recipe in
NavigationLink(recipe.name, value: recipe)
}
.navigationTitle("Recipes")
.searchable(text: $searchText, prompt: "Find a recipe")
}
}
var filteredRecipes: [Recipe] {
if searchText.isEmpty { return recipes }
return recipes.filter { $0.name.localizedCaseInsensitiveContains(searchText) }
}
}
Placement Options
| Placement | Behavior |
|---|---|
.automatic |
System decides (recommended) |
.navigationBarDrawer |
Below navigation bar title (iOS) |
.navigationBarDrawer(displayMode: .always) |
Always visible, not hidden on scroll |
.sidebar |
In the sidebar column (NavigationSplitView) |
.toolbar |
In the toolbar area |
.toolbarPrincipal |
In toolbar's principal section |
Gotcha: SwiftUI may ignore your placement preference if the view hierarchy doesn't support it. Always test on the target platform.
Column Association in NavigationSplitView
Where you attach .searchable determines which column displays the search field:
NavigationSplitView {
SidebarView()
.searchable(text: $query) // Search in sidebar
} detail: {
DetailView()
}
// vs.
NavigationSplitView {
SidebarView()
} detail: {
DetailView()
.searchable(text: $query) // Search in detail
}
// vs.
NavigationSplitView {
SidebarView()
} detail: {
DetailView()
}
.searchable(text: $query) // System decides column
Part 2: Displaying Search Results
isSearching Environment
@Environment(\.isSearching) private var isSearching
Availability: iOS 15+
Becomes true when the user activates search (taps the field), false when they cancel or you call dismissSearch.
Critical rule: isSearching must be read from a child of the view that has .searchable. SwiftUI sets the value in the searchable view's environment and does not propagate it upward.
// Pattern: Overlay search results when searching
struct WeatherCityList: View {
@State private var searchText = ""
var body: some View {
NavigationStack {
// SearchResultsOverlay reads isSearching
SearchResultsOverlay(searchText: searchText) {
List(favoriteCities) { city in
CityRow(city: city)
}
}
.searchable(text: $searchText)
.navigationTitle("Weather")
}
}
}
struct SearchResultsOverlay<Content: View>: View {
let searchText: String
@ViewBuilder let content: Content
@Environment(\.isSearching) private var isSearching
var body: some View {
if isSearching {
// Show search results
SearchResults(query: searchText)
} else {
content
}
}
}
dismissSearch Environment
@Environment(\.dismissSearch) private var dismissSearch
Availability: iOS 15+
Calling dismissSearch() clears the search text, removes focus, and sets isSearching to false. Must be called from inside the searchable view hierarchy.
struct SearchResults: View {
@Environment(\.dismissSearch) private var dismissSearch
var body: some View {
List(results) { result in
Button(result.name) {
selectResult(result)
dismissSearch() // Close search after selection
}
}
}
}
Part 3: Search Suggestions
Adding Suggestions
Pass a suggestions closure to .searchable:
.searchable(text: $searchText) {
ForEach(suggestedResults) { suggestion in
Text(suggestion.name)
.searchCompletion(suggestion.name)
}
}
Availability: iOS 15+
Suggestions appear in a list below the search field when the user is typing.
searchCompletion Modifier
.searchCompletion(_:) binds a suggestion to a completion value. When the user taps the suggestion, the search text is replaced with the completion value.
.searchable(text: $searchText) {
ForEach(matchingColors) { color in
HStack {
<How to use axiom-swiftui-search-ref on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add axiom-swiftui-search-ref
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches axiom-swiftui-search-ref from GitHub repository charleswiltgen/axiom and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate axiom-swiftui-search-ref. Access the skill through slash commands (e.g., /axiom-swiftui-search-ref) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★52 reviews- ★★★★★Nikhil Robinson· Dec 20, 2024
Keeps context tight: axiom-swiftui-search-ref is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ishan Li· Dec 8, 2024
We added axiom-swiftui-search-ref from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Liam Khan· Dec 4, 2024
Keeps context tight: axiom-swiftui-search-ref is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Liam Yang· Nov 27, 2024
axiom-swiftui-search-ref fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Layla Huang· Nov 11, 2024
axiom-swiftui-search-ref has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zaid Johnson· Oct 18, 2024
axiom-swiftui-search-ref has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aanya Tandon· Oct 2, 2024
axiom-swiftui-search-ref fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Olivia Thomas· Sep 25, 2024
Solid pick for teams standardizing on skills: axiom-swiftui-search-ref is focused, and the summary matches what you get after install.
- ★★★★★Oshnikdeep· Sep 21, 2024
axiom-swiftui-search-ref fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Aarav Abebe· Sep 21, 2024
axiom-swiftui-search-ref has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 52